Go Down

Topic: Interface arduino to nissan ecu (Read 2490 times) previous topic - next topic


Hey guys finally bought my first arduino and i want to interface it withmy nissan 200sx (240sx in th US). I've done a little research on the communication between the two sofware wise, but i'm having a little difficulty with the hardware. The ecu uses12v for comms but the arduino obviously only uses 5v ttl. Can i use a resistor divider to drap the 12v signal so i can read it using the arduino? And how do i step up my 5v signal to 12v for transmitting to the ecu?

Thanks in advance guys


What kind of communications do you plan to do? Is it CAN, OBDII? RS232? Do you know the protocol?
Brian from Tacoma, WA
Arduino evangelist - since Dec, 2010.


its none of the above. check out the link for clarification;

i think i've got most of the communications worked out as far as software goes, i just need to know how to convert the tx signal from the ecu down to a 5v signal so the arduino can read it, and convert the 5v ttl tx from the arduino to a 12v signal so the ecu can accept the commands i send it.


To convert from TTL to RS232 you need a MAX232 chip.. If you want to save yourself some work, http://www.ebay.com/itm/RS232-Shield-Arduino-/270801572459  here's an RS232 shield.
Brian from Tacoma, WA
Arduino evangelist - since Dec, 2010.


um pretty sure its not RS232. but i could be wrong seeing as i'm a relative noob when it comes to comms.


actually after reading a little on the net, could i use an RS232 or MAX232 ic to convert the signal? will the -12v output cause a problem or is there a way to bias the ic to only output 0v-12v to the ecu instead of -12v to +12v?


Why not use a Bluetooth/RS232 device attached to aduino and the attach a Bluetooth ODBII device... like ELM327... Arduino adapter usually runs about $6  and the ELM327 runs about $24 and you end up with a nice wireless solution.  I much prefer that to having wires near my legs and feet while driving.


the 40x4 display will actually be mounted in the dash and the consult plug is hidden inside the kick panel so even if i was going to use a consult plug instead of wiring into the loom, there would be no wires hanging around. it'll all be routed up through the underside of the dash. that and adding wireless to cover a 30cm gap seems like a lot of overkill to me. also, the elm327 would be pointless as its a consult interface, not obdII. completely different. i'd rather get some help to figure out how to convert the signals to be readable both ends. i don't just want to make it work, i'm also hoping to learn a little bit as i'm doing it as well.


Dec 06, 2011, 02:13 pm Last Edit: Dec 06, 2011, 02:17 pm by Rayder13 Reason: 1
Will this work or will the transistor not be able to keep up? or are there other issues i'm not seeing?


Looks good to me but suck it and see -not much to making it up on a breadboard
Governments should do what they were designed to do only.
Manage the larger issues best done by Government.
My Family and my Property are no


TX data to ECU level is 12V, idle low (see interface schematic). ECU output is
open collector and can be sourced from the interface logic level (5 V). The ECU
data output is idle high.

Thats from the info i have found on the net about the consult protocol. does that mean that i shouldn't have a 10k pull-up between the transistor and the ecu RX pin? because that would make it idle high instead of idle low like it should be yeah?


my schematic so far if anyone has any useful info to add or any problems that can be seen?

Go Up

Please enter a valid email to subscribe

Confirm your email address

We need to confirm your email address.
To complete the subscription, please click the link in the email we just sent you.

Thank you for subscribing!

via Egeo 16
Torino, 10131