Description Our USB Consult cable allows you to connect your computer to your Z32 for use with various diagnostics and tuning applications. Based on the FTDI interface, it is compatible with practically all major CONSULT-based software, such as Nissan Datascan, ConZult, ECUTalk, Nistune, Nissan Data Voice, and it uses the standard FTDIChip drivers one would use for the BlaZt or PLMS cables. We have specifically engineered this cable to provide the most consistent, reliable connection, so it can be used with realtime tuning software like Nistune, and it has been tested across multiple Z32 ECUs and chassis, so even the fussiest cars will have no problems connecting. Please note: As with all Consult cables, you will need to install the device driver software prior to plugging in and using the cable on your computer. These drivers can be downloaded.

Jul 3, 2010 - Generally all Nissan Consult interface cables should work with all Consult. The steps for actually using the cable and software (see next section). Laptop usb or serial port (or for Pocket PC, into null-modem adaptor or blaZt.

Hello everyone, like many people I'm relatively new to arduino - done several tutorials a couple of my own projects (fan controller for my car, an alarm clock, servo control stuff - just random stuff like that ) but I'm having some issues with my current project and hoping maybe someone can offer some insight to why things aren't working like I think they should. I'm not sure if my problem is software library stuff (which I admit I don't totally understand). 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. The link to his library is: The link(s) to the PLMS info is: http://www.plmsdevelopments.com/diy_consult.htm.

It is using off the shelf software (ECUTalk, Conzult, a couple others). If one of these programs were open source maybe I could decipher how to read/write from the ECU, but I can't find any that are. As for programming on the PC - i have zero experience with most PC programming, especially when it comes to hardware input/output. The arduino is actually a little easier for me, since I did have a C+ class back in college.

I'm not good by any means, but at least part of the time I can understand the code. Programmu bust digits for pc. 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. Tamil songs bgm download. Someone out there has done this successfully, I just need to find who.

Any help anyone can give would be awesome. I'm even willing to donate some $$ for some help. Time isn't cheap, and for someone who isn't interested to look through libraries, code, and protocol to figure out why it's not working and how I can make it work is a lot to ask. 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.