Reading my bin

[vs ss]

.

[Holden202T]

from what i understand you should be able to read it out using the ose flashtool, from there you can view the file and get the tables out you need.

you'll want a usb obd interface to connect to it though if you dont already have one.

[vs ss]

.

[j_ds_au]

Thank Holden. Correct me if I’m wrong, but I thought the flash tool could only read the full 128k on vx/vy pcm.
Thanks for the help.

Correct. For a stock VS O/S, it can only read 64K (except the last byte is garbage). Probably the same with Kalmaker.

Joe.

[vs ss]

.

[Holden202T]

you only need to be able to read the calibration out of it to get the stuff you need though ?

[vs ss]

Yeah mate , that’s all I need. I have a read from before I put the car away a few years back but it doesn’t seem to make sense. Even in hex it’s not normal so I might have to do another read when I drag the car back out.

[antus]

The calibration is the first 32kb only, so you can read it over ALDL. The mapping is:

128kb chip, consider it 4 32kb chunks

1) 0-32kb contains the calibration - this is what you want
2) 32-64kb contains the engine part OS
---------------------------------------------------
3) 64-92kb Empty
4) 92-128kb contains the transmission part OS

So when it runs the computer can only see 1 and 2. So 2 and 4 is swapped as it runs over and over, so when you do a read you get a file the size of 1&2, 1 is fine (the calibration you want) and 2 is a confused and useless mix of 2 & 4 together (doesnt matter for your purpose).

[vs ss]

.

[vs ss]

.