VAG-COM/VCDS EVERYTHING

[Laique]

Hi guys!
Glad that i found this topic :)

I'm looking for an upgrade to 18.2 or maybe 18.9. (This cable works now with 17.1.3.)

There are few things i dont know and hope you can help me.

Here is my cable that came to me last week.

583250

VAGCOM_HWTYPE tells me its:
FW Version: 1.96
HW Version: 0x46

Files that i've found in this thread seem to have the same FW version.

583251

What should i do now?
Do i still have follow the FirmWare upgrade procedure or do i just have to install the newer VCDS, then crack it with VCDS_Loader, and then update the cable using VCDS?

thx

Seriously NOBODY ?!

[eliteland786]

Not pin 1 of FTDI but rather pin 25, I believe. Check the chip orientation!

The EEWrite tool reflashes it to the same HW as it was flashed before. It's impossible to flash it to different one because of different bootloader size/different fuse bits.
In order to reflash from 0x46 to 0x44 you will need to do that using AVR programmer (e.g. USBASP)
No it's definitely pin 1 next to the dot...looked at schematic and that's pin 1.

Not going to bother with re flashing with AVR programmer if it's working let it be.

[eliteland786]

No it's definitely pin 1 next to the dot...looked at schematic and that's pin 1.

Not going to bother with re flashing with AVR programmer if it's working let it be.

Pin 1 is TXD and pin 25 is ground...AGND.

[Elektrik1]

Some progress, made - developed Arduino Mega based bruteforce interface with GAL slot and tested with GAL from working 0x44 cable, chip works fine after such manipulations :)
583320

Wrote simple program to toggle each pin and check remaining pins state:

void setup() {
Serial.begin(115200);
//Main loop
for(int i = 22; i<=39; i++){
//Pin configuration loop
for(int j = 22; j<=39; j++){
if(i == j){
//Set togg'able pin as output
pinMode(j, OUTPUT);
}else{
//All other pins as input (high impedance)
pinMode(j, INPUT);
}
}

//Toggle output high
digitalWrite(i, HIGH);
for(int j = 22; j<=39; j++){
//Skip checking togg'able pin from reading
if(j == i) continue;
//Check if input is high
if(digitalRead(j) == HIGH){
//Print values to UART
Serial.print(i);
Serial.print(" ");
Serial.println(j);
}
}
//Toggle pin back
digitalWrite(i, LOW);
}

}

TODO: implement code for each combination toggle; Karnaugh map minimizer for logic generation.

Results:


OUTPUT PIN 1-(10 skipped, GND)-19

INPUT PIN 1-(10 skipped, GND)-19


1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

-
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1


0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

1
-
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1


0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

1
1
-
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1


0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0

1
1
1
-
1
1
1
1
1
1
1
1
1
1
1
1
1
1


0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0

1
1
1
1
-
1
1
1
1
1
1
1
1
1
1
1
1
1


0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0

1
1
1
1
1
-
1
1
1
1
1
1
1
1
1
1
1
1


0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0

1
1
1
1
1
1
-
1
1
1
1
1
1
1
1
1
1
1


0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0

1
1
1
1
1
1
1
-
1
1
1
1
1
1
1
1
1
1


0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0

1
1
1
1
1
1
1
1
-
1
1
1
1
1
1
1
1
1


0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0

1
1
1
1
1
1
1
1
1
-
1
1
1
1
1
1
1
1


0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0

1
1
1
1
1
1
1
1
1
1
-
1
1
1
1
1
1
1


0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0

1
1
1
1
1
1
1
1
1
1
1
-
1
1
1
1
1
1


0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0

1
1
1
1
1
1
1
1
1
1
1
1
-
1
1
1
1
1


0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0

1
1
1
1
1
1
1
1
1
1
1
1
1
-
1
1
1
1


0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0

1
1
1
1
1
1
1
1
1
1
1
1
1
1
-
1
1
1


0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0

1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
-
1
1


0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0

1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
-
1


0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1

1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
-




As it seems things get tricky, as it seems from datasheet, GAL can be configured as clocked, and registered modes:
583321

So for further investigation I need someone who can tell about known 0x44 configuration (additionally to C3H8 logic), as well as create .JED file with known logic to check if bruteforcer works fine.

Cheers :peaceful:

[Roma77]

Elektrik1 (https://www.digital-kaos.co.uk/forums/member.php/493316-Elektrik1)

The algorithm of work and programming CUPL of FPGA is well described in this article. https://justmoose.ru/?p=17


Laique (https://www.digital-kaos.co.uk/forums/member.php/619849-Laique)
Please read the info file in the kolimer folder, as well as several pages of the forum and you will find the answers.

Please read the info file in the colimer folder, as well as several pages of the forum and you will find the answers.

[schmiddie1982]

Hello @LL,

can someone reupload the newest loader for \/CDS 18.9.0 (DRV) German and the firmware files please ?

Thank you in advance.

Best regards

schmiddie1982

Gesendet von meinem F8331 mit Tapatalk

[kaalis]

What should i do now?
Do i still have follow the FirmWare upgrade procedure or do i just have to install the newer VCDS, then crack it with VCDS_Loader, and then update the cable using VCDS?
Run VAGCOM_HWType.exe to see if you have locked bootloader, then VAGCOM_EEWriteLang.exe if it's not locked and you don't know how old vcds version was used for it, use loader, and then update firmware after port test.



can someone reupload the newest loader for \/CDS 18.9.0 (DRV) German and the firmware files please ?
Check last post from Kolimer, there are still some loader links active.

[Laique]

Run VAGCOM_HWType.exe to see if you have locked bootloader, then VAGCOM_EEWriteLang.exe if it's not locked and you don't know how old vcds version was used for it, use loader, and then update firmware after port test.

Check last post from Kolimer, there are still some loader links active.

thx. for the answear man!

583371
This is all what VAGCOM_HWType.exe is telling me. How do i know if the bootloader is locked ? The cable works with 17.1.3 now.

[kaalis]

That exe is not from 7.2 loader.
Anyway you can try eewrite and it will tell if it's not in bootloader mode or flash it succesfully.

Don't forget to plug it in obd2 port while flashing.

[Laique]

That exe is not from 7.2 loader.
Anyway you can try eewrite and it will tell if it's not in bootloader mode or flash it succesfully.

Don't forget to plug it in obd2 port while flashing.

THANKS A LOT!

The VAGCOM_HWType.exe from 7.2 shows the bootloader is enabled! i will start with VCDS 18.2.0 ENG.
Is the 18.9.0 stable 100% ?

[kaalis]

Latest not very, but you can report your findings in this topic.

[GianniNOS]

Hi, is possible to repair this cable?

[alexm1]

Yes, you can. But first you need "kill" STC, see how in info.pdf from Kolimer zip.

L.e.
You may need to use usbasp programmer, I do not think will work by usb, but you can try...

[liviudiaconu]

hid3, they are, you can see it in screenshots and my reverse engineered schematics, I have 3 of such cables


About your schematic i don't see K-line and L-line Rx. K-line and L-line are bidirectional.
If that transistor with emiter "in air" i assimilate as a diode, can be Rx. And go on 17 and 19 pins of GAL. Thet mean that pins are IN, not OUT.
Look as a correct schematic for a 44HW, not transistors but correct and can see the Rx (K/L lines)

[Laique]

Got the 18.2.0!!! It's ALIVE! :)

@KOLIMER! WHEREVER YOU ARE, GOD BLESS YOU.

Small tribute for you man! ;)
583433

[Elektrik1]

That schematic is for 0x46 transistor based output. You are correct, they are using transistors as diodes, together with zeners it performs level shifting 12V->5V.


About your schematic i don't see K-line and L-line Rx. K-line and L-line are bidirectional.
If that transistor with emiter "in air" i assimilate as a diode, can be Rx. And go on 17 and 19 pins of GAL. Thet mean that pins are IN, not OUT.
Look as a correct schematic for a 44HW, not transistors but correct and can see the Rx (K/L lines)

Thanks to Roma77 example, I have set up known GAL:
583442


which output PIN 9 LOW only when PIN 2 and PIN 3 are low.

Adjusted Arduino code a bit:

unsigned long pow2(unsigned long p){
return 1UL << p;
}

void set_output(unsigned long a){
for(unsigned int i = 22; i<=39; i++){
unsigned long pn = pow2((unsigned long)(i-22));
pn = ((a & pn) == pn);
Serial.print(!pn);
if(pn){
pinMode(i, OUTPUT);
digitalWrite(i, LOW);
}else{
pinMode(i, INPUT_PULLUP);
}
}
}


void setup() {
Serial.begin(500000);
//Main loop
for(unsigned long i = 0; i<=pow2(18UL)-1; i++){
Serial.print(i);
Serial.print("\t");
set_output(i);

unsigned long res = pow2(18UL)-1UL;
for(int j = 22; j<=39; j++){
if(digitalRead(j) == LOW){
bitClear(res, j-22);
}
}

Serial.print("\t");
Serial.println(res);

}
}

And got such input (attachment). Results are good, 262144(including all zeros) combinations on all pins. Now performing on 0x46 GAL. :itsme:

[eliteland786]

Got the 18.2.0!!! It's ALIVE! :)

@KOLIMER! WHEREVER YOU ARE, GOD BLESS YOU.

Small tribute for you man! ;)
583433

Well done...nice touch.

[heshamzn]

hi all im new and i think i cant program my vcds with flash or whatever im not expert on this things but any way that's my vcds and my question can i use it with vcds lite ??
it gives me error message about license and cant check the car with it any more
583451

[Elektrik1]

Performed scan of 0x46 GAL, performed reconstruction using MATLAB, got 31 different cases, as it can be seen, CLK pin and pins >9 does not influence on output logic. GAL logic can be reconstructed with this truth table.

583453

But it's incorrect, since I have filtered out rows by selecting only unique XOR'ed differences of input-output, which hides output pins changes. So I am leaving capture and formatted (raw) input combinations (187498 occurrences, including changing input pins) as an attachment. Every integer represents bit sequence in such manner: PIN1,2,3...9,11,12,...19. According to schematics, PIN 17 and PIN 19 should be inputs, not sure about OE pin.

[alexm1]

hi all im new and i think i cant program my vcds with flash or whatever im not expert on this things but any way that's my vcds and my question can i use it with vcds lite ??
it gives me error message about license and cant check the car with it any more
583451If you can get usbasp programmer and read more on this thread you will manage to repair your cable, if not ...make China happy and buy a new one. I did not try to make it worked with vcds lite as long it is suppossed to work with full program. If vcds lite it is enought for you, than buy a simple kkl cable and will do the job for lite version: search kkl or 409 cable.

[xoom]

Made small application that decrypts firmware from "vi si di es" :very_drunk:

[heshamzn]

If you can get usbasp programmer and read more on this thread you will manage to repair your cable, if not ...make China happy and buy a new one. I did not try to make it worked with vcds lite as long it is suppossed to work with full program. If vcds lite it is enought for you, than buy a simple kkl cable and will do the job for lite version: search kkl or 409 cable.

I will make my self happy and buy one usbasp programmer do i need to buy any thing else ?

[GianniNOS]

Hi, is possible to repair this cable?

anyone in Italy can repair for me this cable? will contact me in pm please
thanks

[alexm1]

@heshamzn

It is necessary to solder 4 wires coresponding those 4 holes to your pcb. You need to power up your cable with 12v from a power supply or direct from your car-obd2.

[DKa0S]

Both A6 2.5 V6 TDi '01-'04 CAN not ready. Why?

[Mario6]

Because there is no "CAN" only "K".

[DKa0S]

Reading very bad or nothing. Can't access. Dunno! No auto scan?


4 Faults Found:
01441 - Low Fuel Level Sensor (G210)
30-10 - Open or Short to Plus - Intermittent
01441 - Low Fuel Level Sensor (G210)
27-10 - Implausible Signal - Intermittent
18057 - Powertrain Data Bus
P1649 - 35-10 - Missing Message from ABS Controller - Intermittent
00741 - Brake Pedal Monitoring
27-10 - Implausible Signal - Intermittent
Readiness: N/A

3 Faults Found:
01441 - Low Fuel Level Sensor (G210)
30-10 - Open or Short to Plus - Intermittent
01441 - Low Fuel Level Sensor (G210)
27-10 - Implausible Signal - Intermittent
18057 - Powertrain Data Bus
P1649 - 35-10 - Missing Message from ABS Controller - Intermittent
Readiness: N/A

