I'm hoping that someone can help me out here. I've found that this seems to be one of the most knowledgeable HalTech forums on the Internet.

Last year I thought I scored a great deal ( E-Bay ) on a used HalTech E11. Came out of a running car and seller promised to refund money if DOA... so I took a chance. Haltech is going onto a vintage 1976 Datsun 280Z ( Fuel Injected ) . BTW, I've owned RX7's before, and was looking for a clean FD LHD... but this car was too good to pass up.

Anyhoo... drove the Z for the summer and then put it away for winter. Been gathering parts for the HalTech conversion. I had no idea about the history of the V1 and V2... and just found out that HalTech has a strict " No support " policy on the V1... as they were all supposed to be returned to the factory. Seems not all of them got returned.

I'm about ready to Bench Test the ECU... but I don't have any software. I'm fearful of trying the V2 software " Online " , as I have no idea if it will work. I don't want to risk " Bricking " the ECU... and I certainly don't want to try a firmware upgrade.

Does any one have the correct software for a V1 that they can assist me with? Or can any one tell me if HalWin 1.62 will work with this ECU? PM me if you want to remain " anonymous " .

Haltech has been helpful ( as much as they could ) by informing me that he " Bugs " in the early units would probably not affect my setup. And it was working " apparently " fine on a Mercedes Inline 6 before.

I have managed to get my hands on a early V1 wiring diagram and just completed a Pin Out test with a DVM last night. Hoping some one can help out. TIA.

 

Have you asked haltech if you can run the V2 software on the V1 unit. I know back in 2005ish they had a direct upgrade program for anyone who had the v1 to upgrade to the v2 as they were going to discontinue all support to the e11v1 .

Supposedly only 100 units were sold of the V1 before releasing the V2. ( and offering the upgrade to any V1 owner) .


I used a e11v2, and worked fantastic.

To run the latest software, they strongly recommend to upgrade the firmware. I guess the issue would be if you could upgrade firmware without bricking the ecu.

Give haltech a call or email, hopefully you didnt end up with a shinnie/expensive box.

 

Just got the problem solved... only took me an all nighter. Went to bed finally at 6:00AM

My big breakthrough was that when you installed HalwIN 1.62 , it loaded PDF's with both V1 and V2 wiring diagrams ( they are different ) AND full instructions for both versions of ECU. So I was able to do a full pin-out test with my DVM and identify all of the various inputs and outputs.


BTW, I'd already contacted HalTech Australia as mentioned. The company has a strict " No support " policy for the V1, so their Techs hands are somewhat tied. . However, after much research on my own, I have found that yes indeedy, the V2 software will work on the V1. At least with HalWin 1.62.

Initially I couldn't get the E11 to come online with either HalWin 1.62 or 1.89. After MUCH research and some posted mis-information, I finally ditched the serial cable, and used a serial to USB adapter that I've used before on OBD2 dongles.

Finally got communication, and could load and save Maps. For those interested here are the settings I used. Change these in WinXP Device Manager ( COM settings ) and the Halwin settings

Com Port = 2
Baud Rate =57600 ( Must use this rate for a serial to USB adapter. Nothing else worked )
Data Bits=8
Stop Bits = 1
Parity = None
Flow Control = None

Finally got the damned thing " Online " , but with ECU Diagnostic Errors. I figured this was because the V1 was running Firmware Version 16 ( instead of 29 )

Then I had a peak at HalWin version 1.89 and found a change log PDF. In that was a single sentence that really gave me hope. In the change log it stated that : " E11-V1 detection had been eliminated " That was a huge find. That meant that earlier software versions MUST have been compatible with the E11-V1

Took the big plunge around 4:00 AM. Updated to Firmware version 29. Was fullt expecting ECU to end up " Bridked " , but at this point I had nothing to lose. Sure would have been nice if HalWin's flash program gave you the ability to backup the old .Bin file !!!! But of course they didn't.

Patience and a lot of praying was when Firmware update completed successfully, I had no more Diagnostic errors and everything seemed to work correctly.

Right now the only glitch I have is the the Quick Ignition Map settings don't want to save. They keep reverting back to defaults. This may be a bug in HalWin 1.62 or it may be linked to the fact that I'm only bench testing. I'm going to have a close look at HalWin 1.71 and browse the change logs.

Not really sure if I want to push my luck though with a second Firmware update though.....

Off to get some coffee. will post back with results.

 

Waiting for Mods to approve my reply?? Included a lot of helpful Info so I hope it didn't disappear.

Long story short. Finally got it to work on HalWin 1.62 and Firmware update B29. Lots of issues with danged COM ports though..

 

good to hear, re assigning com port is easy enough ( i think the older units liked it from 1 to 4 ).

 

Ports were easy. Baud rates and FIFO controls were the difficult parts. Mainly due to some conflicting info. Finally got seraial to USB adapter working at

Com Port = 2
Baud = 57600 ( some info said 19200, which wouldn't work with my USB adapter )
Data Bits = 8
Stop Bits = 1
Parity = None
Flow Control = None
Under advanced settings, FIFO had to be disabled. If FIFO was enabled ( which it is by default in XP ) then the connection failed.

Once I got that all figured out I could finally connect. Working fine with 1.62 and build 29 now.

 

Just an further update on this. HalWin 1.71 with build 32 Firmware also works on the E11-V1. Some added features such as Target AFR ( Sweet ) and accelerator pump GUI is now better. They cleaned up some " Bugs " in the MAP gauge as well.