SDS800X HD Bug Reports + Firmware

[2N3055]

Welcome to the forum.

Nice write up. 

Question
Do you have a Threshold level set within the amplitude of the waveform ?

Hello, and thank you for the nice welcome

The threshold was set at the correct level for the decoder, then copied to the trigger. I also verified that the threshold is correct in the trigger setup menu. And I tried varying the threshold level, with the expected result of no trigger when the threshould is outside the signal boundaries.

So there are no pauses between characters in data stream? Ever?
You are relying solely on 0,5 of bit width in stop bit to distinguish it from standard data bit?
It is easy to have framing errors that way...
I 'we seen such serial data streams but synchronous...

Did you try different speeds?
What you use to create signal? Some microcontroller?

I would need to put something together or create signal on AWG to try to create test vector for this...
I won't be able to work on this till the end of the week..

Yes that is correct, there is no pause between the bytes. In my application, the data is conveyed across signal transformers for which I have minimized the magnetics to just reliably carry my signal. That is why I chose to use manchester encoding and employ a 0x71 byte, which is in no case valid manchester encoded data, to signal the beginning of the dataset within the stream. My STM32 microcontroller has no problems synchronizing with the data stream.

I just tried using 2 stop bits, which did not improve the trigger quality. One thing that is interesting here is the need to set the trigger to 1 stop bit, instead of 2. It will not fire on 2 stop bit UART data when using the 1.5 stop bit or 2 stop bit decoder setting. When the UART configuration is 1.5 stop bit, the trigger setting must be 1.5 stop bit to fire. I did not try lower data rates as the microcontroller is hard wired to the transformer which is just tuned to carry the manchester encoded data over a 6 Mbaud UART. I hope I can try it later using another data source.

At the moment, the data stream is generated on a STM32 microcontroller on a custom board. I have a STM Nucleo-F429ZI here, for which I could adapt the transmitter code. If you are proficient with that, could send you a program which transmits the continuous data stream. I could also provide a wave file from the oscilloscope.

Hello!

I have Nucleo L432KC and F401RE.
Also a scope capture will be fine I can load that in AWG.

If that fails, I will try to recreate it myself but cannot say when, it is kind of busy.

Best,

[eTobey]

Would it not be much simpler/easier to, in the decode list just to save all the decoded data to a CSV?

If the goal is to view it on the scope, segmented would likely be a better option so you can view frame by frame.

I tried two ways to save the data to a file, but this scope cant do this... I doubt that it would work in any other way. So thats about "simpler/easier".     

Segmented is a way, but it wont work, if you have a special trigger for the start of the frames... Search events is a way to go through the frames.

I bought a DSLogic Plus, in the hopes to have something i can work with. Its also a bit of a dissapointment, but with another script ( ) I can work with that. Its a bit cumbersome tough.

[eTobey]

Which command are you talking about here?  There is no reference to the word "export" in the programming manual.

Because the manuals arent that good either! 

[ttelectronic]

I tried two ways to save the data to a file, but this scope cant do this... I doubt that it would work in any other way. So thats about "simpler/easier".     

Segmented is a way, but it wont work, if you have a special trigger for the start of the frames... Search events is a way to go through the frames.

I bought a DSLogic Plus, in the hopes to have something i can work with. Its also a bit of a dissapointment, but with another script ( ) I can work with that. Its a bit cumbersome tough.

I really took the time to look into it. I took a CAN signal, granted just a demo series of data. Expanded out as much as possible, and was able to simply in the result list hit "save" and save a CSV file with all 2000 lines of decoded data with no problem - 2000 appears to be the hard limit on decoded data.

I was also able to do the same via python and see all 2000 lines of decoded data using a slightly different command as stated in the programming manual.

It's simply not possible to help those that do not wish to be helped. Best of luck.

[eTobey]

I was also able to do the same via python and see all 2000 lines of decoded data using a slightly different command as stated in the programming manual.

It's simply not possible to help those that do not wish to be helped.