2 Faults Found:
18265 - Load Signal
P1857 - 35-10 - Error Message from ECU - Intermittent
17087 - Brake Switch (F)
P0703 - 35-00 - Electrical Malfunction

49-10 - No Communications - Intermittent

[Mario6]

In newer cars there is a better description of fault codes, frozen frame and others.

http://wiki.ross-tech.com/wiki/index.php/Category:Fault_Codes

[DKa0S]

If I try to read manually it very hard reading or nothing, no communication or no accsess etc like ABS; Central Elect. In must be read normally?

[Mario6]

Maybe try reflash (update again) Atmega 162 in your cable. I also had problems with connecting in Audi A6 2.5 TDI (2001 and 2003my). I was connecting faster with vag kkl and vcd$ lite 1.2.

[heshamzn]

@heshamzn

It is necessary to solder 4 wires coresponding those 4 holes to your pcb. You need to power up your cable with 12v from a power supply or direct from your car-obd2.

How to power it up with my car obds ?? i think i will make china happy cuz i don't understand this thing att all

[DKa0S]

I'll! Maybe ABS control module fault, ECU reflashed, faulty or brake light switch faulty. I read that brake switch could cause that problems He replaces them and we will try again!

[macwol01]

Even cheaper version of the cable you refer to:
http://www.obd2cartool.com/vagcom-1684-full-active-vcds-1684-diy-vag-com-1684-can-reprogram-language-and-version-p-1266

Basically it's the same just older version but you can always reflash to Kolimer's.

These cables fully support VW Golf 6 (5K).
These cables support K2 with both jumpers (J1 and J5) removed).

What is the jumper setup for a 2014 Seat Leon F5 184 TDI mate ?

My cable is the same as this so after reading 384 pages not come acroos this snipet of info before.

[Tib82]

Hi Guys,

First of all I wish you a Happy New Year!

I checked Kolimer's v7.x packages and it's not clear to me why they have EEWriteLang and HWType files with different file size or data structure. What are the differences between them?
Eg:
EEWriteLang in v7.0 = 927,0 kB
EEWriteLang in v7.1 or v7.2 = 929,0 kB

[kaalis]

eewrite autodetect vid/pid checkbox, hwtype detects bootloader status.
Anyone can see those changes.


What is the jumper setup for a 2014 Seat Leon F5 184 TDI mate ?
Keep both jumpers removed and you will be fine.

[C3H8]

Elektrik,
at least I have problems to follow you.

My suggestion would be:
Let's focus on 32 combinations for input pins 2,3,6,7,8. These pins select the routing of other inputs (11,19,17,5,14) to outputs (18,16,12,13,15).
If you provide the result (which output is following a toggle on which input?) for every of these 32 combinations on pin 2-8 we have the logic.

A GAL 16V8 have some restrictions: pins 1 - 11 can only be an input, pins 12-19 can be both.

Happy new year!




Performed scan of 0x46 GAL, performed reconstruction using MATLAB, got 31 different cases, as it can be seen, CLK pin and pins >9 does not influence on output logic. GAL logic can be reconstructed with this truth table.

583453

But it's incorrect, since I have filtered out rows by selecting only unique XOR'ed differences of input-output, which hides output pins changes. So I am leaving capture and formatted (raw) input combinations (187498 occurrences, including changing input pins) as an attachment. Every integer represents bit sequence in such manner: PIN1,2,3...9,11,12,...19. According to schematics, PIN 17 and PIN 19 should be inputs, not sure about OE pin.

[Elektrik1]

C3H8, Happy new year!

I have already dumped 0x44 and tested if everything corresponds, it fits fine your logic, also shows how different bits (XOR) corresponds to ones that are produced by you decompiled logic. The hardest part is to perform Karnaugh maps on many inputs (>8).

583687

[Elektrik1]

Actually, for 0x46 logic is very similar, but missing 9-th pin changes equations.

583690

[Elektrik1]

Also, C3H8, you decompiled logic is very similar to 'original' 0x44 version but produces a bit different output, four bits are different.
583692

[C3H8]

Elektrik,
regarding the jedec file: Please check your pin 11: your jedec file above (called 0x44) doesn't have the negation on this pin (if I decompiled it correctly since I had to count and copy all the bit positions manually). Please double check (in red) with
nc1=1 i2=2 i3=3 i4=4 i5=5 i6=6 i7=7 i8=8 i9=9 GND=10 !i11=11
o12=12 o13=13 f14=14 o15=15 o16=16 f17=17 o18=18 f19=19 VCC=20

equations

!o18 = !i5 & !i9
# !i8 & i11
!o16 = !i4 & !i9
# !i7 & i11
!o15 = !i9
!o13 = !f14
# !i2 & !f17 & !i6
# !i3 & !f19 & !i6
!o12 = !i2 & !f17
# !i3 & !f19

[C3H8]

Elektrik,
Please check: if this is correct than pin 5 have no influence to the logic. But this pin is connected to the FTDI and Atmel needs to see this pin always on RX0! On the other hand pin 4 have impact to the logic, but there is nothing connected in schematic.



Actually, for 0x46 logic is very similar, but missing 9-th pin changes equations.

583690

[Elektrik1]

Ah, my bad for 11 pin :) got it correctly in excel thou'.

Tried to improvise:
583778

Got green light, but not connects to any ECU, test passes :)
583780

Attaching excel, captured 0x46 logs, and MATLAB code used for analysis and unique combinations extraction

[C3H8]

Elektrik,
with your current logic the ECU can see all the traffic between PC and Atmel. This traffic is on pin 5 (TX TFDI) and a copy to pin pin 15 (RX Atmel). But it is also always on pin 16 and 18 (TX K, TX L). There is something missing in the first 2 lines to keep away all the communication between PC and Atmel, like in this example in red:
!o18 = !i5 & !ix # !i8 & i11

[Elektrik1]

Hehe, actually found the issue, one of wire got broken, so incorrect truth table was generated. Fixed, and got different result.
583979

583981

Filled in formulas for this table, and basically got hardware GAL delete performed on software (lol), and surprisingly it works fine on simple KLine radio, but perhaps won't work on LLine protocols and so on since a lot of cummunication crap is sent to K&L Lines :D

583982

So it seems I have filtered too much combinations leaving only unique combinations (1024 -> 31 combination), which are clearly not enough. :applause:

[Elektrik1]

I am leaving a final excel file here, formulas needs to fixed to match all greens on C3H8 logic test columns. We're very close guys, let's finish it!

[Sean4211031]

Hey guys new to this site, newish to vcds. I bought a cable that came with 18.2.0. I did not remenber seeing the request on not to update it. I did. Cable bricked. I have been led to believe that reflashing the cable can unbrick it. Can anyine here help me out with a guide on doing so. Im not mega tech savvi but i can follow instructions and solder half decent. Any help would he much appreciated

[pablobrsp]

Hi Sean and welcome on board.

You did the same of many other members but here you can find all the documents you'll need to revive your vcds cable. To do so, I kindly suggest you read all the posts since the first one up to the latest.

Unfortunately this is the best way to understand how the cable works getting all information you are looking for.

I apologize my sincerely, but trust me.

KR

Pablo

[pablobrsp]

Hey guys new to this site, newish to vcds. I bought a cable that came with 18.2.0. I did not remenber seeing the request on not to update it. I did. Cable bricked. I have been led to believe that reflashing the cable can unbrick it. Can anyine here help me out with a guide on doing so. Im not mega tech savvi but i can follow instructions and solder half decent. Any help would he much appreciated

Hi Sean and welcome on board.

You did the same of many other members but here you can find all the documents you'll need to revive your vcds cable. To do so, I kindly suggest you read all the posts since the first one up to the latest.

Unfortunately this is the best way to understand how the cable works and get all information you are looking for.

I apologize my sincerely, but trust me.

KR

Pablo

[liviudiaconu]

Hehe, actually found the issue, one of wire got broken, so incorrect truth table was generated. Fixed, and got different result.
583979

583981

Filled in formulas for this table, and basically got hardware GAL delete performed on software (lol), and surprisingly it works fine on simple KLine radio, but perhaps won't work on LLine protocols and so on since a lot of cummunication crap is sent to K&L Lines :D

583982

So it seems I have filtered too much combinations leaving only unique combinations (1024 -> 31 combination), which are clearly not enough. :applause:
Can't be this. pin 11 is logical to have effect, but in formulas aren't.
And as you wrote the formulas ..no gal needed, only wires between pins.

[C3H8]

Elektrik,
you are still more than welcome to generate a very small code table (32 entries) like I mentioned here (https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3461236&viewfull=1#post3461236). Please don't filter or narrow down, every line would be necessary to find the logic. I can do the Arduino sketch if you send me your current one.
I agree with you that in your current map important lines are missing, but in general it would also work with your approach. It is only very complex and could be so much easier.

[xoom]

Elektrik,
regarding the jedec file: Please check your pin 11: your jedec file above (called 0x44) doesn't have the negation on this pin (if I decompiled it correctly since I had to count and copy all the bit positions manually). Please double check (in red) with
nc1=1 i2=2 i3=3 i4=4 i5=5 i6=6 i7=7 i8=8 i9=9 GND=10 !i11=11
o12=12 o13=13 f14=14 o15=15 o16=16 f17=17 o18=18 f19=19 VCC=20

equations

!o18 = !i5 & !i9
# !i8 & i11
!o16 = !i4 & !i9
# !i7 & i11
!o15 = !i9
!o13 = !f14
# !i2 & !f17 & !i6
# !i3 & !f19 & !i6
!o12 = !i2 & !f17
# !i3 & !f19


if i try disassemble on paper i get same results :)

( !i5 & !i9 ) | ( !i8 & !i11 ) = !o18
( !i4 & !i9 ) | ( !i7 & !i11 ) = !o16
!i9 = !o15
!i14 | ( !i2 & !i17 & !i6 ) | ( !i3 & !i19 & !i6 ) = !o13
( !i2 & !i17 ) | ( !i3 & !i19 ) = !o12
Configurations:

All XOR bits its set to 0

AC1-2120 = 1 //Pin 19 set as Input
AC1-2122 = 1 //Pin 17 set as Input
AC1-2125 = 1 //Pin 14 set as Input

Global:
SYN = 1
AC0 = 0
which means Simple Mode

Signature: 0x30, 0x30, 0x20 //whatever it means :)

[xoom]

