Author Topic: ngscopeclient - Ultimate acquisition software / protocol decoder / debug tool ?  (Read 3478 times)

MD1071 and 7 Guests are viewing this topic.

Online Antonio90

  • Frequent Contributor
  • **
  • Posts: 364
  • Country: es
Hi Antonio90 ,

The console says something about the scope answering "welcome to SDS824X HD" after asking for an ID.
I think SDS800X HD support as not yet been merged to ngscopeclient (it is in scopehal git repo, but the ngscopeclient sub-module does not point to the latest commit).
You need to either wait for Andrew to update the dependency or to manually checkout master branch of scopehal repo.
This might be the case. Unfortunately I don't really know what I'm doing, just following documentation step by step, so I'll wait.
 

Offline azonenberg

  • Contributor
  • Posts: 15
  • Country: us
    • Antikernel Labs
Then the terminal just returns "ERROR: Unknown scope type"

Try again with the latest version on git, should have the 800 series support merged?
 
The following users thanked this post: 2N3055

Online Antonio90

  • Frequent Contributor
  • **
  • Posts: 364
  • Country: es
Then the terminal just returns "ERROR: Unknown scope type"

Try again with the latest version on git, should have the 800 series support merged?

Thanks! Compiling now.

EDIT: Compiled and working (on Windows still). Thank you very much Andrew and @fredo_! Will test more tomorrow, it's already 1:45 AM here, and I need sleep. The "filter" section with the block programming interface is just genius BTW, really impressive piece of software.
« Last Edit: September 14, 2024, 11:46:47 pm by Antonio90 »
 
The following users thanked this post: egonotto, fredo_

Offline fredo_Topic starter

  • Regular Contributor
  • *
  • Posts: 78
  • Country: fr
it's already 1:45 AM here, and I need sleep..
Same here, time to go to bed!
 
The following users thanked this post: egonotto

Online Furna

  • Regular Contributor
  • *
  • Posts: 97
  • Country: de
  • I still don't know
Try

cd build
cmake --build . -j4

Hello,

Thanks it compiles now, but it's taking quite a while.

The "-j4" tells the compiler (ninja) to use 4 cores on your PC.
It is more than probable that your PC has more than 4 cores.
ninja by default uses all your available cores.
In short run "cmake --build ." without the "j" switch.
Please note that cmake in turn runs ninja => just run "ninja" as fredo_ suggested and advised in the yet unpublished doc mentioned by azonenberg

Best regards
egonotto
PS: Now it's ready. But my SDS3000X HD is not recognized correctly via LAN.
ERROR: Unknown scope type

Then the terminal just returns "ERROR: Unknown scope type"

Try again with the latest version on git, should have the 800 series support merged?

Yup it is merged and seems to work.
I just cloned and compiled from scratch and  Siglent SDS824X HD is recognized ... I didn't try yet to really take a capture.
Wil let you know when I had it tested better.
The sky above the port was the color of television, tuned to a dead channel.
 
The following users thanked this post: egonotto

Offline skander36

  • Frequent Contributor
  • **
  • Posts: 842
  • Country: ro
Windows version has some sudden closes. Still a lot of work. Maybe the Linux version is more stable.
Anyway a notable and unique approach!
 

Offline azonenberg

  • Contributor
  • Posts: 15
  • Country: us
    • Antikernel Labs
Windows version has some sudden closes. Still a lot of work. Maybe the Linux version is more stable.
Anyway a notable and unique approach!

We're very interested in crash reports as people try on different setups. If you can attach a debugger and get a stack trace of where it died, we can see if that sheds any light on the situation.
 
The following users thanked this post: egonotto

Online Furna

  • Regular Contributor
  • *
  • Posts: 97
  • Country: de
  • I still don't know
Windows version has some sudden closes. Still a lot of work. Maybe the Linux version is more stable.
Anyway a notable and unique approach!

We're very interested in crash reports as people try on different setups. If you can attach a debugger and get a stack trace of where it died, we can see if that sheds any light on the situation.

azonenberg, do you have a preferred debugger and/or na example for a debugger command?
I guess something available with MSYS2 (gdb?) can work?
The sky above the port was the color of television, tuned to a dead channel.
 
The following users thanked this post: egonotto

Offline skander36

  • Frequent Contributor
  • **
  • Posts: 842
  • Country: ro
Windows version has some sudden closes. Still a lot of work. Maybe the Linux version is more stable.
Anyway a notable and unique approach!

We're very interested in crash reports as people try on different setups. If you can attach a debugger and get a stack trace of where it died, we can see if that sheds any light on the situation.
Maybe I will find some time to setup a debugger, as I don't had to deal until now with MSYS (I'm not a programmer). Usually the message that remains in console are errors of communication with the scopes as in pics attached.
Sometime R&S scope (RTB2002) get stuck while the others works.
 
The following users thanked this post: egonotto

Offline fredo_Topic starter

  • Regular Contributor
  • *
  • Posts: 78
  • Country: fr

Update with link to ngscopeclient Windows Installer

And on popular demand, here is a link to the ngscopeclient Windows installer (zip password is 'ngscopeclient').

/!\ Please be aware that you need a Vulkan compatible GPU/video card to run ngoscopeclient. /!\


09/17/2024 Update (d2a1a2f)
  • Siglent SDS: Support for SDS800X HD, SDS1000X HD, SDS2000X Plus, SDS2000X HD, SDS3000X HD, SDS5000X, SDS6000A/L/Pro, SDS7000A models
  • Rigol DHO: Support for DHO800/900, DHO1000 and DHO4000.
  • Other hardware: see ngscopeclient site for a complete list of supported hardware.


Best,

Fredo.
 
The following users thanked this post: egonotto

Offline skander36

  • Frequent Contributor
  • **
  • Posts: 842
  • Country: ro
Hi @fredo_
For Windows installer ngscopeclient msi package, I get this error on launch. An invalid path to fonts. It is repairable by users but you may want to correct this in source installer.
 
The following users thanked this post: egonotto

Offline fredo_Topic starter

  • Regular Contributor
  • *
  • Posts: 78
  • Country: fr
Oops, that's bad !
Thanks for the heads up, let me check that.
[Edit]
Well I was not able to reproduce the problem unless I have a <userdir>\AppData\Roaming\ngscopeclient\preferences.yml from a previous install that points to wrong font paths.
@skander36 can check if the error message was not due to a preferences.yml file existing before your installation (which would be the case if you previously tried your own build) ?
« Last Edit: September 19, 2024, 05:07:32 pm by fredo_ »
 
The following users thanked this post: skander36

Offline skander36

  • Frequent Contributor
  • **
  • Posts: 842
  • Country: ro
Hi, I don't have drive D in my computer. Also /Home/fborry is not from me.
Attached is preferences.yml.
What else can I check?

My build is launching without problems.
 

Offline fredo_Topic starter

  • Regular Contributor
  • *
  • Posts: 78
  • Country: fr
Hi, I don't have drive D in my computer. Also /Home/fborry is not from me.
Yeah that's the path of the source file (see "imgui__draw.cpp, line 2583" in your screenshot) on my build environnement (this is a debug build), not to be confused with the path to look the fonts for.
Maybe try and remove or rename your preferences.yml file and launch the installed ngscopeclient, it should fix the problem.
 

Offline skander36

  • Frequent Contributor
  • **
  • Posts: 842
  • Country: ro
Hi, I don't have drive D in my computer. Also /Home/fborry is not from me.
Yeah that's the path of the source file (see "imgui__draw.cpp, line 2583" in your screenshot) on my build environnement (this is a debug build), not to be confused with the path to look the fonts for.
Maybe try and remove or rename your preferences.yml file and launch the installed ngscopeclient, it should fix the problem.
Ok, that was. Removing preferences.yml has allowed the installed version to launch. Now both instances can be launched.
Thank you!
 
