Can anyone help me with AlfaOBD not able to connect to the Integrated Center Stack?

[RamDiver]

Here's the Hex format being referred to...

When I use AlfaOBD for windoze, the backup config file produced is a readable PDF document.
With AlfaOBD for android, is the backup config file produced a text file containing hex code?

Can it be produced in a usable format or converted to a readable document?

.

 

[SitKneelBend]

When I use AlfaOBD for windoze, the backup config file produced is a readable PDF document.
With AlfaOBD for android, is the backup config file produced a text file containing hex code?

Can it be produced in a usable format or converted to a readable document?

.

Correct, that is the output from the Android app. However, if you run the "Read System Status", you will get an output similar to what you have that looks like this...

 

[RamDiver]

Correct, that is the output from the Android app. However, if you run the "Read System Status", you will get an output similar to what you have that looks like this...

Thanks, that's great to know.

I'll try to remember to request the 'Read System Status' file from android users when required.

So, the only use for the android version of the backup config file is for performing an upload to restore the BCM.

We should update the SOP for android users to include saving both the backup config file and the Read System Status file if that's not already included.

IIRC, the current SOP only suggests saving the backup config file.

.

 

[SitKneelBend]

Thanks, that's great to know.

I'll try to remember to request the 'Read System Status' file from android users when required.

So, the only use for the android version of the backup config file is for performing an upload to restore the BCM.

We should update the SOP for android users to include saving both the backup config file and the Read System Status file if that's not already included.

IIRC, the current SOP only suggests saving the backup config file.

.

Yeah, I've tried to find something to decode it but it was just quicker to look in the system status log to compare BCM config when I was swapping a 2014 for a 2016 BCM.

 

[2016 2500]

I never did update this. I found that the 8.4 upgrade took care of my issues.