Perfect thanks !!! Now i am getting a good decode of what is going on
Glad to hear it works now!
Is there anyway to export the Hex Strings (without decode) into a text file
Yes, you can export your log as a text file (Menu -> File -> Save Log As...) at any time.
I often find it easier when decoding unknown devices (in terms of registers) to look for patterns and things that are constantly changing to give a hint as to what the data could represent.
If you want just the pure data without annotations added by Modbus Analyzer -- remove the Modbus Analyzer layer, and you will get back to the original log. Modbus Analyzer (as well as other protocol analyzers) does not destroy the original log, so it's totally reversible.
Another option to get to the raw data is to post-process the original
.njlog file. It will be more efficient than parsing a hex view inside a text file. The
.njlog file format is open-source (log file structure definitions are in
scripts/api/log_RecordFile.jnc), so you can use any programming language of your choice.
An example of decoding
*.njlog files can be found in
ReplayLogLayer.readLoop(). This plugin reads a log and "replays" TX or RX data with respect to inter-packet delays. It's probably not exactly what you want, but it should give an idea of how to "walk" across a raw
.njlog file to process the captured data.
Your decode window etc is brilliant i must say though !!
Thank you! We work hard to make our product as versatile and convenient as possible, so I really do appreciate such feedback