GROUP BUY: USB CONSULT!

[slipnfall]

Andy: sorry you have having troubles. Just as a quick response, it does sound like the cable is working properly, otherwise that battery voltage you receive back would just be all over the place, if stable at all. If you can return a signal from the ECU that reports correctly, and responds to stimuli (for lack of better terms), then at least the software and connection to the PC is OK. There may still be an outstanding board problem that permits you from connecting from the engine ECU. What year and model? Hopefully Robert can chime in on that ECU part number, along with his results.

[3Q Jay]

The previous owner did have to have the ECU replaced. Could a newer ECU cause this problem? The numbers on my ECU are A18-A32 PO2, 0207, and a large 05.

Andy

My parts book says that ECU is for a 90 california model. onteresting, since the date code is from 1992 (might support statement that it was replaced under warranty). still, the a18-a(xx)-xxx units have the different board that *should* not require additional pull-up on the data tx line.

seems to be only the a18-Bxx-xxx units that usually don't work (hopefully still a temporary condition )

[lino]

Do you have a pic of the original Ian Calum board?

What is an " original Ian Calum board"

[elwesso]

What is an " original Ian Calum board"

The serial interface one.

[lino]

Thank you sir.

[Q451990]

My parts book says that ECU is for a 90 california model. onteresting, since the date code is from 1992 (might support statement that it was replaced under warranty).

Many ECUs and TCUs were replaced with remanufactured transmissions... usually they have a "Remanufactured" sticker on the ECU though.

Heath

[ponzy]

how's the beta OBD? has it been available now in q45.org? pls email me a copy of the beta version on OBD scan, if you dont mind. ponzyq45 at yahoo dot com. thanks a lot heath........

[mxr662]

Andy: sorry you have having troubles. Just as a quick response, it does sound like the cable is working properly, otherwise that battery voltage you receive back would just be all over the place, if stable at all. If you can return a signal from the ECU that reports correctly, and responds to stimuli (for lack of better terms), then at least the software and connection to the PC is OK.

My parts book says that ECU is for a 90 California model. interesting, since the date code is from 1992 (might support statement that it was replaced under warranty). still, the a18-a(xx)-xxx units have the different board that *should* not require additional pull-up on the data tx line.

Ok, so what is the procedure to connect the cable to the car? Key on then connect cable or Key off, connect cable then turn key on? Key on or motor running? Maybe I need to do this differently. I have tried different combinations. I have never got the interior lights to flash off and on when connecting.

[Q451990]

I have never got the interior lights to flash off and on when connecting.

I didn't know they were supposed to... mine haven't. I think I usually just have the car running, then plug it in. Sometimes I plug it in first. I have unplugged it and plugged it in while running... I don't think it matters that much.

Heath

[mxr662]

Anyone have any tips to get this connected to the ECU. Most of my under plenum parts came in and would like to get this connected for a baseline reading before I R+R the plenum.

[3Q Jay]

UPDATE: I got a '90 ECU for $10, and plugged it in. returned the 60u00 p/n straight away. reads all the parametrs available. so, yeah, there are definitely differences in the ECUs.

edit: didn't answer your question, Andy. not sure it's a big swinger, but i connect the usb a-b and the board first, then the consult connector, launch the software, but sometimes get nothing with key on engine off. engine on takes care of that part (with the early ECU).

[3Q Jay]

Heath- did ya get the power balance working? i'm dying to try it.

[Q451990]

Heath- did ya get the power balance working? i'm dying to try it.

We're not getting particularly good results with it. I think the ECU is trying to compensate for the cylinder drop... The programmer is still working on it. I have another beta to test today. We'll see where that gets us.

Heath

[slipnfall]

Guys I haven't forgot about you: I'm hoping Robert will be able to chime in with some suggestions, particularly those with the 94-95 TCS/Actives. In regards to the proper way to connect, it shouldn't matter really: I would suggest connecting the cables before starting the car. This prevents any possible arcing upon contact at the terminals.

