Hi, I've searched everywhere I can think of without success.

Please can anyone tell me what the pretty useless "mismatch in control programming" error actually means?

and what is "training mode"? My guess would be that it won't allow any potentially disruptive operations, but I don't see any difference.

Thanks,
Mike

 

I'm guessing but something like it expects a particular module or software version (from VCATS or as-built) but finds something else.

A further guess is it looks and checks whether in actual programming mode or training.

 

Mismatch in control programming means the controller and a paired module have conflicting settings (usually after a board swap or firmware flash). It's a software config fight, not a hard fault, and it'll block starting until the parameters are rewritten properly via the dealer menu.
Training mode locks out the transfer switch and ignores some faults so a tech can test safely without dropping your house. You don't see a difference because a manual test won't risk a transfer anyway. For a homeowner, it's pointless.

 

Thank you both for responding - much appreciated. The explanation for training mode is more or less what I was thinking, but it's good to get it confirmed.

@RRpip - that error would certainly fit with what I know about the 2005 I'm trying to revive. Hopefully, it hasn't had any attempts to flash anything although heaven knows what the tinkerers have done previously - although a replacement KTM has been tried.

 

Yeah, that's a dead ringer for a corrupted or mismatched ECU flash, especially if a replacement KTM was thrown in at some point. If the maps don't match the immobilizer or dash, it'll brick itself exactly like that. Fingers crossed it's still on the factory firmware and just a sensor or wiring gremlin, but if someone's already been poking around with unknown tools, all bets are off. Your best bet now is pulling the ECU and reading it directly on the bench to see what's actually on there before attempting any reflash.

 

Thanks again.
'Someone' had definitely been poking as the ISO K-line wire had been moved to a different pin (3) on the OBD connector. I read somewhere that pin was used by some diagnostics - clearly not IDS/SDD. Possibly why the dealership couldn't fix the problem either.

I took a copy of the VID block from SDD which appears OK inasmuch as there is data in the correct place and the checksum is good, but that isn't proof that it's OK. My thread is here if you have a spare 1/2 hour or so :
https://www.jaguarforums.com/forum/x...8/#post2864213

The replacement KTM was with the car but not fitted. A 'someone' had left the original wedged in the fascia fusebox, which was not A Good Idea as it was full of water .

I'm using IDS v130 native on XP, but only a clone Mongoose at the moment, and have a B2141 from both the IP and the ABS. SDD help for the ABS error is 'configure the IP'.

I think I need to source a Rotunda VCM before I go any further.

Again, many thanks for your insights.