[anass_f]

I'm a bit confused. I'm currently installing the 10.0 PostSetup -kindly shared by Tadk- onto ODIS7.2.1 because I have VAS5054A only and obviously I'd like to work on the newest cars as well. But, what's the purpose of having a 10.0 PostSetup -also kindly shared by Tadk- installed onto ODIS 8.2.1? AFAIK, ODIS 8.2.1 doesn't support 5054, so a VAS6054A should be present, so why not just install a standard ODIS 10?

[Tizen99]

A reason could be that newer Odis versions can have some bugs, so using an older version can be more stable, especially because Odis 10 has a new programming language.

[Tadk]

I'm a bit confused. I'm currently installing the 10.0 PostSetup -kindly shared by Tadk- onto ODIS7.2.1 because I have VAS5054A only and obviously I'd like to work on the newest cars as well. But, what's the purpose of having a 10.0 PostSetup -also kindly shared by Tadk- installed onto ODIS 8.2.1? AFAIK, ODIS 8.2.1 doesn't support 5054, so a VAS6054A should be present, so why not just install a standard ODIS 10?

8.2.1_test for clone 6154

[tu329]

I have a problem with ODIS-S...

I installed Fantomel's copy of ODIS-S 7.2.1 and Windows 10 drivers for VAS5054A (I have original VAS5054A, bought it from official VW service when they changed to newer VAS6154A). VAS is normally detected in device manager. Also ODIS-S can see the tool. You can also read VIN and start the diagnosis. BUT then the problem occurs: "This is a CAN vehicle but communication with Gateway is not possible." Picture: https://imgbb.com/JQvLvf4
You can read ECU, ABS, and some other modules, but not Gateway, body module, central electrics etc.

I tried it on more cars (Skoda Octavia 2 redesign, Skoda Yetti, VW Golf Mk5, VW Passat 3C) and problem stays the same. Also I tried connecting VAS5054A over the bluetooth or USB. Nothing helps.
That same VAS5054A was working on Windows 7 virutal machine and ODIS-S version 5.something (I forgot the correct version).

I contacted Fantomel and he told me to try with tadk's post setup. So I did update my ODIS-S to tadk's post setup, but problem stays exactly the same!

Does anyone have even slightly idea what is wrong and how to fix my problem? I am out of ideas... :\

I have same problem before .  and after install both java jdk-8u281 & jre-7u45 Fix the problem . you can try it . Everything is ok .

[SerjP]

I spend some time by installing ODIS-S 5.1.6 on Win7x64 having original Postsetup (and native VAS5054a support) and then comparing its GFF log with ODIS-S 7.1.2 1980_test on Win10x64 (using VAS5054a installer by @phantomel) to check if there any missing or extra info available in logs. Found some differences, see the screenshots. GFF was performed on the same car having no any DTC errors.
   

Diffs:

• Section 'Error messages outside guided fault finding:' for both ODIS versions contains the same errors. So I guess they are not related to 1980 Postsetup migration.
     
  
• 1980_test has more untranslated German steps (both ODIS's have en_GB language selected for Postsetup and both ODIS's were switched to same en_GB in Admin)
         
  
• Number of test steps performed more or less the same, they order is slightly different between both ODIS's. All modules are identified identically. All coding and adaptation read the same.
  
• 'Function test 7: ID75_X_1_1216_11_00000' despite the red error has better description in 1980_test: 'No response from the control unit: Emergency call module and communication unit'. There are no such a unit in my car, so the error is expected. BTW both have the same 'Result: X'.
     
  
• A lot of valuable information is missing from the 1980_test version from 'Background checks' section like:
  Transmission mileage, Electromechanical parking brake statistics, Steering wheel angle load, Engine specified torque load, Cruise Control System (CCS), status, etc.
         
  
• Engine code 'CXSA' can be found in ODIS 7.2.1 log and not mentioned in 5.1.6.
  

