Products > Test Equipment

Siglent SDS2000X HD, missing Features and Bugs

<< < (60/76) > >>

tautech:

--- Quote from: Grandchuck on February 07, 2024, 04:00:24 pm ---I am back to report another minor issue.  Could be my thick skull again, but it seems that shut down and power up messes with settings that it should not.  Case in point ... SPI decoding ... the protocol settings (the thresholds) get changed and decoding no longer works after a restart.  Easy enough to fix once one realizes what is happening.

Then I tried saving the setup when decoding was working.  Powered the scope back up and loaded the saved file and the situation was a bit worse because two of the probe settings got changed from X10 to X1 and, once again, the thresholds were wrong.  Again, easy to fix once one realizes what is going on.

--- End quote ---
Siglent know about this and have shared a bug ID for it on their forum.

tautech:

--- Quote from: ebastler on February 07, 2024, 06:32:46 pm ---
--- Quote from: tautech on February 07, 2024, 06:22:54 pm ---Siglent know about this and have shared a bug ID for it on their forum.

--- End quote ---

Is that a public forum or just for dealers etc.? If it's the former -- where to find it?

--- End quote ---
Private beta tester forum. Membership by invite only and access only given to the products you are working on.
I can see lots but not all.

Grandchuck:
I am seeing some trigger instabilities when decoding UART signals.  Screen captures:
  Expected: triggers on falling edge of C1.  This is what is expected.
  DecodeBut: late in the data frame.  The trigger is later than expected.
  JunkDecode: trigger is late.  The trigger is late and the decoding is junk.
  NoDecode: did not trigger in time?  No decoding.

The captures are at 9.6 kbit/s.  At 38.4 kbit/s, there seem to be fewer errors.

tautech:

--- Quote from: Grandchuck on February 09, 2024, 08:04:11 pm ---I am seeing some trigger instabilities when decoding UART signals.  Screen captures:
  Expected: triggers on falling edge of C1.  This is what is expected.
  DecodeBut: late in the data frame.  The trigger is later than expected.
  JunkDecode: trigger is late.  The trigger is late and the decoding is junk.
  NoDecode: did not trigger in time?  No decoding.

The captures are at 9.6 kbit/s.  At 38.4 kbit/s, there seem to be fewer errors.

--- End quote ---
Yep, clear retriggering within packets.
Remedy = add Trigger Holdoff of a little larger value than the largest packet width.

Performa01:

--- Quote from: Grandchuck on February 09, 2024, 08:04:11 pm ---I am seeing some trigger instabilities when decoding UART signals.  Screen captures:
  Expected: triggers on falling edge of C1.  This is what is expected.

--- End quote ---
Falling edge trigger is a bit ambigous with so many falling edges, don't you think?

Modern oscilloscopes have a bunch of powerful triggers for a reason. In your case use a postiive pulse trigger with time the minimum pulse width little greater than one character duration, e.g. about >1 ms at 9k6 should reliably trigger at the start of each packet, regardless of its length.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod