<![CDATA[Capture messages based on CR-LF]]>We are serial logging on a machine. Bytes of Tx and Rx data are saved at 1mS intervals. Messages are truncated per 1mS, and Rx and Tx are interchanged, making the analysis of the log files very difficult.

How can we log the messages in response to CR-LF which indicates the end of a message Tx or Rxd?

]]>http://64.23.185.212/forum/topic/338/capture-messages-based-on-cr-lfRSS for NodeSat, 05 Sep 2026 20:47:48 GMTThu, 13 Nov 2025 14:33:29 GMT60<![CDATA[Reply to Capture messages based on CR-LF on Fri, 21 Nov 2025 11:14:13 GMT]]>A simple TX/RX Filter could be sufficient in many cases. If you want to "de-interlace" the traffic by accumulating TX/RX data and postponing adding it to the log until a certain character (CR/LF) arrives -- a simple custom layer plugin could work. Finally, you can save captured data streams into an .njlog file and post-process it with any scripting language of your choice.

Could you please share an .njlog or at least a screenshot of communications? That would help to choose the best approach.

]]>http://64.23.185.212/forum/post/776http://64.23.185.212/forum/post/776Fri, 21 Nov 2025 11:14:13 GMT