JYE Tech Forum

This is beta version of my version of jye scope. It is written using .NET framework C#. And It is written completely from scratch. I tried at my best to make is extendable to other scope types as I can. It works with windows xp and up (requires .NET framework 4.0 and above)
Check this out:

DSO on GitHub:
https://github.com/nrmtmt/DSO

Wiki page:
https://github.com/nrmtmt/DSO/wiki

GitHub page of GUI:
https://github.com/nrmtmt/PC_Scope

Quick overview of GUI:
https://github.com/nrmtmt/DSO/releases/ ... erview.pdf

Releases:
https://github.com/nrmtmt/DSO/releases
https://github.com/nrmtmt/PC_Scope/releases (this is propably what you looking for)

(Pick version on the top. PC Scope release contains already newest version of DSO.dll file available at time of compilation)
Unpack ZIP file. ZIP file contains PC Scope.exe file and DSO.dll file.

At this moment It recognize only DSO068 and DSO112A. You can test other scope types using "DebugWindow" feature.
It would be massive help to me if anyone who download this software, put here results of using this software with system specification of PC and scope type.

Main work is put on library (DSO.dll). GUI is simple but allows for easily control scope and do measurements using cursors. It alows also to save output as .csv file.
Library and GUI have CPU usage optimized now, I check it with netbook with Intel Atom CPU and it works without problem (but is better to use minium Core2Duo to get best results)
Minimum System requirements (subject to change):
- screen resolution 1024:600

For DSO068 it now works almost flawlessy.
It also partially works with DSO112A, it connects with scope and allows display waveform and play with settings but at this moment there are some bugs though.
Unfortunately for DSO112A there are many issues that I can't overcome with serial communication, especially with acknowledging commands (changing timbase etc.) So at this point I cannot implement it to full extend.
By now you can with DSO112A display waveform graph with current parameters, but you can't reliable change parameters. To workaround this problem you should use this approach : Device -> Stop Capture
-> Manually change parameters to desired one
-> Device ->Start Capture -> Click "Refresh" button.

In order to work with DSO112A you may need to update its firmware to this one:
download/file.php?id=806
I use "CommandDone" data frame implemented with this new firmware for getting acknowledgement that parameters are succesfuly set. But since changing scope parameters are not reliable it's not obligatory but recommended.


GUI relies now only on IScope interface. More about DSO.dll is in wiki page available here:
https://github.com/nrmtmt/DSO/wiki

Without your help I cannot test this app at all.

Sorry for late reply. I just noticed the update in this sub-forum. Unfortunately I can't test the App myself since I am away from office. I will ask some else to test it. If you need any information about the protocols please let me know. We are happy to assist.

Among the oscilloscopes DSO112A is better documented. It might be easier to make it work first for DSO112A.

Yes, I'm using dso112a documentation. Here is GitHub page in which I will commit all updates to this. This is very work in progress.
https://github.com/nrmtmt/DSO

My colleague tested the app with DSO112A. He managed to connect DSO112A to the app and was able to display waveform on PC. But he found the connection was not stable. The attached is the report. Sorry it is in Chinese. Hopefully you can get some information with help of google translate.

Thanks for reply. Tommorow I will try to adress issues described in this paper. I think that your colleague used very first version of app (I assume this from fact that label trigg is not showing any value, only text "trigg"). Version currently attached to this thread is showing current buffer data count for debug purposes and in my opinion works much more stable.

Okay, I'll ask him to test again. He might have downloaded the version right before your updating on Aug. 24.

I noticed that dso112a uses different offsets in config and parameters data frames. So it will be not work at this moment with dso112a (no ability to change settings or retrieve config) I will post here a version that will support DSO112. It will be much easier to do testing on real device. It's a shame that the only real difference with DSO112a frames and DSO068 frames is in its value offsets or positions. So maybe your teammate or someone at all could test this against different computers with dso068.

My colleaque tested the new version. Please see results attached. It was found much more stable than the previous version.

Do you have DSO112A? If you don't we are happy to send you a free sample.

We will test it with DSO068 too.