I have J1708. The RPM gauge is delayed by a few seconds. It does not seem to pause, so it appears as if the gauge is always 2 seconds behind. (EDIT: All gauges are behind.)
After reading the performance section, I am wondering how this is possible. I don't see "Adapter Data Buffer is Full".
I am a software developer and I don't see any reason for this app to be cpu or graphics intensive. If the adapter is getting RPM data 10-100x per second, then I see no reason for any multi second delay between my foot and the display. BLE should be much faster than the serial J1708 bus, right? Displaying this data is trivial for even a very old computer.
There isn't some goofy algorithm that insists on showing each data value, instead of dropping old values is there? I mean, yes, that's exactly what it seems, unless the J1708 bus has this delay in it.
After reading the performance section, I am wondering how this is possible. I don't see "Adapter Data Buffer is Full".
I am a software developer and I don't see any reason for this app to be cpu or graphics intensive. If the adapter is getting RPM data 10-100x per second, then I see no reason for any multi second delay between my foot and the display. BLE should be much faster than the serial J1708 bus, right? Displaying this data is trivial for even a very old computer.
There isn't some goofy algorithm that insists on showing each data value, instead of dropping old values is there? I mean, yes, that's exactly what it seems, unless the J1708 bus has this delay in it.
0