View Single Post
Old 01-21-2011, 05:04 PM   #15 (permalink)
EcoModding Apprentice
Join Date: Jan 2011
Location: Australia
Posts: 179

Sonata97 - '97 Hyundai Sonata GL
90 day: 25.96 mpg (US)

Pulsar - '03 Nissan Pulsar ST
Team Nissan
90 day: 36.09 mpg (US)

Lancer - '04 Mitsubishi Lancer
90 day: 31.11 mpg (US)

Lancer 2.0 - '09 Mitsubishi Lancer
90 day: 27.1 mpg (US)
Thanks: 9
Thanked 16 Times in 13 Posts
Ahh from the thread:
"The criticism was not directed at the code or the concept. It was directed at the "I haven't tested this, but I KNOW it will work" attitude."

As always, third parties have an opinion - I won't add one here.
Or will I. I like the idea, I want to do it.

I'll be giving it a go on my Hyundai Sonata, which has a 12 pin connector.
What I'm lost on and can never seem to find an answer to is the conflicting information out there.

This page mmcdlogger. suggests the data is request / response. You must ask for data to get it.

But, I recall reading that there is a data stream, i.e. you simply listen and process the data that comes along the pin 1 - but the baud rate - I've seen 160-baud, 8192-baud and 1953-baud all mentioned as being the rate used.

I'm not sure what to expect - and I want to go to arduino.

Perhaps someone knows the answers ?
- What is the baud rate?
- Is there a data stream, or must all data be requested?
- Does pin 10 and 12 get shorted for data ?

I also did some checking yesterday too with my multimeter:
- Pin 1 and 12 - this bounces around between 11-13V and 0V with key and engine on.
- Pin 11 (Speed) and 12 stays at 4.69V with the engine on. I haven't checked for variations here.

This link mmcdlogger. says the speed can be requested by ECU.
What's the point of the speed sensor PIN in the ALDL circuit? I think it's duplicated if that's the case, the ECU has speed sensor input, as does pin 11.
  Reply With Quote