PCMTec Development Blog

[VX L67 Getrag]

In case you didn't understand the Vadis format, I've attached the .bin with correct offset

Thats awesome thanks so much, I can't wait to check it out tomorrow, did you hand edit that or do you have a little program that can convert it with the correct offsets & layout?

Now I just need to get a proper file with correct rom info & insert the VIN & should be able to write to these controlers without having to pull them apart....
But that may still be necessary as I believe there may be an internal hardware mod that may need to be done to write to the siemens SID20x range does anyone know about that or confirm/deny?

Thanks again rmrmd1956

[DarrylC]

its not supported by HPT, the Aussie application uses a separate TCM. In the US, its part of the engine PCM

Not sure how the CES24 works but apparently Dimsport supports the Ford ECU

Not quite, Eric told me there are two options for the 6R80. The early ones used a separate TCM and the later ones it was back in the PCM. HPT support both as the Mustangs and trucks have both options.

Interesting, he only mentioned the PCM one. Do you have a list of which has what?

Sorry I don't have the list, email their support team and they may have it for you.

[rmrmd1956]

In case you didn't understand the Vadis format, I've attached the .bin with correct offset

Thats awesome thanks so much, I can't wait to check it out tomorrow, did you hand edit that or do you have a little program that can convert it with the correct offsets & layout?

Now I just need to get a proper file with correct rom info & insert the VIN & should be able to write to these controlers without having to pull them apart....
But that may still be necessary as I believe there may be an internal hardware mod that may need to be done to write to the siemens SID20x range does anyone know about that or confirm/deny?

Thanks again rmrmd1956

It is a addon module in WinOLS but you have to buy it and it is very expensive.

[rmrmd1956]

[quote="rolls"]Also found the unified diagnostic service (OBD2 extension ISO14229) command handler routine, I'm sure this will help with finding out what commands it does and doesn't support.

https://automotive.wiki/index.php/ISO_14229
//0x10 Diagnostic Session Control
//0x11 ECU Reset
//0x14 Clear Diagnostic Information (not supported)
//0x18 ???
//0x19 Read DTC Information (not supported)
//0x22 Read Data By Identifier
//0x23 Read Memory By Address
//0x27 Security Access
//0x28 Communication Control (not supported)
//0x2E Write Data By Identifier (not supported)
//0x2F Input Output Control By Identifier (not supported)
//0x31 Routine Control
//0x34 Request Download
//0x35 Request Upload (not supported)
//0x36 Transfer Data
//0x37 Transfer Exit (not supported)
//0x3D Write Memory By Address (not supported)
//0x3E Tester Present
//0x85 Control DTC Setting (not supported)
//0xB1 DiagnosticCommand

For what its worth I think>
//0x18 Read Diagnostic Trouble Codes By Status

[rolls]

//0x18 Read Diagnostic Trouble Codes By Status

Thanks for that, I found that somewhere else but was unsure if it was actually used. My comments about stuff that's not supported may not be entirely correct either, that was just my assumption from my brief look.

[VX L67 Getrag]

In case you didn't understand the Vadis format, I've attached the .bin with correct offset

Thats awesome thanks so much, I can't wait to check it out tomorrow, did you hand edit that or do you have a little program that can convert it with the correct offsets & layout?

Now I just need to get a proper file with correct rom info & insert the VIN & should be able to write to these controlers without having to pull them apart....
But that may still be necessary as I believe there may be an internal hardware mod that may need to be done to write to the siemens SID20x range does anyone know about that or confirm/deny?

Thanks again rmrmd1956

It is a addon module in WinOLS but you have to buy it and it is very expensive.

Ahh cool about add on module for winols, if only there was a reasonable priced mapping software that wasn't linked to programming software/hardware.
It's pretty easy to convert those VBF files to bin (slight variances though as there's 1552KB & 1498KB files so will be a little different) but this is how to hand edit & takes 30 seconds...
Cut first 3CE
Insert 40000 byte count with FF's from zero
Then at 1C381A insert 3C3E6 byte count with FF's till 1FFBFF
Cut the next "A" length of bytes
At the end cut the last 2 bytes
Insert 200 bytes with FF's should be 2MB in size


But now to add confusion to that I have since got ktag/bdm version of the same file & it's 4MB in size but the 2MB is internal to it....
Even more to add to it the stupidist thing is they can't be read or written over OBDII without mod & the mod is as simple as changing 00 to FF in 1 byte of the 4MB file but ATM the case needs to be opened for it to happen.

[headsex]

and congratulations, that will most likely break your file when converting it from vbf to bin.

Rather than give exact steps that only work on that exact vbf file, Why don't you give more insight to how the file actually stores the binary data?

After the text header part of the vbf file, typically the data is stored with the first few bytes indicating the size and the address, then the actual data, then ending with a checksum.. then repeat for all the different memory segments.

[VX L67 Getrag]

Sorry headsex, looks like I spoke out of school.. yeah that was the steps for that exact vbf... but the other couple I've seen for that model are slightly different size so I'm not 100% on the steps for those... but I look to make sure all the data lines up with same locations after done.

As I said I'm more concerned about getting the bin file in a usable format & then being able to flash it without having to open up case, but in any fact we are going off original topic... SO SORRY FOR ALL IT MAY HAVE CONFUSED

[rolls]

The header is pretty self explanatory, someone could write an automated converter for it in a few hours. Haven't actually needed vbf files yet though, will probably put something up on github one day.

[headsex]

the header text in a vbf file has nothing to do with the structure of the binary held.