Hi all.
After I set up Odis-S, the diagnostics showed error 7237 "Function restriction due to missing message" in the IFE_5F block, which is, the Multimedia block.

Spoiler

Before the DTC appeared, I updated the MIB 2.5 to 480-firmware, and also checked the settings in Car Scanner Pro with ELM327 adapter. I reviewed the Multimedia section in the app a few more times, but did not find any suspicious / inappropriate settings there.

I cannot just erase the fault code - it comes back immediately. 

In Odis-S, there are a lot of options for this block in guided functions, but I don’t want to poke without understanding what’s what.

Spoiler

Could you please advise what can be done here to fix the error?

Many thanks in advance!

This is simply because you would have updated the firmware without having an online ODIS-S session to allow them to do an SVM coding check when applying the new firmware.

 

There are VCDS instructions on "fixing" this non issue fault offline of course, with ODIS-S you should be able to do this also.

 

 

EDIT: This should be enough for you to follow with ODIS-S

https://forums.ross-tech.com/index.php?threads/20023/

Edited 18 October, 20223 yr by varooom
Additional information

3 minutes ago, varooom said:

This is simply because you would have updated the firmware without having an online ODIS-S session to allow them to do an SVM coding check when applying the new firmware.

 

There are VCDS instructions on "fixing" this non issue fault offline of course, with ODIS-S you should be able to do this also.

Thanks for the response. Car Scanner Pro have had such an option in coding to fix MM after firmware update, but it referenced to another DTC. I tried - did not work.

Do you have an idea where shall I dig to find a guide or example of a solution out? 

8 minutes ago, koaly said:

Thanks for the response. Car Scanner Pro have had such an option in coding to fix MM after firmware update, but it referenced to another DTC. I tried - did not work.

Do you have an idea where shall I dig to find a guide or example of a solution out? 

You have 2 choices

 

1. You can ignore this "drastic" sounding fault as it will not affect the unit whatsoever (it's literally because it was not able to talk to factory during update)

 

2. Learn you way around ODIS-S to be able to bring up the measurement blocks and find the one labelled in the VCDS guide above, then with the value in there you can do the XOR calculation and input new value and save.  In theory afterwards the fault should be able to clear.  I cannot help with this side as you have a very old copy and none of the menu's match mine.

Edited 18 October, 20223 yr by varooom
Spellink

You might need to enter a new code as per below link

 

https://mib-helper.com/im-so-xory/

Edited 18 October, 20223 yr by Ecomatt

16 hours ago, Ecomatt said:

You might need to enter a new code as per below link

 

https://mib-helper.com/im-so-xory/

Thanks for the hint. I will check it, but not sure if it might be a solution.

All actions, which have been advised are for DTC 1555, related to non-confirmed FW update. I receive a completly different DTC 7237 "Function restriction due to missing message".

As I understand, the module 5F tries to communicate with another system, but does not receive a response. How could I find it out, from which module the message is missing?

At a guess, something is mis-coded or another module is sad.

 

Unfortunately the ODIS output isn't particularly google friendly - I'd suggest finding someone local with VCDS to take a look.

 

For reference, the OP asked the same on drive2, adding a link in case it gets solved there first: https://www.drive2.ru/l/630192237359150475/

56 minutes ago, langers2k said:

At a guess, something is mis-coded or another module is sad.

 

Unfortunately the ODIS output isn't particularly google friendly - I'd suggest finding someone local with VCDS to take a look.

 

For reference, the OP asked the same on drive2, adding a link in case it gets solved there first: https://www.drive2.ru/l/630192237359150475/

Thanks for the advice!

I got a hint @Drive2.ru to use ODIS-E for finding a link with another module, from which the required message is missing, I will try that and post the result here as well.

I do not have anybody local to try VCDS, but I found some local offers of used VCDS HEX-V2 interface with software 22.3. Looks like copies of original being sold for €80.

Does it make sence to buy such a device in addition to my VAS 5054a?

Is there a benefit of using VCDS instead of ODIS for DTC resolution? 

11 minutes ago, koaly said:

Looks like copies of original being sold for €80.

Don't even think of buying a copy of a VCDS cable, buy the real thing from a local distributor or direct from Ross-Tech in the USA - unless you like using unknown hacked software and are happy to get no support...

4 minutes ago, PetrolDave said:

Don't even think of buying a copy of a VCDS cable, buy the real thing from a local distributor or direct from Ross-Tech in the USA - unless you like using unknown hacked software and are happy to get no support...

I do not think about investing into any new adapter as I am not sure it is required and see no benefits vs ODIS.

My aim is to resolve the DTC and so far it is not clear what to do. I will check ODIS-E with my VAS 5054a adapter. This is what I'm going to do next. 

I have a genuine VCDS HEX-V2 and a cloned VAS5054a with both ODIS-s and ODIS-e.

 

VCDS covers about 99% of my use. It's easier to search for error codes online and tends to give better information, there is also support from Rosstech and their community of users.

I only use ODIS for things VCDS can't do, namely flashing updates, uploading parameter sets, accessing EEPROMS or calibration of certain modules.

 

A genuine HEX-V2 3-VIN is around £225 but there must be some folk in Austria with genuine versions. I'm not sure if we get many on this forum...

I have exaclty your error. Did you managed to fix it?

sorry to unearth an old message but i have the exact same code after infotainment unit was upgraded via Odis.

I dont have VCDS but do have a Icarsoft scan tool that does mostly what i need

Did also have an error code B201AAOO which i managed to clear using adaptations/confirmation of instalation change and generating a new HEX code via the above suggested site but still have U111100 code Function missing due to missing message.

Everything works as its meant to but annoying have just one fault code left on the log

Any help or guidance would be very appreciated

You have a Picture from the Error Message from the Tool?

this all i have at the moment sorted out the first fault code but struggling with the second one...read all the info on this post even tried C9 D2 hex code (51666) but would not accept this in adaptions.....I am considering buying VAG com unit but if its something i can do with my scan tool would love to do it

just for reference the first code was deleted from original hex code 3ED6 with a online converter came out to f7 04 which allowed me change in adaptation/confirmation of instal change and thus deleted first fault code