I really don't understand ECU/Datalogging

[mindset]

I've been doing a lot of research lately on datalogging and ecus and pocket loggers. Unfortunately, I fail to comprehend how that whole situation works. From what I know a datalogging cable, hooks up from the OBD to a palmpilot/labtop and relays info to the palmpilot, is that correct? But, you can't tune the car unless if you have a socketed EPROM, right? What's the difference between hooking up the palm pilot to the EPROM and connecting it to a OBD port? And the DSMlink is hooked up through the socketed EPROM correct? why not the OBD port? I'm confused on this whole situation. Thanks.

 

[slowstang]

Ok lets clearify a couple of things. Your confusing a loggger with a tuning system that has logging capabilities.
1) Logging software and equipment - Includes Palm Pilots aka pocketloggers or just loggers (and some laptop logging software). They use a serial cable to plug into your ODB port. They only relay information given by the computer. Useful for monitoring the car's vitals. They cannot tune anything in anyway. Can be used with eprom or non-eprom ecus.
2) Tuning software and equipment with logging capabilites - (not including standalones or things like AFC or Translators) - DSMLink DOES require an eprom to work. Eprom sockets give it a centralized point to store the information for the ECU to use. The DSMLink chip plugged into the socket contains a small pcb board and allows Link to do what it does. Changes are made in the DSMLink software on a laptop that is plugged into the OBD port as well and the information is relayed to the chip plugged into the ECU. (not a cable that's plugged directly into the Eprom chip).

Hope this answers your questions.

BTW equipment that tune by modifying the air signal sent to the ECU (AFCs and Translators) work by 'fooling' the computer and do not involve an EPROM chip so it is irrelevant if you have one or not.

 

[mindset]

Thanks, that helps a lot.