Everytime I need to work on some serial decoding I end up debugging the scope instead of the project.
I am generating 9600 baud, 8-N-1 UART packets (The classic "Hello World!"). My siglent SDS1104X-E scope cannot decode correctly the SPACE (0x20) character and it cannot trigger on UART. I set trigger on START and it triggers on any High to Low transition, in the middle of a packet. I set trigger on DATA 0x20 and it triggers on any character.
I tried my micsig TO1102 and it works just fine.
How can the SDS1104X-E can have a BUG on a so simple decoding and triggering task? Nobody is using these options on this scope?
SDS1104X-E UART trigger START. That does not seem to be a START BIT or it is, but the decoder cannot recognize a valid UART stream
![Siglent SDS1104X-E UART Decoder and Trigger issues (BUG?)](https://www.eevblog.com/forum/index.php?action=dlattach;topic=233688.0;attach=950478;image)
SDS1104X-E UART Decode cannot identify a perfect 0x20 character
![Siglent SDS1104X-E UART Decoder and Trigger issues (BUG?)](https://www.eevblog.com/forum/index.php?action=dlattach;topic=233688.0;attach=950482;image)
SDS1104X-E UART trigger DATA = 0x20. Where is 0x20?
![Siglent SDS1104X-E UART Decoder and Trigger issues (BUG?)](https://www.eevblog.com/forum/index.php?action=dlattach;topic=233688.0;attach=950490;image)
Micsig TO1102 UART trigger DATA = 0x20 and perfect decoding
![Siglent SDS1104X-E UART Decoder and Trigger issues (BUG?)](https://www.eevblog.com/forum/index.php?action=dlattach;topic=233688.0;attach=950486;image)