The following users thanked this post: egonotto, fredo_

Offline fredo_Topic starter

  • Regular Contributor
  • *
  • Posts: 78
  • Country: fr
Updated ngscopeclient Windows Installer

Here is an updated version of ngscopeclient Windows installer (zip password is 'ngscopeclient') including LA support for Siglent SDS HD scopes.


09/21/2024 Update (dc26783)
Siglent SDS: Added support for Logic Analyzer.

« Last Edit: September 21, 2024, 07:53:04 am by fredo_ »
 
The following users thanked this post: egonotto, lapot2

Online Furna

  • Regular Contributor
  • *
  • Posts: 97
  • Country: de
  • I still don't know
Updated ngscopeclient Windows Installer

Here is an updated version of ngscopeclient Windows installer (zip password is 'ngscopeclient') including LA support for Siglent SDS HD scopes.


09/21/2024 Update (dc26783)
Siglent SDS: Added support for Logic Analyzer.


Works for SDS824X HD analog channels; unfortunately I have no LA to play with.
« Last Edit: September 21, 2024, 12:21:08 pm by Furna »
The sky above the port was the color of television, tuned to a dead channel.
 
The following users thanked this post: fredo_

Offline voltsandjolts

  • Supporter
  • ****
  • Posts: 2420
  • Country: gb
The Rigol DHO1000 series have quite a rudimentary FFT implementation, which is a great shame as the frontend is quite good. It would be fantastic if ngscopeclient could implement FFT using raw data from scope and provide normal/peak/average spectrum - the features I miss the most on DHO1K.
 
The following users thanked this post: egonotto

Offline azonenberg

  • Contributor
  • Posts: 15
  • Country: us
    • Antikernel Labs
We can do FFTs on input from any supported scope.

The FFT filter outputs only the FFT of the current input, but there are separate filters for peak holding and exponential moving average that can be applied to the output spectrum which in combination should give the behavior you want, I think.
 
The following users thanked this post: egonotto, voltsandjolts, fredo_

Offline azonenberg

  • Contributor
  • Posts: 15
  • Country: us
    • Antikernel Labs
Hi, I don't have drive D in my computer. Also /Home/fborry is not from me.
Yeah that's the path of the source file (see "imgui__draw.cpp, line 2583" in your screenshot) on my build environnement (this is a debug build), not to be confused with the path to look the fonts for.
Maybe try and remove or rename your preferences.yml file and launch the installed ngscopeclient, it should fix the problem.
Ok, that was. Removing preferences.yml has allowed the installed version to launch. Now both instances can be launched.
Thank you!

Yep you got hit by https://github.com/ngscopeclient/scopehal-apps/issues/707. We don't have a root cause but there's a fairly straightforward workaround we can do to at least avoid a crash when it happens. But there's a million other things I'm juggling and this one hasn't got to the top of the stack.
 
The following users thanked this post: egonotto, skander36, fredo_

Offline Bidi533

  • Newbie
  • Posts: 2
  • Country: li
Wow! Thank you very much for sharing this here and providing the pre-complied versions. I tried it quickly with my own DHO804 and it worked! Definitely keeping an eye out for future development of this project.
 
The following users thanked this post: egonotto, fredo_

Online MD1071

  • Newbie
  • Posts: 1
  • Country: ca
hey, software looks amazing. thanks for thr windows installer. I used the windows installed and got it running, however get issues when trying to add my rigol DS1054 scope over LAN. I'm able to ping thr scopes IP and it's good, I can get IDN? using python pyvisa too so seems like connection with my PC is good. However when I try to add it using ngscopeclient, I get three bad IDN warnings and then it terminates

I used the windows installer and it's the ngscopeclient 0.1-dev+dc26783 [DEBUG BUILD]

amI using the wrong version or something?

the path I used is scope IP : 5555
manual says rigol port is 5555
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf