its in firmware (Flash1.96_HW_0x44.bin, Flash1.96_HW_0x46.bin)
@ 3E00 offset
its in firmware (Flash1.96_HW_0x44.bin, Flash1.96_HW_0x46.bin)
@ 3E00 offset
alinutz198 (16th January, 2018)
can i read before firmware from mi interface?
what is pinout of 46 hardware interface
Anyone have clean loader v5?
contact me on PM
Clean = without Kolimer Logo on start
Last edited by relax80; 21st January, 2018 at 07:17 PM.
bibkare (23rd January, 2018)
You can get the loader without Kolimer's logo here.
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.
1 6 D (22nd January, 2018), alexm1 (21st January, 2018), bibkare (23rd January, 2018), fantomel (22nd January, 2018), H2Deetoo (23rd January, 2018), hartklep (24th January, 2018), jakuza (22nd January, 2018), liviudiaconu (25th January, 2018), mrle9 (24th January, 2018), SergeyIg (30th January, 2018)
For sellers, the text is a problem.
Chinese remove it and enjoy a lot of this free lunch
Hello to everybody!
I’ve been watching for this conversation for a quite long time. In summer even tried to report, that V2 loader with 17.8.1 were made mess with coding bits and adaptation channels description, but it was not possible for me to register on forum.
First of all many thanks for all, who are trying to make "it" work!
Yesterday I tried all combinations with my cable (Atmega162, FT232BM, HW Type 0x44). Unfortunately still fully functional version is only 11.11.0_En.
Loader V5 with 17.8.0_En or 17.8.1_En doesn’t evensee my cable! After pressing Test button in program, I’m getting “Interface: Not found” answer. Perhaps because of “BM”FTDI chip???
Loader V2 with 17.1.3En works fine from the first look: description of bits and adaptation channels are fine. But if I try to work with program a little bit longer (10-15 min), I’m starting to get “Communication lost with control module” massages. For example, if I start “Auto-Scan” procedure it’s in 100% cases never have been complete. Auto-Scan process always interrupts with massage “Communication lost”. And, that is most scared, during auto-scan process, program is messing with order of scanned control modules! It starts from 01 (Engine CM) than after some address (let’s say 19)program, instead of next control module, proceed querying 01 address ones again!
So unfortunately I can’t confirm, that V2 loader with 17.1.3_En is fully functional.
P.S. May be anybody have any idea, how to solve “Interface not found” answer on my cable with V5 Loader version???
Last edited by Vet; 23rd January, 2018 at 02:26 AM.
Bookmarks