Quicky questions

[monaro308]

I was checking a log i did last week in the munro and i noticed that in the data list view,its detected 8 cyl mode but 6cyl memcal.
It is a V8 memcal eeprommed of course but running the Ostrich 2.0 emulator...is it because of the Ostrich emulator?
Another thing i came across today,i was going to set up my VE tables in open loop only just to have a play around and when i was adjusting the Closed Loop params - C/L min and max temps,as i'm uploading the changes to ecu i always get a message
"Attempting to write a V1.1.1 cal to a V1.1.0 Use flash tool to convert the calibration"
I am sure i am using all the latest files.
If i up the scale temp gradually,TP updates the file but will not upload the change without that message.
Maxxing out the temps in one hit,TP will not update it
I am emulating (highlighted) and aquire data is on.
Am i doing something wrong
cheers...mario

[vn5000]

If the engine has not been started you will get 6 cyl memcal but when you start it it corrects itself to 8
Have you uploaded the whole v111 bin to the nvram or just the cal as you may have the v110 code still on the nvram.
edit :didnt notice your using ostrich , how are you emulating ,using plugin or ostrich ,what has tuner pro detected as hardware, maybe its confused by both.

[antus]

"Attempting to write a V1.1.1 cal to a V1.1.0 Use flash tool to convert the calibration"

Thats probably true. Use VL400s flashtool to send any complete original bin file from the ose12p v1.1.1 zip file to the ecu. Power cycle the ecu/car and then the flashtool should connect and say v1.1.1. Then send you cal.

[monaro308]

I had a quick look tonight with the laptop and it connects as V1.1.0 and not 1.1.1
I'm sure i haven't got any V1.1.0 files on my laptop and even did a search.
TP5 shows all the V.1.1.1 files on the top bar.

I also havent used flash tool before and had a look ...i select "VR in vehicle" and as i'm not using a BCM i deselect "Detect BCM chatter"....correct??
I was able to "get bin" from my ECU and saved it to a folder but thats as far as i got tonight.
I d/loaded the V1.1.1 zipped files again just in case and learning how to upload the new BLCF bin or cal file to my ECU using
Flashtool....its new to me so bare with me
Curious as to why its showing V1.1.0 after a fresh XP install about a month ago
cheers...Mario

[antus]

I had a quick look tonight with the laptop and it connects as V1.1.0 and not 1.1.1

This is whats in the ecu.

TP5 shows all the V.1.1.1 files on the top bar.

This is what files you have loaded to do the editing in tunerpro. Nothing forces you to load the right files, and the error message from the plugin in there to let you know you have a mismatch.

I also havent used flash tool before and had a look ...i select "VR in vehicle" and as i'm not using a BCM i deselect "Detect BCM chatter"....correct??
I was able to "get bin" from my ECU and saved it to a folder but thats as far as i got tonight.

I d/loaded the V1.1.1 zipped files again just in case and learning how to upload the new BLCF bin or cal file to my ECU using
Flashtool....its new to me so bare with me

Cool. If you have nvram, pick write bin, and pick one of the bin files from the v1.1.1 zip file. That'll sort out your mismatch. If you have eeprom and ostrich, then dont use oseplugin as that is for the nvram method. Refer to other documentation about how to the ostrich to tune. You can still use 12p and the 12p xdf/adx files, but the ostrich is a different interface you'll need to configure approprately.

Curious as to why its showing V1.1.0 after a fresh XP install about a month ago
cheers...Mario

Either it always was, or the version string has been corrupted somehow on the ecu, or somehow a different file has been loaded to the ostrich emulation ram.

[monaro308]

Thanks Antus,thats explains it.
The ECU would still have V1.1.0 bin/cal in it.
So all my standard changes ie PPK and TCC lock speeds from v1.1.0 i carried over to V1.1.1 that i haven't updated until i tried yesterday.
Yeah eeprom and Ostrich is what i'm using.
Cheers...Mario