I have my haltech all wired up, but the ECU Manager cannot connect to the ECU.

The USB-UART driver cannot take COM 3 because its taken on my compy, I tried COM 6, COM 2, and COM10 in both direct connect to that com, auto detect, with the key in the run position and with the key out.

Anything I can do?

I hear the haltech turn on, it primes the fuel, so I don't think its the wiring harness.

 

I tried this with a different computer, no go.

If I recall correctly the UART settings were

9600 baud
0 Parity bits
1 Stop Bit

 

Anybody??

Anything I can do/try?

 

Ok, here are somethings you can try.

The first one i am going to recommend is this, take your ECU out of the car, or if you have WiFi and can go online with your lappy while you have your Haltech Platinum box connected to the USB cable (it doesnt have to be powered up), then open your internet explorer, click Tools/Windows Update, go into Windows Update and select the custom update options, let Windows check your machine and suggest updates. Pay close attention to the "Suggested Hardware Updates", with your Haltech ECU connected it should detect the UART hardware and suggest an updated driver for it, if it does download and install it. After this, try to connect again. If you are running Windows Vista, it might not offer a newer driver, this fix is mainly for XP. The latest driver version that works with XP is 4.80.1.0, i think in Vista its a 4.40.x.x.

After you do this step, go into your Device Manager, and set the following Port Settings:

Bits Per Second: 57600
Data Bits: 8
Parity: None
Stop Bits: 1
Flow Control: None

And lets say for argument sake you select COM2 as your port, and in ECU manager, dont use Auto Detect and manually select that same COM2, after you do this the first time you wont have to change that, since it will always shoot to com2 when ever you reconnect the USB cable.

Try to go online again, if it still wont go online, and without turning the power off, or closing ECU Manager, simply disconnect the USB cable, you'll hear a blip from windows when you do (make sure your volume is on and high enough), then reconnect the cable (you'll hear another blip) and then try to go online again. Sometimes you have to try going online 2 or 3 times.

If it still wont go online, turn the power off on the car, disconnect the USB cable, restart the laptop, after it restarts, do these steps in this order:

Restart laptop
Reconnect USB cable to laptop and ECU
Start ECU Manager
Turn ECU ON (power on the car)
Then try going online again.

Let me know of all this helps or not.

 

I will try this out and report back.

Thanks.

 

Okay, I downloaded the new driver. It came up as 5.4.0.0 released 12/10/2008. The one on the update website listed it as 4.80.1.0 like you had.

I went through and tried all of your suggestions, still no dice. I tried unplugging and plugging in the Haltech maybe 20 times and no go.

 

Ah! interesting, i just did the Windows update my self and see what youre talking about, there is a new driver on there, my setup works, so i am a little reluctant to update to this one, in have 4.80.1.0 right now.

I will try to find the 4.80.1.0 so i can reinstall it just in case and then test this new one.

 

Ok, well I outsmarted myself. I went to the manufacturer of the USB-UART chip and downloaded the drivers from there. And now windows won't load the drivers correctly.

The plus side of this is that i have wanted to reinstall windows for some time now. Hopefully I will get done with that tonight.

Do you have a separate installer for the 4.80.1.0 driver?

 

Ive found this thread about this issue:

http://www.cygnal.org/ubb/Forum9/HTML/001782.html

I cant find the 4.80 driver online anywhere, only 5.xx versions. The versions of ECU manager before 1.03 came with 4.40 driver, i think 1.03 comes with 4.80, if it comes with 4.40 only, i suggest you stick with that version and try to get it working.

 

If you have the 4.80 driver, you can post that up and I can install it manually.

 

I dont, i just got it through windows update a few months back when ECU Manager v1.02 was out.

 

I mean, you do have it on your computer. Try plugging in a haltech platinum and seeing if you can find the location of the driver from the device properties of that driver. If you can find the location of the driver file on your computer you can get the driver itself.

 

Is this what you want me to get you? I think its gotta be more files than that.

 

Ok, i think i found what you need, there is a folder inside the ECU Manager folder within the Program Files called USB Driver Installer, ive taken that entire folder and zipped it for you, so do the following having your Psport ECU disconnected from the laptop/usb cable.

