Delco OSE FlashTool V1.51

[VL400]

It should be able to work on any ECU that has bi-directional ALDL. On most bins we have just patched the mode 10 'clear malf' command to be 8/16 byte write. For bins that are recompiled we have added new ALDL modes 11,12 and 15.
Mode 11 - Write with up to 8 bytes
Mode 12 - Write with up to 128bytes
Mode 15 - Read 128bytes

The reason for having two write modes is because mode 11 uses the CPU RAM as a buffer while mode 12 uses the some NVRAM free space as a 130odd byte buffer. The frame format is simple...
1 - Device ID
2 - Number of bytes
3- Mode
4 - Address to start the write MSB
5 - Address to start the write LSB
6-N - <Data to write>
N+1 - Checksum

[robertisaar]

that actually doesn't sound too bad to deal with...

for my purposes, i can use part of the 2K of extra SRAM for temporary storage of the bytes to be written to the NVRAM. i'll probably impliment my own mode 12 since that will have less overhead when doing writes. mode 2 dumps seem to be the easiest way to get portions of the BIN out as well. anybody have a commented section of code they want to share to get this up and running quicker?

free space in the PROM is currently an issue though, i've been patching stuff in and have literally run out of room on a 32KB PROM.... internal mods to the ECM to open it up to the full 64KB have been interesting. so it may be a little while before i can test anything.

[VT Bob]

Great work VL400,

Have installed the new NVRAM into my ECU and using the FlashTool to read/write cal changes to the W5.1 bin. Working flawlessly. Very Happy.

[VL400]

Good to hear VT bob


Have also updated the program to V1.38. Only minor changes..
- When writing a bin if auto fix checksum is selected the program will first checksum the BIN and fix the checksum bytes prior to writing anything
- When selecting 'write cal' it now shows both bin and cal files (still only writes the cal if a bin is slected)
- Fixed knock retard item in 12P ALDL message editor, was 8 bit item defined as 16 bit

[Yortt]

Good to hear VT bob


Have also updated the program to V1.38. Only minor changes..
- When writing a bin if auto fix checksum is selected the program will first checksum the BIN and fix the checksum bytes prior to writing anything
- When selecting 'write cal' it now shows both bin and cal files (still only writes the cal if a bin is slected)
- Fixed knock retard item in 12P ALDL message editor, was 8 bit item defined as 16 bit

Re: " Fixed knock retard item in 12P ALDL message editor, was 8 bit item defined as 16 bit"
I have a problem with a turbo 4 cylinder I have converted from code 59 to 12 P this has fixed all low speed drivability and idle issues there was with code 59. However when logging with tunerpro it is generating substantial knock 10 - 12 degrees at around 4000 to 500rpm the fuel delivery and timing is the same as code 59 which only generated very low level of knock at the same rpm I consider this not to be true knock, does your comment" Fixed knock retard item in 12P ALDL message editor, was 8 bit item defined as 16 bit" have anything to do with this?

[Holden202T]

no it doesn't, the issue was when i defined a custom message to display knock retard it was a 16bit option but the data is only a 8 bit, it just made the item in the adx show up as maxed out until changed to 8 bit.

I believe all VL400 has fixed is when you define the knock retard item in a custom message it makes it 8 bit now instead of 16 bit.

he might be able to give me info on it or correct anything i have gotten wrong.

[VL400]

Exactly as holden202 described, was purely an ALDL display issue when defining custom mode 6 messages (the knock item is actually16bit but only 8 bit is required for logging).

Getting OT to the flashtool, but have you changed to a different knock filter? Can also use the ignore knock counts table in 12P if you are certain its false knock.

[Yortt]

Exactly as holden202 described, was purely an ALDL display issue when defining custom mode 6 messages (the knock item is actually16bit but only 8 bit is required for logging).

Getting OT to the flashtool, but have you changed to a different knock filter? Can also use the ignore knock counts table in 12P if you are certain its false knock.

Yes I have changed to an American 4cyl knock board/memcal but I also used the same memcal I used with code 59 with the same result abnormal knock. I put 747 pcm back in with code 59, knock was at a low level and what would be expected with the applicable boost and timing. I don't want to use the ignor knock count as I am running 25psi boost and want knock retard to be active and functioning correctly as this was the primary reason for using Delco on this conversion

Next test is to use a VR manual pcm piggy back style with a Kalmaker bin just to log knock to see what the result is.

Thanks for the responses

[VL400]

12P has knock count logging to the NVRAM Clear the table in TunerPro and go for a lap

[VL400]

V1.39 released for support of new V2 write bins and MAF extended bins