<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Help with Serial Terminal Logging and Data Parsing]]></title><description><![CDATA[<p dir="auto">Hello  everyone</p>
<p dir="auto">IoNinja is a great tool for testing and logging serial communications, which is why I recently started using it. I could use some assistance with a couple problems I hve encountered, though.</p>
<p dir="auto">Logging data from several serial devices at once is part of my current project. I hve configured the Serial Tap and created distinct sessions for every device; but I am having trouble efficiently handling the log files. Can the log files be automatically labeled or arranged according to the session name or device ID?</p>
<p dir="auto">I have to extract certain information from the logs; including error codes and timestamps; and export it for additional examination. Although I am not familiar with jancy, IoNinja appears to support scripting with it. Is there a straightforward sample script that shows me how to extract and process particular data fields from logs?</p>
<p dir="auto">I would be very grateful if someone could share some advice on how to maximize performance when handling large volumes of data.</p>
<p dir="auto">I appreciate your help in advance</p>
]]></description><link>http://64.23.185.212/forum/topic/323/help-with-serial-terminal-logging-and-data-parsing</link><generator>RSS for Node</generator><lastBuildDate>Mon, 10 Aug 2026 22:41:51 GMT</lastBuildDate><atom:link href="http://64.23.185.212/forum/topic/323.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 29 Nov 2024 15:09:49 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Help with Serial Terminal Logging and Data Parsing on Tue, 03 Dec 2024 04:09:37 GMT]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">It's not very clear what you mean by "automatically labeling log files according to the session name or device ID". When you create a new IO Ninja session, the log is stored in a temporary file. When you save the session, you explicitly specify a directory name to store the session data (or a single file name if you only need to save the log file) -- so you are the one picking the file names.</p>
<p dir="auto">If you need to post-process the log files externally, you can do it in any language of your choice (Python, JavaScript, C, etc.) The <code>.njlog</code>  file format is very simple. A brief overview can be found here: <a href="https://ioninja.com/doc/developer-manual/logging-engine.html" rel="nofollow ugc">https://ioninja.com/doc/developer-manual/logging-engine.html</a>) and all the internal structures are open-source; see <code>scripts/api/log_RecordCode.jnc</code> and <code>scripts/api/log_RecordFile.jnc</code> for all the relevant declarations.</p>
<p dir="auto">Let me know if you have any follow-up questions regarding the file format.</p>
]]></description><link>http://64.23.185.212/forum/post/714</link><guid isPermaLink="true">http://64.23.185.212/forum/post/714</guid><dc:creator><![CDATA[Vladimir]]></dc:creator><pubDate>Tue, 03 Dec 2024 04:09:37 GMT</pubDate></item></channel></rss>