Attempt to draw it with crocodile physics (not 100% sure if it's correct) ;)

https://i.imgur.com/PjPQo68.png

[C3H8]

The signature bytes have no effect to the chip. You can leave a message for your descendants here.

[Elektrik1]

C3H8, 32 entries is not enough, because there's more inputs (19, 17, 14) which are dependent too. Already launched Quine-McCluskey algorithm to recreate functions for full 1024 cases combinations. Already got logic for PINS 12,15,18, which does fit all the cases (all greens). Still waiting for pins 16 and 13, because of high complexity, it may take a while.

If reconstructed will be inaccurate (missing some combinations), or will never end, will launch Espresso algorithm.

[xoom]

This is how inputs looks when press TEST Button.
Message (0x53, 0x04, 0x82, 0xD5) is command to test K Lines.. and after that ATF16V8 gets PIN7 pulled LOW and next PIN8 gets pulled LOW
https://i.imgur.com/ZfygO75.png
Then here is connection to immobilizer module (25) :
First it sends 5 baud init on both K and L lines.. then communicates on 9500 baud only on K Line:
https://i.imgur.com/NJM8HEa.png

[xoom]

You can download Saleae Logic software to open capture files attached below:

[xoom]

Here is Power Up results:
https://i.imgur.com/NpXYzF9.png

[Elektrik1]

Ok guys, good news, I have managed to recreate logic by Espresso logic minimizer, got all greens, leaving excel here, now reading back and comparing original 0x46 chip and my compiled one to check if all input combinations matches 100%. Cable works fine. Will post .JED and source code later. Attaching Final excel.

Update:

Here's final logic:


PIN 18
---------------------------------------
(1) X = I
or K;

not X = not I and not K;
---------------------------------------

PIN 16
---------------------------------------
(1) X = I and M
or I and N
or I and Q
or L and M
or L and N
or L and Q;

not X = not I and not L
or not M and not N and not Q;
---------------------------------------

PIN 15
---------------------------------------
(1) X = N;

not X = not N;
---------------------------------------

PIN 13
---------------------------------------
(1) X = C and F
or F and M
or F and Q;

not X = not C and not M and not Q
or not F;
---------------------------------------

PIN 12
---------------------------------------
(1) X = C
or Q;

not X = not C and not Q;
---------------------------------------


Which corresponds to:


Name 0x46 ;
PartNo 00 ;
Date 2019-01-02 ;
Revision 01 ;
Designer Elektrik ;
Company * ;
Assembly None ;
Location ;
Device g16v8a ;

/* *************** INPUT PINS *********************/
PIN 2 = i2 ; /* */
PIN 3 = i3 ; /* */
PIN 5 = i5 ; /* */
PIN 6 = i6 ; /* */
PIN 7 = i7 ; /* */
PIN 8 = i8 ; /* */
PIN 11 = !i11 ; /* */

/* *************** OUTPUT PINS *********************/
PIN 12 = o12 ; /* */
PIN 13 = o13 ; /* */
PIN 14 = f14 ; /* */
PIN 15 = o15 ; /* */
PIN 16 = o16 ; /* */
PIN 17 = f17 ; /* */
PIN 18 = o18 ; /* */
PIN 19 = f19 ; /* */

!o18 = i11 & !i8;
!o16 = (i11 & !i7) # (!i6 & !i5 & !i2);
!o15 = !i5;
!o13 = (!f17 & !i6 & !i2) # !f14;
!o12 = !f17 & !i2;


100% match to 1024 combinations logic, will check to all possible pins and outputs. Attaching fully working 0x46 .JED

We made it!

0x46.JED:



CUPL(WM) 5.0a Serial# 60008009
Device g16v8as Library DLIB-h-40-2
Created Fri Jan 04 18:22:51 2019
Name 0x46
Partno 00
Revision 01
Date 2019-01-04
Designer Elektrik
Company *
Assembly None
Location
*QP20
*QF2194
*G0
*F0
*L00256 11111111111111111111111110111110
*L00768 11111111111111111111101111111110
*L00800 10111111111110111011111111111111
*L01024 11111111111110111111111111111111
*L01536 10111111111111101011111111111111
*L01568 11111111111111111110111111111111
*L01792 10111111111111101111111111111111
*L02048 00000000001100000011000000100000
*L02112 00000000101001001111111111111111
*L02144 11111111111111111111111111111111
*L02176 111111111111111110
*C21AA
*A040

[Jackson0]

Hi,

I have an old V704 Cable (Atmel162,FTDI,GAL,CAN) with killed EEprom.

Has someone an actual or pre-actual Version in German Hex/Ept File for me?

Regards,
Jackson

[xoom]

Hi,

I have an old V704 Cable (Atmel162,FTDI,GAL,CAN) with killed EEprom.

Has someone an actual or pre-actual Version in German Hex/Ept File for me?

Regards,
Jackson

Try read back like 10 pages back and you'll find kolimers loader and you can reflash your cable to german version.

[liviudiaconu]

[...]

Which corresponds to:
!o18 = i11 & !i8;
!o16 = (i11 & !i7) # (!i6 & !i5 & !i2);
!o15 = !i5;
!o13 = (!f17 & !i6 & !i2) # !f14;
!o12 = !f17 & !i2;[/CODE]

100% match to 1024 combinations logic, will check to all possible pins and outputs. Attaching fully working 0x46 .JED

We made it!

0x46.JED:



CUPL(WM) 5.0a Serial# 60008009
Device g16v8as Library DLIB-h-40-2
Created Fri Jan 04 18:22:51 2019
Name 0x46
Partno 00
Revision 01
Date 2019-01-04
Designer Elektrik
Company *
Assembly None
Location
*QP20
*QF2194
*G0
*F0
*L00256 11111111111111111111111110111110
*L00768 11111111111111111111101111111110
*L00800 10111111111110111011111111111111
*L01024 11111111111110111111111111111111
*L01536 10111111111111101011111111111111
*L01568 11111111111111111110111111111111
*L01792 10111111111111101111111111111111
*L02048 00000000001100000011000000100000
*L02112 00000000101001001111111111111111
*L02144 11111111111111111111111111111111
*L02176 111111111111111110
*C21AA
*A040


With this my compilation appear like..


Location
*QP20
*QF2194
*G1
*F0
*L00256 11111111111111111111111110111101
*L00768 10111111111110111011111111111111
*L00800 11111111111111111111101111111101
*L01024 11111111111110111111111111111111
*L01536 10111111111111101011111111111111
*L01568 11111111111111111110111111111111
*L01792 10111111111111101111111111111111
*L02048 00000000001100000011000000100000
*L02112 00000000101001001111111111111111
*L02144 11111111111111111111111111111111
*L02176 111111111111111110
*C222A
*A207

Which optimization used you?

And...

!o18 = i11 & !i8;
!o16 = (i11 & !i7) # (!i6 & !i5 & !i2);

For sure is not !i11?

[xoom]

!o18 = i11 & !i8 < - is this should not to be like: !o18 = (!i11 & !i8) # (!i5 & !i9) ? :)

[liviudiaconu]

i9 not used in 46..so..!i9 is 1 allways?

[xoom]

it is used in both 0x44 and 0x46... FTDI TX pin goes there

[xoom]

i9 not used in 46..so..!i9 is 1 allways?

hmm or maybe it doesn't checked china board and yes its not connected :) but would be interesting to see original version

[liviudiaconu]

I remember the year when i modified my first 704 with RL by rerouting 3 wires and rewrote GAL with "44".jed (see Aminebot file).
The FTDI Tx go to pin 5 GAL (STC, R50/R51/Reseter used too and desoldered)

So, for sure the pin 9 not used.

In my .jed two lines are reversed like in last 46.jed posted by Elektrik

*L00768 11111111111111111111101111111110
*L00768 10111111111110111011111111111111

*L00800 10111111111110111011111111111111
*L00800 11111111111111111111101111111110

Where i wrong?

I made only two modifications (without this the .jed is more different)

Elektrik say this:

PIN 18
---------------------------------------
(1) X = I
or K;

not X = not I and not K;
---------------------------------------

PIN 16
---------------------------------------
(1) X = I and M
or I and N
or I and Q
or L and M
or L and N
or L and Q;

not X = not I and not L
or not M and not N and not Q;
---------------------------------------

PIN 17 MAYBE 15...
---------------------------------------
(1) X = N;

not X = not N;
---------------------------------------

PIN 13
---------------------------------------
(1) X = C and F
or F and M
or F and Q;

not X = not C and not M and not Q
or not F;
---------------------------------------

PIN 12
---------------------------------------
(1) X = C
or Q;

not X = not C and not Q;
---------------------------------------

Which corresponds to:
!o18 = !i11 & !i8;
!o16 = (!i11 & !i7) # (!i6 & !i5 & !i2);
!o15 = !i5;
!o13 = (!f17 & !i6 & !i2) # !f14;
!o12 = !f17 & !i2;

With this obtained

*QP20
*QF2194
*G1
*F0
*L00256 11111111111111111111111110111110
*L00768 10111111111110111011111111111111
*L00800 11111111111111111111101111111110
*L01024 11111111111110111111111111111111
*L01536 10111111111111101011111111111111
*L01568 11111111111111111110111111111111
*L01792 10111111111111101111111111111111
*L02048 00000000001100000011000000100000
*L02112 00000000101001001111111111111111
*L02144 11111111111111111111111111111111
*L02176 111111111111111110
*C21AA
*A220

[liviudiaconu]

Look difference RL46 vs BM 44 GAL to FTDI/Atmega pins

[Elektrik1]

liviudiaconu (https://www.digital-kaos.co.uk/forums/member.php/161166-liviudiaconu), ,yeah PIN 15 there should be, typo. Sorry forgot to post the header, this is full project:


Name 0x46 ;
PartNo 00 ;
Date 2019-01-02 ;
Revision 01 ;
Designer Elektrik ;
Company * ;
Assembly None ;
Location ;
Device g16v8a ;

/* *************** INPUT PINS *********************/
PIN 2 = i2 ; /* */
PIN 3 = i3 ; /* */
PIN 5 = i5 ; /* */
PIN 6 = i6 ; /* */
PIN 7 = i7 ; /* */
PIN 8 = i8 ; /* */
PIN 11 = !i11 ; /* */

/* *************** OUTPUT PINS *********************/
PIN 12 = o12 ; /* */
PIN 13 = o13 ; /* */
PIN 14 = f14 ; /* */
PIN 15 = o15 ; /* */
PIN 16 = o16 ; /* */
PIN 17 = f17 ; /* */
PIN 18 = o18 ; /* */
PIN 19 = f19 ; /* */

!o18 = i11 & !i8;
!o16 = (i11 & !i7) # (!i6 & !i5 & !i2);
!o15 = !i5;
!o13 = (!f17 & !i6 & !i2) # !f14;
!o12 = !f17 & !i2;

i11 is inverted in pin definition.

[Mrjitter]

hi

Searching through my old files I found this ....

https://rapidgator.net/file/4ed94933047c152ab0a9ae973d1f7625/From_Russia_with_love.zip.html

I think this file corresponds to a gal file of type 0x46 for the images found in the doc attached in the files.

the doc translate by google to english ...

https://rapidgator.net/file/91f7ea316a9a33ca8785aa5735dddd3a/4.ru.en.doc.html


Please .... anyone can post the .jed gal file for 0x44 type ?

Regards

[heshamzn]

how to power up vcds with 12 v i got the ordino programer and i shearched here no pic how to do it i cant do it in my car obd2 the operation will be done here at my home in which pins i connect the ac charger 12 v to the vcds ?

[Roma77]

[QUOTE = Mrjitter; 3464667] hi

При поиске в моих старых файлах я нашел это ....

https://rapidgator.net/file/4ed94933047c152ab0a9ae973d1f7625/From_Russia_with_love.zip.html

Я думаю, что этот файл соответствует файлу gal типа 0x46 для изображения, найденные в документе, прилагаемом к файлам.

Документ переведен Google на английский ...

https://rapidgator.net/file/91f7ea316a9a33ca8785aa5735dddd3a/4.ru.en.doc.html


Пожалуйста .... кто-нибудь может опубликовать файл .jed gal для типа 0x44?

С уважением [/ QUOTE]
Пожалуйста

[C3H8]

I wonder why pin 19 and pin 3 is not used any longer? Audi needs RX on L Line?!

[jan4]

heshamzn


obd connector pin 16 + , 5 -

[Elektrik1]

Mjriter, it's 0x44 jed in your pack. C3H8, l line only needs to be output for 5baud wake process on old vw/audi ecu's. No other data is sent there afaik. That's why Lline input is not used.

[Mrjitter]

Ok Elektrik1

Thank you for the clarification

Regards

[liviudiaconu]

liviudiaconu (https://www.digital-kaos.co.uk/forums/member.php/161166-liviudiaconu), ,yeah PIN 15 there should be, typo. Sorry forgot to post the header, this is full project:


Name 0x46 ;
PartNo 00 ;
Date 2019-01-02 ;
Revision 01 ;
Designer Elektrik ;
Company * ;
Assembly None ;
Location ;
Device g16v8a ;

/* *************** INPUT PINS *********************/
PIN 2 = i2 ; /* */
PIN 3 = i3 ; /* */
PIN 5 = i5 ; /* */
PIN 6 = i6 ; /* */
PIN 7 = i7 ; /* */
PIN 8 = i8 ; /* */
PIN 11 = !i11 ; /* */

/* *************** OUTPUT PINS *********************/
PIN 12 = o12 ; /* */
PIN 13 = o13 ; /* */
PIN 14 = f14 ; /* */
PIN 15 = o15 ; /* */
PIN 16 = o16 ; /* */
PIN 17 = f17 ; /* */
PIN 18 = o18 ; /* */
PIN 19 = f19 ; /* */

!o18 = i11 & !i8;
!o16 = (i11 & !i7) # (!i6 & !i5 & !i2);
!o15 = !i5;
!o13 = (!f17 & !i6 & !i2) # !f14;
!o12 = !f17 & !i2;

i11 is inverted in pin definition.

OK. What you do'it in definitions is what i obtained by following your formulas and modifying equations.
With your present equations i obtained the same file..

With ONE exception: lines 768 and 800 REVERSED. Yes, this two lines reffer at the same OUT but, why in my generator appear reversed?

Can you, please, send me your settings in WinCUPL?
Thank you..


A question:
When obtained truth-table of 46 GAL you run ALL combinations? I mean including pin 3 and pin 19 influences?

An idea: for see if .jed is correctly generatde try to obtain the same tables as with original.
Compare. If the same results, the equations are OK.

[hid3]

Does anyone own a genuine HEX-V2 and is willing to help?
If so, please write me a PM directly.
Thank you.

[Elektrik1]

To match 100% input-output correlation (all 262144 combinations on app pins) to original 0x46 GAL, some additions were added, final code which confirms it is 1:1 clone:

Name 0x46 ;
PartNo 00 ;
Date 2019-01-02 ;
Revision 01 ;
Designer Elektrik ;
Company * ;
Assembly None ;
Location ;
Device g16v8a ;

/* *************** INPUT PINS *********************/
PIN 2 = i2 ; /* */
PIN 3 = i3 ; /* */
PIN 4 = i4 ; /* */
PIN 5 = i5 ; /* */
PIN 6 = i6 ; /* */
PIN 7 = i7 ; /* */
PIN 8 = i8 ; /* */
PIN 11 = !i11 ; /* */

/* *************** OUTPUT PINS *********************/
PIN 12 = o12 ; /* */
PIN 13 = o13 ; /* */
PIN 14 = f14 ; /* */
PIN 15 = o15 ; /* */
PIN 16 = o16 ; /* */
PIN 17 = f17 ; /* */
PIN 18 = o18 ; /* */
PIN 19 = f19 ; /* */

!o18 = i11 & !i8;
!o16 = (i11 & !i7) # (!i6 & (!i5 # !i4) & !i2);
!o15 = !i5 # !i4;
!o13 = (!f17 & !i6 & !i2) # !f14;
!o12 = !f17 & !i2;

0x46 JED:


CUPL(WM) 5.0a Serial# 60008009
Device g16v8as Library DLIB-h-40-2
Created Sun Jan 06 19:17:12 2019
Name 0x46
Partno 00
Revision 01
Date 2019-01-02
Designer Elektrik
Company *
Assembly None
Location
*QP20
*QF2194
*G0
*F0
*L00256 11111111111111111111111110111110
*L00768 11111111111111111111101111111110
*L00800 10111111101111111011111111111111
*L00832 10111111111110111011111111111111
*L01024 11111111111110111111111111111111
*L01056 11111111101111111111111111111111
*L01536 10111111111111101011111111111111
*L01568 11111111111111111110111111111111
*L01792 10111111111111101111111111111111
*L02048 00000000001100000011000000100000
*L02112 00000000101001001111111111111111
*L02144 11111111111111111111111111111111
*L02176 111111111111111110
*C299A
*AFE8

Don't know why it also responds on signals on pin 4 as well (which is not connected), maybe for some hybrid china clones, don't know. Attaching .JED project, which can be opened with WinCupl (open as project), also leaving pin combinational responses for original 0x46, compiled with this code 0x46, also performed check of original 0x44 response tables, and C3H8 compiled logic response (which I do confirm corresponds 100% to all original 0x44 input-outputs).

All decimals represented in such was:


DEC
PIN19
PIN18
PIN17
PIN16
PIN15
PIN14
PIN13
PIN12
PIN11
PIN9
PIN8
PIN7
PIN6
PIN5
PIN4
PIN3
PIN2
PIN1


0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0


1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1


2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0


...




















262143
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

[liviudiaconu]

pin 4 not used in "46".
Still nothing about pins 3 and 19.
I think must be like in "44" equations for 12 and 13..

Something like

! p12 = ((p17#p2)&(p19#p3));
! p13 = (p17#p2#p6)&(p19#p3#p6)& p14;

[porkyseen62]

thanks kolimer , good job

[Elektrik1]

Pin 4 is not used, but is written in logic somewhy.

No pin19 and pin 3 usage in original GAL as well. I think it's normal, since LLine (19) input is not needed for any car afaik, it's onyl needed as an output for 5baud communication to wake up ECU. So only output. I may try to add logic you written, but perhaps test won't pass then. I have old ecu which needs LLine for wake up, and logic without 3 and 19 pins works fine there.

[BASi77]

Perhaps the KKL protocol is no longer used, but there is software support in version HW46.


; =============== S U B R O U T I N E == HW:0X46

sub_229:
sbi PORTA, PORTA4
lds r24, Kx_ctrl
clr r25
sbrs r24, 5
rjmp loc_231
cbi PORTA, PORTA5 ; K-line select
rjmp loc_232
; --------------------------------------

loc_231:
sbi PORTA, PORTA6

loc_232:
sbrs r24, 6
rjmp loc_236
cbi PORTA, PORTA6 ; KL-line select
rjmp loc_237
; --------------------------------------

loc_236:
sbi PORTA, PORTA6

loc_237:
lds r24, Kx_stat
clr r25
sbrs r24, 2
rjmp loc_23E
cbi PORTA, PORTA0 ; K-line select
rjmp loc_23F
; --------------------------------------

loc_23E:
sbi PORTA, PORTA0

loc_23F:
sbrs r24, 3
rjmp loc_243
cbi PORTA, PORTA1 ; KL-line select
ret
; --------------------------------------

loc_243:
sbi PORTA, PORTA1
ret

; End of function sub_229

I propose to test this logic:



Name 0x46 ;
PartNo 00 ;
Date 2019-01-07 ;
Revision 01 ;
Designer XXX ;
Company * ;
Assembly None ;
Location ;
Device g16v8a ;


/* *************** INPUT PINS **********************/
PIN 2 = i2 ; /* K-line select */
PIN 3 = i3 ; /* KL-line select */
PIN 4 = i4 ; /* */
PIN 5 = i5 ; /* FT_TXD */
PIN 6 = i6 ; /* FTDI <-> KKL enable */
PIN 7 = i7 ; /* K-line select */
PIN 8 = i8 ; /* KL-line select */
PIN 11 = i11 ; /* TXD1 */


/* *************** OUTPUT PINS *********************/
PIN 12 = o12 ; /* RXD1 */
PIN 13 = o13 ; /* FT_RXD */
PIN 14 = f14 ; /* TXD0 */
PIN 15 = o15 ; /* RXD0 */
PIN 16 = o16 ; /* TX1 K-line */
PIN 17 = f17 ; /* RX1 K-line */
PIN 18 = o18 ; /* TX2 KL-line */
PIN 19 = f19 ; /* RX2 KL-line */


o18 = ( i11 # i8 ) & ( i6 # ( i5 & i4) # i3 );
o16 = ( i11 # i7 ) & ( i6 # ( i5 & i4) # i2 );
o15 = i5 & i4;
p13 = ( p17 # p2 # p6 ) & ( p19 # p3 # p6 ) & p14;
p12 = ( p17 # p2 ) & ( p19 # p3 );

[Elektrik1]

Perhaps the KKL protocol is no longer used, but there is software support in version HW46.


I propose to test this logic:


I have modified it a bit, but it show this (does not work)

584904


Name 0x46 ;
PartNo 00 ;
Date 2019-01-02 ;
Revision 01 ;
Designer Elektrik ;
Company * ;
Assembly None ;
Location ;
Device g16v8a ;

/* *************** INPUT PINS *********************/
PIN 2 = i2 ; /* K-line select */
PIN 3 = i3 ; /* KL-line select */
PIN 4 = i4 ; /* NC but exists in original */
PIN 5 = i5 ; /* FT_TXD */
PIN 6 = i6 ; /* FTDI <-> KKL enable */
PIN 7 = i7 ; /* K-line select */
PIN 8 = i8 ; /* KL-line select */
PIN 11 = i11 ; /* TXD1 */

/* *************** OUTPUT PINS ********************/
PIN 12 = o12 ; /* RXD1 */
PIN 13 = o13 ; /* FT_RXD */
PIN 14 = f14 ; /* TXD0 */
PIN 15 = o15 ; /* RXD0 */
PIN 16 = o16 ; /* TX1 K-line */
PIN 17 = f17 ; /* RX1 K-line */
PIN 18 = o18 ; /* TX2 KL-line */
PIN 19 = f19 ; /* RX2 KL-line */

o18 = ( i11 # i8 ) & ( i6 # ( i5 & i4) # i3 );
o16 = ( i11 # i7 ) & ( i6 # ( i5 & i4) # i2 );
o15 = i5 & i4;
p13 = ( f17 # i2 # i6 ) & ( f19 # i3 # i6 ) & f14;
p12 = ( f17 # i2 ) & ( f19 # i3 );

This might be because logic needs to be negated (all pins are pull-upped internally).

Edit: inverted gives positive result on green light and test passes:


!o18 = (!i11 & !i8) # (!i6 & (!i5 # !i4) & !i3);
!o16 = (!i11 & !i7) # (!i6 & (!i5 # !i4) & !i2);
!o15 = !i5 # !i4;
!o13 = (!f17 & !i2 & !i6) # (!f19 & !i3 & !i6) # !f14;
!o12 = (!f17 & !i2) # (!f19 & !i3);


And it does connect to my old KL-Line ECU just fine.

584906


A lot of differences to input-output combinatiosn to "original" chinese 46.
584908


Latest project source:


Name 0x46 ;
PartNo 00 ;
Date 2019-01-02 ;
Revision 01 ;
Designer Elektrik ;
Company * ;
Assembly None ;
Location ;
Device g16v8a ;

/* *************** INPUT PINS *********************/
PIN 2 = i2 ; /* K-line select */
PIN 3 = i3 ; /* KL-line select */
PIN 4 = i4 ; /* NC but exists in original */
PIN 5 = i5 ; /* FT_TXD */
PIN 6 = i6 ; /* FTDI <-> KKL enable */
PIN 7 = i7 ; /* K-line select */
PIN 8 = i8 ; /* KL-line select */
PIN 11 = i11 ; /* TXD1 */

/* *************** OUTPUT PINS ********************/
PIN 12 = o12 ; /* RXD1 */
PIN 13 = o13 ; /* FT_RXD */
PIN 14 = f14 ; /* TXD0 */
PIN 15 = o15 ; /* RXD0 */
PIN 16 = o16 ; /* TX1 K-line */
PIN 17 = f17 ; /* RX1 K-line */
PIN 18 = o18 ; /* TX2 KL-line */
PIN 19 = f19 ; /* RX2 KL-line */

!o18 = (!i11 & !i8) # (!i6 & (!i5 # !i4) & !i3);
!o16 = (!i11 & !i7) # (!i6 & (!i5 # !i4) & !i2);
!o15 = !i5 # !i4;
!o13 = (!f17 & !i2 & !i6) # (!f19 & !i3 & !i6) # !f14;
!o12 = (!f17 & !i2) # (!f19 & !i3);


and .JED for it:


CUPL(WM) 5.0a Serial# 60008009
Device g16v8as Library DLIB-h-40-2
Created Mon Jan 07 02:05:26 2019
Name 0x46
Partno 00
Revision 01
Date 2019-01-02
Designer Elektrik
Company *
Assembly None
Location
*QP20
*QF2194
*G0
*F0
*L00256 11111111111111111111111110111110
*L00288 11111011101111111011111111111111
*L00320 11111011111110111011111111111111
*L00768 11111111111111111111101111111110
*L00800 10111111101111111011111111111111
*L00832 10111111111110111011111111111111
*L01024 11111111111110111111111111111111
*L01056 11111111101111111111111111111111
*L01536 10111111111111101011111111111111
*L01568 11111010111111111011111111111111
*L01600 11111111111111111110111111111111
*L01792 10111111111111101111111111111111
*L01824 11111010111111111111111111111111
*L02048 00000000001100000011000000100000
*L02112 00000000101001001111111111111111
*L02144 11111111111111111111111111111111
*L02176 111111111111111110
*C37E2
*CEE9

Conclusion: my original GAL did not have this LLine readout functionality, only output wakening (5BAUD init sequence) functionality, which did also worked fine.

[liviudiaconu]

I saw in the past more schemathics named "original"..for 44 and 46 too..

Only one of them having pin 4 pulled-up external too. Attached..
See ONLY pin 4 is pulled-up externaly. That make me think is used in logical as 1. pins 1 and 9 not used, so..not connected.

And another thing: the programm having a button named "OBD II". Is for generic and, as i saw work only for engine for other cars.
When i am lazzy time to time erase DTC for engine for my old Corsa 2001.
Is very possible using LLine for this "OBD generic"..
Is very possible too RT excluded the LLine support in 46 HW. I don't remember when 46 released..If someone having old installers can see in wich version appear HPxxx.bin. But this not explain why LLine circuit still exist.
Is very possible too, chineses tried extract dump or a person for them..and..extracted truncated or truncated by himself for this motive ("is old, no need")

[kaalis]

And it does connect to my old KL-Line ECU just fine.

584906


mmm, 16v from dinosaur age.
Haven't tried connecting it yet. But thanks for picture.

[kaalis]

Is very possible too, chineses tried extract dump or a person for them..and..extracted truncated or truncated by himself for this motive ("is old, no need")
I have old NEC clone hex-v2 fake. In Kolimer hw info tool it shows up as 0x46. K2 (L) didn't work in even when cable was brand new. Now something has fried inside and voltage regulator has 7V in input and 5V in output.

K1 sometimes work, sometimes not. Shi##y cable.

[Elektrik1]

I saw in the past more schemathics named "original"..for 44 and 46 too..

Only one of them having pin 4 pulled-up external too. Attached..
See ONLY pin 4 is pulled-up externaly. That make me think is used in logical as 1. pins 1 and 9 not used, so..not connected.

And another thing: the programm having a button named "OBD II". Is for generic and, as i saw work only for engine for other cars.
When i am lazzy time to time erase DTC for engine for my old Corsa 2001.
Is very possible using LLine for this "OBD generic"..
Is very possible too RT excluded the LLine support in 46 HW. I don't remember when 46 released..If someone having old installers can see in wich version appear HPxxx.bin. But this not explain why LLine circuit still exist.
Is very possible too, chineses tried extract dump or a person for them..and..extracted truncated or truncated by himself for this motive ("is old, no need")

No need for external pull-up resistor, GAL chips have internal weak (~50K) pullup to VCC.

[liviudiaconu]

In this case, why RT mounted 1K on pin 4 to +?

[Elektrik1]

In this case, why RT mounted 1K on pin 4 to +?

585041

Because GAL chips have ACTIVE pull-ups, resistor is an PASSIVE pull-up, it ensures always logical 1 on pin 4 even if VCC glitches occur (very small chance), it's just right way to terminate floating pins. Wonder why they didn't do it as well on pin 1 and 9, but perhaps that's because only PIN 4 is affecting logic (still not sure why it's defined in logic if it has static state, but it's question for RT).

[liviudiaconu]

RT never answer you or me..we know why..
We can suppose: maybe RT prepared logical for another pin (pin 4 in this case) and:
-the developing of that logic never applied.
-this logical applied for first series of "46" and after RT eliminated pin 4 from this and pulled up.

[hid3]

They're even not familiar with their own PCB layouts of previous HEX+CAN revisions, there's not a chance they remember how they did that crap some time ago...

BTW, take a look at this Dictator's post: https://forums.ross-tech.com/showthread.php?16983-Changed-longcoding-of-central-electric-09-byte-18&p=151751&viewfull=1#post151751

They try to make illusion that the "dangeous methods of the loader" is the root cause of shifted adaptation channels, long coding wrecks, etc but in no way that this is caused by their implemented shit to desperately fight with this :D

[Roma77]

I saw in the past more schemathics named "original"..for 44 and 46 too..

Only one of them having pin 4 pulled-up external too. Attached..
See ONLY pin 4 is pulled-up externaly. That make me think is used in logical as 1. pins 1 and 9 not used, so..not connected.

Today came 10 boards that I ordered in China according to this scheme))) we will experiment)
During the week I’ll check and if everything works well, I’ll post here gerber files.
585518

[romaiz]

hi guys, how you all doing?
ive still got a problem with my interface its a vagcom 178 and has the atmega162 have followed the pdf files and reflashed the interface with usbasp.
when i open VAGCOM_HWType.exe and click read it comes up No interface found. I have +12v to pin 16 and GND pin 4. but when I have usbasp connected to the interface and I run VAGCOM_HWType.exe it finds the interface straight away firmware version 1.96 and HW Type 0x44. when I open vcdsLoader and click test it finds the interface, as soon as I plug in to car and test again no interface found.
all help will be very much appreciated

[Roma77]

hi guys, how you all doing?
ive still got a problem with my interface its a vagcom 178 and has the atmega162 have followed the pdf files and reflashed the interface with usbasp.
when i open VAGCOM_HWType.exe and click read it comes up No interface found. I have +12v to pin 16 and GND pin 4. but when I have usbasp connected to the interface and I run VAGCOM_HWType.exe it finds the interface straight away firmware version 1.96 and HW Type 0x44. when I open vcdsLoader and click test it finds the interface, as soon as I plug in to car and test again no interface found.
all help will be very much appreciated

After usbasp firmware, firmware cannot be 1.96, it should be 1.95 and then you update the firmware with the version of the program you want to use.

[kaalis]

it can be 1.96 if he is using avrdude and USBASP_write_0x44.cmd file.

[romaiz]

After usbasp firmware, firmware cannot be 1.96, it should be 1.95 and then you update the firmware with the version of the program you want to use.

hi Roma77 when i first flashed the interface using vcdsloader v6.3 and reinstalled vagcom it asked me to upgrade firmware to 1.96 but even then vagcom kept dropping the interface, and then wouldnt pickup the interface when plugged into the car. now it seems like the interface isn't getting 12v, but when I connect usbasp and then read HW Type it reads.
can you explain to me how to flash it with usbasp? maybe I am doing something wrong?
thanks again

[Roma77]

hi Roma77 when i first flashed the interface using vcdsloader v6.3 and reinstalled vagcom it asked me to upgrade firmware to 1.96 but even then vagcom kept dropping the interface, and then wouldnt pickup the interface when plugged into the car. now it seems like the interface isn't getting 12v, but when I connect usbasp and then read HW Type it reads.
can you explain to me how to flash it with usbasp? maybe I am doing something wrong?
thanks again
I think you did everything right the first time, but if you think that there is no +12 volts then the LED will not shine, if not + check the protective diode and the 7805 transistor, and better show a good photo of your board from both sides, GND on 4 and 5 pins.
P.S. I read the preceding advice that the guys have already given you, they all told you to follow the instructions and do not deviate,

[romaiz]

I think you did everything right the first time, but if you think that there is no +12 volts then the LED will not shine, if not + check the protective diode and the 7805 transistor, and better show a good photo of your board from both sides, GND on 4 and 5 pins.

would a 12v car battery charger be ok to use or no?

[kaalis]

Use PC power supply if you want to do it indoors.

[romaiz]

Use PC power supply if you want to do it indoors.

yes ive just used a led driver and powered it up and it workes ive just flashed the interface with usbasp using vcdsloader v2 0x44 so hopefully it will work just going to plug it in the car and ill let you guys know the resuts
thanks again

[xnevri00]

Hi guys,

when I was changing idle speed (01-engine->security access - 16->pin 12233->adaptation -10-> channel 06), I found there unknown channels (06,17,18,19,20,21,22) with exchangeable values (see file).
Do someone know the description (label) and value range for these channels ?
P.S. I have Octavia 2 2006 BKD DSG
Thanks in advance:)

[kaalis]

06 could be this:

A006,0,Idle Speed Adjustment
A006,1,Engine Speed,(actual)
A006,2,Engine Speed,(specified)
A006,3,Operation Status
A006,4,Accel. Pedal Pos.,Sensor 1 (G79)
Didn't find other channels in 18.9.0.4 label file

[xnevri00]

Hi, yes channel 06 is setting of idle speed, thanks... But I don't know the other channels 17,18,19,20,21,22. A long time I search them :/

[BASi77]

17,18,19,20,21,22. A long time I search them :/

The following lbl files may be useful :

[safm]

Hello everyone.

This is a real clone of Hex V2 or is a normal Hex Can with a different case?

https://www.obd2cartool.com/atmega-vag-hexv2-vag-1890-usb-interface-vcds-hex-v2-full-actived-free-shipping-p-1554?zenid=86ihd65f1okjt97asr4gcdkro6

Thanks

[mikroel]

Hello everyone.

This is a real clone of Hex V2 or is a normal Hex Can with a different case?

https://www.obd2cartool.com/atmega-vag-hexv2-vag-1890-usb-interface-vcds-hex-v2-full-actived-free-shipping-p-1554?zenid=86ihd65f1okjt97asr4gcdkro6

Thanks
real hex v2 clone doesn’t exist on the marker,yet


Sent from my iPad using Tapatalk

[mikroel]

Today came 10 boards that I ordered in China according to this scheme))) we will experiment)
During the week I’ll check and if everything works well, I’ll post here gerber files.
585518

nice work


Sent from my iPad using Tapatalk

[xoom]

Here are my gerber files for VCDS that i made long time ago :)
https://i.imgur.com/wdqwPJe.png

And manufactured boards:
https://i.imgur.com/ddOqATl.jpg

Gerbers Attached:

[Roma77]

Here are my gerber files for VCDS that i made long time ago :)

And manufactured boards:

Gerbers Attached:
good job 0x44 version, I probably will order a couple of boards for your gerberas, only perhaps I will replace si9200 with tja1050 and si9241 with l9637d, I will have to change the scheme a little bit, 9637 easier and cheaper for me to buy, 1050 has a built-in filter on the can-bus

[hid3]

What is the purpose of all this? To me all of this looks like reinventing the bike. Items available in mass production (which they are in this case) will always be cheaper than building something yourself. Will you improve something with your own design? I highly doubt that.

[Roma77]

What is the purpose of all this? To me all of this looks like reinventing the bike. Items available in mass production (which they are in this case) will always be cheaper than building something yourself. Will you improve something with your own design? I highly doubt that.
​It’s not for money)) I don’t know what you are doing, but it’s always a pleasure for a radio amateur to collect something with his own hands and then he is very proud that it works, so it’s a goal to collect something and not to buy something ready.

[jan4]

aren't those pcb's more expensive than a complete cable......................

love the initiative by the way

[xoom]

good job 0x44 version, I probably will order a couple of boards for your gerberas, only perhaps I will replace si9200 with tja1050 and si9241 with l9637d, I will have to change the scheme a little bit, 9637 easier and cheaper for me to buy, 1050 has a built-in filter on the can-bus

if you want i can send you layout file for sprint layout? :)

