Latest LCode version

[NEtech]

Or do i use the ",I," code line function wrong?

I check the rest later, but yes you use it wrong
I is for airbag info.
The info must be after the coding text or the red LC,00,6=, LC,00,7= ...

 

[etz2k]

I is for airbag info.
The info must be after the coding text or the red LC,00,6=, LC,00,7= ..

@NEtech can you give me an example how it should look like, please?
Seems i'm a fool, i only get errors.

 

[NEtech]

About what
"I", that is internal use, no use for your examples.
For "=":
LC,00,2=,Data i Byte 08 & Byte 23
LC,00,4=,Data i Byte 08 & Byte 23

 

[etz2k]

For "=":
LC,00,2=,Data i Byte 08 & Byte 23
LC,00,4=,Data i Byte 08 & Byte 23

I think you like to kidding me a bit

 

[NEtech]

If needed for new VCDS release.
Here is the latest LCode version.
{2.0.18.0}
{Possible to copy Short Coding to Windows Clipboard again, Insert button}

 

[etz2k]

I tried the the "LC,00,X=, Info" between 2 pulldown menu, but then the 1. pulldown menu don't work properly. Seems like i do things, that are not intended by you.
Sorry, it's my fault.
My goal was to insert infos in the MK60EC1 LBL (coding), so that the coding is a bit easier to understand, but it shouldn't look so unclear, because of to much text in a line/menu (but that's not easy).
But anyway your prog is really great.

 

[etz2k]

Hi @NEtech,
can you make it so, that the use of the "Ctrl + F12" function, to remove the VIN-Bytes, also pay attention to the LBL-file byte description? Because only remove the VIN-Bytes mix up the description for the bytes (if you don't use a special LBL that's w/o the VIN-Bytes).

The small window that show the mirrored Hex value is a nice help, but a function in the script language to define (for example) that the Hex value of byte 20 is the mirrored Hex value of byte 12, whould be so great for coding sometimes.

 

[NEtech]

can you make it so, that the use of the "Ctrl + F12" function, to remove the VIN-Bytes, also pay attention to the LBL-file byte description? Because only remove the VIN-Bytes mix up the description for the bytes (if you don't use a special LBL that's w/o the VIN-Bytes).

If possible, I don't think it is so easy.
I tried to change some of the xpl files and remove VIN, it takes about 2 minutes (used Visual Studio Code).

The small window that show the mirrored Hex value is a nice help, but a function in the script language to define (for example) that the Hex value of byte 20 is the mirrored Hex value of byte 12, whould be so great for coding sometimes.

Please explain with an example.
What script language?
I don't calculate between 2 different Bytes, if for example Byte 20 is 0x43, then the mirrored value is 0xC2

 

[etz2k]

If possible, I don't think it is so easy.

OK

What script language?

How do you call the language in the .LBL or .XPL files ?

I don't calculate between 2 different Bytes, if for example Byte 20 is 0x43, then the mirrored value is 0xC2

Yes, i know that, it only shows the mirrored value of the selected byte in the small window (on the right side).

Please explain with an example.

My question was/is, if you can add a commando in the "script language" of the LBL/XPL files, that can convert the hex value of a defined byte and automatic write this new hex value to another selected byte?

Example for a ABS Coding:

LC,00,4~7,10,|  Ibiza Hatch & ST (6J)
LC,00,4~7,20,|  Polo Hatch (6R)
LC,00,4~7,30,|  A1 (8X)
LC,00,4~7,40,|  Fabia / Roomster (5J)
LC,00,4~7,50,|  Polo Sedan (61) (rus)
LC,00,4~7,60,|  Polo Sedan (60)
LC,00,4~7,70,|  Fabia Sedan (Skoda Rapid)  (NA)
;
LC,14,#0       ;"New Commando" to read the hex value of byte 0 (or any other defined byte) and insert the mirrored hex value here (byte 14) automatic,
                 if hex value of byte 0 is edited by the user. Also disable to edit byte 14 by user. (Maybe only a info message like: "Mirror-Byte, use byte 0
                 to edit" or so.)
;
LC,15,0,Info

I hope you understand what i mean