Thread: TP scale

TunerCode is a complete package that comes with all the files you need. It includes a bin file which contains the custom firmware. It also includes a TunerPro XDF file for modifying (tuning) the bin, and a TunerPro ADX file, which tells TunerPro how to talk to the ECU for data logging. It will be available soon for $100, which includes a $100 credit towards the purchase of a Calum RTV2 board.

Dave

^^^^ All I want is to get a data log with Knock as part of the data log so i can tune the timing values to the point that there its no knock mostly on turbo cars...

Even with this TunerCode you'd need a tunable ECU right. either the old fashion way with burning chip or a CalumRT ecu.

To data log Knock Sensor? Nope, a consult cable can just sit there and watch the address that you provide via Data Scan, I doubt it would do data logging though .

From the sounds of TunerCode, that might be the best $100 you can spend on an ECU. Especially if all the features will work on B14's.

I played with the TP scale a little but I couldn't really get it to act right. with how the TP dips after 5800rpm it was and is still a little wacky to tune. I moved the TP colums around it was something like 36 44 60. Then I moved it around to 44 60 65 70. I copied the fuel chart/colum from 60 and pasted them in 65 and 70. With doing this I figured I could tweek the higher TP. But this made the car inconsistant. If I did a 1st through 3rd run like i was at my 1/8 mile track the AFR would drop to 11.5:1-10.8:1. I was happy with that. But if I was to do a 4th gear only pull from 2500-6800rpms (like a Dyno run) it would be very lean. I saw numbers as high as 13.1:1 -12.9:1 AFR. So I scaled the TP in the maps back down to 44 50 55 60 and the car became much more consistant. In a drag run 1st-4th it would run in the 11.0:1 AFR and dip to 10.8:1 AFR at red line. In a dyno style run it would drop to 11.6:1 AFR and 11.0:1 AFR at redline. I'm happy with this. Some say it may still be rich but on pump 93 thats what a tunner at Dyno4mance tunes to. I dunno I'm gonna leave it for a while and work on cruising afrs now. I.m getting a nice 15.0:1 afr at 65-70mph cruising but if I'm in a hurry at 80mph my AFR stays around 16.5:1 AFR and sometime creaps up to 17.0:1 AFR. Looking up the TP colum and RPM the numbers are the same. The colum is set to 180 in both situations. Guess i'll play with it and see how it goes. I can't wait for tuner code to come out. I'm more excited about just one fuel map to tweak on.

Not what I meant Vadim

So what if you can see that it is knocking using a consult cable. If you can't tune the ECU you could only do it the old fashion way. By turning the distributer. The way I'm reading it TunerCode is for tunable ECU's not stock OEM ECUS. But maybe I'm wrong.

Ah I see what happened there, in your 4th gear, you had the load but not the RPM's. So what you need to do is adjust the lower part of the map.

This can be hard to fine tune and make sure it is "safe" in all working conditions. The way I test higher gears and lower parts of the map is, put the car in 5th gear at like 20 MPH and WOT it. Then watch the MAP trace and your A/F ratios.

Keep in mind, when data logging TP, just because your at XX amount of TP, that doesn't mean you will be in that column. Say if you are driving at 75 TP, and your scale is 70-80, you will be going in the 80 Column.

TunerCode firmware (bin) runs on stock OEM ECU hardware, provided the ECU has a programmable daughter board. This can be either a basic daughter board, with removable chips that are programmed with a prom/flash burner, like a Moates Burn1. Or it can be a real-time programmable daughter board, like a Calum RTv1 or v2. Real-time programmable means the tune can be modified while the engine is running, so changes take affect right away, or in "real-time".

Dave

yeah thats how I understood it. You either need a moates burner or a realtime ecu.


As far as tuning goes I think I've got it were I want it. Just needs a little tweaking in the middle of the map and should be fine. I understand that the Map can only have 16 colums so tuning has to be kinda in an area not just trying to mess with a single cell. Hope that makes sense. Plus some where some one said there is a tiny delay in datalogging so just cause it says that is the TP and RPM doesn't mean it's spot on