OSE 12P V112

[Holden202T]

fixed thanks!

[ToyHicko]

Just letting you know I was just looking at the bins supplied in the zip file for V1.10 and notice that the V6 is still version 1.05. Not a big issue but thought I'd like to know.

[VL400]

Thanks, it was something that was found awhile back and meant to fix .. better do that! Its a field thats not used for any code detection so doesnt break anything but is confusing if your using TP to check the cal.

[blownvp]

hi hows everyone.just wondering if its possible to add n alpha tps only no map sensor to the ose 12p for people running multiple throttle bodies.cheers darren.

[VL400]

I will check it out, there are a few ways it can be done but really the only way that would be possible (due to having only 23 free bytes of calibration space) would be to substitute the MAP load variable with a TPS load variable. There is however some code that may work for your setup .. PIS Firmware . Am pretty sure this can do alpha-n (it def does alpha-n blending).

[vn5000]

Just a thought , with the 808 you could make eprom pin a15 active , then use a 512k chip for 12p and you you have at least another 128k free to write more code and cal data and still leave plenty of space for ecu ram.

[VL400]

Yeah thats on the cards if I was to fill the entire 32k memory, at the moment there is still lots of space its just the way its been allocated. Have defined the memory into a few areas - cal(8000-9AFF), ALDL(9B00-9FFF) program code(A000-FBFF) and flashwriter(FC00-FF7F). As it turns out I could have allocated more to the cal segment as thats the only segment that is close to full but when initially setting up the code figured it would be heaps (seeing as its nearly double what the factory code had), just did not count on all the stuff the 808 could do!

The trouble with changing it now is all the tools are setup to use that mapping and would mean exceptions to the rules on a per version basis If it ever gets to it maybe 12P V2xx would be a 64k bin

[blownvp]

cheers thanks for the reply.darren

[Holden202T]

i've been using this a bit lately and getting frustrated with the monitors not being real easy to work out because target afr will have a label of AFR and wideband has the same etc, tps will just be % .... so i've gone through and labelled them all meaningfully and here they are for anyone wanting.


i also noticed the 0-25v input was still labelled as the crank time counter so i have updated it to do its rightful task!

[VL400]

Updated the 12P package with these ADX files - they are v1.09 now.