[maxnix]

So I am a little confused.

Is it a requirement that certain drivers have to loaded for the board and chip on the NICO cable? Or will the WinXP SP2 drivers suffice?

[slipnfall]

Yes in fact the drivers should be installed *before* the USB cable is connected for the first time. This sets the system up to automatically use the new drivers.

[Q45tech]

In the Consult reading the ecu model number is part of the PROCESS in deciding how to further communicate with ecu.

The Consult III comes with a Panasonic tough book for a reason to avoid driver differences between operating systems and and USB interfaces.

Even the old Consult I has 2 different modes to test things: ACTIVE and FUNCTION............plus various lockout to be sure the coolant was 174F or 10 minutes had gone by before the override was possible.

Not all these tests were built into ecu, some were developed later than 1989 and were created in the Consult software..........commanding the ecu to turn off automatic idle speed mainteance and automatic ignition advance control.

[Q451990]

Not all these tests were built into ecu, some were developed later than 1989 and were created in the Consult software..........commanding the ecu to turn off automatic idle speed mainteance and automatic ignition advance control.

Any idea how the software does this? Can you tell me what the software would need to lock to make the power balance results valid? I'm assuming IAC/AAC opening, and some other things... maybe injector pulse width, timing advanvce?

Heath

[mxr662]

Any idea how the software does this? Can you tell me what the software would need to lock to make the power balance results valid? I'm assuming IAC/AAC opening, and some other things... maybe injector pulse width, timing advanvce?

Heath

I'd be happy if I could get it to read the trouble codes

[mxr662]

I'd be happy if I could get it to read the trouble codes

Gave it one more try and it works.

-Connected all cables-Key off-Booted Computer-Started software-Started Car -Connected

Andy

[Q451990]

-Connected

Whooo hoo! Bet you're reading codes too

[PopPop]

Whooo hoo! Bet you're reading codes too

Here's a reman unit!

[qsiguy]

.....Thanks again to everyone. Please visit http://consult.hackthebox.org for important install instructions and required device drivers.

Mac users: I don't have a dedicated install guide for you, but just email me and I'll let you know where to find drivers.

What's up with the site? Seems to be a dead link? Just down for the time being or what?

[qsiguy]

Setup question. I followed your instructions and the cable has been found. Trouble I'm having is that it assigned COM11 and if I try and change it the computer says COM3-COM10 are in use but I don't know what for. In Datascan you don't have the option of entering COM11 to use. Looks like it's only single digit COM ports.

Any ideas?

[slipnfall]

Re: the website... it's hosted on a buddy's cable modem, so it is likely just down for upgrades or something. If there's drivers or something you need, feel free to email me.

As far as the COM ports go: what OS are you running?

[3Q Jay]

i sent Robert a '94 TCS unit to play with and see if there's a fix.

[qsiguy]

...As far as the COM ports go: what OS are you running?

Windows XP Home

[qsiguy]

I got it worked out and working. I tried the demo of Datascan and it works fine. I swapped my '93 NICO ECU with my stock '94 ECU and it works fine as well. Am I the first? Anyway, with my '94 the ECU part number that shows up on Datascan is 23710-68U12. Can't remember which number showed up for my '93 NICO ECU but it was different.

Now I need to buy the full version of Datascan.

As far as the com port issue, I just manually changed it to com9. It said it was in use and complained but I did it anyway and it worked fine. It was probably just previously used for a cell phone connection or something.

[qsiguy]

ECU Talk also connected to my '94 ECU. I was able to reset my knock trouble code and read all the gauges. Here's a screenshot. My O2 gauges are all over the place. I need to get this car figured out. Knock code popped back on shortly again.

1994 Q45 stock ECU

Here's a screenshot of the Datascan demo gauges. I purchased the full version with the logger but haven't got it yet. Guess they will send me a registration # or something.

1993 NICO Stage 1 ECU

[slipnfall]

I'm glad you got it worked out: were you able to change the port setting of the cable?