Possibly the Burn 2 chip addressing and buffer addressing is not correct? Example below if for the '9625 64K 27SF512 PCM.
Chip Addressing
Start Address in Hex = 000000
End Addressing in Hex = 00FFFF
Buffer Addressing
Start Address in Hex = 000000
End Addressing in Hex = 00FFFF
It's embarrassing to ask:
Is the chip correctly installed in the Burn 2.
Is the correct chip selected to read / write / erase?
dave w
Morning Dave!Originally Posted by dave w
The addressing is correct for the chips. Have tripled checked that as it was my first error when trying to read the memcals when If first received the Burn2
The chips are the SST 27SF512's that Moates sent me with my order. The chips are set away from the zif handle as outlined in the instructions.
Tried both chips.
When Erase is selected is shows successful really quick.
When verify chip empty it takes a few seconds then tells me the chip is not empty.
Isn't learning fun?
On another note, I may have figured out part of my problem outside of the tune. With my modified distributor, it is possible when I locked the advance I got the rotor out of phase with the stator. Will have to research that this evening.
Thanks, Louis
Jack of all trades, absolutely master of none! Too many projects, not enough time and limited funds.
Geronimo, Guadalupe County, Texas
1993 K1500 Suburban - SBC Refit retraining the TBI and Computer Control.
2004 Z66 Avalanche 5;3 to 6.0 LQ9 upgrade - project pending
Tech Support at Moates is 1st Class.
poked and prodded a bit with Team Viewer, changed some firmware settings and bingo. Working as advertised now.
Jack of all trades, absolutely master of none! Too many projects, not enough time and limited funds.
Geronimo, Guadalupe County, Texas
1993 K1500 Suburban - SBC Refit retraining the TBI and Computer Control.
2004 Z66 Avalanche 5;3 to 6.0 LQ9 upgrade - project pending
Do you happen to remember which settings were changed?
Stepped the firmware back one update to 1.00.3518.00 now!
Edit: trial and error update.
For my particular computer (Win10 64-bit HP) I found that if my port latency was set at anything other then 1, the data was getting scrambled on read and programming the chips.
This is in settings, device manager, ports, under the advanced tab.
Last edited by trlrider; 05-18-2021 at 03:34 PM. Reason: clarification
Jack of all trades, absolutely master of none! Too many projects, not enough time and limited funds.
Geronimo, Guadalupe County, Texas
1993 K1500 Suburban - SBC Refit retraining the TBI and Computer Control.
2004 Z66 Avalanche 5;3 to 6.0 LQ9 upgrade - project pending
Continuing the learning and understanding.
My factory PCM (8625) has the BLCP .bin with a $E6 mask. That .bin appears to be oddity as it is not listed on this forum under that PCM
So I have been looking at a 7427 PCM that I have with the BJLH .bin and $OD mask to as a learning PCM and to possible swap into the Sub as it appears to be better liked then the 8625.
Anyway when I read the original BJLH chip, I see some oddity's compared to the same .bin file type downloaded from the forum for the 7427.
Inquiring because I don't want to make changes and burn a chip, and find out the hard way I am somehow corrupting the data in the transfer.
One for instance is the Main Spark Table vs MAP vs RPM below:
20.0 20.0 20.0 20.0 20.0 18.3 17.2 12.3 11.3 9.1 6.3 4.2 3.2 2.1 1.1 0.0 -0.7
20.0 20.0 20.0 20.0 20.0 18.3 17.2 12.3 11.3 9.1 6.3 4.2 3.2 2.1 1.1 0.0 0.0
20.0 20.0 20.0 20.0 20.0 20.0 20.0 16.2 14.1 10.2 9.1 5.3 4.2 2.1 1.1 0.0 0.0
20.0 20.0 20.0 20.0 20.0 20.0 20.0 18.3 15.1 13.0 10.2 7.0 5.3 3.2 1.1 0.0 0.0
20.0 20.0 20.0 20.0 20.0 20.0 20.0 18.3 16.2 14.1 11.3 9.1 7.0 5.3 3.2 2.1 1.1
21.1 21.1 21.1 21.1 21.1 21.1 21.1 19.0 18.3 15.1 13.0 11.3 9.1 7.0 5.3 4.2 4.2
22.1 22.1 22.1 22.1 22.1 22.1 22.1 20.0 19.0 16.2 14.1 12.3 10.2 9.1 7.0 6.3 6.3
23.2 23.2 23.2 23.2 23.2 23.2 23.2 22.1 21.1 18.3 16.2 14.1 12.3 11.3 9.1 9.1 8.1
25.3 25.3 25.3 25.3 25.3 25.3 25.3 23.2 22.1 19.0 17.2 15.1 13.0 12.3 11.3 10.2 40.4
36.9 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8
79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 40.4 36.9 79.8
79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8
79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 40.4 36.9 79.8 79.8 79.8
79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8
79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 40.4 36.9 79.8 79.8 79.8 79.8 79.8
79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8
79.8 79.8 79.8 79.8 79.8 79.8 79.8 79.8 40.4 36.9 79.8 79.8 79.8 79.8 79.8 79.8 79.8
The same table downloaded from this site is:
20.0 20.0 20.0 20.0 20.0 18.3 17.2 12.3 11.3 9.1 6.3 4.2 3.2 2.1 1.1 0.0 -0.7
20.0 20.0 20.0 20.0 20.0 18.3 17.2 12.3 11.3 9.1 6.3 4.2 3.2 2.1 1.1 0.0 0.0
20.0 20.0 20.0 20.0 20.0 20.0 20.0 16.2 14.1 10.2 9.1 5.3 4.2 2.1 1.1 0.0 0.0
20.0 20.0 20.0 20.0 20.0 20.0 20.0 18.3 15.1 13.0 10.2 7.0 5.3 3.2 1.1 0.0 0.0
20.0 20.0 20.0 20.0 20.0 20.0 20.0 18.3 16.2 14.1 11.3 9.1 7.0 5.3 3.2 2.1 1.1
21.1 21.1 21.1 21.1 21.1 21.1 21.1 19.0 18.3 15.1 13.0 11.3 9.1 7.0 5.3 4.2 4.2
22.1 22.1 22.1 22.1 22.1 22.1 22.1 20.0 19.0 16.2 14.1 12.3 10.2 9.1 7.0 6.3 6.3
23.2 23.2 23.2 23.2 23.2 23.2 23.2 22.1 21.1 18.3 16.2 14.1 12.3 11.3 9.1 9.1 8.1
25.3 25.3 25.3 25.3 25.3 25.3 25.3 23.2 22.1 19.0 17.2 15.1 13.0 12.3 11.3 10.2 9.1
26.0 26.0 26.0 26.0 26.0 26.0 26.0 24.3 23.2 22.1 18.3 17.2 16.2 14.1 13.0 12.3 11.3
27.1 27.1 27.1 27.1 27.1 27.1 27.1 26.0 24.3 22.1 20.0 18.3 17.2 15.1 14.1 13.0 12.3
30.2 30.2 30.2 30.2 30.2 30.2 30.2 30.2 25.3 23.2 21.1 20.0 19.0 17.2 17.2 16.2 15.1
30.2 30.2 30.2 30.2 30.2 30.2 30.2 30.2 26.0 24.3 22.1 21.1 20.0 18.3 18.3 18.3 17.2
30.2 30.2 30.2 30.2 30.2 30.2 30.2 30.2 26.0 24.3 22.1 21.1 20.0 18.3 17.2 16.2 15.1
30.2 30.2 30.2 30.2 30.2 30.2 30.2 30.2 26.0 24.3 23.2 22.1 21.1 19.0 18.3 17.2 16.2
30.2 30.2 30.2 30.2 30.2 30.2 30.2 30.2 26.0 24.3 23.2 22.1 21.1 19.0 18.3 17.2 16.2
30.2 30.2 30.2 30.2 30.2 30.2 30.2 30.2 26.0 24.3 23.2 22.1 21.1 19.0 18.3 17.2 16.2
Starting at 3200 RPM with the table from my junkyard pcm, what is with all the 79.8?
I have the same experience reading a BDJY memcal, both are $OD mask.
Both with the same $OD .xdf and .adf files from the forum!
Is the file being corrupted on the read, or is that common on a factory file from a stock vehicle?
Trying to learn what is going on.
FYI - this occurred before and after the Moates technician worked on my Burn2 firmware.
Thanks in advance!
Last edited by trlrider; 05-14-2021 at 03:28 PM.
Jack of all trades, absolutely master of none! Too many projects, not enough time and limited funds.
Geronimo, Guadalupe County, Texas
1993 K1500 Suburban - SBC Refit retraining the TBI and Computer Control.
2004 Z66 Avalanche 5;3 to 6.0 LQ9 upgrade - project pending
The 4L60E is either definition file $E6 or $OD. The 4L80E is either definition file $31 or $OE.
Looking at a .bin file with the INCORRECT definition file (.xdf) is the most likely explanation why the spark values starting at 3200 RPM's are all 79.8 degrees.
Disasters can happen at the speed of a mouse click!
dave w
Posting Permissions
Reply With Quote
Bookmarks