[Mrjitter]

Hi

Its really neccesary FT232BL with 0x44 interface ??
Its ok this schema for 0x44 interface ??

Regards

[mikroel]

if you want i can send you layout file for sprint layout? :)


it will be very nice if you can send sprint layout file

also if you have few empty PCB i will buy

[xoom]

4 boards left at the moment :)
Here is Sprint Layout5 file:

[Roma77]

Hi

Its really neccesary FT232BL with 0x44 interface ??
Its ok this schema for 0x44 interface ??

Regards
Honestly, this is not a very good scheme 0х44, I don’t understand why to put the L7812 and then a 5 volt Zener diode, it is easier to set 7805 if the Zener diode fails the ports of the laptop explode).

[jakuza]

I saw in the past more schemathics named "original"..for 44 and 46 too..

Only one of them having pin 4 pulled-up external too. Attached..
See ONLY pin 4 is pulled-up externaly. That make me think is used in logical as 1. pins 1 and 9 not used, so..not connected.

And another thing: the programm having a button named "OBD II". Is for generic and, as i saw work only for engine for other cars.
When i am lazzy time to time erase DTC for engine for my old Corsa 2001.
Is very possible using LLine for this "OBD generic"..
Is very possible too RT excluded the LLine support in 46 HW. I don't remember when 46 released..If someone having old installers can see in wich version appear HPxxx.bin. But this not explain why LLine circuit still exist.
Is very possible too, chineses tried extract dump or a person for them..and..extracted truncated or truncated by himself for this motive ("is old, no need")

I can't download this file, is it removed?

Elektrik1 (https://www.digital-kaos.co.uk/forums/member.php?u=493316) amazing work regarding GAL chip. Thank you for your time!

[mikroel]

4 boards left at the moment :)
Here is Sprint Layout5 file:

i briefly checked your pcb and have one question ?

where is 22pF connected, one side is connected to OSC 7.37MHz and the other side of capacitors is in the air?

[Mrjitter]

Hi

i put the zener component, but its a normal diode . Its for apply 5v from usb to all circuit, to program the atmega. Not neccesary 12v from OBD connector .
I have not usbasp, i have old stk500 program interface. This interface has not 5v to supply atmega.

Regards

[Roma77]

[QUOTE = mikroel; 3469662] Я кратко проверил вашу печатную плату и у меня есть один вопрос?

где 22pF подключен, одна сторона подключена к OSC 7,37 МГц, а другая сторона конденсаторов в воздухе? ​​[/ QUOTE]
everything is good the second side on gnd

[mikroel]

[QUOTE = mikroel; 3469662] Я кратко проверил вашу печатную плату и у меня есть один вопрос?

где 22pF подключен, одна сторона подключена к OSC 7,37 МГц, а другая сторона конденсаторов в воздухе? ​​[/ QUOTE]
все хорошо, вторая сторона на gnd

