Edit: DSOX2000/3000 UART testsignal has 8O1 parity not 8N1

[Pinkus]

EDIT: I will not change the following as it might help somebody later with the same problem. In short: You should know, that the 19.200 baud UART testsignals of the scope does not come with "no parity" (as I thought) but "odd parity".
Thus there is no bug within the scope - the bug was in front of the scope 


Hello,

by creating my comparison (see here: https://www.eevblog.com/forum/testgear/agilentkeysight-dsox2000a-vs-dsox3000a/msg692627/#msg692627) I found something strange:

Can someone with a DSOX2000 or DSOX3000 (or MSOX) please check this if you can reproduce the following. I do not want to report this as a bug if it is none (could be my mistake), however it looks to me, the serial UART decoder does have a bug. You will need serial decoders and training signals enabled on your device.

What to do to reproduce:
1) Press Help, switch on training signals, select UART.
On Pad Demo2 now a 19.200 baud UART signal appears.

2) Now connect an analogue probe to pad Demo2 it and start the serial decoder.
Settings are 19.200 baud, 8N1, Output in ASCII

3) Set trigger type to Serial UART (note: settings were timebase: 1ms, vertical: 1V/div)

The decoder should show "KEYSIGHT" but ... every 2nd character is missing and in the lister error frames are shown (see attached pictures "19200 Baud...")

Only if you manually select the baud rate 18.200 baud, the decoding of the 19.200 baud signal works flawless!!
(see attached pictures "18200 Baud...")

I encountered that in firmware 2.38 and now upgraded to 2.39 and it is still the same.
For me, the UART decoder does not work correctly (at least not at 19.200 Baud).

Can please confirm this somebody? Please do not tell me I am doing something wrong as that would impair my self-confidence 

Used hardware by me: MSOX3024a with several options (all official), 300 Mhz passive probes.

P.S.: as the bitrate measurement is also showing 19.200 baud, I am assuming that the used testsignal is fine - I did not double check yet with UART/RS232 signal from a different source.

[AndyC_772]

On my scope (f/w version 2.35), the demo signal has odd parity. The 8N1 setting is wrong, it should be 8O1.

[Pinkus]

Oh my god....   shame shame shame - shame on me 
I will leave the post online as others might need this too. However I will change the title.

  Dang!

[Campus]

Hi,

it's working as expected for me as well after changing to odd parity. This is with firmware 2.39.

Best,
Campus