Haltech Trouble with HalwinV_1.89....
#1
Trouble with HalwinV_1.89....
Hey guys, I need some help with my E11v2. I have finally completed my new build and just installed the haltech E11v2 and am haveing problems loading a map. I had the great experience of having to find an old laptop so I would be able to go online with the ecu, and now once I am online I cannot load a map. I have the 1.89 version with the build 35 firmware. Everything else seems fine but when I try to load a map it gives me an Error report wich says this....
HalwinV1.89 exe. has encountered a problem and needs to close. We are sorry for the inconvenience.
If you were in the middle of something the information you were working on might be lost.
Please tell Microsoft about this problem.
We have created an eerror report that you can send to us. We will treat this report as confidential and anonymous.
I have searched the forums and found some info on loading maps or updating firmware inproperly, but nothing I find helps me. Any ideas are apreciated...
Thanks
HalwinV1.89 exe. has encountered a problem and needs to close. We are sorry for the inconvenience.
If you were in the middle of something the information you were working on might be lost.
Please tell Microsoft about this problem.
We have created an eerror report that you can send to us. We will treat this report as confidential and anonymous.
I have searched the forums and found some info on loading maps or updating firmware inproperly, but nothing I find helps me. Any ideas are apreciated...
Thanks
#2
Try unistalling the 1.89 you have and reload a new copy from the Haltech website. If that doesn't work try loading in the build 32 firm ware, and then reload the build 35 firm ware, but use new copies from the Haltech website.
#4
I'm having a similar issue myself. I just got my e11 wired. Once I went online with the ecu, it said I had the ver 1.62 already installed. I had already previously downloaded the latest 1.89 on my lap top a few months back so I could familarize myself with the software. I went on ahead input all my settings to configure the ecu. Every now and then I would still get the same program error message that needs to be shut down. I was always able to re-start halwin to finish resetting up the computer. Do I need to download the older 1.62 w29 firmware and start upgrading the ecu back up to 1.89 or just keep the build 35 firmware that I already have and load it into the ecu?
#5
Well I searched some more and found one of Claud threads about proper firmware updating. It turns out that I only originally downloaded the 1.89 software but never downloaded the build 35 firware that goes with it. Do I have to install build 32 b4 install build 35. Or can I just install build 35 and call it a day?
#6
Well I uploaded the build 35 firmware last night and the programming is working much better. No more software errors and such. Now I still have to figure out my no spark problem.
#7
Reloading the firmware worked for me, but only after reloading it straight to my old laptop that I am using strictly for my haltech from haltechs website. In the past I had loaded the software onto my office computer wich is windows XP, copying it to a disc then loading it to my laptop wich is windows 98. I am thinking this is were my problem came from. After I figured out a way to get my old laptop online I downloaded the software and firmware again but this time it went straight to the laptop, did not go from one OS to another, now it works great!
Trending Topics
#8
Reloading the firmware worked for me, but only after reloading it straight to my old laptop that I am using strictly for my haltech from haltechs website. In the past I had loaded the software onto my office computer wich is windows XP, copying it to a disc then loading it to my laptop wich is windows 98. I am thinking this is were my problem came from. After I figured out a way to get my old laptop online I downloaded the software and firmware again but this time it went straight to the laptop, did not go from one OS to another, now it works great!
Yea updating the firmware helped me with my software glitches.
Now as for my no spark issues, I just figured that out too. It turned out that I was too heavily relying on the set-up diagrams in the tip and set-up page. Those diagrams are biased to the Psport ecu's. I have an E11 w/milispec harness. I'm using the Fd trigger set-up with my NA 20b. I wired the two green ground wires to my triggers as per the diagram. Well on my E11, those two green wires are not connected based on the Haltech web site diagram. ClaudioRx7 made a comment on that post that the older ecu's wouldn't have those wires and that we would have to use the two blue wires for ground. At the time I didn't comprehend what he ment so I fallowed his diagram instead. No spark. So now I rewired the trigger wires using the blue wires for gorund and now I have spark. Hopefully today after recharging my battery, I can do the 1st start. Wish me luck.
#10
Yea updating the firmware helped me with my software glitches.
Now as for my no spark issues, I just figured that out too. It turned out that I was too heavily relying on the set-up diagrams in the tip and set-up page. Those diagrams are biased to the Psport ecu's. I have an E11 w/milispec harness. I'm using the Fd trigger set-up with my NA 20b. I wired the two green ground wires to my triggers as per the diagram. Well on my E11, those two green wires are not connected based on the Haltech web site diagram. ClaudioRx7 made a comment on that post that the older ecu's wouldn't have those wires and that we would have to use the two blue wires for ground. At the time I didn't comprehend what he ment so I fallowed his diagram instead. No spark. So now I rewired the trigger wires using the blue wires for gorund and now I have spark. Hopefully today after recharging my battery, I can do the 1st start. Wish me luck.
Now as for my no spark issues, I just figured that out too. It turned out that I was too heavily relying on the set-up diagrams in the tip and set-up page. Those diagrams are biased to the Psport ecu's. I have an E11 w/milispec harness. I'm using the Fd trigger set-up with my NA 20b. I wired the two green ground wires to my triggers as per the diagram. Well on my E11, those two green wires are not connected based on the Haltech web site diagram. ClaudioRx7 made a comment on that post that the older ecu's wouldn't have those wires and that we would have to use the two blue wires for ground. At the time I didn't comprehend what he ment so I fallowed his diagram instead. No spark. So now I rewired the trigger wires using the blue wires for gorund and now I have spark. Hopefully today after recharging my battery, I can do the 1st start. Wish me luck.
Thread
Thread Starter
Forum
Replies
Last Post
FC3S Timmy
2nd Generation Specific (1986-1992)
16
10-03-15 01:08 AM
Red-Dragon_Akuma
New Member RX-7 Technical
11
09-28-15 06:09 AM