yes yes i saw in the mean time.

[Roma77]

With such success, friends will soon come to this topic RT and offer a contract for the development:peaceful:

Xoom (https://www.digital-kaos.co.uk/forums/member.php/107832-xoom) Thank you, I just uploaded your gerber archive to JLC

[xnevri00]

Hi, thanks for your help but in adaptation group "Axxx" there are not these channels :/ It's like a puzzle :)

[Roma77]

Hi

i put the zener component, but its a normal diode . Its for apply 5v from usb to all circuit, to program the atmega. Not neccesary 12v from OBD connector .
I have not usbasp, i have old stk500 program interface. This interface has not 5v to supply atmega.

Regards
Then you can even reduce the cost of your scheme, throw away 2x9637 + 7812 = comparator lm339:peaceful:

https://i.imgur.com/d42eO24.png

[Mrjitter]

I certainly don't understand how I could reduce the cost. but the goal is not to reduce costs, it is to have a 100% operational interface.

I'm not a vagcom expert, I had an interface like the one in the attached image, it broke down and I used the gal coming from this interface for mine. But when I tested it on an audi a3 2006 year, the interface doesn't erase faults. I had the doubt if the scheme was the right one.

Regards

[Roma77]

I certainly don't understand how I could reduce the cost. but the goal is not to reduce costs, it is to have a 100% operational interface.

I'm not a vagcom expert, I had an interface like the one in the attached image, it broke down and I used the gal coming from this interface for mine. But when I tested it on an audi a3 2006 year, the interface doesn't erase faults. I had the doubt if the scheme was the right one.

Regards
Honestly, I stumbled what you want, you wipe out your schemes and boards, then write that you don't even have a normal GAL and programmers, sorry, I don't understand you, can anyone else understand and help

[Mrjitter]

Honestly, I stumbled what you want, you wipe out your schemes and boards, then write that you don't even have a normal GAL and programmers, sorry, I don't understand you, can anyone else understand and help

it's simple ....

Is the scheme posted above ok for use with a type 44 gal jed file and kolimers firmware 0x44 ?

Regards

[Roma77]

it's simple ....

Is the scheme posted above ok for use with a type 44 gal jed file and kolimers firmware 0x44 ?

Regards
then everything is simple .....
collect and check :peaceful:

[Mrjitter]

then everything is simple .....
collect and check :peaceful:

Yes ....is made and tested in a audi a3 . I don't have a gal programmer yet, so I used the old one.
The result is that after making an autoscan and finding several faults, the interface does not erase them, for this , i doubt if the scheme was correct.
Greetings and thank you for taking the time to answer.

[flavyus1987]

I think you need to know type of broken interface, donor gal, x44 or x46. And after that, program ftdi and atmega with corect informations.

[Mrjitter]

I think you need to know type of broken interface, donor gal, x44 or x46. And after that, program ftdi and atmega with corect informations.

Hi

This is the interface .... i think it is 0x44

Regards

[gas43]

Hi, is it possible this cable (soft. 12.12) to upgrade easy?
https://ibb.co/fNL4zTC
https://ibb.co/PwzGgc6

[hid3]

Yes. For me it would be very easy.

[gas43]

I will immediately start reading 508 pages!! :p

[sahraoui1]

Hi, no
Originally Posted by kolimer View Post
A small Xmas present for everyone. Loader v7.2.

https://anonfile.com/K6Edt2n1bb/VCDSLoader_v7.2_zip
https://bayfiles.com/LaE7t2neb3/VCDSLoader_v7.2_zip
https://sendit.cloud/rkjgukdtbi6l
https://dbr.ee/pRvZ
https://www.dropjiffy.com/f/1RZITC1B
https://www.mirrored.to/downlink/IL28B8RH
https://clicknupload.org/yu067zfrpivj
https://userscloud.com/gcffimyjew97
http://uppit.com/ga8fqyx8evq1
https://1fichier.com/?lpqy20bquuhyshpfj1so
http://www.solidfiles.com/d/e88qBjzMaNXZY
https://uptobox.com/mf289uadv7in
https://www37.zippyshare.com/v/2go6ewCD/file.html

[liviudiaconu]

I don't understud..is a new one version of 7.2? Or the same as in past and poster hunt posts?

[costyone]

Hi guys, this clone can be updated with VCDS loader, thanks. 586596586597586598

[Roma77]

Hi guys, this clone can be updated with VCDS loader, thanks. 586596586597586598
Hi, no, it is impossible it is on the NEC chip

[costyone]

[QUOTE = Roma77; 3470752] Ciao, no, è impossibile che sia sul chip NEC [/ QUOTE]

so in no way can you upgrade to a newer version

[kaalis]

Actually you can. Get another nec clone or just pcb with newer version, put it into your existing plastic case and here you go... you have upgraded your old nec clone.

[jan4]

It is a repost of the links .


I don't understud..is a new one version of 7.2? Or the same as in past and poster hunt posts?

[turboleak]

what is the difficulty of doing a hex-v2 clone versus a hex-can? Or, maybe put in another way, why the effort to replicate what already exists ( hex-can clones ) instead of spending effort trying to do something new ( hex-v2 clone )?

[Fabio89]

what is the difficulty of doing a hex-v2 clone versus a hex-can? Or, maybe put in another way, why the effort to replicate what already exists ( hex-can clones ) instead of spending effort trying to do something new ( hex-v2 clone )?
i also want to know
i'm waiting a clone version of Hex-v2 that works on MQB Cars

[kaalis]

If someone asks will you lend your genuine hex-v2 for disassembling/research purposes?

[turboleak]

are you replying to my question? if so, does your answer imply that the difficulty on cloning a hex-v2 is having an original cable to research/disassemble?

[hid3]

Yes.
Anyone having HEX-V2 - let me know. We will not disassemble it, don't worry :)

[BASi77]

Found the image of genuine HEX-V2 pcb. CPU STM32F415VGT6.

TOP:

586911

BOT:

586912

[kaalis]

Wow, "bottom side" soldering of obd2 pins looks ugly as hell.
Not possible to make a clone just by looking at pcb :)

[hid3]

HEX-CLONE+CAN are soldered much better than this shit. You hear it, Uwe?
Besides, there're quite a lot Dead-on-Arrival real HEX-V2's. How's that? Dictator, could you please comment about the quality of the "Proudly made in the USA" devices? Or are they actually made in Africa, by the native children? :D

[BASi77]

I do not think that this is the quality of the soldering ross-tech. I can assume that the owner of the cable took a photo after the repair.

[hid3]

I don't think it has been repaired. But flux should always be washed off in any case.
They build these interfeaces in SA and probably China.

[BASi77]

Anyways it is useful to know what the original looks like.

[tk500]

No.
Will not work on new cars.

[FoxMulder]

And x44 is better ?

[hid3]

There's no "better" or "worse". It's just different types. Both are equally good.

[FoxMulder]

and both can not get the new cars?

[liviudiaconu]

MQB platform ONLY REAL V2

[kaalis]

Any new "bugs" in 18.9.1 release?

[liviudiaconu]

Work with seven point two?
L.E. Tested quickly with 16 ecus autoscan.
Serial still resist. LC work. Must testin more time..

L.L.E. Tested again more like 10 mins. Still working.

[whatispro]

Hello guys,


I'm back with some news around my old cable vcds (10.6.4) that i would like to update to a 18.2.0 (english) and 18.2.1 (french),

- Is the 18.2.0 VCDS a stable version or what version do you recommend me ? i would like to be able to run the 18.2.1 french version also , so do you thing that it's possible to use the 2 versions without rewriting the eeprom , please ?


- Do i have to use the loader from the 6.2 / 6.3v of kolimer or can i use the loader from the last package 7.2 v, please, what is the difference, please ?


Thanks in advance for your help.

[Roma77]

Hello guys,


I'm back with some news around my old cable vcds (10.6.4) that i would like to update to a 18.2.0 (english) and 18.2.1 (french),


The 1st thing, i have experienced the VCDS USB eeprom upgrade without a 12V connection , how is it possible ?


I have connected the cable to my computer's USB port and also to the USBASP programmer and in this case, no problem, the process seems working correctly as you can see in following screenshots :


How is is possible ? VCDS cable could be powered by the power delivered by 2 X usb power = 11 V or ?


587618 587619 587622




After i have 2 questions :


- Is the 18.2.0 VCDS a stable version or what version do you recommend me ? i would like to be able to run the 18.2.1 french version also , so do you thing that it's possible to use the 2 versions without rewriting the eeprom , please ?


- Do i have to use the loader from the 6.2 / 6.3v of kolimer or can i use the loader from the last package 7.2 v, please, what is the difference, please ?


Thanks in advance for your help.
There is nothing strange in this, it means that atmega162 is powered from the port usb and the stabilizer is powered on the КL lines, flashing any version of the language you need, English will work too. 2 X usb(0,5A) power ≈ 5,5V 0.9A:tears_of_joy:

[liviudiaconu]

Details, please..

[liviudiaconu]

Wich O.S., and wich cable?
Used on 2 kinds of cables on W7 and W10 64bit. Worked well in autoscan.
One "44" first model with RL and L9637 and one "46" HexV2.

First test is possible to give "Can NR", is an older issue. But the rest..worked well.

[kayne30]

I own a real hex v2
Ich besitze ein echtes Hex v2

[whatispro]

Hello again,

It’ working correctly now.

Thanks !

[igt]

Hi.
I have this cable . Vcds 18.2.1 and i have multiple rod file missing error .. so cable is pratically unusable.

What kind of chip does it have ?
Is it upgradable ?


Thanks

[sahraoui1]

Hi ,reflashe thé câble , it will be ok

[Tyrex]

Hello. This interface can be repaired? Now its not connecting to CAN due a firmware upgrade from official web site (stupid i know). Thx. P.S. 588467588468P.S. Now i see a modification inside with this red cable. This is a SH interface.

[kaalis]

Hi ,reflashe thé câble , it will be okwhere do you see atmega162?

[hid3]

Wrong message

[networkers]

Hi,


Hello. This interface can be repaired?

what is happened to this interface? Bad soldering, maybe short circuit.

Throw it away and buy a new one!

[pocinas]

Hello. This interface can be repaired? Now its not connecting to CAN due a firmware upgrade from official web site (stupid i know). Thx. P.S. 588467588468P.S. Now i see a modification inside with this red cable. This is a SH interface.On the 2nd photo right side Yellow element, capacitor....resolder in correct possition

1st photo. Chip from right side. Pin 20 and 21 have short... it is correct?

[Tyrex]

I allready buy a new Hex v2 18.9. This old one i try to repair-it just for my curiosity. Bad soldering on old interface is not my work, i buy-it like that.

[igt]

where do you see atmega162?


So ? i dont understand...
Is it flashable or not ? And primary ...Is there a solution to Rod files missing error to keep it in life ?

[networkers]

Is it flashable or not

No, it is not updatable, because it has an ARM microcontroller (with non public china firmware inside) instead of Atmega162.
The best part is: The case incl. torx screws :-)

[asd2000]

Yes, same here. Seems to work fine!


hi.... work with orignal DRV Version ? wich version u using ?

my cable works now with 18.2.1 DRV and Loader 7.2

[razvan2003]

I have a 10.6 vcds cable.
I unscrewed it and it's an atmega162V.
I removed STC chip.
I soldered PINS from tutorials from above 100% correctly, i checked twice with multimeter. I gave 12V voltage and the LED stays green, or when i dont it blinks red.
I have a USBASP V2 LC Technology.
And when i want to program, progisp says "chip enable program error" on both cases.
I tried a lot of drivers and still nothing.

Photo with PCB: https://imgur.com/a/4zPAdpP

Thank you for your time!

[Roma77]

I have a 10.6 vcds cable.
I unscrewed it and it's an atmega162V.
I removed STC chip.
I soldered PINS from tutorials from above 100% correctly, i checked twice with multimeter. I gave 12V voltage and the LED stays green, or when i dont it blinks red.
I have a USBASP V2 LC Technology.
And when i want to program, progisp says "chip enable program error" on both cases.
I tried a lot of drivers and still nothing.

Photo with PCB: https://imgur.com/a/4zPAdpP

Thank you for your time!
If you are 100% sure that you are doing everything correctly and you have called up all the contacts and cable at the moment, then the worker thinks that it is erased with ID 1E: 94: 04 on FF FF FF, now it needs to be desoldered and restored through JTAG.

(https://www.jtag.com/ru/)

[macwol01]

Hi Lads

Just updated my cable to Kolimer 7.2.

Can i run VCDS 18.9.1 with 7.2 ?

Is there a test i can run on the cable to check if long coding will work before i actually try ?

thanks

[kaalis]

Yes, save actual coding and just try. If necessary, restore.

[razvan2003]

If you are 100% sure that you are doing everything correctly and you have called up all the contacts and cable at the moment, then the worker thinks that it is erased with ID 1E: 94: 04 on FF FF FF, now it needs to be desoldered and restored through JTAG.

(https://www.jtag.com/ru/)

Can you explain a little more about what i am supposed to do?

Thank you again!!

[BASi77]

Does anyone have photos of the micro-СAN circuit board? What CPU chip is used in it?

588994

[macwol01]

Yes, save actual coding and just try. If necessary, restore.

If long coding is not working due to the cable and i try it and it messes something up.

Then how can i restore it with the same cable that messed it up ?

Has to be another way of testing if long coding will work.

[kaalis]

Benchtest identical ecu.

[jayooo]

Hello everyone,

I am reading the whole thread and trying to understand all the great information. I have had a few Chinese cables in the past, none of which have had Atmega chip, so I am looking to buy a new one with better hardware that I can keep up to date, however I am confused about the best one to buy and I wondered if someone could help me please?

I see obd2cartool.com recommended a lot in this thread, but I am confused about the best one to buy;

https://www.obd2cartool.com/vagcom-1684-full-active-vcds-1684-diy-vag-com-1684-can-reprogram-language-and-version-p-1266?zenid=9k8mbqjtdl8v43ntkn3nen2sn3&zenid=9k8mbqjtdl8v43ntkn3nen2sn3 - This one I see mentioned as a good choice which can be upgraded

https://www.obd2cartool.com/atmega-vag-hexv2-vag-1890-usb-interface-vcds-hex-v2-full-actived-free-shipping-p-1554?zenid=9k8mbqjtdl8v43ntkn3nen2sn3 -This one I see has kolimer's name in the listing, so again this is a good choice? I realise this is probably just Hex Can internals in a v2 case

http://www.obd2cartool.com/vagcom-178-hex-can-usb-interface-vcds-1781-online-update-version-16-multilanguage-p-1263 - This one says I can update online with original software and can stay connected to the internet, can I not use internet with the other options?

The price difference is not that important I just want to make sure I buy the best equipment, but option 3 sounds like the best as I can just update online like original?

Thanks

[kaalis]

choose #2 (fake hex v2), it's voltage regulator doesn't heat up as "previous generation". You can upgrade yourself when it's possible.

[jayooo]

Thanks for the reply kaalis, I will go with #2.

I just have a few more questions (apologies, this is new to me and I have not fully read the whole thread yet) Can internet stay enabled with blocking in the hosts file? Is there a detailed step by step for how to update these within this thread? (Im about 100 pages in so far so I may find it), I have read the info.pdf in the loader download but it is still not 100% clear to me.

Finally, is bootloader already enabled in fake hex v2? Id like to avoid USBASP if possible.

Thanks again

[Mario6]

I had the one from the first link. I have easily updated it from version 18.2.0 EN (I received this version) to 18.9.0 EN and 18.9.0 AKP via USB. I did not pay attention to excessive heat.

[kaalis]

Internet is disabled inside from loader itself, but hosts file will not hurt anyway. Bootloader is unlocked.

Update? Run newer vcds installation and use newer loader if possible.

[jayooo]

Great, thanks kaalis and Mario6 for your help, I will make a purchase and look forward to finally owning a cable I can update!

[skillerkid]

Hi everyone!
I repaired a couple of VCDS cables in the past mostly cablwes up to VCDS805, but today I got a vcds 908 RL version, It has ben updated via internet so now not working.
As I read about 50 pages of this topis I understand it is a :( FT232RL the most difficult one to repair
here's a picture of PCB:
190548
now my questions :)

If I follow this aminebot tutorial :
- Reflash Atmega with 908 dump 908.rar (http://www.digital-kaos.co.uk/forums/attachments/f104/18713d1273711973-tutorial-vcds-805-programming-upgrading-908.rar).
- Remove components IC8 , R50 , R51 , D7 as shown on the pic with red arrows.
- Re-flash FTDI with this dump (http://rapidshare.com/files/386124337/908WORK.rar).
- Re-flash GAL16V8 (ATF16V8) with this dump (http://rapidshare.com/files/386649857/GAL16V8_PLCC.rar).
- Solder 3 wires as shown on the pic with blue lines.
- Extract files in this archive (http://rapidshare.com/files/386648601/VCDS_908.0_mod.rar) to your VCDS directory.
Is there a new method?
What tool do i need to reprogram GAL ?

or can I try this method ? remove the gal :
190550
Thanks in advance for help!!!!

Can you please post a link where i can find the files you mention above? Thank you in advance.

[macwol01]

Link please


Link please

Here

https://www.obd2cartool.com/atm-vag-com-1890-vcds-189-full-active-enfrde-vag-hex-can-crack-cable-free-shipping-p-1566

But id buy this cheaper and will update to 18.9 with v7 loader

https://www.obd2cartool.com/vagcom-1684-full-active-vcds-1684-diy-vag-com-1684-can-reprogram-language-and-version-p-1266

[Roma77]

Sorry, random post.

[IJskonijn]

Hi guys, can someone help me?
I've got a problem with one of my cables. My PC froze and I pulled the cable out, now it doesn't get recognised in Windows.
I tried to delete drivers and reflash with kolimers tool. It succeeds, but when I try to use the cable after flashing, VCDS cant find it. And it doesn't get recognised by Windows.

I hope this makes sense :tears_of_joy:

[macwol01]

Can you check if the cable is recognised on another PC with VCDS installed ?

That way it will eliminate a cable fault or driver/install fault on first PC.

[IJskonijn]

Can you check if the cable is recognised on another PC with VCDS installed ?

That way it will eliminate a cable fault or driver/install fault on first PC.

I will try that this evening, thanks!

[deandc]

Dear Kolimer, HID3 and all other coders,

As everyone is aware, the HEX-V2 interface that we use is just an improved HEX+CAN. R0$$ Tech released the original HEX-V2 to support newer cars and modules. Furthermore did they program a year checking mechanism in the VCDS software, which will tell you that you are using an old interface if you are trying to read a control module on a MY2019 car, although the interface can still read the module. In my opinion this is a sad move, as the old interface can still read out and code the module.

Today I installed VCDS 18.9.1 with VCDS Loader 7.2, hoping that maybe they enabled coding and adaptions for my car (MY2019 Superb), as my interface could still read the modules. But yet again the popup came, saying that my interface was too old. But suddenly I found a bypass around this year checking mechanism, which allowed me to do adaptations and coding on the desired module.

Apparently each time that you select a control module, he will read out the year of the car, so how did I bypass this?

1) Turn on the ignition (no running engine)
2) Read out all the control modules
3) Before selecting the desired control module, turn off the ignition and then select the desired module (don`t wait too long to select the module, as the electricity running through the modules is only for a short period now)
4) Normally he will read the desired module, and the adaptations and coding button will not be greyed out
5) Now you can turn the ignition back on and do your coding/adaptations (AT YOUR OWN RISK!)
6) If you want to go to another control module, please repeat step 3 till 5

I hope this procedure will work for you guys as it worked for me.

@Kolimer and @HID3
Maybe you could create a patch which disables this year checking mechanism?

Regards,
Dean

[hid3]

Do not worry, we are aware of this and this is already taken care of. This was quite unfair purely sales-driven move to make users think that their HEX+CANs are really incompatible in order to promote sales of the new gen expensive interfaces. Many owners who run workshops actually got caught by that and purchased/upgraded.

Funny enough how R0$$ guy made a lot of mistakes where Golf 6, Audi A3 8P and similar cars started getting popups about not suported vehicles :rofl:
One member is already enjoying the improvements. Will you be the 2nd one?

[deandc]

Do not worry, we are aware of this and this is already taken care of. This was quite unfair purely sales-driven move to make users think that their HEX+CANs are really incompatible in order to promote sales of the new gen expensive interfaces. Many owners who run workshops actually got caught by that and purchased/upgraded.

Funny enough how R0$$ guy made a lot of mistakes where Golf 6, Audi A3 8P and similar cars started getting popups about not suported vehicles :rofl:
One member is already enjoying the improvements. Will you be the 2nd one?

Can't thank you guys enough for the hard work you are doing. I will report back to you regarding the update! Cheers

[kaalis]

New releases of ENG and FRM. Enjoy.

[pusho]

Hi guys! Someone has the 12.10.3 version? I lost the CD, thanks in advance

[Mario6]

Hi guys! Someone has the 12.10.3 version? I lost the CD, thanks in advance

Try from here.
(slow download)

https://zachowajto.pl/!t759Hmgt/vcds-beta-12-10-3-installer-china-exe

[pusho]

Try from here.
(slow download)

https://zachowajto.pl/!t759Hmgt/vcds-beta-12-10-3-installer-china-exe

Thanks Mario!

[Hikage]

hello i need info about this cable, do i have a good cable or not because some chip doesnt have information and dont see ftdi.
This is a cable from a seller on aliexpress send it with vcds 18.9 saying cant update and send it with different language like mine is english and french.https://prnt.sc/mch5nchttps://prnt.sc/mch5nc
i have a cd with installer and loader on english and french but used my already installed vcds with kolimer 7.2 and cable
590556590557590558590559

can i use it without risk or do i need to do some special search before like dump the flash with a usbasp before use it on a 2018 golf?

edit:

Elektrik1, before jumping to straight conclusion that some of your cables are really 0x46, better check them manually.

0x44: ATmega 34 and 35 pins are connected to GAL pins 5 and 4 accordingly and GAL pin 9 is connected to some pin on the FTDI (use multimeter in diode testing mode to confirm).
0x46: no connection from ATmega 34 and 35 pins exist to any pins of GAL and GAL pin 9 is NOT connected to FTDI and GAL pin 5 is connected to FTDI.

If you have anything between those two, then you have a cable-mutant
according to what say hid3, i have a 0X44 because i see atmega 34 and 35 connect to PALCE16V8 and pin 9 are connected to (unknow)ftdi pin 9.
i test this one with multimeter for affirm this

[Fabio89]

Do not worry, we are aware of this and this is already taken care of. This was quite unfair purely sales-driven move to make users think that their HEX+CANs are really incompatible in order to promote sales of the new gen expensive interfaces. Many owners who run workshops actually got caught by that and purchased/upgraded.

Funny enough how R0$$ guy made a lot of mistakes where Golf 6, Audi A3 8P and similar cars started getting popups about not suported vehicles :rofl:
One member is already enjoying the improvements. Will you be the 2nd one?

Great to know ! Im also interested if release some patch for MQB 2019+ models

[joker01]

guys vcds ecu number 17 instrument, login is the pin code of the instrument cluster ???

[Hikage]

hello i need info about this cable, do i have a good cable or not because some chip doesnt have information and dont see ftdi.
This is a cable from a seller on aliexpress send it with vcds 18.9 saying cant update and send it with different language like mine is english and french.https://prnt.sc/mch5nchttps://prnt.sc/mch5nc
i have a cd with installer and loader on english and french but used my already installed vcds with kolimer 7.2 and cable
590556590557590558590559

can i use it without risk or do i need to do some special search before like dump the flash with a usbasp before use it on a 2018 golf?

edit:

according to what say hid3, i have a 0X44 because i see atmega 34 and 35 connect to PALCE16V8 and pin 9 are connected to (unknow)ftdi pin 9.
i test this one with multimeter for affirm this



FW Version : 1.96
HW Version : 0x46
Identification : ROSSTECH
Bootloader : Enabled


i joined a progisp backup, i made with progisp before flash or change anything to the cable

this is the store where i buy the cable
https://fr.aliexpress.com/store/product/2018-New-Arrival-VCDS-HEX-V2-Interface-VAG-COM-18-9-VAG-COM-18-9-FOR/621261_32970197026.html


when plug with 12v on my house, i got this
590588

[kaalis]

hello i need info about this cable, do i have a good cable or not because some chip doesnt have information and dont see ftdi.
If you paid for it more than 25-35usd then seller totally got you. You could have found a better fake v2 clone.

[Hikage]

If you paid for it more than 25-35usd then seller totally got you. You could have found a better fake v2 clone.
i pay it 29usd and other cable i see with know to work cable are 2 usd less expensive

[hid3]

Hikage, your cable is 0x44 HW. There is FTDI - it's FT232BL/BM with external EEPROM.

[kospoz]

I have one sklad cable and i have updated to 18.9.i saw many times on uds protocol when i hit engine writes very quickly number from ecu but takes long time to connect . sometimes searching and searching and never saying retrieving slaves.i have reinstalled it again but same thing.other times working good.any tips for this?

[file1]

Hi Everyone,
I have vcds hw 0x44 and tl866 . Can somebody gave me the .jed file for gal/atf or tutorial how to program atf memory?

Thank you

[whatispro]

Hello,

Could anybody tell me what is the difference berween the FTDI FT232RL and the FTDI FT232RQ , please ?

What is the best one and why ?

Thanks in advance.

Cheers

[AceDuk]

Hi to everyone,

I have few questions:
Can VCDS still match(program) immobilizer (IV,V) from [17 - Instruments] and also do i need 4 digit pin like old IMMO2 and IMMO3?
If yes is it same procedure like IMMO2 and IMMO3?
More specific i'm asking for GOLF MK5, Seat Leon 2008, Polo 2007.

Thank you :)

[kowalwalcz]

Hi to everyone,

I have few questions:
Can VCDS still match(program) immobilizer (IV,V) from [17 - Instruments] and also do i need 4 digit pin like old IMMO2 and IMMO3?
If yes is it same procedure like IMMO2 and IMMO3?
More specific i'm asking for GOLF MK5, Seat Leon 2008, Polo 2007.

Thank you :)Special tools, obd. Vcds not working

Wysłane z mojego EML-L29 przy użyciu Tapatalka

[AceDuk]

Special tools, obd. Vcds not working

Wysłane z mojego EML-L29 przy użyciu Tapatalka
So VCDS cannot program key transponder for those cars? GOLF MK5, Seat Leon 2008, Polo 2007

[Col19]

Hi friends

My mission is to install the Kolimer project on the Hexv2 map, here are the images of the map, thank you to everyone for your contributions, your help and your information. Respect to the DigitalKaos community.


591471

591472
Look "Hex V2"

591475
Here you have the model AES

591477
591478
591479

Shame on those who sell this work without permission or even without offering a commission to
☆ Kolimer ☆

Thanks again to everyone for your sharing and your support for the whole community "DigitalKaos" Respect for ☆ Kolimer ☆ the unforgettable man in the world.

[1nteger]

Hi everyone.

I took a vcds 18.9.0 with install cd and loader from aliexpress. I installed vcds to my pc without antivirus and internet connection. I plugged the cable to car and my pc. Test is ok. No fail k1 k2 and can( can sometimes not ready) I have always ‘communication error’ and ‘no response from controller’ faults

I conmected to ecu than after 5 seconds. Communication faults indicated on the pc
What do you think about it?
Any advices for fix the problem?

edit for the pictures591735591737591738591739


CAN:OK and sometimes CAN:not ready ?

ftd2x.dll ı found it. what will ı do with this dll? like cracking old games ? copy to vcds file foldeR ?
Like cracking old games? Copy to vcds file folder?

[hid3]

^^^^^
Well, that is one of the reasons why it's always better to buy from a trusted store, like OBD2CarTool rather than some random Aliexpress seller which sells "almost the same stuff" for much cheaper.

Guys, you need to understand that there is a reason why it may be cheaper. ATmega162 and FTDI chip themselves cost almost half of the cable's price. But there are even more components inside. Sometimes you come accross fake components, missing components or sth similar when getting the "same or very similar" cable from unknown source. I don't believe that for one living in France a few extra bucks for a known-good cable make any sense. Your minimal montly wage is 1150 EUR, isn't it? Go ahead and compare it to the rest of EU countries.

Anyway, it's up to each person to decide what he wants to buy. But sometimes you get what you pay for.

[liviudiaconu]

Hi everyone.

I took a vcds 18.9.0 with install cd and loader from aliexpress. [...]
Any advices for fix the problem?

Photos with both sides of PCB?

[1nteger]

I dont know how can ı upload the picture this website first help for uploading picture and friends sorry about bad english ı cant talk very well in english:(

HEX+Can one side and other side VAG 189

[liviudiaconu]

Repeat:

Photos with both sides of PCB? NOT with case..

[whatispro]

Hello,

Could anybody tell me what is the difference berween the FTDI FT232RL and the FTDI FT232RQ , please ?

What is the best one and why ?

Thanks in advance.

Cheers

[Col19]

^^^^^
Well, that is one of the reasons why it's always better to buy from a trusted store, like OBD2CarTool rather than some random Aliexpress seller which sells "almost the same stuff" for much cheaper.

Guys, you need to understand that there is a reason why it may be cheaper. ATmega162 and FTDI chip themselves cost almost half of the cable's price. But there are even more components inside. Sometimes you come accross fake components, missing components or sth similar when getting the "same or very similar" cable from unknown source. I don't believe that for one living in France a few extra bucks for a known-good cable make any sense. Your minimal montly wage is 1150 EUR, isn't it? Go ahead and compare it to the rest of EU countries.

Anyway, it's up to each person to decide what he wants to buy. But sometimes you get what you pay for.

Hi friends

HID3 friend, i did not know that Aliex ... sell less good quality products than OBD.diy, desolate if i made a mistake, you're no longer experimenting, i know that chips are mostly copies,

Personally i replace the chips according to the pictures shared by the great friends of the Net like Fantomel ...

Dear HID3, my goal here was to help the community of Kolimer and his team "You". As we can take advantage of Kolimer's work, i wanted to do a little bit of service to this great DigitalKaos community, I apologize if I made a mistake.

Thank you for all that you do for us the peoples of the world. Finally, money is not a problem, only i did not want to pay a few more Euro to receive the same final product but i was wrong, if those of OBD.diy are better, then it is the place to buy, if you advise is that you know, thank you again and I will try to delete the link.

Good continuation.

[Fabio89]

Hi everyone.

I took a vcds 18.9.0 with install cd and loader from aliexpress. I installed vcds to my pc without antivirus and internet connection. I plugged the cable to car and my pc. Test is ok. No fail k1 k2 and can( can sometimes not ready) I have always ‘communication error’ and ‘no response from controller’ faults

I conmected to ecu than after 5 seconds. Communication faults indicated on the pc
What do you think about it?
Any advices for fix the problem?

Do you also copy ftd2xx.dll from CD to VCDS directory?
I ask it because usually, CD come with missing this file.
Try donwload VCDSLoader and copy the file to VCDS directory and test again

[sympho]

Anyone know pinout for this cable pcb??
591608591608

[petraa123123]

hello I got a cable vag 178 to this cd VCDS-Release-17.8.0 VCDS-EN-17.1.3 cable can not test I would know someone to advise? in the cable is atmega 162 there is 6pin to programming. the first picture is plugged into the car only in pc

591617591618


ello I got a cable vag 178 to this cd VCDS-Release-17.8.0 VCDS-EN-17.1.3 cable can not test I would know someone to advise? in the cable is atmega 162 there is 6pin to programming.

[alexm1]

Anyone know pinout for this cable pcb??
591608591608Rigth side pcb.
Identify Atmega 162, see the DOT=small circle on it?
There is pin nr.1-Mosi- coresponding to first hole (in the pcb).
1 mosi 2 miso 3 sck 4 reset
See pichttps://uploads.tapatalk-cdn.com/20190130/5542a1df3e5eeb02195abb18ee6ea454.jpg

[alexm1]

Hello,

Could anybody tell me what is the difference berween the FTDI FT232RL and the FTDI FT232RQ , please ?

What is the best one and why ?

Thanks in advance.

CheersI saw deffective cables with both FTDI types, RL it is more easy to be replaced, so...take a good look to choose a cable with Atmega162 that.s your goal.

[petraa123123]

Hello, what do you do with the cable? Thank you.

[1nteger]

ı fixed it guys thanks a lot for helps. I contacted to my seller. He sends me another link for loader. And ı apply new programme and start again. I connected and no faults.
Thanks.

[lucas7117]

Hey techys!
I have '08 Audi Q7. It had a lot of issues. Long story short. Car came from auction. Missing many many modules for MMI
Bought missing modules. Now I got system protection at telephone(Bluetooth) module, mmi interface module(head unit),
and amplifier(sound system). MMI screen finally lights up but there is no sound. Somehow I have to connect all these modules
to this one car. What are my options? Only odis? What about avdi/abrites? I thought about doing it through j2534 box buying subsriction
but they only sell it for 1 year.
All opinions are welcome!

[kaalis]

18.9.1 NEZ released.

[brainsucker]

Hello everyone, and thanks for the work you are doing.

So, is there any place where I can sign-up for beta-testing of the loader with MY2019 support? ;)

Thanks.

[kowalwalcz]

Hello everyone, and thanks for the work you are doing.

So, is there any place where I can sign-up for beta-testing of the loader with MY2019 support? ;)

Thanks.Dream on with MY 2019...

Wysłane z mojego EML-L29 przy użyciu Tapatalka

[brainsucker]

Dream on with MY 2019...
Well, the limitation looks like quite artificial, purely software based, so I don't think it will stand for too long...
Beside that

Do not worry, we are aware of this and this is already taken care of....
One member is already enjoying the improvements. Will you be the 2nd one?

[wamba16]

ı fixed it guys thanks a lot for helps. I contacted to my seller. He sends me another link for loader. And ı apply new programme and start again. I connected and no faults.
Thanks.

can you put the link of the new charger please, I have the same problem with this type of cable

[ccr64k]

32 bit version unpacked

[kaalis]

So, you checked all download links that Kolimer have posted?
Read forum rules about your first post.

[ccr64k]

Is it safe to use VCDS 18.9.1 with Kolimer 7.2? Test with 12 V and GND on OBD without being connected to CAN went fine.

[kaalis]

There are 2x 18.9.1 (ENG) released this year. Last doesn't let to connect to Engine with CAN.
It's safe. How not safe can it be?

[lucas7117]

Hey techys!
I have '08 Audi Q7. It had a lot of issues. Long story short. Car came from auction. Missing many many modules for MMI
Bought missing modules. Now I got system protection at telephone(Bluetooth) module, mmi interface module(head unit),
and amplifier(sound system). MMI screen finally lights up but there is no sound. Somehow I have to connect all these modules
to this one car. What are my options? Only odis? What about avdi/abrites? I thought about doing it through j2534 box buying subsriction
but they only sell it for 1 year.
All opinions are welcome!

So I just had some help from my college who has vvdi prog and vvdi he was able to take protections off.

[ccr64k]

There are 2x 18.9.1 (ENG) released this year. Last doesn't let to connect to Engine with CAN.
It's safe. How not safe can it be?
Whether it will not brick the ATMEGA cable. Do you know, where the version of 18.9.1 which is able to connect to Engine using CAN can be downloaded?

[BASi77]

... the version of 18.9.1 which is able to connect to Engine using CAN can be downloaded?

may be v 2019.1.14.0 : http://ge.tt/7pxHyIu2

[Tib82]

may be v 2019.1.14.0 : http://ge.tt/7pxHyIu2
I checked the SHA of the 19.8.1 versions.

c9da064c588913c9773f6306d9bb03f9dced1108 << BASi77's link
e247ce66ec07b69ccd3b52802745e05870f62947 << Current version on the official site

Is it means that the BASi77 shared the first release what works well, and the current (second) version of 18.9.1 is $h!t (cannot connect to the engine)?

[pocinas]

Hello,

Could anybody tell me what is the difference berween the FTDI FT232RL and the FTDI FT232RQ , please ?

What is the best one and why ?

Thanks in advance.

CheersJust diffrent Package

RL is SSOP28 and RQ is QFN32

[ccr64k]

may be v 2019.1.14.0 : http://ge.tt/7pxHyIu2
Definitely different unpacked exe, I am going to publish unpacked release 1 exe, so you can compare. So far different OEP and about 32 bytes more data in .rdata section in release 2.

[ccr64k]

32 bit version unpacked

[kaalis]

18.9.1 NEZ released.
and once more.

+AKP