Carista not picking up fault code

tomlinp76

Registered User
Hi, wondered if anyone can help answer this question.

I bought into Carista to try to help diagnose a lighting malfunction fault, however only once have I been able to return an error code with it (930056 Light Switch). Subsequently when I've tried to re-scan, the app gets 30% through, the fault clears from the display, and I'm told zero errors. Within 20 seconds the bing and message pop up again.

If I physically disconnect the switch, it will return a different fault code due to no communication.

What seems to be happening is by doing a diagnostic scan, Carista has done something to clear the fault, before it's got to 100% completion, therefore not really helping me!

Is this down to the basic £15 nature of the Carista OBD2? I take it that VCDS provides a deeper scan of all modules? I was hoping Carista would help me before shelling out on a replacement identical part.

Cheers.
 

V6_Man

Moderator
Staff member
Moderator
VCDS Map User
Hi, wondered if anyone can help answer this question.

I bought into Carista to try to help diagnose a lighting malfunction fault, however only once have I been able to return an error code with it (930056 Light Switch). Subsequently when I've tried to re-scan, the app gets 30% through, the fault clears from the display, and I'm told zero errors. Within 20 seconds the bing and message pop up again.

If I physically disconnect the switch, it will return a different fault code due to no communication.

What seems to be happening is by doing a diagnostic scan, Carista has done something to clear the fault, before it's got to 100% completion, therefore not really helping me!

Is this down to the basic £15 nature of the Carista OBD2? I take it that VCDS provides a deeper scan of all modules? I was hoping Carista would help me before shelling out on a replacement identical part.

Cheers.

Why don't you use the VCDS map and find a member closer to where you live. I am sure they'll be happy to scan the car for you for a few beer tokens.

It appears to me that that the OBD connector has decided to not work.
 

tomlinp76

Registered User
Thanks I’ve done just that, vcds should provide the info I need before going out and buying another light switch!

Cheers
 

rum4mo

Registered User
That is unfortunate, I've found that Carista will always reveal any faults that VCDS will, but for some newer controllers, Carista is a bit behind with handing over a correct fault definition.
I use Carista only for "on the road" fault reading, VCDS for everything else.
Carista's "one click" code changing is handy though for people that maybe should not be dabbling in code changing!
 

tomlinp76

Registered User
Thanks, it appears that Carista and VCDS would not show the fault code that was causing the bulb malfunction light to come on. Eventually after visiting a couple of specialists, I had to go back to the dealer. They sorted it quickly, identifying a module software miscommunication. They reloaded the original software update meant for the A3 2014 model.

In the end it seems one of those issues that only a dealer with access to a range of past software updates was able to solve. A surprise really, as most independents with VCDS and ODIS seem to be able to do everything else...

I've still got Carista by the way, at the price I paid for it, it's great to have in the glove box just in case...
 
Top