I’ve always been interested in ECU logic and system controls, and one thing always plagued me. Why doesn’t someone just create a stand alone ECU device that will allow a car to pass ODB2. I guess system control nerds aren’t car nerds. Sad…
I wouldn’t mind really digging into a ECU set up, but it would probably be a GM set up as I’m a fan for some reason. If I only had zee time.
I think I understood that. NYS via OBD2 mandates the OEM PCM, which in turn constrains how the actual sensors communicate. These sensors don’t work with the engine control you want to use? That’s a fucker.
Close- the sensors themselves will work fine, but the trigger wheels they read are different. The Gen-2/3 Vipers use a 10-slot reluctor ring, and a single step 170*/190* Cam Position configuration. The Gen-4 uses a 60-slot+ ring, and about 4 different slots, which variable positioning.
Most of the sensors are going to be usable on both systems, some will have to be redundant… but I am hoping the Motec Outputs can mimic some of the redundant ones to simplify things.
Oh, so you’ll be seeing a false signal from them.
Either way, looks like a big clusterfuck. Have fun!
That… it does! lol
or at least a OBD-2 trickery box that simulates what NYS wants to see. 
that couldnt be that hard… all it needs to do is respond to requests and spit out certain types of data…
Brian
Someone would make a killing if they designed a PCM emulation box that took generic inputs and converted them to OEM specific protocols, as well as said “all is well” on the OBD-2 front…
there is a guy that is doing that in the honda realm. just found it last night.
he has a vid on youtube and i saw some info on pgmfi.org.
i want him to adapt it to take megasquirt serial data and translate it to an OBD2 protocol that subaru uses and also chryslers as well.
Brian