Trinity + Analog Input = Data Stream Lost?
Posted: Mon Apr 14, 2014 8:34 am
A couple of years ago I wired up an LC-1 to my Trinity, and enjoyed logging wideband AFR with my other pids. Over time Trinity started to lose connection with the car more frequently, with the "data has halted - waiting for engine to start" message. I had assumed it was my OBD connector, but I've come to the conclusion that it's when the analog input is connected that I get this error. When it's not connected, I can datalog all day, even the AFR pid with no reading.
Why would connecting the analog input cause the Trinity to throw this error? It almost feels like it's vibration/movement related, if I sit at idle I can datalog, but as soon as the car starts to move, Trinity freaks out.
Any ideas?
Why would connecting the analog input cause the Trinity to throw this error? It almost feels like it's vibration/movement related, if I sit at idle I can datalog, but as soon as the car starts to move, Trinity freaks out.
Any ideas?