DIM U2300 error

[Swer]

Hello guys. I have an active error DIM: U2300 - Central Configuration- System programming Failures- Invalid incompatible configuration. Even after doing a Restore to OEM, the error still remains. What am I doing wrong? Thank you.

[nlis]

Hello guys. I have an active error DIM: U2300 - Central Configuration- System programming Failures- Invalid incompatible configuration. Even after doing a Restore to OEM, the error still remains. What am I doing wrong? Thank you.

I'm getting the same error on my XC60 II MY2022. What software version do you have? 
I found old logs from Orbit, where the car configuration hadn't been changed yet, so this error must have occurred earlier.

[Swer]

Hello guys. I have an active error DIM: U2300 - Central Configuration- System programming Failures- Invalid incompatible configuration. Even after doing a Restore to OEM, the error still remains. What am I doing wrong? Thank you.

I'm getting the same error on my XC60 II MY2022. What software version do you have? 
I found old logs from Orbit, where the car configuration hadn't been changed yet, so this error must have occurred earlier.

Newest orbit software :/

[nlis]

I meant the software version in the car. What system do you have? Sensus or Android Automotive?

[Swer]

I meant the software version in the car. What system do you have? Sensus or Android Automotive?

Sensus, my XC90 2016.

[x119]

Have you tried locking the vehicle and leaving it for a period? Overnight perhaps. 

Then read dtc, clear and run it for a day before checking again. 

A lot of things in these vehicles require sync, that takes time.

[Swer]

Have you tried locking the vehicle and leaving it for a period? Overnight perhaps. 

Then read dtc, clear and run it for a day before checking again. 

A lot of things in these vehicles require sync, that takes time.

Ok, I'll try, maybe it will help. Thanks

[Power6]

This is a general issue, and should have it's own FAQ probably...troubleshooting "bad" configs. Not every setting is going to be supported by every car, the nature of a universal central config. We'll start here and I can probably turn this into a post for the FAQ.

When you get this trouble code from a module, it is telling you that it doesn't "like" one of the configs you have set. The way config works, each module has it's "items" it takes from central config, then sets it's operation accordingly. If it doesn't have an operation for the config value you have set, it's not an expected option to be used among what it's capabilities are, something like that, then the module sets that code. Bottom line you set a config with OrBit that the DIM doesn't like. You can figure out which item is the problem:

In OrBit, you can read data from each module, including the invalid config items. I'll walk through it quick here, not having access right now to take screenshots.

On the ECU Tools tab, there is the "ECU Function Request" area which currently only has the Read Data by Identifier service. You can change the "Active Diag ECU" to the one to work on, in this case change it to the DIM. The list of data identifiers will populate based on the DIM module. You should find one of those is "invalid config..." or similar, you can use the "filter" box search to filter the list rather than scroll through all, I beleive it is DID "E103" though. Select that and "Send to ECU". You will get a return results window, and those results, should be a list of all config items that are invalid. Listed will be the "first invalid config" with item number first, corresponding to the same item number in the OrBit Configurator table. The next entry will be "first invalid config" value that is the problem, this is good to confirm that it's the value you set for that config item in the configurator table, and you will know that the DIM does not like/support it. 

If there is a mismatch between the value given in in the results for the "invalid config item" and the value you have actually set, this usually means the module needs a reset to "take" a new config item, most modules don't need this (HCMs do, and BCM/BCM2 need "ABS Config clear" to take new config changes)

If there are multiple items invalid the subsequent entries are filled in (second, third etc.), if not the results will just show "0s" for the rest of the results slots.

This is the general way to see which item is a problem, when the module sets the DTC code for invalid config.

[chess]

This is a general issue, and should have it's own FAQ probably...troubleshooting "bad" configs. Not every setting is going to be supported by every car, the nature of a universal central config. We'll start here and I can probably turn this into a post for the FAQ.

When you get this trouble code from a module, it is telling you that it doesn't "like" one of the configs you have set. The way config works, each module has it's "items" it takes from central config, then sets it's operation accordingly. If it doesn't have an operation for the config value you have set, it's not an expected option to be used among what it's capabilities are, something like that, then the module sets that code. Bottom line you set a config with OrBit that the DIM doesn't like. You can figure out which item is the problem:

In OrBit, you can read data from each module, including the invalid config items. I'll walk through it quick here, not having access right now to take screenshots.

On the ECU Tools tab, there is the "ECU Function Request" area which currently only has the Read Data by Identifier service. You can change the "Active Diag ECU" to the one to work on, in this case change it to the DIM. The list of data identifiers will populate based on the DIM module. You should find one of those is "invalid config..." or similar, you can use the "filter" box search to filter the list rather than scroll through all, I beleive it is DID "E103" though. Select that and "Send to ECU". You will get a return results window, and those results, should be a list of all config items that are invalid. Listed will be the "first invalid config" with item number first, corresponding to the same item number in the OrBit Configurator table. The next entry will be "first invalid config" value that is the problem, this is good to confirm that it's the value you set for that config item in the configurator table, and you will know that the DIM does not like/support it. 

If there is a mismatch between the value given in in the results for the "invalid config item" and the value you have actually set, this usually means the module needs a reset to "take" a new config item, most modules don't need this (HCMs do, and BCM/BCM2 need "ABS Config clear" to take new config changes)

If there are multiple items invalid the subsequent entries are filled in (second, third etc.), if not the results will just show "0s" for the rest of the results slots.

This is the general way to see which item is a problem, when the module sets the DTC code for invalid config.

Excellent advise. Solved my U2300 DTC issues. Was able to figure out errors on ECM and PSMD modules.