Search results

It sounds like the interface doesn't have good enough signal strength in the car to stay connected to your home wifi. You might want to try an OBDII extension cable to move the interface from down in the footwell to up on the dash where it can get better signal, or see if you can move the car...

What color are the LEDs? Have you tried a different USB cable such as one that is known to work with a different interface?

If it were me, I would install VCDS on that windows 10 pc, then you can update the interface with VCIConfig much more easily, and if you encounter something that doesn't work through mobile you can use full VCDS on that PC.

Are you saying that VCDS on a PC works to scan now, but VCDS-Mobile is missing half the modules from the scan? If so, can you post the part of the mobile autoscan you were able to get?

If you are willing try making a debug log: VCDS [Options] -> Debug level=1024 [Save] then reproduce the problem, email the debug log from the vcds/debug folder to support@ross-tech.com

Have you tried this with VCDS on a PC? Also if you need ASAM data for mobile, you should try connecting the interface with USB and checking for updates via VCIConfig it should download the rod files.

What does the updates tab in VCIConfig show, have you tried to update like that with PC and interface connected via USB or is it not found by VCIConfig either?

If you switch to the beta channel you will need to repeat this update again, you just downloaded the release channel rods. But go ahead and see how that works, on this year vehicle I doubt the beta has any better coverage. If you cleared the rod data, you may need to repeat this update again...

Bump for beta CB V0.4656 * Support for larger packets needed by certain platforms

Most clicks should not take 4-5 seconds, that sounds like maybe there is a lot of congestion in your wifi environment or the signal strength is bad? You might want to try connecting the interface to a PC and updating with VCIConfig to download the asam data, this can remove your phone and wifi...

Please try switching your interface to the beta channel as described in your other thread here: https://forums.ross-tech.com/index.php?threads/45219/post-367434 Then try the autoscan with mobile again and see if it has coverage for this updated module. You might need to check for updates again...

With the interface connect to PC via USB, in the [Advanced] tab of VCIConfig please try switching your interface to the beta channel and then [Check for Updates] download the set of updates that is available there. In the [Options] page of VCDS-Mobile you should now have a [Bypass DoIP]...

The mobile functionality is not at the same level of support as PC, but it should be able to decode fault codes, do you still have issues with this?

You might want to try switching your interface to the beta channel via the advanced tab of VCIConfig and then check for updates to download the newer dataset that is there which might have better coverage. You may need to do another autoscan and check for updates again to get the newer rod data...

You need to be able to get the rod/ASAM data for this to work, try connecting the interface to a PC with USB and then check for updates using VCIConfig.

Have you tried using a different PC to update the interface and get around this issue?

You might want to try switching your interface to the beta channel in the [Advanced] tab in VCIConfig, and then checking for updates again to download that new dataset and see if it has better coverage.

Was anything else updated on the PC?

Ok data sample rate should not be zero Hz, it sounds like some kind of comms issue here. If you are willing you can try to make a debug log of this, in VCDS-Mobile [Options] -> debug level= 001f [Submit] then go to a session and try to run measuring values, let it run for a minute then back...

I will look into this, but for now you can always click into the log, click [Download Log] and then attach it to an email yourself.