HEX Reader
jwells
Posts: 25
I am trying to fault find a device attached to an NI-3000 and the device uses HEX strings to communicate. I have been logging all communications to a file and notepad will not read the hex codes in the file (?? Q).
Do any of you use any HEX readers that you could recomend ?
Do any of you use any HEX readers that you could recomend ?
0
Comments
http://www.hhdsoftware.com/Products/home/hex-editor-free.html
The device I am logging has no fixed end of line or beginning of line characters and occasionally it varies in length. When writing to the log file I add a time to the start of the line to allow me to easily see when the command was sent and it also helps divides the log file up a bit so I can quickly find the information and see patterns.
When I use the HEX viewer it has no structure to how it is viewed and justs wraps it in fixed widths presenting a window full of HEX. It would help if I could identify a set of characters as EOL markers or split it out into blocks, which I would match up to my date stamps to help break the view up, but I?m not sure if that?s possible.
I then thought it may be easier to decode the HEX and write the logs files in ASCII, then I could present them how I wanted and view then in notepad.
e.g.
<date>: $01,$02,$05
<date>: $03,$02,$05,$02,$05
Line 1 :: 09/28/07: $01 $02 $05 $0A $FF - 02:18:50
Cheers
Glad to help. FORMAT() is the super-duper big brother/cousin of ITOA() and is extremely useful indeed.
Cheers.
This line works fine:
outstring = "outstring,'$',FORMAT('%02X',instring[x]),$20"
But I should have wrote it this way instead:
outstring = "outstring,FORMAT('$%02X',instring[x]),$20"
Alot of people don't know, but there is actually a debug.axi include file that is installed with studio.
see the include file below. It contains alot of x to string conversation for sending to terminal.
C:\Program Files\Common Files\AMXShare\AXIs\debug.axi