Well, what about posting that script? You are actually not that helpful with your post...

[KungFuJosh]

Well, what about posting that script? You are actually not that helpful with your post...

Still rude as hell.

Here's a suggestion- try this instead: "Thank you for your reply, and taking the time to try and help me. Would you mind sharing that script?"

[ebastler]

Well, what about posting that script? You are actually not that helpful with your post...

I think ttelectronic has already done that, in reply #301 above.

Code: [Select]

import pyvisa as visa
sds804 = visa.ResourceManager('@py').open_resource('TCPIP::192.168.1.x::INSTR')
print (sds804.query(":DECode:LIST1:RES?"))


[eTobey]

Well, what about posting that script? You are actually not that helpful with your post...

I think ttelectronic has already done that, in reply #301 above.

Code: [Select]

import pyvisa as visa
sds804 = visa.ResourceManager('@py').open_resource('TCPIP::192.168.1.x::INSTR')
print (sds804.query(":DECode:LIST1:RES?"))


He wrote some code lines in his text. Thats not what i call a script, rather some "hints". He has also made no reference about that particular "script".

Still this is just a workaround for a feature that is not that usable... 

[ebastler]

He wrote some code lines in his text. Thats not what i call a script, rather some "hints". He has also made no reference about that particular "script".

Still this is just a workaround for a feature that is not that usable... 

You are just being stubborn now. Please don't dig that hole any deeper for yourself.

Those three lines of code capture the core concept and teach you (and us) which SCPI command to use to get all data. They also constitute a working script. But we don't even have to get into that argument, because...

... it was you who introduced the term "script" into the discussion. ttelectronic only talked about "do[ing] the same via python and see all 2000 lines of decoded data using a slightly different command as stated in the programming manual." Please see the dialog snippet below.

So you certainly don't get to complain that it was not a "script" in whatever nomenclature you like to apply. Just use the information provided, or don't if you prefer to ignore it, and move on.

I was also able to do the same via python and see all 2000 lines of decoded data using a slightly different command as stated in the programming manual.

It's simply not possible to help those that do not wish to be helped.

Well, what about posting that script? You are actually not that helpful with your post...

[eTobey]

Ifthatisascriptthenthisisaperfectlyfineformattedtextandiamstillwonderingwhyyouareevencaringaboutastubbornguylikeme 

[ebastler]

Look, Tobias -- there were many opportunities where you could have handled this differently:

