The standard analyser windows on loop get me what I need but it’s a bit hard to read conversations vertically My scenario is that I’m trying to sniff traffic between two devices that use 115,200 async serial to communicate. I actually came on to post a suggestion for the terminal window but found this while searching to check if the question had already been asked.

I wasn’t sure whether to reanimate an old thread or start a new one but the idea above about redirecting the terminal output to a virtual com port is such a good one I though I’d jump on the bandwagon here. I think there are still 5 characters that fall back to “?” because there is no displayable version in any encoding scheme. tabs, line feeds and carriage returns are interpreted as the correct control character by the terminal. The tiny text you can’t quite read are the Unicode control pictures for characters like null. Here is a sample of writing all bytes 0-255 to the new terminal. PUTTY also supports reading from named pipes. Right now, you can’t open that named pipe without disrupting the software, but we’ll open that up in the future so you can easily read from the named pipe from any application, or route it into a file. We’ve started using native named pipes, one for each analyzer, to stream results to the UI.For serial, it displays most bytes in Latin-1, but for non-displayable characters, I added fallbacks to Windows-1252 and to Unicode Control Pictures. We improved the formatting of terminal results for Serial, SPI, and I2C, to behave much more like an actual terminal.We rewrote the terminal implementation and changed 2 things: Interesting! We’ve actually implemented something very similar a few weeks ago, however we haven’t exposed the functionality to users yet. So the feature would be reducted in this sentence: streaming the decoded protocol into a virtual COM port opened “ad hoc”.

Serial monitor windows