[Node]

It's elementary. IF your module is from you car and there were no funny things done to car, then WinKFP will read current ZB from UIF and will find the updated number correctly.

When funny things ARE there OR unit comes from some random source, you CAN'T trust UIF, firstly because you don't know what car it comes from and secondly (and quite frequently) because UIF may contain garbage. It's not a problem to write any random things into it... Either on purpose or because someone already tried funny things on it...

So in later cases you ALWAYS start from the label on the unit and follow the files manually looking for the same HW number. How to do that AFAIR I already explained.

---

And then there are cases where some idiot mixed internals into wrong cases Thankfully these are rare

[thecarfixer]

Yep, makes sense, start from the label, find the hardware, match up to your type code (where possible!) and find the right ZB.

So I think, for my FRM3 swap, I managed to wing it with prog zusb-update because thankfully the right type code and options exist within that software. I think FRMs are a bit of a different case because they're very 'adaptable' given the units are used over multiple cars in different ways. (Obviously caveats still apply there)

I'm still very confused as to the hardware mismatch on the Kombi. But it works, so don't mess for the sake of it. I did have a right old game with the DME not seeing ambient temperature, but a day or two AFTER I fitted and coded it, and ISTA remediation said to reset the variant coding on the DME, which did work. It's working now with no faults.

I'm going to learn more about NFS, because clearly this is the better method as it then orchestrates Win KFP to do its bidding, but is able to look at KMM.

Thank you, I appreciate your help.

[thecarfixer]

As a footnote to this, I got ISTA P installed (my god the space it takes up is huge) and looked at the measures plan.

So it moaned about the CIC, the FLA I’d retrofitted, and wanted me to replace the FRM3 I’d fitted, but what was telling is there was no suggested update for the Kombi. Also my DME WAS listed as having the wrong ZB, with a suggestion, as well as my FAS module (of all things).

So the moral of the story is don’t blindly update modules with WinKFP prog-zb update as it’s not right. I won’t be doing that again, without more careful verification (via looking at the KMM, or using ISTA to see what the measures plan is.

[bmchicago]

most likely if you put a used FRM3 in there, the I-level does not match your factory i-level and is complaining because the data is not correct. The FA may be correct, but the factory i-level must match the vehicle's build.

[thecarfixer]

I’d changed the ilevel to the correct one.

[Node]

If you have FRM3 replaced most likely you ended up with "wrong" one. It MAY work ok without any problems, just it's NOT the one which SHOULD be in your car - maybe it's for more featured car (or less, but then you definitely have something not working) or older than your car or something else.

P.S. Follow the files and find by yourself what is the problem. I see it as a good exercise for learning... Or post data here.

[thecarfixer]

But the car was built with an FRMFA, so any FRM3 is going to be seen as ‘wrong’?

The zb I’d flashed my original FRMFA to (9128184, it was originally 6961134) WAS the suggested zb replacement, by ISTA P.

But I’d fitted an FRM Max Brose, and programmed it to 6827074, which gave me welcome lights, DRLs and FLA all controllable via the CIC - with the FRMFA, even when updated to latest zb won’t let you switch those options on and off via the CIC.

I thought (and will recheck) that 6827064 would match my type code.

[Node]

What is your type code?

[thecarfixer]

The type code is VB32

[Node]

Add XFRM and ISTA-P will probably stop complaining...