Make Actisense (NGT-1) format available for TCP connections

[skrue]

Hi, I have built a small gateway with ESP32 that outputs Actisense NGT-1 compatible binary data via a TCP connection.

However, in visual-analyzer, I can select this format only for serial connections, so I have to use a virtual serial port software that connects to the TCP server and then connect visual-analyzer to that virtual COM port. Seems unneccessary and overcomplicated to me, so supporting the binary format for TCP connections would be appreciated!

On a different note (happy to open a separate issue if you want me to): When turning on logging, Actisense binary data is not correctly forwarded to the logfile. When I choose "Source Format" or "Actisense Serial Format" as the log output formats, both of those will give me different flavors of human-readable data, but not the real NGT-1 compatible binary format (which could then be inspected with Actisense's own software like EBL Reader).

Also, I am a little confused by your naming of the different Actisense formats.
As to my knowledge, there is the binary format (as described here) and the ASCII format (as described here). I think the binary format is what is typically referred to as "Actisense Serial" and that can also be read by the canboat actisense-serial software. When being logged or displayed, this format will not be human-readable. So being specific and consistent in naming these two formats throughout the applicatoin would be helpful 👍

Cheers!