In general, almost all the information is the same. But I'm a little worried about the lack of some important data in the "Background checks" section in 1980_test. I'm debating whether or not to revert to 5.1.6 as it has more info available, better translation, and I don't plan to read fresh cars.
Hope you enjoyed the comparison.

[jhon006]

Test 1980 Vw pasat 2010 2.0 Cr all Ok Guided fault finding
Vas 6154

[jo27hn]

Test 1920 skoda fabia 2019 all ok vas 5054
Test 1920 audi q3 2021 all ok vas 5054

[daMassa]

I have a problem with ODIS-S...

I installed Fantomel's copy of ODIS-S 7.2.1 and Windows 10 drivers for VAS5054A (I have original VAS5054A, bought it from official VW service when they changed to newer VAS6154A). VAS is normally detected in device manager. Also ODIS-S can see the tool. You can also read VIN and start the diagnosis. BUT then the problem occurs: "This is a CAN vehicle but communication with Gateway is not possible." Picture: https://imgbb.com/JQvLvf4
You can read ECU, ABS, and some other modules, but not Gateway, body module, central electrics etc.

I tried it on more cars (Skoda Octavia 2 redesign, Skoda Yetti, VW Golf Mk5, VW Passat 3C) and problem stays the same. Also I tried connecting VAS5054A over the bluetooth or USB. Nothing helps.
That same VAS5054A was working on Windows 7 virutal machine and ODIS-S version 5.something (I forgot the correct version).

I contacted Fantomel and he told me to try with tadk's post setup. So I did update my ODIS-S to tadk's post setup, but problem stays exactly the same!

Does anyone have even slightly idea what is wrong and how to fix my problem? I am out of ideas... :\

I have same problem before .  and after install both java jdk-8u281 & jre-7u45 Fix the problem . you can try it . Everything is ok .

Thanks for idea! I reviewed my Java installations and found out that I had only JRE 64bit. When I installed 32 bit version I got a little bit of breakthrough. I don't have CAN error message anymore but still it can't read out gateway and rest of the processors.

Now I will try isdochegal's method from the page before and I will let you know the results.

[daMassa]

Try the file from the attachment and report.
This has already helped some people with the CAN problem. It's just a self-extracting Winrar archive that I made myself.

I tried your method. Unfortunately its even worse then it was. Now ODIS can't see VAS communication at all.
VAS is recognized by computer - everything OK in device manager. Also, EDIC app can see VAS, and its saying that USB connection is OK. But ODIS can't recognize connection with car (car symbol with question mark, key symbol with question mark). So no luck with this patch, at least for me.

Two dead ends for now. Tu329's idea with Java didn't resolve the problem and your patch didn't help.
I will try to extract VM with old ODIS from laptop that died on me, and try if my VAS is still okay or maybe gone bad.

To all others: when you start up ODIS without VAS tool connected, what do you see under Extras (right menu) > Diagnostic Interface ?
Is it normal to see VAS5054  (or whatever tool you have) even if there is no VAS tool connected to laptop?

[SerjP]

Try the file from the attachment and report.
This has already helped some people with the CAN problem. It's just a self-extracting Winrar archive that I made myself.

I tried your method. Unfortunately its even worse then it was. Now ODIS can't see VAS communication at all.
VAS is recognized by computer - everything OK in device manager. Also, EDIC app can see VAS, and its saying that USB connection is OK. But ODIS can't recognize connection with car (car symbol with question mark, key symbol with question mark). So no luck with this patch, at least for me.

Two dead ends for now. Tu329's idea with Java didn't resolve the problem and your patch didn't help.
I will try to extract VM with old ODIS from laptop that died on me, and try if my VAS is still okay or maybe gone bad.

To all others: when you start up ODIS without VAS tool connected, what do you see under Extras (right menu) > Diagnostic Interface ?
Is it normal to see VAS5054  (or whatever tool you have) even if there is no VAS tool connected to laptop?

Yes VAS5054 is displayed with no tool connected