![]() |
vERSION V1.89 any comments?
I was wondering if anybody has used the new build and software. I most interested in the auto tune application. Any thoughts or experiences? Any suggestions?
Aldo |
Not on the Auto Tune thing but I've had issues with consistency of the boost controller. Plus the car I was working on had a random hiccup for no reason while under load.
B |
Golden!!
The auto tune doesn't work for me but I am not running the Haltech default RPM ranges. And I thought I have seen a couple mentions that the default settings need to be used if the auto tune is to work properly. On issue with the boost controler that I had was when I loaded in my 1.71 map the "time before boost control" setting was up at 60 sec when the range is 0-10 sec and I got really bad boost oscillation. Just setting it back to zero fixed that problem. |
Originally Posted by moremazda
(Post 8622681)
Golden!!
The auto tune doesn't work for me but I am not running the Haltech default RPM ranges. And I thought I have seen a couple mentions that the default settings need to be used if the auto tune is to work properly. |
I am in the process of figuring out how to make the boost control work right now. hehe.
|
You probably have to make the autotune map have the same rpm ranges as the fuel maps for it to work.
Regarding the boost control issue, try starting from scratch with the default map and bring all your settings over. |
Originally Posted by slo
(Post 8622884)
You probably have to make the autotune map have the same rpm ranges as the fuel maps for it to work.
Regarding the boost control issue, try starting from scratch with the default map and bring all your settings over. |
auto tune
where is that setting that displays 0 -15500? Which range are you guys using?
Aldo |
Originally Posted by 13B-RX3
(Post 8622697)
Any of the default ranges or the 0-15500 default range? That would explain why the autotune doesn't work for me.
I'll give that a try and see what happens. |
Autotune does not work for me.
Hooking up the A/D1 to the wideband displays properly but has incorrect mv readings on datalogging laptop or ecu. Otherwise works just like 1.71 with a few options I will use. EGT and a/f ratio's now datalogged via laptop. Ian |
Originally Posted by IAN
(Post 8625169)
Autotune does not work for me.
Hooking up the A/D1 to the wideband displays properly but has incorrect mv readings on datalogging laptop or ecu. Otherwise works just like 1.71 with a few options I will use. EGT and a/f ratio's now datalogged via laptop. Ian If you open up the Data Page for the Analog inputs, you will also see AFR displayed as the units assigned. |
why does haltech release products/software that has non-functional "features"
|
Originally Posted by jacobcartmill
(Post 8628610)
why does haltech release products/software that has non-functional "features"
|
Originally Posted by Claudio RX-7
(Post 8627871)
Although i have not checked autotune yet, i know for a fact that 1.89 does display AFR correctly in the datalogs, the CSV file, the datalog viewer and of course the software screen, i have verified this.
If you open up the Data Page for the Analog inputs, you will also see AFR displayed as the units assigned. Attempted another firmware update and closed loop worked but I moved the wideband back to a/d2. Did not bother to see if a/d1 datalogged properly. And I will not bother again since my ecu and connectors is under the carpet where the stock ecu was. |
So I changed the load points in the target AFR map to match the fuel map and the quick tune feature still doesn't work for me.
|
Here's my list of issues. Has anyone noticed the same ones?
1. O2 Feedback works off and on (no its not the settings, after a reset its not working) 2. RPM cells change after saving (I have to update them before running car each time, yes they were locked, I have tried saving online offline different maps nothing works) 3. Logs are in mv but don't match WBo2 Output or any lambda/afr scale (13:1 =.4 mv) 4. Sensor Calibration Tables all call out EGT at the top of all the sensor windows (bright side the units come in correctly psi=fuel pressure, F=egt) 5. Data view logger does not come up when opening log (intermittently happening) 6. Automatic Generation of Firing never works correctly for Seq/Dir Rotary I have started over 2 times with maps and software in order to make sure it was not a bad install. I am going to do it again for the 3rd time today to see if it works again. |
Originally Posted by fritts
(Post 8630824)
Here's my list of issues. Has anyone noticed the same ones?
1. O2 Feedback works off and on (no its not the settings, after a reset its not working) 2. RPM cells change after saving (I have to update them before running car each time, yes they were locked, I have tried saving online offline different maps nothing works) 3. Logs are in mv but don't match WBo2 Output or any lambda/afr scale (13:1 =.4 mv) 4. Sensor Calibration Tables all call out EGT at the top of all the sensor windows (bright side the units come in correctly psi=fuel pressure, F=egt) 5. Data view logger does not come up when opening log (intermittently happening) 6. Automatic Generation of Firing never works correctly for Seq/Dir Rotary I have started over 2 times with maps and software in order to make sure it was not a bad install. I am going to do it again for the 3rd time today to see if it works again. 2. I had issues before on this. The problem I found is that you cannot just click on each cell and type in the rpm range you want and then save. You have to hit enter after each data point entry then it should save into each cell then save the file. 3. I have the same problem. 4? 5. I have datalogging problems all the time. Especially onboard ecu. Sometimes it just freezes or just plan does not display correctly. Datalogging more then 180secs seems to freeze the datalog screen when you zoom into it. (You cannot go back and see the rest of the datalog. It just plain dissappears.) Haltech more or less said operator error or just plan windows vista issues along with old age com port to new usb adapter issues. It probable has alot to do with processor vista garbage. 6? I also have unintentional firing off of the A/C circuit. The output to the clutch coil inconsitantly without reason pulls in. Could be the way its wired or some strange electrical gremlin. But its wired the same way as my old E6K system and that worked flawlessly. Note:My issues does not garantee unit is a problem child. It can be be anything. |
7. Datalogs that don't use the default Haltech format don't get saved
|
Originally Posted by fritts
(Post 8630824)
6. Automatic Generation of Firing never works correctly for Seq/Dir Rotary
|
Main Setup-- Auto Generate Firing Angles
After setting everything else it has never given me the correct firing 1, 0 2, 180 |
That doesnt make sense. What does it do when you hit autogenerate angles?
|
A lot of stuff this software does doesn't make sense...
When I set it to rotary/Seq/Direct fire and hit auto generate I get this 1, 0 3, 540 4, 0 2, 0 |
My dear Fritts, you are not supposed to use that sort of firing order when dealing with a rotary. And if you have set your engine like that you are certainly not going to get to run correctly.
The firing order on a 2 rotor 13B is: 1st Rotor to Fire : 1 = 0 degrees 2nd Rotor to Fire : 2 = 180 degrees Configuring to Direct fire (when using Rotary mode) tells the ECU to fire each rotor alternatively 180 degrees from each other, with the ignition split for the trailing plugs. As we all know, each leading plug fires together every 180 degrees, with the corresponding rotor's trailing plug firing at the split angle indicated. Even though you are connecting each individual Ign output to an individual coil, the firing strategy remains the same. The benefit of firing them in a "Direct Fire" manner is that the charge time on each individual output can be configured individually, were as in a "Wasted Spark" setup, where you're firing a single dual coil for both plugs, the current necessary for obtaining the same power in the spark needs be split between the 2 towers, requiring a higher charge time. If this has been the way you've got it setup all along then im sorry to say its completely wrong. |
Quicktune does not work on the E8 ecu due to no Spare AD1.
Future firmware/software upgrade will fix that. Most of the other problems I see being reported above I have not experienced with the latest firm/software. Boost control, O2 correction, wideband logging in afr's etc. just to name a few all function perfectly for me.
Originally Posted by TweakGames
(Post 8628691)
It will be more profitable for them to spend the time on their new ECU so they can sell more and start the cycle over again.
It's comming time with all the advanced features Haltech is providing that factory hands on TRAINING would be required for reliable use. Makes no sence releasing all these features to the general public of which many still don't have the experience just in general tuning much less the experience for advanced fetaure use. Simply providing instructions in an owners manual will not cut it. If it was that simple then we all would be able to fly planes just from reading a manual. For example where in the manual 'gear boost correction' is explained in detail? Something that I have firgured out on my own since it's release in the 1.62 version. I keep hearing about the same old problems or difficulty in getting certain features to function properly. Prime example would be 'Closed Loop Boost Control'. Again the general instructions given in the manual does not touch base with it's capability or provide any trouble shooting suggestions. I know of one particular setting that is not covered that would solve many of the instability problems in boost control that people have. |
I'm not stupid I'm not trying to fire the engine that way that is what automatically generate angles sets. I then go in and change it to 1,0 2,180. I would think though that the program should be smart enough to set the correct angles/firing order.
Originally Posted by Claudio RX-7
(Post 8632274)
My dear Fritts, you are not supposed to use that sort of firing order when dealing with a rotary. And if you have set your engine like that you are certainly not going to get to run correctly.
The firing order on a 2 rotor 13B is: 1st Rotor to Fire : 1 = 0 degrees 2nd Rotor to Fire : 2 = 180 degrees Configuring to Direct fire (when using Rotary mode) tells the ECU to fire each rotor alternatively 180 degrees from each other, with the ignition split for the trailing plugs. As we all know, each leading plug fires together every 180 degrees, with the corresponding rotor's trailing plug firing at the split angle indicated. Even though you are connecting each individual Ign output to an individual coil, the firing strategy remains the same. The benefit of firing them in a "Direct Fire" manner is that the charge time on each individual output can be configured individually, were as in a "Wasted Spark" setup, where you're firing a single dual coil for both plugs, the current necessary for obtaining the same power in the spark needs be split between the 2 towers, requiring a higher charge time. If this has been the way you've got it setup all along then im sorry to say its completely wrong. |
| All times are GMT -5. The time now is 08:01 AM. |
© 2026 MH Sub I, LLC dba Internet Brands