• You could have read ttelectronics' first post (#301) carefully and would have found the required information right away.
• You could have asked him politely to clarify (your #306).
• You could have thanked me for pointing you to the required information.
• You could have taken a hint that you are being unreasonable.

But with uncanny assurance you chose the wrong turn at every single corner. Bravo.

[eTobey]

Not an issue, but deserving a  :
When choosing a file to load the setup or reference from, every file is shown regardless of its fileformat.

That has the charme of a program from the last century.

(see attachment)


Edit:
Just watched a video, and it has a part that reminded me of this fact (just this part that lasts about 10 seconds - i cant create a link that starts playing at this part):
youtube.com/watch?v=652ibqTeYc0&t=214s

Why is that, that we are moving backwards? Its ridiculous!

[tautech]

When choosing a file to load the setup or reference from, every file is shown regardless of its fileformat.

That has the charme of a program from the last century.

So ?

Expressly intended/designed to be this way.

RTFM
29 Save/Recall  P208
https://int.siglent.com/u_file/download/24_02_20/SDS800X_HD_UserManual_EN01A.pdf

Furthermore, SDS800X HD are a bargain priced DSO that for the most part have many of the same features as its bigger brothers therefore any wholesale changes would need to apply to all models and in doing so break the workflow of the many existing users.

One needs to see the bigger picture.....

[eTobey]

Expressly intended/designed to be this way.

Furthermore, SDS800X HD are a bargain priced DSO that for the most part have many of the same features as its bigger brothers therefore any wholesale changes would need to apply to all models and in doing so break the workflow of the many existing users.

Intentionally made worse then good? Thats exactly like in the videolink... Why on earth??? 
Another one: In order to type a space or a "-" for example, you have to click three times on the keyboard. Which is exactly worth three of these: 

And if the software is developed for many models, I am really glad that i have not bought a more expensive one. The dissapointment would have been HUGE.

There shouldnt be so many bugs issues in it, at least not huge ones like trigger holdoff not working, IF it was developed for many models...

[tautech]

Expressly intended/designed to be this way.

Furthermore, SDS800X HD are a bargain priced DSO that for the most part have many of the same features as its bigger brothers therefore any wholesale changes would need to apply to all models and in doing so break the workflow of the many existing users.

Intentionally made worse then good? Thats exactly like in the videolink... Why on earth??? 
Another one: In order to type a space or a "-" for example, you have to click three times on the keyboard. Which is exactly worth three of these: 

Really, have you not yet plugged a proper keyboard into it so to ease all the pain you are suffering ? 

[KungFuJosh]

Really, have you not yet plugged a proper keyboard into it so to ease all the pain you are suffering ? 

No thanks! Then we'd have to read all his posts about his keys sticking. 🙄

[eTobey]

Really, have you not yet plugged a proper keyboard into it so to ease all the pain you are suffering ? 

I should have plugged in a proper scope... This is just one example of its deficiencies...
Another one: 15 clicks (and the filename was only one letter!) to have the mask in place, were - if it would be a "great" scope, one click could have done that. 

Did i meantion, that after such doing, the trace is offset? There were even other cases, where a trace would have even changed its scale.

[KungFuJosh]

Sell the scope. I'll buy it from you. $200 USD. It's defective and you hate it, so that should be a good deal for you.

[Furna]

https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/msg5657745/#msg5657745

[Bill3745]

I didn't see this in the thread so apologies if it was already reported, but I have had the FFT function "lock up" on me a few times where the only way to get it running again is to reboot the scope. The scope itself stays responsive, it is only the FFT that stops working where it will not respond to any parameter changes or display any signal. Turning the FFT function off and then on again does not seem to help. Unfortunately, I do not know of a specific sequence of actions to reliably reproduce the bug. I am using the latest firmware -  1.1.3.8 - on a SDS814X HD.

[Martin72]

Hi,
It's good that you have provided the model and firmware version.
Now, the settings and your measurement setup would be interesting.
The settings can also be saved and uploaded so that every SDS800X HD owner can reproduce them.

[Bill3745]

Hi,
It's good that you have provided the model and firmware version.
Now, the settings and your measurement setup would be interesting.
The settings can also be saved and uploaded so that every SDS800X HD owner can reproduce them.

If I can get it to happen again I'll save the exact setup and post. The scope had been up and running for several hours and I was trying to reproduce some of the results Performa01 posted in the Review & Demonstration thread.  The second time it locked up I was doing the FFT dynamic range test with the combined 10.1 MHz and 9.9 MHZ signal being feed into channel 3. The other setting were pretty much the same as what was posted in that thread.

[patrik96]

My problem is the following, my HD804 does not remember the set of the AC position after switching off,
On one channel, typically CH1, it switches to DC position after each switching on and has to be reset.
The display shows AC position but the reallyti is DC..

[eTobey]

Just another issue...

Just like not remembering the clock when turning off, even if it is still plugged in, and the power button stays light up. 

[eTobey]

I captured a CAN-Bus for 10s (1s/div), but it does not show the data at that scale, at a scale lower (500ms/div) it shows WRONG data. At 200ms/div ("pot wrong.png") it shows seemingly correct data. Now how can i be sure, that such data is correct?  (This is a general question)

Another question:
If this firmware is beeing used for more expensive devices, i guess those have the same issue?

Edit:
That what looks right, has actually wrong data in it. Compare "act wrong1.jpg" and "act wrong2.jpg".

Edit:
Confirmed for USART too.