Posts made by Gary Pupurs

Thanks! That simple regex ([\x52\x57]....) does work somewhat, but it also highlights any data within the payload that has an ASCII R or W, instead of only at the start of the packet. But that's useful enough for now, I appreciate it.

I did look at the custom plugin page a few days ago, but since it's been decades since I coded C++, I didn't try to write one. Thanks for the sample, I will customize it a little, see what it can help me out with.

(There does seem to be a bug in your sample code that is eating the character before the trigger. What previously was:

50 52 4f 47 52 41 4d                             PROGRAM

is now with the BreakOnChar layer:

52 4f                                            RO
52 41 4d                                         RAM

...mentioning it just in case someone else tries to use the code.)

Can you post some regex examples in the documentation on how to use "Colorize Log"? I tried it, but can't figure out the correct regex. I got a single hex value to highlight with 0x52, but no further.

Also, I found a bug, whenever I use this regex, it crashes IO Ninja: ^\x52
Seems to be the caret(^) triggering the crash.

Here is a sample of the serial port data:

52 02 00 10 00                                   R....
57 02 00 10 00 00 00 00 00 00 00 00 00 00 00 00  W...............
00 00 00 00 00 69                                .....i

52 02 00 10 01                                   R....
57 02 00 10 01 00 00 00 00 00 00 00 00 00 00 00  W...............
00 00 00 00 00 6a                                .....j

52 00 06 20 63                                   R.. c
57 00 06 20 63 16 25 50 00 00 00 00 00 00 01 00  W.. c.%P........
00 00 00 ff ff ff ff 00 57 58 5f 49 4e 44 59 20  ........WX_INDY 
00 00 00 00 00 ca                                ......

52 and 57 are commands. I'd like to colorize or bold the next 4 bytes, ideally with the 3rd of the 4th byte (block size) unbolded.
So it looks something like this, so it's easier to see the separation between the device's mem address and data being dumped:

52 02 00 10 00 R....
57 02 00 10 00 00 00 00 00 00 00 00 00 00 00 00 W...............
00 00 00 00 00 69 .....i

52 02 00 10 01 R....
57 02 00 10 01 00 00 00 00 00 00 00 00 00 00 00 W...............
00 00 00 00 00 6a .....j

57 00 06 20 63 16 25 50 00 00 00 00 00 00 01 00 W.. c.%P........
00 00 00 ff ff ff ff 00 57 58 5f 49 4e 44 59 20 ........WX_INDY
00 00 00 00 00 ca ......

(I am using this for developing a driver for the open source project CHIRP at https://chirp.danplanet.com/ . It is software to program and configure amateur radios (ham radios), and share channel configs across different radios. The manufacturers' software is usually very badly written with poor UI, and usually can't import/export to CSV to allow sharing channel/frequency configuration with another brand of radio. I plan to recommend IO Ninja for a workgroup license with other developers there. It works great for this purpose.)