Unnable to log/wont connect to ecu

bobbymorgan425 · **Joined:** Fri Jan 19, 2007 11:51 am **Posts:** 9

gabedude wrote:

bigdweeb wrote:

hrm... have you gone through Device Manager to make sure no other serial ports or modems are also trying to use the same COM port that logger software is trying to talk to the cable on?

If you can't change it through the Device Manager, I would think you can change it through your registry with regedit. I can't guarantee any changes to registry will work and you should proceed with caution. Make a backup through regedit if you are going to try this.

As I said I don't have a cable, but I am basing this off a generic USB to Serial converter as I would think it would be similar. When you have the cable plugged in, you should see what port it is using somewhere in registry, I think in HKEY_LOCAL_MACHINE->HARDWARE->DEVICEMAP. I believe this is a read-only value... changing it didn't change the port settings for my usb converter.

Once you know what port the cable is working on, you can search for that string, in my case COM4.

You should find the actual configuration for the device somewhere further down in the registry. In my case it was in
HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Enum
Under there I found a subfolder for my cable. If you expand it out you should find a folder called Device Parameters, and in there you should find a key called PortName. You can try changing that value to the port the logger is trying to connect to and plug it in. If you check
HKEY_LOCAL_MACHINE->HARDWARE->DEVICEMAP
it should show the port you just changed the cable to.

Making this change may not be reflected in Device Manager though. There was another string somewhere in the Enum subfolder called FriendlyName that seems to control that but I wasn't able to change it.

That worked for me on different hardware, YMMV

Do not do this. I am a driver developer. Trust me, you can F things up easy in that section of the registry.

You can go into Device Manager after you have the tactrix plugged in. Underneath the ports section you should see an entry for the tactrix virtual com port. You can change the port # there if there is a conflict. Try COM4, COM6, whatever. Mine shows as COM6 and it works fine. I am on Vista however. This driver is what is used to log, it is almost the same thing as a USB to Serial converter under the hood. They can be problematic at times, but you can get around it. You can also disable any modems you do not use or any built in serial ports in the bios to free up resources.

-Gabe

I was able to get it to work !!!
I had 1 and 3 in use, so I just set up 3 for the tactrix cable and presto
it works fine......

gabedude · **Posted:** Fri Jun 01, 2007 9:25 am

kascade wrote:

Just to clarify things, the logger is not at fault here. It is a problem with your Ecuflash drivers installation. I replicated the problem on my laptop and the fix was to uninstall ALL tactrix/openport/ftdi related drivers, uninstall ecuflash, delete ecuflash directory, reboot, reinstall ecuflash and drivers, plug in cable, point the popup to the correct ecuflash drivers directory and follow prompts (may have to do this twice), open RomRaider and logger and should now see the new com port.

I used EcuFlash 1.30.

Yeah the FTDI driver installer seems a bit wacked at times. You can also do a manual reinstall without having to uninstall ecuflash.

Hand driver reinstall option:

Delete the correct *.inf (there may be more than one) from Windows\inf directory (you will have to find the one containing the text "FTDIBUS.INF")

In Device Manager, remove the tactrix device listed under "Ports" and "Universal Serial Bus controllers).

Unplug cable.
Plug in cable.
Windows will ask for new driver (it may ask you twice as there are several .sys and .dll (driver) files that get installed).
Point windows to C:\Program Files\OpenECU\EcuFlash\drivers\x86

Driver should install correctly. Driver installers are often written so badly that micorosft has devloped their own driver installer (DIFXApp). FTDI does not use this driver installer.
-Gabe

kascade · **Posted:** Fri Jun 01, 2007 5:15 pm

Hi Gabe, I tried doing what you suggested but when I plug the cable in it is only recognized as a USB device, no port is added under Ports in device manager. I do notice that an item "Openport USB driver" appears in the Add/Remove programs list. It doesn't appear there when the cable is recognized as a COM port. Any idea how to get it recognized as a port as well? I assume something is screwed with the FTDI drivers.

thrlskr · **Joined:** Sun Mar 11, 2007 5:21 pm **Posts:** 8

kascade wrote:

Just to clarify things, the logger is not at fault here. It is a problem with your Ecuflash drivers installation. I replicated the problem on my laptop and the fix was to uninstall ALL tactrix/openport/ftdi related drivers, uninstall ecuflash, delete ecuflash directory, reboot, reinstall ecuflash and drivers, plug in cable, point the popup to the correct ecuflash drivers directory and follow prompts (may have to do this twice), open RomRaider and logger and should now see the new com port.

I used EcuFlash 1.30.

I'm having the same problem as the original poster; however, I don't know how to follow the above instructions. I followed the above instructions except I don't know where to delete the ecuflash directory. This must be an important step because I still couldn't get RomRaider logger to talk to my ecu.

I can however log with logworks2 and flash with ecuflash, so I think the problem is with RomRaider.

thrlskr · **Joined:** Sun Mar 11, 2007 5:21 pm **Posts:** 8

thrlskr wrote:

kascade wrote:

Just to clarify things, the logger is not at fault here. It is a problem with your Ecuflash drivers installation. I replicated the problem on my laptop and the fix was to uninstall ALL tactrix/openport/ftdi related drivers, uninstall ecuflash, delete ecuflash directory, reboot, reinstall ecuflash and drivers, plug in cable, point the popup to the correct ecuflash drivers directory and follow prompts (may have to do this twice), open RomRaider and logger and should now see the new com port.

I used EcuFlash 1.30.

I'm having the same problem as the original poster; however, I don't know how to follow the above instructions. I followed the above instructions except I don't know where to delete the ecuflash directory. This must be an important step because I still couldn't get RomRaider logger to talk to my ecu.

I can however log with logworks2 and flash with ecuflash, so I think the problem is with RomRaider.

Any ideas or help?

kascade · **Posted:** Tue Jun 26, 2007 3:52 am

the ecuflash dir is usually in c:\program files\openecu\ecuflash

i can't guarantee that the above method will work however it did for me at the time.

e-rue · **Joined:** Fri Oct 13, 2006 3:32 pm **Posts:** 15

if you are unable to get your machine to connct to the ECU to datalog and all you see is com3 listed in the pull down, then you have probably not installed the driver for the cable. i made the same mistake when i got a new computer. the driver for the cable is uncluded in ECU flash but not included in RomRaider. once you download ECUflash and install the driver for the cable, just restart the datalogger and it will automatically show up as the correct com# in the pull down depending on which USB port you have the cable plugged into. if you use a different port next time you will probably have to install the driver a second time for the additional port.

e

RomRaider

Forum rules

Unnable to log/wont connect to ecu

Who is online