There is any chance to test on "the bench" CAN conection? What module can I take apart from a car, power on 12v, wiring to interface an give a have test(options-test-k1k2 Can-ok)?
There is any chance to test on "the bench" CAN conection? What module can I take apart from a car, power on 12v, wiring to interface an give a have test(options-test-k1k2 Can-ok)?
And I will get CAN -Ok?
If I remember well Golf MK4 does not have CAN.
It could have it, communicate through "can" between some ecu's or devices but diagnostics are still through K line.
Better find ecu from mk5 or passat b6.
Last edited by kaalis; 16th March, 2018 at 06:54 PM.
alexm1 (16th March, 2018)
Yes, it will show CAN - OK..
i'm fixing VCDS cables like for 8 year.. i have on table AirBag Module to test all communications.. for airbag you can even disconnect K line and it will talk via CAN "TP 1.6 - 1281" protocol..
canok.jpgprotocol.jpg
When I will get airbarg module or a Can gateway module, I will aks for your help for wiring to the cable if you got time.
Thank you.
Last edited by alexm1; 17th March, 2018 at 02:08 PM.
after update succesfuly executed. i have that error.
unknown version. unknown2.jpg
and do not do update to firmware in interface vcds 17.1.3
unknown1.jpg
Well, recheck fuses, wiring and do it again.
I'm using Kolimer's 6.3 loader on VCDS 18.2
I was previously using VCDS 17.1
In January, I had to reflash my cable because the license was deactivated. Reflashing it made it so the CAN connection would appear as "OK" when you test, but there are certain modules which do not respond when trying to open them using VCDS. Previously (before the license was invalidated) I was able to access these modules - for example, the instrument cluster. Now it takes a very long time for the module to open and when I open the fault codes, it says that the DTC's aren't supported by the controller or that the module wasn't communicating. I read somewhere that 17.1 had issues with CAN connections, but updating to 18.2 did not fix it. I'm not sure if this is an issue specific to my vehicle (maybe the module is actually bad) or there is an issue with the cable/software. Has anyone else had this issue or heard of it and how did you fix it? Thanks!
i have checked and rewriting v1,v2,v5,v6 .
all write succesfuly. but same error apear.
unknown version
unknown1.jpg
and when vcds 17.1.3 try to do update
unknown2.jpg
Hardware Type HW 0x46 : no connection from ATMega162 pins 34 and 35 to GAL chip.
use extremeburner for chip erase the atmega.then rewrite with . bat and avrdude
Maybe your .bin files are corrupt. Check with md5 / sha256 checksum:
f711a3b077037e69952d94b31adb89a7d8eebb433d4929a058 084ca9a7da6e99 eepromavr_HW_0x44.bin
30b2e5465a5cc5d83e579ce4c3ede4eba24554949d5bf6f8fd 51105252d9479c eepromavr_HW_0x46.bin
d66c037de99f4cf3c4084d117b129974838a64b6d8b730235b c32f17226c8e65 Flash1.96_HW_0x44.bin
74dd842393635f4e0e582eb5e673ebbeeec66c7980413c9773 c53d13d9c5e1c9 Flash1.96_HW_0x46.bin
9d63c66029b3cc9843a93f6fc58e5e56 eepromavr_HW_0x44.bin
62d0fe850389c6c9ef419c7d9027da1e eepromavr_HW_0x46.bin
dae92be3ad5109999685a9b7df3c8b9f Flash1.96_HW_0x44.bin
e50a34ec175d178f5ed60376c316a680 Flash1.96_HW_0x46.bin
Bookmarks