Basically, there's a consult library out there provided by a user named Crim - he claims it works with his arduino and an LCD screen (at least it did at one point). He's been off here for a couple of years and I'm working on something similar and trying to use his (slightly modified) library. There's also some info on the Nissan Consult interface provided by PLMS Development about address requests that return certain values.
My hardware setup is a nano running the serial LCD on pin 11, and the hardware serial is used to connect to an RS232-TTL adapter from NKC Electronics ( this one - -to-TTL-converter-board-DTE-with-Male-DB9-33V-to-5V_p_369.html ). This is connected to a consult to serial cable that I purchased from amazon a while ago.
Nissan Consult 2 Software Download
DOWNLOAD 🔥 https://urllie.com/2xYdas 🔥
The consult cable works when used with a Serial-USB adapter and a computer to access the information. I have tried numerous programs with the consult cable + serial-usb adapter and it works fine when connected this way. My issue seems to be when the arduino tries to connect to the ecu via the consult cable. The program will work fine up to the point it tries to get the part num, and it fails. It also fails on the coolant temp and RPM.
There have been a few other posts on here about this exact topic, and the ones I have found have kind of died without a resolution ever coming about (or if the problem/program was resolved, they never posted back)- so there is a chance people out there are trying the same thing or have done the same thing. I have seen videos on youtube of people using an arduino to communicate with their nissan Consult interfaced ECU, but unfortunately non of those videos post a link to source code, or the link is dead, and archive.org can't bring it back...
robtillaart - I'm pretty sure you are correct about it not actually initializing. After fiddling with it some last night, I don't think it actually looks for the correct response - it just looks for anything on the RX line. I started by plugging/unplugging the jumper wires that connected the RS232-TTL adapter to the arduino TX/RX lines and found that if I unplugged the RX line it and reset it would give the "failed to connect" message in the code. However - immediately upon connection it would say it was connected, without the TX/RX lights on either the adapter or the arduino flashing(or maybe they just flashed so fast I couldn't see it). It would then continue to say "Connected to ECU" and try to read the two programed values, but always return "could not read value" - even if I disconnected the lines. This morning I did some more fiddling and noticed that If I connected a female RS232-TTL adapter (not connected to anything else) to the male RS232-TTL adapter that is connected to the arduino, it would say it was connected to the ECU, even though it clearly isn't. Then I connected another arduino to the 2nd rs232-ttl adapter and used a software serial/hardware serial echo to send/receive the code from the consult arduino. (see pic) Using this method I confirmed that I can send junk to the consult unit (using the echo unit) and it will say that it's initialized. The info I guess I need to learn more about how this serial communication stuff works.
Like I mentioned previously, the consult cable will work with a USB-Serial adapter and my laptop. I have not been able to find any open source software for the Consult Interface. Maybe I can use a serial sniffer program on the virtual serial port to see what the PC is sending/receiving over the serial port?
So, after working on this a little more, I believe the issue is the RS232-TTL adapter not communicating correctly with the consult adapter. The way i tested this is using two adapters, one male & one female, and hooked them up to eachtother- rx to tx and tx to rx. Gave them both 5V and tried to see if it would just pass the signal from the USB adapter through - it wouldn't.
Using the other program I found I was able to get the consult adapter to work and display data correctly. Seems the previous library didn't do a good job of connecting with the ecu. the good news is that with the new program I was able to get it to interface using a RS232-TTL converter, so I will be able to use my Mega and maybe do some data logging as well as add some other features that I was wanting.
Using the other program I found I was able to get the consult adapter to work and display data correctly. Seems the previous library didn't do a good job of connecting with the ecu. the good news is that with the new program I was able to get it to interface using a RS232-TTL converter, so I will be able to use my Mega and maybe do some data logging as well as add some other features that I was wanting.
basicmods:
So, after working on this a little more, I believe the issue is the RS232-TTL adapter not communicating correctly with the consult adapter. The way i tested this is using two adapters, one male & one female, and hooked them up to eachtother- rx to tx and tx to rx.
Hi!
I want to create device like you.
Can you plz explain for what purpose did you use RS232-TTL converter ? Why do not connect uart (tx-rx) to rs232 on consult adapter ? Seems Crim didn't use any converter at all.
As far as the code that I got to work - it was some code that I borrowed from a nice member named vojta78 of nissanclub.cz; his youtube video has a link to his code. It does work with a serial arduino.
I've kind of stopped working on this project as I have a new ECU for my car (NismotronicSA) that does not support consult output (it uses the consult connection to log the data internally). There is an interface for the Nismotronic to use an external screen, however the developers do not want to release the interface protocol.
I have a Nissan consult I've used for years to diagnose issues with my 240 and TOTALLY expected to find a consult plug on the pathfinder....I can't. I have looked high and low. removed panels, pulled out switches above the fuse box on the dash, I have spent an hour outside ripping my truck apart looking for this thing and I can't find it.
Thank you. Yeah it's a bit baffling that the 1991 Pathfinder didnt have the 14 pin consult plug seeing as the nissan 240sx of that same era did. There is a 12 pin black plug in that location but I cant seem to find a 12 pin consult. I'm curious in if I would be able to get a 14 pin connector, swap it out, and use the consult... probably not. But I wonder if.
Have a Nissan car built between 1989-2000? This is the USB consult tool you need. Built strong, so it won't fall apart on you like some of those clones out there! With this essential device in your collection, easily diagnose and monitor engine performance at home - no more costly trips to an auto electrician when that check engine light flashes up again! Works with Windows systems (laptop or tablet) for easy set-up.
Product NISSAN CONSULT USB ENGINE CODE READER. The application was placed on a Nissan N14, 1.6 de, mod. 1994.
It works perfectly. I tried many apps. (ECU Talk - consult - NDS 1Data scan) . He responds very quickly and conveys a lot of information.
nissan datascan license is only $50 so meh ..worth it I reckon as you get free updates and it's actively developed I think. Has all the goodies in it so you don't need to switch between different programs. Nice logging and replay and graph functions too..pretty handy.
Q: What does this item can do and can not do?
A:Nissan counsult III has two model.MI and VI,VI is for diagnose and MI is for waveforms test.Our nissan counsult III can realize the function of VI model but can not do MI model.
I have been playing with the software for a few days now and am not having any luck getting my 2005 nissan patrol connected. i have a nisbie BT adapter ( Nisbie Bluetooth BT3V24BA to OBD) and a serial cable running an FTDI chip. both connect to other software fine but on real dash i cannot get a connection at all. my Patrol is a y61 2005 model with an OBD2 port running Consult 1. has anyone managed to get it working with this model or any pointers on things i can do?
Nissan, which was already suffering from slumping sales before the pandemic hit, said last year that it would cut about 12,500 jobs from its global workforce. On Thursday, Uchida declined to reveal if more jobs would be cut as part of the overhaul, saying that Nissan still needs to consult with unions and other stakeholders.
At Iberdrola, we want to build an electric, healthy and accessible energy model for all, which is why we are committed to global action. Here you can consult the renewable projects that we develop at Iberdrola Energa Internacional, beyond the countries where we have a direct presence through Iberdrola Espaa, Scottish Power, Avangrid, Neoenergia and Iberdrola Mxico. be457b7860
Azerbaycan Dili Test Banki Cavablari 1 Ci Hisse
VERIFIED CorelDRAW Graphics Suite 2019 Torrent
Jamie Oliver 15 Minuten Rezepte Pdf 30 firework conocidos n
Rudramadevi Movie Download In Telugu Mp4 2015l