What that code does is appear on the network as a siglent signal generator, the scope then sends it commands as it would to an actual device, the PC then converts these commands and spits it back out to the other brand device in the correct format for that device, over USB or ethernet.
The scope pretty much sends commands like "Generate a 10Hz Wave", measure for 1 acquisition period, "Generate a 12Hz Wave, measure... etc,
In the video this is the "C1:BSWV FREQ,10" line where you see the number counting up. I "think" the device then grabs the same value as "C1:PAVA? PKPK" to plot amplitude, and C1-C2:MEAD? to plot phase.
I've been playing with the SAG1021 to better learn its limits, And at this point I am starting to think up how I might script it, but would still be nice to have commands for it
What i was after was a command that would put it in a bode plot mode with the parameters exposed so I could set the center, span, etc via scpi,
When I the click on instrument Control the black background appears immidiately and the address http://192.168.251.1xx/Instrument/novnc/vnc_auto.php.
Right after that a red line appears below the address field and a note saying WebSock error: [object Event] .... nothing
When I the click on instrument Control the black background appears immidiately and the address http://192.168.251.1xx/Instrument/novnc/vnc_auto.php.
Right after that a red line appears below the address field and a note saying WebSock error: [object Event] .... nothingI had the same issue when I did a firmware upgrade but missed the software upgrade.
After doing the software update everything is fine.
Hi,
my software revision is indeed the 7.0.6.1.26 .... so I downloaded the OS zip-file.
Now I just need to get me a 8G or 32G USB stick.
Thanks alot and I´ll report if that solved my prob.
Calvin
Hello, I have purchased a SDS1204X-E 4CH oscilloscope and I have the following problem:
I place a 36 MHz 3 cycles burst in channel 1 and everything works ok until I enable channel 2. In that moment the trigger becomes erratic, randomly jumping between the first and the second edge of the signal.
The problem coincides with the fact that the oscilloscope changes the sampling rate from 1 Gs/s to 500 Ms/s when I enable channel 2.
The same happens when I have only channel 1 enabled (1Gs/s) but the signal has more than 72 MHz.
I updated firmware from SDS1004X-E_6.1.25R2_EN to SDS1004X-E_6.1.26_EN and the problem persits.
best regards,
Hello, I have purchased a SDS1204X-E 4CH oscilloscope and I have the following problem:
I place a 36 MHz 3 cycles burst in channel 1 and everything works ok until I enable channel 2. In that moment the trigger becomes erratic, randomly jumping between the first and the second edge of the signal.
The problem coincides with the fact that the oscilloscope changes the sampling rate from 1 Gs/s to 500 Ms/s when I enable channel 2.
The same happens when I have only channel 1 enabled (1Gs/s) but the signal has more than 72 MHz.
You can see the problem here: https://youtu.be/stSIxn6YvJU
I updated firmware from SDS1004X-E_6.1.25R2_EN to SDS1004X-E_6.1.26_EN and the problem persits.
best regards,
Hello, I have purchased a SDS1204X-E 4CH oscilloscope and I have the following problem:
I place a 36 MHz 3 cycles burst in channel 1 and everything works ok until I enable channel 2. In that moment the trigger becomes erratic, randomly jumping between the first and the second edge of the signal.
The problem coincides with the fact that the oscilloscope changes the sampling rate from 1 Gs/s to 500 Ms/s when I enable channel 2.
The same happens when I have only channel 1 enabled (1Gs/s) but the signal has more than 72 MHz.
I updated firmware from SDS1004X-E_6.1.25R2_EN to SDS1004X-E_6.1.26_EN and the problem persits.
best regards,With difficult to trigger non-repetitive signals Trigger Holdoff can make all the difference and allow for 'rock solid' triggering.
Holdoff is default to Close (80ns) so lengthen it to just greater than the length of the burst and if needed you can extend it to a max of 1.5s.
Tell us if that works.
Hi,
while trying out the webserver control I got an issue.
When doing history at first the monitor picture updated as its supposed to do, but when I switched to full screen it stopped.
From then on even with new starts of the webserver and the scope the picture didn´t update history frames at all.
All else -the normal scopeing via webserver- worked ok.
The scope´s own controls worked fine also .... so its just the history mode which seems to have issues.
regards
Calvin
So I have been having trouble connecting my scope to my wifi network. I have correctly entered in all software keys so that the wifi option is enabled. I have also updated to the most recent firmware version 7.1.6.1.26. I am using the siglent official TP-Link TL-WN725N wifi adapter and the device recognizes this adapter when it is plugged in (the little green LED also blinks).
My DHCP setting is turned on.
When I enter in the wifi network name and password (which I have verified are both correct many times), it says "connecting" and then it will fail to connect with the message "WLAN connection failed". Figuring that maybe it was a bad wifi adapter, I plugged it into my desktop and successfully connected to that same WIFI network without problems.
I have no idea what to do next. I have tried resetting my router, changing the name of the wifi network, changing the wifi network password, reflashing the firmware on the scope, and a number of other things. What should my next step be?
EDIT #2: I have finally connected via WiFi. The SSID cannot have any spaces or special characters, in my case. The PSK also cannot have any spaces or special characters, and must be less than 20 characters long. Also the IP address must be set manually.
That is a pretty ridiculous set of demands for this device, and hamstrings it's utility in a commercial/research environment where the user does not necessarily have such tight control over the SSID or PSK that they use to connect to WIFI. This definitely needs to be addressed in an update.
I have performed all of the aforementioned tasks suggested by tautech while sitting right next to my router and still no luck.
Is it possible that the problem is that my SSID has spaces in it?
EDIT: changing SSID to have no spaces, special characters, and less than 20 characters did not fix the problem.
EDIT #2: I have finally connected via WiFi. The SSID cannot have any spaces or special characters, in my case. The PSK also cannot have any spaces or special characters, and must be less than 20 characters long. Also the IP address must be set manually.
That is a pretty ridiculous set of demands for this device, and hamstrings it's utility in a commercial/research environment where the user does not necessarily have such tight control over the SSID or PSK that they use to connect to WIFI. This definitely needs to be addressed in an update.
I purchased a SDS1104X-E in November in Australia and it has the following:
software version: 8.0.6.1.26
fpga version: 2018-07-26
hardware version: 01-03
I purchased a SDS1104X-E in November in Australia and it has the following:
software version: 8.0.6.1.26
fpga version: 2018-07-26
hardware version: 01-03
Interesting...
Can you send me a copy of the .app file?