1st Gen Haltech ECU Discussion

Exactly. Bypass the pnp harness altogether

 

Thanks to the Excel magic of @turbodb I am starting to compile an idea of what the stock ignition map looks like. This is a preliminary result of 3 separate drive with mixed conditions.



Gonna try to fill more of it in and get better averages

 

Is this with the FMU installed?
Or are you not going to run one?

 

No FMU for me, just gonna run 450cc injectors. This is literally just recorded output from my stock computer as I drive around though

 

Charged me less then $275 for a piggy back fic6 harness https://www.autosportwiring.com/index.html

They do stand alone harness's also.

 

I like that pricing

 

I'm assuming that's staying out of WOT/open loop? What are you reading those with?

 

It doesn't discriminate between open/closed loop, frankly that's fine because in that load cell it probably shouldn't be closed if the load is that high. This is done with high polling rate OBDII datalogging.

 

Could you expand on this? Just using an OBD2 reader and datalogging to a CSV file and filing in an excel sheet?

 

Yup, I'm using my OBDLinkSX and reading it on my tuning laptop with OBDWiz. In OBDWiz I chose the PIDs I wanted to monitor (the fewer you monitor the faster the polling rate) and literally set it to log those PIDs for the entire length of drives. Then those lists get put into the excel sheet which sorts them my RPM and LOAD % and plots the ignition degrees, obviously theres more than one ignition degree value per cell when youre recording for so long so it averages them. This give a realistic value and keeps it safe so an outlier can't make the list f'd up.

 

Hmm, you might be getting some inconsistencies on the right side and bottom of the table then. If you're feeling up to it, a standard deviation for each cell would be interesting

 

For the record, this was my tuning spreadsheet I made a long time ago for the FTC which is basically an extended version of what it looks like turbodb made you

 

This is more of an @turbodb question. I'm not an excel guru and I'm unsure if that's something that it can generate easily. I'm really concerned with normal driving range to be honest. High load low rpm whole important is pretty easy to tune and to be honest low values are expected. It needs more data and I haven't had time to drive the thing more yet. If anyone wants to try I can give them the Excel sheet. I'm just taking a bunch of rides where I drove like I usually do, a bunch of those averaged seems like it should arrive at a safe enough number

 

I guess I'm ultimately a little confused because it was you who originally told me those OBDII values were not absolute timing advance.

 

I don't know when I would have said that, it can be true of the 3RZ and 1FZ. The 5VZ has no adjustable metrics. You can even check base timing by bridging TE1 and E1 if you want to make sure. I guess in a literal sense it may not be absolute, there is drift with higher RPM. If we were talking about it with the FIC that also affects absolute timing advance cause it alters it and the computer is unaware.

 

Think you can shoot me your excel sheet? I'll log up my timing table. Not that I have time to drive my truck right now.
I can be a bit more aggressive with my timing since I'm going to use a knock sensor.

 

@treyus30

I know XL, but I'm not all that familiar with tuning, so what do you mean by showing a stdev for each cell? You just mean to show the stdev for each bucket, instead of the avg? Essentially, a second table that you'd view to see how consistent each bucket is?

 

Yup

 

Gotcha. Well, Zane, here's an updated workbook. I also threw in a table of the count of data points per bucket, just to make sure I was getting the right values for the STDEV. Note, calcing STDEV this way is very CPU intensive; took most of a minute with all 20 cores of my i7 12700 CPU pegged.

@Speedytech7

 

Gonna make my 3770k catch fire then haha