Haltech Elite Issue
Hi guys,
Recently I started running into a weird issue with my car on the Haltech Elite 1500. Car is currently just FBO, otherwise bone stock internals.
The Haltech is reading an error code of "Trigger 1: No Home" and with the stock ECU, the car starts right up with AFR's at idle at around 15.
I\ve been on the Haltech for the past year now and this just started happening the last few weeks.
We replaced the following items so far:
- New cam sensors
- New battery
- New Walbro 255 fuel pump (Old one was also a Walbro 255)
Oddly enough, the car functioned normally for 1 day after I replaced it with the new Walbro fuel pump, drove with absolutely no issues and then a week of sitting, the problem reappeared.
If anybody has any insight, it would be hugely appreciated because I am completely stumped ..
Recently I started running into a weird issue with my car on the Haltech Elite 1500. Car is currently just FBO, otherwise bone stock internals.
The Haltech is reading an error code of "Trigger 1: No Home" and with the stock ECU, the car starts right up with AFR's at idle at around 15.
I\ve been on the Haltech for the past year now and this just started happening the last few weeks.
We replaced the following items so far:
- New cam sensors
- New battery
- New Walbro 255 fuel pump (Old one was also a Walbro 255)
Oddly enough, the car functioned normally for 1 day after I replaced it with the new Walbro fuel pump, drove with absolutely no issues and then a week of sitting, the problem reappeared.
If anybody has any insight, it would be hugely appreciated because I am completely stumped ..
NOPE. No idea. If you log whatever you usually log, and you can send to me in CSV I can take a look, definitely no promises tho.
Purely out of interest does it mean it won't start with the Haltech? IF YES, can you log the cranking to see if there is a sync?
Edit: Let me explain... OEM ECU is dumb. With standalone ECUs I can tell if it syncs aka sees all CAM/CRANK sensors. Only then, once it syncs and sees the tooth pattern.... (ready?).... will it fire injectors. This hopefully will help me, help you, determine if it's the fuel or the trigger sensor for CAM(s) or CRANK
.
Purely out of interest does it mean it won't start with the Haltech? IF YES, can you log the cranking to see if there is a sync?
Edit: Let me explain... OEM ECU is dumb. With standalone ECUs I can tell if it syncs aka sees all CAM/CRANK sensors. Only then, once it syncs and sees the tooth pattern.... (ready?).... will it fire injectors. This hopefully will help me, help you, determine if it's the fuel or the trigger sensor for CAM(s) or CRANK
.
So it doesnt start with the Haltech and it does with the OEM ECU? That tells me the issue is with the Haltech. Really that simple. If you get continuous trouble free run time with the OEM ECU, then the Haltech likely has an issue. Send the ECU to haltech and have them go through it.
So it doesnt start with the Haltech and it does with the OEM ECU? That tells me the issue is with the Haltech. Really that simple. If you get continuous trouble free run time with the OEM ECU, then the Haltech likely has an issue. Send the ECU to haltech and have them go through it.
Questions we want to know answers to are* did you check crank RPM, did you check sync state, did you check basic tune configuration, did you upload a base map designed for your injectors and try again to see if starting fresh helped?
Those are the questions we want to ask and basic troubleshooting steps we want to suggest before blaming any piece of hardware or software.
How does it help simply sending the ECU back to the manufactured? Ridiculous. At least speak with their support.
Extremely general answer. Not helpful at all.
Questions we want to know answers to are* did you check crank RPM, did you check sync state, did you check basic tune configuration, did you upload a base map designed for your injectors and try again to see if starting fresh helped?
Those are the questions we want to ask and basic troubleshooting steps we want to suggest before blaming any piece of hardware or software.
How does it help simply sending the ECU back to the manufactured? Ridiculous. At least speak with their support.
Questions we want to know answers to are* did you check crank RPM, did you check sync state, did you check basic tune configuration, did you upload a base map designed for your injectors and try again to see if starting fresh helped?
Those are the questions we want to ask and basic troubleshooting steps we want to suggest before blaming any piece of hardware or software.
How does it help simply sending the ECU back to the manufactured? Ridiculous. At least speak with their support.
There is a new DTC for P0373 and upon more googling, it seems like it might be the crank position sensor.
I will be replacing the crank sensor soon and will hope that is the cause of the issue although I recall billman stating he’s rarely seen our crank sensors fail.
The car was dyno tuned by my local tuner whos done other s2000’s with no issues as well, been driving on this tune for the past year with no issues until now.
There is a new DTC for P0373 and upon more googling, it seems like it might be the crank position sensor.
I will be replacing the crank sensor soon and will hope that is the cause of the issue although I recall billman stating he’s rarely seen our crank sensors fail.
There is a new DTC for P0373 and upon more googling, it seems like it might be the crank position sensor.
I will be replacing the crank sensor soon and will hope that is the cause of the issue although I recall billman stating he’s rarely seen our crank sensors fail.
hey mate, i had my s2000 tuned using a haltech elite 1500 and also have the same error code popping up. now mine starts up fine, albeit with a slight delay which is expected but whenever i get that error code, it wont start. i need to turn engine car off completely and then try again and then it would work.
i have also pico scoped both cam sensors and they are fine, idle control valve was checked and sorted. car was idles very rough on haltech ecu. as soon as i put the OEM ECU back in, engine starts instantly and it idles fine.
taking it back to the tuner and he is going to work on the idle issue for me but not sure what he is going to do about he intermittent problem of the error code P0373.
also i checked for error codes with the OEM ECU and no codes were found for timing or anything.
Have you had any luck since your last post? any updates?
i have also pico scoped both cam sensors and they are fine, idle control valve was checked and sorted. car was idles very rough on haltech ecu. as soon as i put the OEM ECU back in, engine starts instantly and it idles fine.
taking it back to the tuner and he is going to work on the idle issue for me but not sure what he is going to do about he intermittent problem of the error code P0373.
also i checked for error codes with the OEM ECU and no codes were found for timing or anything.
Have you had any luck since your last post? any updates?
Trending Topics
The car was dyno tuned by my local tuner whos done other s2000’s with no issues as well, been driving on this tune for the past year with no issues until now.
There is a new DTC for P0373 and upon more googling, it seems like it might be the crank position sensor.
I will be replacing the crank sensor soon and will hope that is the cause of the issue although I recall billman stating he’s rarely seen our crank sensors fail.
There is a new DTC for P0373 and upon more googling, it seems like it might be the crank position sensor.
I will be replacing the crank sensor soon and will hope that is the cause of the issue although I recall billman stating he’s rarely seen our crank sensors fail.
Thread
Thread Starter
Forum
Replies
Last Post









