Databus fault but to what is there no communication
- Thread starter Jlamuk
- Start date
Hmmm... obviously not an easy one.
Anything coding changes in 17-Instruments before/after towbar installation.
Have you got a VCDS Auto-Scan before towbar installation?
It is set to installed. I have also gone through the installation instructions on the pf jones website and all the adaptations appear to have been done (where the option exists, some of the listed adaptations don’t exist in my van) https://www.pfjones.co.uk/pfjoneswiringkits/19270574PF-VW-T6.1-19.pdf
Was there available VCDS Experimental coding view on 17-Instruments - to see if there is more information available.
Your coding in byte 12 differs from all other scans (checked 11 this far) - yours hex_24, others mostly hex_04 or a few hex_14
PS. Instead of photos you could make screen captures by pressing Alt-PrintScreen, and then paste into e.g. Paint, or directly in posting.
there is some VCDS Experimental coding view on 17-Instruments - but it is only for bit 0 noise/sound actuator installed and bit 2 alternative dimming function active. These were only changing the value from 24 to 20 or 21.
I did a manual coding change to make the 24 into 14 and now the Databus error has gone (thank you).
Are you able to tell me what the difference is between hex 24, hex 14 and hex 04? Although the problem appears to be resolved I would like to know what the problem was rather than just blindly accepting it as being resolved!
Sorry for the taking of photos of the laptop screen, there is no WiFi up the road at the barn and mobile signal is not good enough to tether the laptop to a phone.
That's excellent news
I'm also curious to know what's the difference. Need to look if I can find the common factor in my T6.1 scan collection - the trailer assist possibly onboard
Hex 24 = 0010 0100
Hex 14 = 0001 0100
Hex 04 = 0000 0100
Then in post here VCDS Fault 17: Instruments -Databus - Missing Message inst
the code was 34 with the same ARA_01 missing message
Hex 34 = 0011 0100
So common with both "faults" is the certain bit set.
Could it be that the kits are being shipped with instructions for a t6 where the “2” relates to a function in a t6 module and not in the t6.1 modules?That's excellent news View attachment 314109
I'm also curious to know what's the difference. Need to look if I can find the common factor in my T6.1 scan collection - the trailer assist possibly onboard
Hex 24 = 0010 0100
Hex 14 = 0001 0100
Hex 04 = 0000 0100
Then in post here VCDS Fault 17: Instruments -Databus - Missing Message inst
the code was 34 with the same ARA_01 missing message
Hex 34 = 0011 0100
So common with both "faults" is the certain bit set.
I suppose I could go through the adaptations in the pf jones instructions and see if anything has changed
Scanned through 58 of T6.1 Auto-Scans with same 17-Instruments (7LA 920 941 A). Only factory codings hex 04 (60%) and hex 14 (40%) were found.
I'm highly confident someone just had mistaken the coding. Also now the disappearance the ARA_01 message suggests that the 17-Instruments is not any more expecting to receive the message.
Trailer assist retrofit indeed has the byte 12 bit 5 set
I spent a bit of time today going though the adaptations in the instruments module and nothing has changed from what the adaptations should be when adding trailer electronics.Scanned through 58 of T6.1 Auto-Scans with same 17-Instruments (7LA 920 941 A). Only factory codings hex 04 (60%) and hex 14 (40%) were found.
I'm highly confident someone just had mistaken the coding. Also now the disappearance the ARA_01 message suggests that the 17-Instruments is not any more expecting to receive the message.
Trailer assist retrofit indeed has the byte 12 bit 5 set
If indeed someone made a change to the coding by accident or other it would be interesting to see what they were trying to accomplish.
Alternatively amidst vw’s cost cutting that appears to be everywhere in the t6.1 startline maybe vw were shipping them with what ever module they had in a box (possibly also due to short supply due to COVID) which in some cases led to miner compatibility issues
