Haltech E8/E11 features not working in 1.71 and 1.82B, boost control anyone, poss fix inside
E8/E11 features not working in 1.71 and 1.82B, boost control anyone, poss fix inside
I have been troubleshooting an issue with the closed loop boost control and also the wastgate map not working on my E8, for a while.
On the phone with haltech, also reading other posts on this forum you will see that I am not the only one.
Today I downgraded to halwin 1.62 with B29 firware But this wasn't the fix. With the wastgate map as the limus test this **** still didn't work (wasn't willing to put in the work necessary to test the close loop boost control).
So I upgraded back to 1.82B using the proper sequence, but just before I loaded my map (which I have been using with 1.82, previously with 1.71, and before that with 1.62...) after I loaded the default e8 map.
I tried the wastgate map, and holy **** it worked. keyed on then key off and its still working.
Ok so next rather than load my own map I load the haltech 2 rotor base map.
Guess, what its dead again... Back to the default map, and it works..
Next up I tried the 4cyl seq map, dead again.
You get the picture..
There is something faulty in how the haltech maps are FWD's compatible.
So the long term proper fix would seem to be recreating the map by transferring the values into halwin loaded with the default map.
Havn't tried it yet, but I'm itching to do so.
the next question, WHO IS TO SAY WHAT OTHER FEATURES MIGHT BE AFFECTED BY THIS BUG
On the phone with haltech, also reading other posts on this forum you will see that I am not the only one.
Today I downgraded to halwin 1.62 with B29 firware But this wasn't the fix. With the wastgate map as the limus test this **** still didn't work (wasn't willing to put in the work necessary to test the close loop boost control).
So I upgraded back to 1.82B using the proper sequence, but just before I loaded my map (which I have been using with 1.82, previously with 1.71, and before that with 1.62...) after I loaded the default e8 map.
I tried the wastgate map, and holy **** it worked. keyed on then key off and its still working.
Ok so next rather than load my own map I load the haltech 2 rotor base map.
Guess, what its dead again... Back to the default map, and it works..
Next up I tried the 4cyl seq map, dead again.
You get the picture..
There is something faulty in how the haltech maps are FWD's compatible.
So the long term proper fix would seem to be recreating the map by transferring the values into halwin loaded with the default map.
Havn't tried it yet, but I'm itching to do so.
the next question, WHO IS TO SAY WHAT OTHER FEATURES MIGHT BE AFFECTED BY THIS BUG
Ok, here's the lowdown. Load your DEFAULT base map onto the ECU, the base map for v1.82 or even 1.71, depending on what version of software you are using. Also! very important! disconect your coils/ignition components when you do this!
Then you'll have to open another window of halwin offline and load your old map onto that, and basically copy/paste all your settings onto the online program and your ECU, once you're done SAVE THAT MAP! and you'll be fine.
Also! those STANDARD maps in the halwin software are so old its ridiculous, dont use them, they need to be updated, they've been past on from version to version without being properly updated.
So do that and you should be ok.
Then you'll have to open another window of halwin offline and load your old map onto that, and basically copy/paste all your settings onto the online program and your ECU, once you're done SAVE THAT MAP! and you'll be fine.
Also! those STANDARD maps in the halwin software are so old its ridiculous, dont use them, they need to be updated, they've been past on from version to version without being properly updated.
So do that and you should be ok.
my most obvious issue would be demonstrated by configuring an output as the wastgate output, then going to the wastegate map, highlighting all bars and moving them up.
The output as seen in the aux outs data page would go to 100% regardless of where it should be.
If you didn't start with a default map, I would say using claudio's copy procedure would be a safe bet.
After all who knows what other features this issue could effect
The output as seen in the aux outs data page would go to 100% regardless of where it should be.
If you didn't start with a default map, I would say using claudio's copy procedure would be a safe bet.
After all who knows what other features this issue could effect
This is exactly the issue we were having. In the datalog and trace the pwm output was just pegged at 100% duty. Are you saying that starting with a fresh base map fixed that?
Starting from the Default map approriate to the haltech version you are running will fix it.
Do not use any of the maps in the haltech base maps folder, use either default or Default_E8 depending on what you've got.
To demonstrate the fix, save your current map, then load the base map configure an output as the wastgate output, then going to the wastegate map, highlighting all bars and moving them up to about 50%.
It only took about an hour at most to move all the settings over going screen by screen.
Don't forget to check or reconfigure all sensors.
Do not use any of the maps in the haltech base maps folder, use either default or Default_E8 depending on what you've got.
To demonstrate the fix, save your current map, then load the base map configure an output as the wastgate output, then going to the wastegate map, highlighting all bars and moving them up to about 50%.
It only took about an hour at most to move all the settings over going screen by screen.
Don't forget to check or reconfigure all sensors.
I don't know if this is related, but.. I had problems loading a map into 1.71 that was originally created in 1.62; the throttle pumps were WAY off. I finally loaded the 1.62 map into 1.71 in the offline status, then saved it. then went online and reloaded the 1.71 version and the throttle maps were ok.
Trending Topics
This is because there was a dramitic change to how the throttle pumps work between 1.62 and 1.71.
I doubt if its a related problem.
I doubt if its a related problem.
I don't know if this is related, but.. I had problems loading a map into 1.71 that was originally created in 1.62; the throttle pumps were WAY off. I finally loaded the 1.62 map into 1.71 in the offline status, then saved it. then went online and reloaded the 1.71 version and the throttle maps were ok.
ok, then why did the throttle maps get all screwed up if i tried to import the 1.62 map directly into 1.71 while online
but if i imported off line in 1.71 then saved it... then whent on line with 1.71 and loaded the map it was ok even with the changes in the throttle pump U/I
Thread
Thread Starter
Forum
Replies
Last Post



