Autoprom suddenly not found by TunerPro

**sbnova** · 4 Weeks Ago

I was using TunerProRT yesterday morning to datalog while on my way to work. I got to work and reviewed my log and planned some changes. This morning I open TunerProRT so I can connect to the Autoprom and upload my new .bin, and I cannot get TunerPro to recognize that the autoprom is connected.

I have verified the com port (COM3) in the device manager and in tunerpro. When I attach the cable my laptop make a chime, indicating that it knows a cable or device is attached and/or detached.

Via searching my laptop, I found that windows updated on the 25th, and installed those updates on the 26th.... which is when my problem started. So I uninstalled those updates. No change.

I read that the autoprom has drivers, but I dont remember ever installing them, and moates web site is long gone to search for them. Can anyone verify the need for a specific driver for an autoprom? I did go to the FTDI website and downloaded and installed their drivers, and windows says my drivers are up to date.

I even tried a new cable from my laptop to the autoprom, no change.
Ive rebooted my computer countless times, no change.

Its killing me that this whole setup has been working flawlessly until suddenly today!!!!

Please help!!!

**TriumphR3** · 4 Weeks Ago

It’s a long shot but, Might try a previous version of Tunerpro.

**sbnova** · 4 Weeks Ago

This is REALLY FRUSTRATING!!!
I deleted and reinstalled TunerProRT (V5, same version, but I thought maybe a new/clean copy might make a difference), no change

Then I remembered my '94 Tahoe has a functioning Moates Ostrich attached to its ECM. I cant connect to that either!!!

Hardware not found.....

**boba** · 3 Weeks Ago

I'm no windows expert, but check user permissions on your comm port and make sure it hasn't been changed to admin access, also baud rate on the port.

**sbnova** · 3 Weeks Ago

I was looking into permissions, but I didn’t know there were permissions on com ports.
A friend of mine has tunerpro installed on his laptop and he connected to the same autoprom, so the problem is clearly my laptop