Garbled (original binary un-decoded?) output for "Faults Found"

[yarikoptic]

My kid got 2017 A3, I did basic diagnostics using BlueDriver (there is no CEL).
It gave bunch of stored errors (they reappear if reset), so I decided to invest into Audi-specialized Ross-Tech's "VCDS-Mobile with HEX-NET Enthusiast".
Connecting from the browser (I do not use Windows much), I get e.g.

   1 │ Fri,May,22,2026,21:22:01 
   2 │ VCDS Mobile 0.4713.0.5
   3 │ 
   4 │ Fri,May,22,2026,21:22:01 
   5 │ VCDS Mobile: 0.4713
   6 │ Data Version: 30000060
   7 │ 
   8 │ Scan: 01 02 03 05 08 09 10 13 15 16 17 19 22 2B 3C 42 44 52 5F 6C
   9 │      BB BC CF
  10 │ 
  11 │ 01-Engine -- Status: OK 0000
  12 │ 02-Auto Trans -- Status: OK 0000
  13 │ 03-ABS Brakes -- Status: Malfunction 0010
  14 │ 05-Acc/Start Auth. -- Status: OK 0000
...
  38 │ Address 01: Engine  (CNTC)  Labels: 06K-907-425-V1.clb
  39 │     Part No SW: 5G0 906 259 L   HW: 06K 907 425 B
  40 │     Component: 2.0l R4 TFSI  H13 0002
  41 │     Revision: --H13---
  42 │     Coding: 0A1D00124426010F3000
  43 │     Shop #: WSC 06385 790 00016
  44 │     ASAM Dataset: EV_ECM20TFS0205G0906259L 001004
  45 │     ROD: EV_ECM20TFS0205G0906259L.rod
  46 │     VCID: 373188DF59AF0CE9FB3B09-8062
  47 │
  48 │ 7 Faults Found:
  49 │ Z��T���^GA^S��]^O��$^EV�Q�^N^F^M��o^Pt�\^EO�Fz�(�
  50 │ f^^�^T#�^_并���>τ���9,a�^A�G��1�?^EPb�^C�^Gy^_
  51 │ =�!�;���V]^SP<��^^�O^P�
  52 │ ^E���)�v9�o~_F�P�L/��
  53 │ �+�C��9jf�����(S��P�����.^F�\[�x"WVw^V��
  54 │ �CFw��yX�Z
  55 │ �w�
  56 │ ��D^Pv�[Q$5T3R2B1001624001^Z<C,�z�<
  57 │ I^AX]:��^G��w*�220q^_    -�.�^S�Xd{�����^Y^S��|f_
  58 │ ��2#�M��m����/�����*fiԃ�^Z^E^D<p��Nۑ�l^ZI'
  ...

and similarly in other sections where Faults are Found.

How can I get those Faults decoded?

 

[stefdds]

For now, I would use the full VCDS version on your PC and we can sort out the VCDS mobile later on.

Sticky - How to post an Auto-Scan

Using the classic, Windows-based VCDS: Also, please wrap your Auto-Scan data in CODE tags, like this: Chassis Type: 4G0 Scan: 01 02 03 05 08 09 0E 10 13 15 16 17 19 28 36 3B 3C 42 44 46 47 52 53 55 56 5F 62 72 82 84 85 8B 8E 8F 90 VIN: WAUBGAFC5CN015352 01-Engine -- Status: OK...

forums.ross-tech.com

 

[Shaun]

I would suggest to try switching your interface to the beta channel in the advanced tab of VCIConfig, then check for updates again and you should get a newer set of updates, see if that newer data resolves this issue.

 

[yarikoptic]

thanks! will do when I get a next touch to with the Windows laptop... atm the beast stands with battery disconnected anyways.

 

[yarikoptic]

roger that with upgrade, and refetching those extra lists after initial scan, I got everything decoded. Now just need to wrap my head around

My few cents on UI:

- Having "Check Feat. Update" button above that "Beta" update channel inspires to click it.
- since also applicable to overall "Update" placement is a bit counterintuitive or "incorrectly suggestive"
- Then, clicking "Check Feat. Update" resets "Beta" to "Release", spends some seconds, and only then reports some error. Naive/newbee user needs to note to reclick "Beta", find that other "Update" tab and do update there...

I think at least it would make sense
- to adding some text (there is lots of real estate there) to clarify what that "Update Channel" applicable to
- to not reset it by clicking "Check Feat. Update". If not intended to be ran without entry of the "Feat. code" - gray it out until value entered