RaceChrono + OBDLink LX, no more data after stopping and starting engine

I'm using RaceChrono with an OBDLink LX on a Caterham. The starter seems to trip out the OBD-II logging. It's fine if I start the engine before starting the log (or start within the expert setting 'initialisation delay', so I set it to 10000 to give me 10 seconds to start the engine). However when I come back to the pits, stop and start the engine and go out again, the rpm and throttle position readouts stick at their values just before the engine turned off. The connections screen shows OBDLink LX is still connected. To get the throttle/rpm to update again I can:
stop the log and start a new one (after starting engine)
or
disconnect / reconnect the car battery to power down / up and the OBDLink, just before I restart engine
Any ideas? In the next version, could you reinitialise OBD-II, when the rpm data sticks on a non-zero value for some time? I don't mind testing!

Thanks!

Comments

  • Which version of RaceChrono are you using? Similar bug got already fixed in v6.4.1. If your version is older, please update and try again.
  • oh, great! I was running 6.3.5, have updated to 6.4.1, will do another test, thanks!
  • So it's definitely better now, I can start the logging before starting the engine, but I still get no data after stopping the engine and starting it again on this car. I made a device output log when this happened, hopefully that will help! (I cut out the middle but I can send the entire log if that helps).

    <--14:37:25.866 OUT-->ATZ\r
    <--14:37:27.873 IN -->\r\rELM327 v1.3a\r\r>
    <--14:37:27.873 OUT-->ATE0\r
    <--14:37:37.999 IN -->ATE0\rOK\r\r>
    <--14:37:38.000 OUT-->ATL0\r
    <--14:37:38.137 IN -->OK\r\r>
    <--14:37:38.137 OUT-->ATSP0\r
    <--14:37:39.213 IN -->OK\r\r>
    <--14:37:39.214 OUT-->ATS0\r
    <--14:37:39.348 IN -->OK\r\r>
    <--14:37:39.349 OUT-->ATH0\r
    <--14:37:39.485 IN -->OK\r\r>
    <--14:37:39.486 OUT-->0100\r
    <--14:37:39.596 IN -->SEARCHING...\r
    <--14:37:44.337 IN -->4100FF969E19\r
    <--14:37:44.405 IN -->\r>
    <--14:37:44.405 OUT-->0120\r
    <--14:37:44.607 IN -->412020043401\r
    <--14:37:44.675 IN -->\r>
    <--14:37:44.676 OUT-->0140\r
    <--14:37:44.878 IN -->414040000000\r
    <--14:37:44.945 IN -->\r>
    <--14:37:44.946 OUT-->010C\r
    <--14:37:45.080 IN -->410C0E18\r
    <--14:37:45.081 IN -->\r>

    ...

    <--14:38:20.590 OUT-->0111 1\r
    <--14:38:20.628 IN -->411113\r\r>
    <--14:38:20.629 OUT-->010C 1\r
    <--14:38:20.642 IN -->410C0000\r\r>
    <--14:38:20.643 OUT-->0111 1\r
    <--14:38:20.685 IN -->411113\r\r>
    <--14:38:20.686 OUT-->010C 1\r
    <--14:38:20.697 IN -->410C0000\r
    <--14:38:20.698 IN -->\r>
    <--14:38:20.699 OUT-->0111 1\r
    <--14:38:20.713 IN -->411113\r\r>
    <--14:38:20.714 OUT-->010C 1\r
    <--14:38:20.726 IN -->410C0000\r\r>
    <--14:38:20.727 OUT-->0111 1\r
    <--14:38:20.738 IN -->411113\r\r>
    <--14:38:20.739 OUT-->010C 1\r
    <--14:38:20.748 IN -->410C0000\r\r>
    <--14:38:20.749 OUT-->0111 1\r
    <--14:38:20.761 IN -->411113\r\r>
    <--14:38:20.762 OUT-->010C 1\r
    <--14:38:20.778 IN -->410C0000\r\r>
    <--14:38:20.778 OUT-->0111 1\r
    <--14:38:20.788 IN -->411113\r\r>
    <--14:38:20.789 OUT-->010C 1\r
    <--14:38:20.799 IN -->410C0000\r\r>
    <--14:38:20.800 OUT-->0111 1\r
    <--14:38:20.882 IN -->411113\r\r>
    <--14:38:20.884 OUT-->010C 1\r
    <--14:38:20.998 IN -->410C0000\r\r>
    <--14:38:20.999 OUT-->0111 1\r
    <--14:38:21.011 IN -->CAN ERROR\r\r>
    <--14:38:21.012 OUT-->010C 1\r
    <--14:38:21.024 IN -->CAN ERROR\r\r>
    <--14:38:21.025 OUT-->0111 1\r
    <--14:38:21.035 IN -->CAN ERROR\r\r>
    <--14:38:21.036 OUT-->010C 1\r
    <--14:38:21.045 IN -->CAN ERROR\r\r>
    <--14:38:21.046 OUT-->0111 1\r
    <--14:38:21.059 IN -->CAN ERROR\r\r>
    <--14:38:21.060 OUT-->010C 1\r
    <--14:38:21.073 IN -->CAN ERROR\r\r>
    <--14:38:21.076 OUT-->0111 1\r
    <--14:38:21.087 IN -->CAN ERROR\r\r>
    <--14:38:21.087 OUT-->010C 1\r
    <--14:38:21.096 IN -->CAN ERROR\r\r>
    <--14:38:21.097 OUT-->0111 1\r
    <--14:38:21.111 IN -->CAN ERROR\r\r>
    <--14:38:21.112 OUT-->010C 1\r
    <--14:38:21.122 IN -->CAN ERROR\r\r>
    <--14:38:21.123 OUT-->0111 1\r
    <--14:38:21.132 IN -->CAN ERROR\r\r>

    at the end those error lines keep repeating for a few minutes, the engine gets restarted and the data doesn't come back.
  • Any idea at which point this CAN ERROR starts appearing? Did you turn off the engine at this point, or did the OBD-II reader just fail for some reason? I don't know how to recover from this...
  • around when the engine was turned off and restarted. If you can't recover don't worry (although I'm hoping perhaps you could try to reinitialise if you get continuous errors..?), I'm thinking it's something odd with this car's ECU, I think my OBDLink is good. Also I can workaround; either starting a new log or toggling the battery kill switch (it's a race car) makes it work on the next engine start!
  • Ok, sounds like it could be recovered with simple reader reset. I cannot test it, but I can make it reset if too many CAN ERROR's are received. I'll let you know once it's in the build.
  • great, thanks!
  • v7.0.3 attempts to fix it. Available soon.
  • got it, works great, thanks so much for making it work on this car (o:
Sign In or Register to comment.