2003 VQ's with Haltech
 

Hey guys,

Just tryin to get a read on the number of people with 2003 G/Z's that are using a Haltech and have no problems using firmware 1.04 or later.

I've read a few posts from other 2003 users that have/had electrical problems. I just want to confirm that the vast majority of the 2003 users dont have any problems with the new firmware.

I'm hoping my firmware issues are really just isolated to my box, not a general model year.

Thanks!

I have 2003 but didnt update my box since i got it over a year ago. i want to but not sure about the benefits of it.

so you are still on V1.0? V1.06 has soo m anymore features. plus you can always go back to 1.0 if you want.

That would be sweet if you could load it and see how it runs...

Bump. Any answers regarding the original post?

Had issues with firmware over 1.04 not 1.04 itself. The idling went all over the place.... using MAF and not MAP to tune. :)

I dont have any issues with version 1.04. I'm upgrading to version 1.07 next week and I'll report back with any issues

you map with MAF or MAP? Would be interesting to see if you get the same issues that I did.

1.07 was giving me issues i downloaded 1.06 and works good.

any reason why u wouldnt go with a f-con? never heard of problems with them i dont think...

there is no 1.07 firmware :dunno: only 1.07 ECU manager software. 2 different things.

I'm talking about the firmware thats flashed on the Haltech. I wonder if alot of people think that just because you are loading the latest ECU manager that it is also updating the Haltech firmware. Its not...

There is no problem using Haltech 350Z EMS On 2003 350Z.
In this one case of str8dum1, there is obviously something going on and we are digging into his specific ecu currently. If anyone else is experiencing problems, I urge you to contact me so we can get them resolved. http://www.injectedperformance.com/h...ress_image.gif

To clear up any confusion on current software and firmware:
Software: Current version is 1.07.2 (autosave bug, details below)
Firmware: Current version is 1.06.1 (stable)

The current version of software 1.07.2 is having an autosave problem with some ECUs, including ecus beyond the 350Z line. Symptoms: The software will lock up upon connecting to the ecu. Haltech is aware and working to get the next release of software out asap with that autosave bug fixed. If anyone is having problems with 1.07.2, go back to 1.06.

1.06 is available on our site, www.injectedperformance.com/haltech

Thanks Hal! Hopefully if anyone is having problems they get up with Hal. Cant progress this EMS unless there's full disclosure feedback :thumbup:

Well, my haltech should be back today. Hal found no problems with my original one but shipped a new one just in case. Didnt get a response about the AUX input turning on when the key was at "ACC" so hopefully the new box fixes that.

Will update later today, hopefully with all good news

Well, zero change with the new box.

A map used in V1.0 firmware runs fine while the exact same map but upgraded for 1.06.1 will not hold rpm.

Also, the aux output still grounds out in the ACC position.
Here are the 3 vids to show what I am experiencing.

The 1st is V1.0 firmware. Then I reflashed the ECU with V1.06.1 using the same map, tried to repeat the same steps as in the 1st video. If the car wasnt misfiring it was running around 13:1 AF, but the missing obviously is causing overly rich readings because unburned fuel is dumping out the exhaust.

The 3rd vid is just a demo of the AUX out grounding.

Hopefully Hal can come up with a solution ASAP.
Vid 1, Firmware 1.0
http://www.youtube.com/watch?v=xiyRYpGIlzY

Vid 2 Firmware 1.06.1
http://www.youtube.com/watch?v=2uma8vUQ448

Vid3: Aux output grounding in the ACC position
http://www.youtube.com/watch?v=xsEb7UBmd9w

The solution is the same as I told you before we swapped ecus out. Use a different map.

It is either a problem specific to your vehicle (which I can not explain without further diagnostics), or a problem with your map.

That is so weird. Are you sure everything is the same between the two maps used with the different firmwares? Same firing angles, etc.? You can export individual tables as 2D grids into excel and then reimport them. I'd use a completely generic base map from Hal and then paste your fueling tables back into it and see if it fixes the problem... Perhaps there is a hidden setting that is screwed up in the 1.06 map that you are using.

In regards to the aux output, my meth system doesn't get any power until the car is running, so I'd never have even noticed it... My aux is set up as a failsafe anyway and cuts boost solenoid output, so maybe it's a glitch but one that's easily overcome so long as it works while the car is running, right?

ya I just made a new map using the 106 base map. The original map was a 104 backbone. Cant test til the morning though.

In terms of the maps, they are the same as they can be by hitting the 'upgrade' button between firmware flashes.

When I tried to copy the grids, it only would let me paste tham as bitmaps into excel...?:dunno:

The aux output is easy enough to fix as I can just pwer the trigger relay with my fuel pump 12V since thats only on when the car is on. But that just begs the issue, what's going on....

to copy the cells just highlight all the cells in table and control-c then control-v into excel. Assume this is what rcdash means as I just tested it and it works. Just make sure your X and Y axis are correct before pasting in.

With the AUX the easiest would be to disconnect the POS connector and test with a multimeter as this will rule out your current meth setup (even though u state it works with the Utec). I would also test with different different AUX triggers in the software ie: Just a simple test with RPM or TPS while using the multimeter. No fancy AND or OR statements. Just one trigger. Make sure when all the triggers are disabled in the software it is not grounding either.

My assumption is that the AUX has nothing to do with the oem engine harness as there is no oem dependency for it to work (besides the signals from OEM to Haltech). So if it grounds when unplugged then I would assume there is fault either in the haltech, map or the haltech harness. Working around the problem does not solve the problem.

HAL might be able to provide a better way to test this though.

ya it grounds in the ACC position without the aux out being checked 'on' in the software. IE, i dont even have it setup to use( all disabled) . I've checked with a MM, and it grounds the wire coming off the weather pack connector.

Well at this point, there doesnt seem to be much more that Haltech USA can do short of seeing the car in person. I have changed maps, like was suggested, and rebuilt a new map from the V1.06 350Z basemap. No change.

There are still some parameters such as dwell time etc that have not been changed from stock, but other maps I have seen, seem to leave those alone. :dunno:

I guess the current course of action is to get it drivable with V1.0, get to the tuner, and go from there. :(