Hey all.. just checking with the collective on 511 faults (KOEO) that keep getting thrown.
Don't remember seeing this one until recently, when I swapped to 4DBG/N4AGB_v14a+ (prolly the most solid def we have thanks to Jase and other's hard yakka). It's an EFIIXR6 auto with no major mods, however I'm running a homebrew bank switcher on the J3.

511 normal for J3? Can it be fixed in the bin? Cause any issues?

As to the 511, the intarnets search button did give a few Aussie hits the net only gives a shows it's common on chipped stangs in the US.. some say it's normal for all J3 prom overrides, others say it's new/recently appeared on their chipped ECU's.. and some say their car has been playing up since it appeared.

Someone also said it was a bad J3 connection.. will try another chip..

Another few threads might shed more light on what a 511 means, how it gets there/how to avoid it - seems to be related to the bin's checksum? And the calibration/KAM/EEPROM data? ..whether there's a mismatch between bin eeprom layout, or perhaps the bin's checksum range mistakenly includes EE mem locations?
Anyway that's just what I made out of the bits I've read so far. It's all a bit too deep for a dabbler like me, without ploughing more man-weeks into yet another side-project

Quote"
Reset the EEC last night and reloaded my base calibration.. Got this from MG @ Tweecer. Pretty much exactly what you said, except he updated the strategy. Thought it would be good info for you too..

"511 is due to the change in the calibration. set the checksum base
address to zero to clear that one. The others are the cause for the
shifting, PIP is used throughout the strategy for different things
including trans functions. TFI, distributor, etc....

You can check the TP signal with the key on, engine off and RT logging.
Sweep the throttle slowly to the floor and back watching/logging the tps
voltage and see if you get drop outs/spikes in the voltage."

Also, MG updated the VEX1 and AHCA strategies to fix the problem..

"I located the checksum base address for VEX1 and AHACA, they have both
been uploaded to the Software Updates folder in the files section. Save
them to our data folder at C:\Program Files\STKR 1.30\Data\"
"

Short answer is, yes it's a checksum mismatch, and no it will not affect any other operation.

Cheers,
Jason