Ian, I sent a debug log with just 1 gauge. It is CAN frame 264, little endian, starting bit 7 for 8 bits...it's reading the bits in reverse order.

Ian, I sent a debug log with just 1 gauge. It is CAN frame 264, little endian, starting bit 7 for 8 bits...it's reading the bits in reverse order.

bump

I'm not having issues with gauges on the dashboard other than receiving no data, I'm just not getting results when editing/testing signals in the edit...

No bridge and no firewall. I did lots of logging via terminal apps well before CAN monitoring was a thing in TP, so there's lots of data available on...

Thanks, Ian, for taking another look. I'm sure you are correct. Like I said before though, it does work consistently with the delay set at 0B for that...

Bump

Ian, Did you get my last couple debug logs?

Long post...sorry! Here's an update for anyone who may come across this thread. Ian didn't find what was causing the reported errors in the debug l...

Ian, Did my debug data make it to you?

Ian, I sent you an error log this morning, and I also just sent you an email.

Thanks, I'll run a debugging session either today or tomorrow. I've been wondering if it could be bus collision, but it seems like the dropped frames ...

Cintakc and Ian, thank you both. I ended up turning off the "Faster communication" but left the auto timing enabled and removed everything from the...

So I removed all of the init string commands, and the diagnostic start/stop commands. Then I turned off the "Faster communication" and turned on "Disa...

Cintakc, that didn't help, still losing frames. It works great as the only gauge, and only maybe once or twice a minute it will lose a frame when I ad...

So the custom init string seems to have worked great, but I only had the one gauge on the dashboard. I tried adding more gauges and the problem comes...

Thanks cintakc, I'll try that. I've been trying flow control mode 2 (adapter sets the header automatically) but haven't tried mode 1. Most of the o...