Search results

  1. S

    VCDS not working after update

    Try booting your computer into safe mode with networking, and then try to perform the updates like that. Most likely some third party software like mouse or touchpad software is interfering with the ability to open the interface.
  2. S

    Blank screen when connecting through WiFi and Android mobile phone

    Can you please post a screenshot of exactly what you are seeing?
  3. S

    Blank screen when connecting through WiFi and Android mobile phone

    Have you tried opening VCDS-Mobile in a web browser like chrome? There is button for doing this from within the app if it has detected the interface, even if it hasn't loaded the page this should work.
  4. S

    VCDS mobile app (and HEX-NET) on my Android

    If you open VCDS-Mobile in a browser via IP address and then type in the page /autodata.txt something like this http://192.168.10.178/autodata.txt where the IP address is your interfaces IP address, the data might still be there if you haven't done another scan since.
  5. S

    VCDS Interface Config WiFi password doesn't accept 64 hexadecimal characters

    I believe the interface does not support a key length of 64 is why that is not being accepted. Do you have control of this wifi network? If so, the only thing I could recommend is changing the password to a format that the interface supports.
  6. S

    Vcds is intermittently working on one car.

    This sounds like it is not detecting that the ignition is on, are you sure the ignition is on and the interface is seated all the way into the DLC port?
  7. S

    Interface Update Fail

    What dataset version does VCIConfig show, is it 00000046? There could be a problem with the SD card in the interface, but you should still be able to use it with VCDS without this. You could try with the interface powered up, hold the red button down for about 50s. You should get a long beep...
  8. S

    Hexnet functionality suggestion - standard measuring blocks

    If entering the measuring block manually with the existing interface does not work, then there is an underlying problem perhaps with the way the interface is processing these values or perhaps a general communications issue with this control module. Presenting this info with a different user...
  9. S

    Hexnet functionality suggestion - standard measuring blocks

    It sounds like maybe this isn't compatible with your tune. If you want to make a debug log for one of the blocks that's not working, say 18, the process would be like this: [Options] -> debug level:001f [Submit] then go to measuring values, put 18 in the field as described above and [Submit]...
  10. S

    Hexnet functionality suggestion - standard measuring blocks

    So what happens when you type 14 in the field and click submit?
  11. S

    Hexnet functionality suggestion - standard measuring blocks

    If I understand correctly, you are wanting to manually view a block by group number in a non-UDS controller? You can do this by typing the number like "11" into the search field on the measuring values selection page and then hit [submit] it should manually pull up the group even if that group...
  12. S

    Interface errors

    FWIW the English VCIConfig 2.301 build was last done on 12/6/22. If the files were touched since then they may have been re-signed or something, but the underlying build did not change. I wonder, could this be a case of a program like windows defender maybe sandboxing VCIConfig do to a false...
  13. S

    Interface errors

    Do you have DELL or Alienware mouse or touchpad software installed? If so, try closing that software either from the taskbar or taskmanager.
  14. S

    Interface errors

    Have you read through this thread? There are a number of tips on how to resolve this issue.
  15. S

    VCDS-Mobile stuck on K-line

    You could try mounting the card on windows and running a disk clean, that might be able to fix it. If the card is readable but just won't write, you could also try copying the data to a new card.
  16. S

    VCDS-Mobile stuck on K-line

    If you are trying to make this log through VCDS-Mobile, then the debug level would be 001f. See if that makes the log.
  17. S

    Buzzer inside HEX-2

    It indicates on certain error conditions of the interface/vehicle, such as alerting for a stuck K-Line. It is more used on the HEX-NET interfaces, where it also indicates for some SD card problems and SD card reset, as well as indicating on button presses for switching wifi mode.
  18. S

    VCDS-Mobile stuck on K-line

    Sure, if this is with VCDS 1028 debugs are a good start. Can it talk to the other modules individually?
  19. S

    Connecting without a PC

    You had several Dataset Updates to perform, and without a PC these need to be done incrementally, please continue with the updates until it says you are up to date.
  20. S

    Connecting without a PC

    I have switched your interface to the beta updates channel, where there is a newer dataset available. Please check for updates again to download that update, and then try the scan again.
Back
Top