Thread: ECUTalk and NissDataScan help

OK, so I've got a NissDataScan CONSULT module from Australia, and I've got an old laptop onto which I've loaded ECUTalk (hey, it's free). I'm having problems getting the Consult module to communicate properly with the computer.

So, I'm trying to find out in what sequence I should be turning things on. Here's what I've got:

Laptop (connected to NissDataScan via a serial cable, which I assume is COM1 in the software)
ECUtalk software
Car with Consult module (NissDataScan)
RS232 mode in Consult module.

What I did was connect the cable, turn on the computer (so it would recognize the connection, I hope), fire up the car, and switch the DataScan to RS232. At this point, the ECUTalk software told me that the connection had failed and it would try again in five seconds. Did this repeatedly. I have tried other COM ports in the software with no success. I also tried re-starting the computer, thinking that maybe the car/Consult reader had to be active to be recognized by the computer, but it didn't work.

I feel like this should be a simple thing, but I can't figure it out - unless the ECUTalk just won't work with the NissDataScan module.

Any help GREATLY appreciated.

You need to install a usb to serial driver I think. It comes usuallly on the datasacan disk. Tipically it uses Com5 port iirc.

I'm not using a serial-to-USB port. This laptop is 5-6 years old and has a serial port, so I'm just hooking the DataScan in that way.

Configured the serial baud rate correctly? 9600 AFAIK.... Also make sure you know definitely which COM port it is so there's no guessing there - find out!

i believe you have to turn the car on and then open the software. that is with datascan though, so im not sure about ecutalk. also which cable did you get? mine is the plms one and it has three leds on the black box on the cable to tell you when the connection is made and when it is transferring data.

OK, lets start from what SW you are actually trying to use.. what EXACTLY is the "Datascan you switched to RS232" and the "NissDataScan module" you refer to later???

As far as I KNOW, NissDatascan is a SW program supplied by BlaZt for a fee, that does work with a Consult cable.

ECUTalk is .. exactly the same thing.. a program that interfaces the Consult calbe and .etc., etc.

I am not sure but from your description, it sounds like you are connecting the Consult cable to the laptop, RUN the Datascan program which obviously connects to the cable in COM1 and "blocks" other programs from accessing COM1 and then.. you are running ECUTalk and trying to also connect to COM1????

YOu can only have ONE program accessing COM1 (or COMwhatever) at any time.

What I do without failure is:

1. Turn computer ON.
2. Connect cable to Consult port (this may be done prior to 1 as well).
3. Turn KEY to ON (not engine, just KEY-ON) and run ECUTalk or any other program (like Datascan, FreeConZult, whatever)...

At this point it should connect automatically, or after searching all COMx ports or by manually assigning COM1 to the program (whichever this may be).

Hey Kent,

So did you say you got the ECUTalk running on your laptop...or did you want me to help you get it working?

-saaby

It's running, it was a loose wire that's been re-soldered now. What I'd like is help setting up and using the datalogging function.

according to what you said you are using two different logging software at the same time ...hmmm