Proxi alignment Request out of range error

[drfloyd99]

Hi,

I tried to activate Android Auto on my Fiat Tipo 1600.

While writing back the new proxi configuration I got the following error message
Request out of range error
[102A] errors: Byte 83: 4F->4B

I've only changed something after byte 150. So I have no idea why there is an issue with Byte 83. Now the odometer is blinking.
I've also tried to copy back the original data, but Multiecuscan says that the identification data has changed and I don't know if I should confirm this message box.

Has anyone an idea on this.
Thanks

[shpuncik]

check FESLog files in MES folder and trace back if you by mistake didn't change anything else.

[drfloyd99]

Hi,

I've tried various versions now.
Back to the original configuration
proxi alignment without any changes

But the error is everytime the same
Schreiben des Moduls: Knoten Airbag (NAB/ORC) FEHLERHAFT! - Request out of range error
[102A] errors: Byte 83: 4F->4B

I've also found other proxi configruations regard android auto and Fiat tipo in this forum and also those examples have Byte 83 set to 4F. So could it be that this is an issue with Multiecuscan version or my OBD adapter?

I'm using version 4.7R3
Thanks

[drfloyd99]

So finaly the Proxi alignment is OK again.

To me it seems that this out of range error is something like a bug.

If I perform the same alignment a second time (wihtout any changes) the aligment is OK again although the error message still comes up.
And Byte 83 is still set to 4F

Maybe someone with deeper knowledge about this topic can check if it is a BUG or not.

Thanks for Help

[djbase667]

Did you ever find a solution, I have a similar problem.

Airbag Node (NAB/ORC) FAILED! - Request out of range error

[102A] errors: Byte 69: 7C->4C

-> It keeps on failing.... Even if I retry with same values.

Thanks!,
Davide