Haltech Output Wire
01-13-2010 | 01:53 PM
#23
come on at 90
turn off at 89
come on at 90
turn off at 89
Which would kill your fans pretty quick.
It is something called hysteresis I *think*. (I learnt this new word from the guys at haltech)
I posted a thread on the haltech forums to see if there is a response.
01-13-2010 | 03:07 PM
#24
neat.
is there somewhere you read how to manipulate commands like that?
cant wait for an input/output box cuz then you could have all sorts of nice warning lights using that function
is there somewhere you read how to manipulate commands like that?
cant wait for an input/output box cuz then you could have all sorts of nice warning lights using that function
01-13-2010 | 08:11 PM
#25
Deanfootlong,
I had the first gen red box ECU with v1.0 of the firmware and had it setup to turn on my thermo fans via the IPDM which requires a ground trigger like that is outputed via the Haltech. This worked perfectly and was setup like the image attached allowing the fans to come on 90 and then stay on until temp dropped to 82.
I received a new silver unit with 1.06. Configured the same and had the same issue as you. The ground output was always grounded and hence my fans would come on straight away.
Not the answer you are after but hopefully puts your mind at ease as your not the only one having this issue.
I had the first gen red box ECU with v1.0 of the firmware and had it setup to turn on my thermo fans via the IPDM which requires a ground trigger like that is outputed via the Haltech. This worked perfectly and was setup like the image attached allowing the fans to come on 90 and then stay on until temp dropped to 82.
I received a new silver unit with 1.06. Configured the same and had the same issue as you. The ground output was always grounded and hence my fans would come on straight away.
Not the answer you are after but hopefully puts your mind at ease as your not the only one having this issue.
interesting. so you are still having this problem? or you resolved it somehow?
01-14-2010 | 02:46 PM
#29
I don't want to upgrade the old unit as I do not have the orginal firmware incase I wanted to downgrade it.
I will down grade the 1.06 box I have to 1.04 and test still wont be conclusive but if it works it would be a bonus.
At the end of the day we are assuming it is the firmware but it also could be the harness.
I will down grade the 1.06 box I have to 1.04 and test still wont be conclusive but if it works it would be a bonus.
At the end of the day we are assuming it is the firmware but it also could be the harness.
Last edited by MR RIZK; 01-14-2010 at 02:51 PM.
01-15-2010 | 08:22 AM
#31
01-18-2010 | 12:01 AM
#33
Results from my testing
New harness on new ECU - Constant ground
Old harness on new ECU - Constant ground
Old harness on old ECU - Works fine
New ECU = Silver box with 1.06
Old ECU = Red box with 1.00
New Harness = With O2 break out
Old Harness = Without O2 break out
So from the above the issue would lie in the firmware or the box.
New harness on new ECU - Constant ground
Old harness on new ECU - Constant ground
Old harness on old ECU - Works fine
New ECU = Silver box with 1.06
Old ECU = Red box with 1.00
New Harness = With O2 break out
Old Harness = Without O2 break out
So from the above the issue would lie in the firmware or the box.
01-18-2010 | 08:57 AM
#36
Deanfootlong:
I just pulled one of the emails we exchanged, where I loaded your map into an ecu I had on the bench. The map you supplied that was giving you trouble was 1.04, same as the firmware you were running.
If there is something going on with 1.06 I am happy to test and work on that, but first, you have a problem with your wiring configuration being that it would not work with a tested-good 1.04 map/firmware.
"I just setup the test bench with your map loaded into an ecu running 1.04 firmware. When I powered up the ECU, the output was not active - shown both in the software and verified with a continuity tester on the output to ground.
To verify the continuity test and the function of the output, I modified your map to turn the output on when RPM under 3300. After restarting the ecu to make the changes take effect - the output was active (grounded) verified both in the software and with the multimeter setup.
I have attached the modified map I used for testing.
It sounds to me as though you have something wrong with your relay/wiring setup. "
I just pulled one of the emails we exchanged, where I loaded your map into an ecu I had on the bench. The map you supplied that was giving you trouble was 1.04, same as the firmware you were running.
If there is something going on with 1.06 I am happy to test and work on that, but first, you have a problem with your wiring configuration being that it would not work with a tested-good 1.04 map/firmware.
"I just setup the test bench with your map loaded into an ecu running 1.04 firmware. When I powered up the ECU, the output was not active - shown both in the software and verified with a continuity tester on the output to ground.
To verify the continuity test and the function of the output, I modified your map to turn the output on when RPM under 3300. After restarting the ecu to make the changes take effect - the output was active (grounded) verified both in the software and with the multimeter setup.
I have attached the modified map I used for testing.
It sounds to me as though you have something wrong with your relay/wiring setup. "
01-18-2010 | 09:23 AM
#38
^ If it doesn't work with 1.04 (which we know works), there is no sense in changing to 1.06.
If you feel confident that your wiring is correct, feel free to send the unit in for inspection. Contact Ryan here at Injected Performance (859-224-0461) for shipping/inspection details.
If you feel confident that your wiring is correct, feel free to send the unit in for inspection. Contact Ryan here at Injected Performance (859-224-0461) for shipping/inspection details.
Last edited by Dynosty; 01-18-2010 at 09:25 AM.
01-18-2010 | 09:39 AM
#39
i plan on sending it to you when I swap my motor. for now it'll have to wait as its my semi-daily driver. how about the other guys problem in this thread? and suggestions for him?
01-18-2010 | 09:54 AM
#40
^ MR RIZK deals directly with Haltech Australia. While he may be on current firmware now, he is often on beta items which we do not offer support for, in that circumstance. His ECU was never distributed through us or Haltech USA, and as such, may not have comparable experiences or solutions.
Last edited by Dynosty; 01-18-2010 at 11:15 AM.