Suggested by Sorama on the EEVblog forum. Thank you!
| Bit fields | |
| Value | |
| Zoomed out | |
| Errors |
Zoomed in far enough, each character on an RS232 or UART9 lane is drawn as its parts: the start bit green, the data bits as a box in the decoder's colour (blue for a 9-bit UART's address character), the parity bit magenta (on UART9 the address bit takes its place) and the stop bits white, each at the time the decoder sampled it from the start bit's edge, so the fields sit under the bits on the trace. None of these colours is a decoder's colour, the address blue or the error red.
The value is centred on the character's data bits, the same way on every character, so a row of bytes reads as a column of values each under its own bits. It is always shown whole: the text, or the value without its tag (12 for A:12) when the box is narrower.
A field is drawn on its own when one bit is at least 4 pixels wide and the value fits whole in the data bits; at 9600 b/s that is 1 ms/div and finer on the scope's screen. Zoomed out further each character is the box it was, with its value while it fits and a plain mark when not even that does, and characters closer than a few pixels merge into one bar. The event table, the saved table files and :BUS<n>:DATA? are unchanged.
A character that failed a check keeps the error red: its data box, and the bit that failed, a parity bit that does not match or a stop bit at space. The bits that passed keep their colours, so the lane shows which check failed.
The RS232 and UART9 decoders hand the lanes each character's start, data, parity or address, and stop bit times from their own bit timing; the lanes draw them apart in four colours, or the plain box when a bit is narrower than 4 pixels.
8E1 and 8N1 characters at 10 samples a bit, a parity error and a framing error, 9-bit multidrop traffic with 7 and 8 data bits and two stop bits; on both families a 9600 b/s text line, stopped, drawn at 20 ms/div (plain boxes) and at 500 us/div (the bit fields, every value whole).
It reaches the scopes with the next release.
Zoom in on one of your UART or RS-485 lines and tell us whether the colours and the value read the way you like on the R&S.
Each UART character on the decode lane split into its start bit, data bits and stop bit in their own colours, with the value centred under the data bits.
When doing UART decoding, it would be nice to see the start and stop bit, in a different color from data bytes. Below it should show the value, vertically aligned. I like the way R&S scopes do it.
Try it and tell us what to change: reply on NovaOS's thread on the EEVblog forum.