OSE 12P V112

[Holden202T]

[Six_Shooter]

Ok, so I need some clarification here.

I've been told that I can not set-up the flex tables without the use of an NVRAM. Does that mean that what I thought I did last night, didn't actually set-up the flax table?

What I did was opened Tuner Pro RT V5, opened the V111 XDF, opened one of the .cal included in the V111 .zip download, edited the MAP sensor settings, saved that .cal under a new name. I then opened the flash tool, then opened the modified cal, made all of the changes I needed to set the flex table as I wanted (KPH vs MAP for boost control), saved cal. I then modified an XDF from within the flash tool, very cool BTW, and saved it.

I was then able to open the new XDF, and cal in Tuner Pro and everything looked correct, but is it? I don't have a harness made for my test bench yet for the 1227165, otherwise I'd test it and see.

[Jayme]

yes everything is good. the .cal now has some settings saved (that are not editable in tunerpro) to tell the code which sensor / axis labels to use. the xdf has been edited to match what has been edited in the cal. the catch is, you now need to use that cal in your ostrich. if you had nvram you could open the flashtool and click upload cal. with an ostrich you need to use a .bin, which means you need to use a hex editor to insert the .cal into a full .bin, then use that.

[VL400]

As there is unlikely to be another bin using flex tables will change the flashtool to make it work with both bin and cal files.

The reason it was done with only cal support was to make it easier to handle multiple code releases that used flex tables. 12P is a special case where the cal is the first thing in the bin, so it actually does not matter if it was a cal or bin. But on other bins where the cal was shoved in the middle of code space being able to ID the file and work with only one set of offsets meant using only a cal was easier.

[Six_Shooter]

So what I did didn't actually set up the flex table? Or just that I wouldn't be able to use it in the Ostrich (or on an EEPROM)?

So this means that thus far for someone to use a flex table they would have to own an NVRAM, create a tune, and then burn the bin to an EEPROM to be able to use an EEPROM for $12P with flex tables?

It would be great to be able to set up $12P completely without needing to get another device. I mean I'm sure I'd use it, but I already have 3 Ostriches and an Auto Prom already.

Also is there any issue with conectivity using the onboard ALDL connection for logging (1227165)? Is the added logging hardware needed in the '808 simply because this circuitry doesn't exist in it?

Thanks

[antus]

The cals as read by the flashtool dont contain the program code (just the calibration portion). I think tunerpros idea of a cal might be the same as bin (and does contain the program code). Your calibration portion will be correct. If the code portion is missing, you need to concatenate it, but if it is there then your bin is ok. Without the nvram the flashtool cant upload the cal to a pcm over aldl, so getting it in there just gets a little more clumsy but it will work fine.

[Six_Shooter]

I'll have to look again, but it seemed like all of the tables (in the cal) were populated just like when I loaded a bin.

Any idea if the NVSRAM from Moates would work the same as an NVRAM module?
https://www.moates.net/nvsram-module-ki ... l?cPath=64

[Jayme]

yeah the tables are all there. a bin has 2 parts. the calibration (where all the tables are) and the code (where the brains reside) in 12P the first 7K of the bin is just the calibration (notice a cal file is only 7 kb? ) the last 25k is the code. so for the sake of small loading times when using nvram you can use just only the .cal to edit the tune and reinsert it into the nvram later. this is easy as the flashtool can upload the .cal. with your ostrich you cant just load a cal in to it and run it as there is no code, so you need to use a hex editor to copy the .cal into a .bin so that it has the code, then it will run

[Six_Shooter]

I see what you're saying now.

I can pull that off, as long as I know the starting and ending addresses, or by the sounds of it, end address.

Or wait for vl400 to update the flash tool to also work with bins. lol

I'm not going to be doing this real soon, because I need to make an adapter harness first, and that will take some time.

[VL400]

So this means that thus far for someone to use a flex table they would have to own an NVRAM, create a tune, and then burn the bin to an EEPROM to be able to use an EEPROM for $12P with flex tables?

It would be great to be able to set up $12P completely without needing to get another device. I mean I'm sure I'd use it, but I already have 3 Ostriches and an Auto Prom already.

Your actually the first person in nearly 4 years that 12P has existed to bring this subject up Will change the flashtool so it supports bins.