lemta (12th June, 2019)
Will the cable not get killed if the serial is blacklisted in the software? There is no known way to flash it to work again if that is the case.
What I also don't understand is how it is so easy to just install the software on the ARM cable whereas everyone else with ATmega162 chip needs Kolimer's modified loader in order to bypass security. How can it be that easy?!!
NEC and ARM devices are not killed.
The device will work. Of course, provided that this device works with version 17.1.3.
lemta (12th June, 2019)
Big Thanks kolimer
Thanks, interesting. Got it working on cable that was "made" for 17.8.0 version. Did connect engine ecu through CAN but K lines in cable were already fried before.
One observation. RT-usb.dll is missing in C-Tools directory for C-test.exe to run properly.
This version is using 32bit vcds.exe from original 19.6.0 released May 31th.
Just a guess: modified RT-usb.dll and custom RT-logs.dll?
Last edited by kaalis; 12th June, 2019 at 09:30 PM.
Well, something must be different from the original.
And what about CAN commands sniffer. C-Sniffer.log can be useful when simulating blocks when debugging. When deciding the issue with MY 2019+.
So I installed v19.6.0c onto my cable shipped with v17.1.3 ARM chip. It activated ok but when doing auto-scan from modules 44 onwards IIRC it errors cannot access the modules. When it gets to the end the application closes itself down.
EDIT: Also there is no way to cleanly uninstall software. I am running 64bit Windows 10 - could the 32bit v19.6.0 be the problem? EDIT2: Actually I'm not even sure the v19.6.0c is 32bit version, just thought I read something that it said it was.
Last edited by lemta; 12th June, 2019 at 10:55 PM.
Last edited by Roma77; 13th June, 2019 at 06:59 AM.
I checked the VCDS-HC-19.6.0 c version by connecting on the table to 2 units
1- the 2010 dashboard
2 - the 2006 getway using the ATmega cable and noticed a few features
1) When you first connect the cable sees the installation sheet but after a short time it ceases to see it
The first connection
g.JPG
after a short time
g2.JPG
To make everything work you need to close and reopen VCDS
2) Connecting to the dashboard writes "Unsupported Vehicle" although it is 2010 release
u.JPG
3) If immediately after you run VCDS to connect to supported units that it will work, but if you hold the connection he always will write "Unsupported Vehicle"
Immediately after the launch of VCDS
u3.JPG
After a short time after starting the VCDS
u2.JPG
C-Sniffer Work better)
s.JPG
Col19 (25th June, 2019)
Funny enough that both, "Unsupported vehicle" and "Function not supported by GW" are Dicatator's issues...
I can calculate ABS module codings for:
* Continental/Teves MK60EC1 and MK60;
* TRW systems in Passat B6 / B7 / CC /Tiguan;
* MK100;
* Bosch ABS8.2, ABS9.0 and ESP8.2, ESP9.0;
* EBC 460 (UP!, Mii, Rapid, CitiGo, Fabia, Toledo, etc) New!
* ... and other VW/Audi/Seat/Skoda modules.I can assist with repairing \/CDS interfaces.
Bookmarks