Connecting to ECU is "Hanging", aka not connecting

[Devestater147]

Hey Everyone!

I'm using Nissan DataScan 1 v1.63 on a ThinkPad T590 laptop running Windows 10 Pro 64x and using ECUTalk's Consult 1 to USB adapter to connect to my 1992 Nissan Sentra SE-R.

I recently upgraded from my old laptop, and can no longer use the old one. The previous laptop worked fine, but now i'm having some difficulty with my new laptop. Nisscan has been activated but whenever i press connect nisscan takes forever, and doesn't connect to the ECU at all. I've let it sit for an hour, but the progress bar will just stay stagnate with one blue bar. When i go to settings, press "find ECU" nisscan will say completed.

I've looked in Windows device manager and confirmed the right com port (4), matched the speed of the port as well at 9600. All the USB drivers are up to date. I even downloaded and installed current drivers from FTDI's website per ECUtalk's FAQ. Though i didn't uninstall the previous drivers, not that i think that was necessary.

I guess i am at a loss and am looking for some help to remedy this issue. IDK if this is operator error, a setting in the software, or the cable is bad.

Let me know what you all think i should do.

Cheers.

[Tom]

Under Settings->Communication disable the Auto option next to the COM Port setting. This way the software will not try any other Com Ports and fail immediately if there are any issues.

In your Windows Device Manager, what is the Device Status for your adaptor's Com Port?

[Devestater147]

Thanks Tom for reaching out.

NDS com port was on 3, but the auto was checked. The port speed was at 2600, and i changed it to 9600 to match the device manager settings. IDK if the port speed matters, but i figured making them match is better than if they were different.

Here are some links to some screenshots of what you asked about:

• Windows Device Manger:
https://gyazo.com/80aedb61fd87fa711373b19bd3038b50

• Ports General Setting Tab:
https://gyazo.com/424e076b7601b8a13f25fc331cb75ff9

• Port Settings Tab:
https://gyazo.com/e768b109556d7ab5865b75d17442cc7f

• NDS Communication Setting Tab:
https://gyazo.com/9beb665c90bb82c45796d07c945e4f7d

I'm currently not by my car to test after adjusting the settings, but I'll report back regardless.

Let me know if this looks good.

Cheers.

[bignycatx]

One day I got lazy and didn't want to move my laptop close to my car so I used a USB extender cable but could never get the ECU to connect. It works fine without the extended cable though. Are you using a extended or long cable?

[Devestater147]

BUMP...

Hey everyone,

Apologies for the long absence. Life got in the way, but I'm back in the garage and wrenching on my '92 SE-R. Recently tackled the head gasket, and the car's running/driving great. However, I'm still banging my head against the wall trying to connect to the ECU with NDS1.

Like i mentioned before, using a newer laptop running Windows 10 Pro, x64 OS, and Processor, and only using the ecutalk consult cable, no extensions. I'm wondering if the lack of an x86 instruction set on my t590 thinkpad might be causing issues with NDS1. I've done the usual troubleshooting—uninstalled NDS1 with Revo Uninstaller, reinstalled it, uninstalled the ECU talk cable drivers, reinstalled those too, prompted windows to start NDS1 in Windows CP SP3 compatibility mode and run as administrator—but no luck so far.

Do I need to dig up an old T40 Thinkpad that has an x86 or x86_64 instruction set to get NDS1 to work properly? I feel like it's something simple, but I'm just stuck and frustrated at this point.

Any advice would be greatly appreciated.