1. Take YOUR USB Driver Installer folder, copy it to your My Documents so you can go back to it in case something goes wrong.
2. Subsitute your entire folder with THIS ONE
3. Restart your machine
4. Go to the Device Manager and into the Port for your CP210 controller, hit UPDATE DRIVER and let windows try to find it on its own, if it doesnt, manually go into your new USB driver folder you put into the Haltech folder under program files and look for the driver there.
5. Reconnect your Psport ECU, if it asks you to look for the driver say yes and let it search again.
6. After its done, check to see what version of the driver you have under the device manager, you should have 4.80.

My final suggestion is to completely uninstall ECU manager and the CP210 drivers. Reinstall ECU Manager and if it installs driver 4.40 stick with that one, dont try to update, and go through my initial suggestions on trying to get it to connect. Oh! and i almost forgot, there were 2 instances where the USB cable Haltech provided were no good, get a couple cables and try that out too, you never know, but in the end, if you can see the CP210 UART controller on the device manager the cable should be ok, if you cant, then yes, there's a problem with that, but id try different cables, just in case.

I had a tough time the first time around trying to connect to 2 Psport units but eventually i got it to work.

 

Ok, I have a fresh install of XP, I will grab two spare cables and try this out either tomorrow night or Saturday.

Thanks again, Cladio. I will post up my results as soon as I get them.

 

Still no go, the driver in the folder wouldn't update and I had to install in manually. It still came up as 4.4 after installing it though, any chance you uploaded the wrong folder? The readme file of the uploaded folder confirms its 4.40

BTW, here is an interesting tidbit on the drivers. It seems other people have issues with the new 5.X driver and SIlabs wont give out the old 4.X drivers.
http://www.everythingusb.com/forums/...threadid=16116

 

As the thread i posted earlier stated, the 4.xx versions upto 4.80 where developed by that other company, not SilLabs, so i am honestly out out of solutions for you. My 4.80 driver came from the microsoft update page, i can guarantee you that, but if they updated to this new 5.xx version in recent months i dont know what to tell you.

I guess that driver folder i put up has the original install program files and not the actual drivers which may be in the windows folder but i dont know which files would be needed.

Sorry i cant be of more help. Try and contact the support guys at Haltech Oz, support@haltech.com, see if they can shed some light on the situation you're experiencing.

 

To add closure to this thread, member moremazda ripped into the wiring harness and found that the ground wire that connects to the ECU power relay was severed near the connector end.

This clearly would cause no power to flow to the ECU creating the no connection issue.

 

Geez! its ALWAYS something you never expect it to be. Did you guys notice if it was a manufacturing defect or something got pulled inside the harness, or what? We never did discuss "was the ECU powering up?" did we, serves us right damn it! Im gonig to go bang my head a few times as punishment. How do you put the little emoticon banging its head on the brick wall?

 

I am not really sure if it was a manufacturing problem, I didn't get to see it personally. This connection problem has been one annoyance in a series of many, so it was the straw that broke my back if you will.

Moremazda picked up the car and went through it all.

To get the head bash you have to hit 'more' on the smilies window.

 

Yeah, it was a pain to have to deal with it, but the problem was something else entirely, ECU wasnt even turning on, it was never going to communicate. The reason i say that is cause this sort of thing happens often, you get someone that thinks they have a specific problem (no comms) and they stay focused on that and not try to find out whats the cause of that. Its partly my fault, after your 10th post about not being able to connect i should've thought about those things, i always ask people to tell me if their ECU is powered up before any of this.

 

No big deal. It was probably missed since the fuel pump was priming. It wasn't until moremazda said 'the priming doesn't ever stop, that's a problem' is when I thought outside of a communication problem.

After that I was able to guess at a power problem since the unit wasn't stopping the priming sequence.

Besides, you were probably the most helpful. The haltech support people told me that 'if its hooked up it should work'. Great....

And moremazda contacted Chris Ludwig over the phone and said he was extremely helpful as well, which I would believe.

 

Hell yea, Ludwig is a badass.... I just hate having to wait 2-4 weeks for a backordered item (basically the MAIN thing holding my swap back... a friggen clutch/flywheel ) before I get to toss my Haltech in.