First let's get the Logging working, then both your 50% charging,
your commute, and then your deep charging would be great logs.
If you log to RealTerm format, then CAN-Do is able to read that
file, but the messages only have 1-second time stamps, not the
millisecond time-stamps that CAN-Do supplies.
So, putting out the 11-byte one-channel format that the GID-Meter
uses, and logging direct to CAN-Do would be a bit better, IMHO.
I believe that you know the 11-byte format, and now that you have
modified the program, and accomplished good data output,
changing to the 11-byte format should be easy.
I think that you can still use RealTerm to log the binary format,
and use a HexEdit program to look at the captured binary data.
I do not know if the "lincomatic" hardware/firmware captures
All the CAN Messages, but it might.
With the GID-Meter's present firmware, some too-fast messages are lost.
The hardware is capable of getting them all, but the example firmware
that we used, in conjunction with the "standard" CAN-support library,
did not re-enable the receiver fast enough to catch messages that arrived
too soon after the preceding message. We need to re-write the firmware
to use an interrupt to very quickly dump the Message into a ring buffer.
Hopefully, that simple change should do it. If not, we can use more than
one of the hardware message buffers. We have already tried that.