Consult/ECUtalk, etc - 94 Q45t

[Warspite]

Looks like I hit a brick wall (fortunately, NOT with the G50)...

Check Engine light is on solid, slight shake during idle, and when in gear, a severe pulsing from front right brake.

So, I pulled out the infamous serial ODB adapter, and tried to read the error codes, to no avail. ECUtalk (v1.3.3) doesn't communicate with the device (default is COM1), and eFormance Consult detects the device, can "talk" to two registers, but errors out (unable to initialize ECU during auto-scan).

Now, SOMETHING must be talking to the ECU, since I was able to clear the airbag flashing light, which came on after I switched programs. Even tried ConZult (yea, it's for the 300ZX, but when I bought the ODB/Serial adapter, it came with the unit...), but alas, this didn't initialize the ECU either.

Does anyone use these aftermarket Consult-wannabees with any success?

Or, is my ECU simply toast, and hope that there is Wes Special NICO-ECU for a 94 G50....with 228K mikes...

[goody90q45]

Are you using a serial port or USB port cable?

[Warspite]

I have the serial port adapter. Flasing green LED when connected to ODB connector in fuse panel.

Comm settings:9600 8 bit, 1 stop bit. (default settings).

Of course USB would have been better....

[goody90q45]

I had problems with the first USB consult cable I got from Blazt, sent it back, and they returned a newer version with a MTDI (?) chip which worked fine. Same problem- always searching to connect to the ECU and the invalid COM port message.

It sounds like you have a consult cable with a serial port connection that you've converted with an adapter to USB? IIRC, the original serial port connection was the most reliable but now you'd need to own an older, slower laptop.

[Warspite]

Believe it or not, it's a true Serial version, with NO USB adapter. The laptop is about 2 years old, with the typical 16550 UART for a serial port. I've even tried slowing down the interface from 9600 to 4800 BPs, with the same results.

It would be nice to know what error codes are being logged before I have the poor beast limp into T3 for diagnosis.

There's a steady idle on the tach (no difficulty or hesitation starting up), but a shake in the vehicle, which could be a number of things (misfire, coil pack, injector, you name it). Dash indicator reads OK, then goes to Odometer. No strange noises from the engine, though.

I hope that ODB-1 is more intuitive than my 1978 Buick Regal was. Years ago, I made it to the off-ramp on the Long Island Expressway (The Nation's longest parking lot), where I threw a rod, and white smoke came out from under the hood. Then, and only then, did the Check Engine light come on. So, I did what the light said to do. I then proceded to open the hood, and was greeted by my oil filter rolling onto my shoe!

I hope that won't be the case here!

[goody90q45]

did you try chamging COM ports? I think I'm running on COM4.

[Warspite]

It's a Dell laptop, which is generous with the USB ports, but only 1 serial port. It defaults to Com1 (and no other one would be recognized).

[goody90q45]

I'm no computer expert and my son helped me with the setup of my consult cable. You wil default to COM1 but there is a way to go into the program files and change the setting for ECUtalk to a different COM port and then go into SETUP in the program itself and change the COM port to match. The serial port connection normally has the least connection issues so changing the COM port may help.

Hopefully someone here with a lot more computer knowledge than me can guide you through the steps. Good luck

[maxnix]

If you only have one serial port, chances are it is COM0.

[Warspite]

Unfortunately, only the Registers are in Hex (which start with 0 and end in FF, which means 255).

COM ports actually use conventional numbering scheme.

I guess I needed to know if anyone else on this forum has success with the legacy Serial version of the Consult (PC) adapter, would a USB adapter work with this unit? Amazing that even with smooth-sounding idle, there is a serious shake, and still I get an OK off the odometer, as if nothing is wrong!

In the past, I had T-3 install the Blue performance struts, so now I can't even bounce the car to determine where the intermittant "crunch" sound comes from. I'd just rather show up there with a list of error codes in hand (if I could not take care of them myself...).

[Infinitiguy19]

The diagnostic information screen only helps to diagnose the electrical transmission problems, low washer fluid and other listed in the FSM.

Is the Check engine light on?

I have a cable for sale from E-mance if you want it.

[Warspite]

Naturally, Check Engine light is on, since Murphy's Law has yet to be repealed.

Is your cable USB to ODB connector, or is it serial?

I just might try the infamous Serial-to-USB connection, and see if it picks up the Consult wannabe as a new hardware device.

Thanx, Paul!

[Infinitiguy19]

Mine is serial, But I bought a serial to USB 6 foot adapter.

[Warspite]

SInce the green LED on the Consult adapter IS on, it does get power from SOMEWHERE. I'll try the serial to USB adapter method first.

It's great that someone has been down this road before.

[Infinitiguy19]

Did you try another program? how about OBD scan tech Nissan?

[qsiguy]

I've never had any trouble connecting to my car with either serial or USB. I have a couple different options to connect and it almost always works. I have tried a couple ECU's that would not connect and have tried it on other peoples cars without success. I had a 94T model for a while and it would never connect. I also tried pulling the ECU from that car and connecting to my turbo and still was not able to connect to that ECU. For some reason some cars/ECU's don't want to connect. Doesn't seem to be any rhyme or reason I can narrow down.

BTW, I've used Calumsult, ECUTalk, Nissan Data Scan, OBD Scantech Nissan and have been able to connect with them all. I prefer ECUTalk to most. I also have the ECUTalk V2 digital display/consult unit. Works great as well.

Sorry not to have any answers to help you.