C. Ludwig

iTrader: (27)

Have run across some anomalies this past week and would like to hear what the establishment has to say. Working with an early E6X. Haven't looked at the build number or firmware but it's a red case, pre internal MAP sensor.

1) We set it up in a 1st gen drag car two years ago and wired in the two-step through the spare A/D at that time. At some point since the owner removed the two step then needed it re-installed this past week. I remembered something being odd about it when I wired it the first time but I didn't make notes of the install and had to start again. My head said the red/black wire of the spare A/D needed to be grounded to activate the aux rev limit. That didn't work. With the spare A/D programmed for aux rev it would not rev past that limit whether the input was grounded or not. Called Haltech USA and asked Matt. He said ground it to activate it. I hung up and tried it again. Didn't work again...really! The next step I tried was to wire in a pull-up resistor to make sure the spare A/D input wasn't floating when the ground was removed. Didn't make a difference. Still had the aux rev limit engaged at all times. Turns out we needed to apply 5v+ to the input at all times and then open the circuit when we want to activate the aux rev limit. Just like I'd set it up two years ago but forgot about we needed to wire in a normally closed relay through the clutch switch. With the clutch pedal out the relay is closed and supplying 5v+ to the spare A/D input (red/black) and we get full revs. When the clutch pedal is pushed in the relay opens and the spare A/D in is allowed to float which activates the aux rev limit.

So why is Haltech saying to ground it when that doesn't work? Or is this particular box a freak?

2) When datalogging with the same ECU we're having issues with sporadic data feeds only on the dyno. Only thing we can think is that it's heat related. We were on the dyno last weekend and it was HOT. Datalogs would start recording data then the timer would freeze. Once you came off the throttle at the end of the run the timer would jump ahead and start counting again. When you stopped the log and viewed it the data from the time the timer stopped until it started again was missing. The chart would be filled in with a straight line to connect the data points but when scrolling across the line the numbers just weren't there. Thinking maybe it was a PC issue we tried two different laptops and both had the same problem. Went back to the dyno today and had the same issue.

Now where it's weird is that at the track on Wednesday and Friday we datalogged all night with no issues. Only thing I can think is that the ECU sits on the firewall right behind the downpipe. At the track there is actually some air moving through the car to cool things off a bit and not so much on the dyno. But the ECU functions perfectly on the dyno and if it were going to be a heat issue effecting the processor I would think it would effect engine performance and not just logging performance.

Thoughts?

3) Just playing around I tried to view some datalogs taken with the 1.26 software on the 1.71 software. The numbers just didn't jive. We were shifting at about 9000 rpm and that showed correctly on the 1.26 viewer and the 1.62 viewer. But when those same logs were pulled up with the 1.71 software it was showing the shift points at about 8000 rpm. I haven't logged anything with 1.71 yet but have two cars to work on in the next couple weeks and was wondering if I should expect the same results with data logged through the 1.71 software?

Claudio_Haltech

Ok, i know Haltech tells people to ground the Spare A/D wire to use it as activation for things like NOS or Antilag, but in the manual it only states to use the Aux In wire. And from what i have seen of the E6X functionality, the Spare A/D wire is a 0-5V input were it will read anything 0-5V, if you ground the wire, theres no voltage going through it. Try the Aux. In wire to do the activation, i know that works putting it to ground.

What i think is the way the Spare A/D works is like how you say, if it has 5V it will work as on/off when set to that, and with no voltage (or ground) it will sit at what ever the internal programing of the firmware is set to.

On the datalog issue, i think that may be something when you're on the dyno and on the track, temperatures will be cooler from air flow and weather conditions, and we all know high temperatures make any computer of any kind perform lousy.

And finally, on the datalog viewer, the E6X is totally different than the E8/E11, and i am under the impression that the viewer for each ECU only reads the files from each ECU, so i would assume you'd get funky readings from using the wrong viewer. But dont quote me on that, cause a CSV file is just a file with data in it, and the viewer is supposed to just display each channel logged in the file, but im not 100% on this.

There is a guy on the Oz951 Haltech forum that came up with a simplified datalog viewer for Haltech CSV files, you might wanna give it a try, it works pretty good.

Here's a link to that thread: http://www.oz951.com/halforum/bbs/viewtopic.php?t=376

Is that E6X red box with old lable or new lable?

C. Ludwig

iTrader: (27)

The Aux In does not support Aux RPM (two-step) as an option that it will control. That would of been the first input I would of liked to have used but it's not an option.

My thoughts on the datalog file viewer was like you said. A .csv file should be a .csv file. The 1.62 version (E8/11) reads the same numbers as the 1.26 (E6X). But there are a couple options (not terribly productive options, but options none the less) in the 1.62 that aren't available in the 1.26. Only reason I tried the files on the 1.71 is to see if there were some more options available in the newer software. Guess the reason I asked the question was to see if anyone had worked with the 1.71 software yet and is there an inherent problem with the logging software?

I sent Haltech Aus an email about these issues and will post back here with what they say. I'll get a build number and firmware number for it.

I'll check out the log viewer. Thanks for the link. I acutally don't use the Haltech log viewer much. I load the .csv files into Excel and work with them there. Allows me to convert the numbers to imperial measurments which I am more comfortable with and I personally like seeing the numbers more than looking at the graphs. Anyway... whatever works right?

I'll check the box next time we're messing with the car. I'd guess it's the old label. The box is probably almost three years old.

Claudio_Haltech

Well here's the thing, Aux. RPM Limit isnt among the Aux. Inputs features, its on the Spare A/D, it should be in both, but Haltech never put it in there, as a matter of fact, i just noticed that the Gas Compensation Option in the X software, which is supposed to be for LGP applications, clearly says in the Main Setup window "always on" an "use Aux. In", if you go to the Aux. In features, Gas compensation isnt there, its in the Spare A/D, these a few of the quirks that Haltech probably didnt get around to fixing in these versions of software (its the same in v1.25 and 1.26).

What i understand from your comments is that you want to use both the Aux. RPM Limit AND the Antilag feature together is that correct?

What i would suggest you try is the Anti-Lag on its own, basically by retarding the ignition enough the revs wont go as high and you will build boost quickly.

But i understand your line of thought.

C. Ludwig

iTrader: (27)

Not really interested in using the anti-lag. I've used that and understand how it works and how to engage it. Just was mainly asking if anyone else has enabled the Aux Rev Limit through the Spare A/D and why Matt is telling me to ground it when that obviously isn't the way to make it functional.

crispeed

I have notting positive to add to this thread!
Claudio knows my opinion of the E6X software both dos and windows versions.
It starts with P and ends with S.
Sometimes I wonder if the X was pre S or K.

C. Ludwig

iTrader: (27)

So true. But it has dual maps.