Author Topic: Fixing EasyScopeX  (Read 8737 times)

0 Members and 1 Guest are viewing this topic.

Offline Erwin RiedTopic starter

  • Regular Contributor
  • *
  • Posts: 206
  • Country: no
Fixing EasyScopeX
« on: July 28, 2013, 03:23:38 am »
Hi, weeks ago I ordered a Siglent scope, and it arrived yesterday (I was really tired of using the portable DSO quad crap! and I just need the basics in a scope, but WHAT A DIFFERENCE! knobs! :-DD). Testing the software I notice how crappy is EasyScopeX! I can't even get connection with the device, so I decided to disassemble the executable and rebuild it. This is an early version to the application. This should work on any scope that uses NI-VISA drivers, or serial/ethernet:


I am not sure how legal it this, but you won't believe how crappy is EasyScope coded inside, it is like a University first year student work, everything is duplicated, every control/function has a chinglish or no senseful name at all, not maintainable at all and everything is hard-coded and ugly.

All the dialogs are beautiful now, they still don't work perfectly because I still need to learn all the commands and procedures (and remove the bug avalanche from the base version), but eventually it is possible to get a rock solid version:


Source repository: https://github.com/eried/EasyScopeX/
Binaries download: http://www.mediafire.com/?9abncjydjgbeoxk 
(replace the files in EasyScopeX program files, and run as administrator for now, because the snapshot feature is so crappy implemented that requires access to the disk)

____________________________________________________

There is just a little thing tricky to compile the source. Some components licenses. I personally own a legal dotnetbar license (check the new Style menu options!), but there is a paid control called CWUIControlsLib, installed by EasyScope installer as cwui.ocx, System32 folder). I am guessing the license for this thing is expensive, and in trial mode is hard to use because it limits to 5 minutes the design time so for the moment if you want to help, I can describe what to do (but no share that file :) ):

1) The limitations in design time are for sure linked to this dialog:


2) So we find the resources: great a switch case redirecting to all the trial warnings:


3) Earlier in the code, there is a jump that skips all these warning-goodness, so we just replace that:


4) Then the evaluation text:


5) Easier than the dialogs, there is a reference to the text and a jump. Save both changes and start to help me coding a better EasyScopeX  :-BROKE
« Last Edit: July 28, 2013, 03:28:12 am by Erwin Ried »
My website: http://ried.cl
 

Offline Evi

  • Regular Contributor
  • *
  • Posts: 115
  • Country: ru
Re: Fixing EasyScopeX
« Reply #1 on: August 04, 2013, 09:09:50 am »
Interesting.
The sw could find my Rigol DS2202 via net and that is all at the moment.
May be new version...
« Last Edit: August 04, 2013, 09:22:38 am by Evi »
 

Offline Erwin RiedTopic starter

  • Regular Contributor
  • *
  • Posts: 206
  • Country: no
Re: Fixing EasyScopeX
« Reply #2 on: August 12, 2013, 09:22:56 am »
Interesting.
The sw could find my Rigol DS2202 via net and that is all at the moment.
May be new version...

I can try to make it work with your scope (via remote support for example, if you install the free visual studio express). Is the official one working?

My website: http://ried.cl
 

Offline echen1024

  • Super Contributor
  • ***
  • Posts: 1660
  • Country: us
  • 15 yo Future EE
Re: Fixing EasyScopeX
« Reply #3 on: August 12, 2013, 04:06:11 pm »
Thank you! EasyScope is a heap of shit! I love ths new version.
I'm not saying we should kill all stupid people. I'm just saying that we should remove all product safety labels and let natural selection do its work.

https://www.youtube.com/user/echen1024
 

Offline illyesgeza

  • Contributor
  • Posts: 41
Re: Fixing EasyScopeX
« Reply #4 on: August 15, 2013, 10:16:47 am »
I have tried this version of easyscope
At least this one find my Siglent dso
Most of commands are working
But if I use Channe1 or Channel2 in the Trace menu I got this message:
"Input string was not in a correct format", and no trace apears.
 

Offline Erwin RiedTopic starter

  • Regular Contributor
  • *
  • Posts: 206
  • Country: no
Re: Fixing EasyScopeX
« Reply #5 on: August 15, 2013, 09:49:43 pm »
I have tried this version of easyscope
At least this one find my Siglent dso
Most of commands are working
But if I use Channe1 or Channel2 in the Trace menu I got this message:
"Input string was not in a correct format", and no trace apears.

Yeah, as I said the original code is extremely ugly, I still don't have a lot of time to rebuild it, but certainly it can be done.
My website: http://ried.cl
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf