Latest LCode version

[etz2k]

OK, now it works fine if i use "LC,00,0+,..." lines before the "LC,00,0,..." lines, vice versa it don't (still overwrite the description, but no problem if you know it).
But, if i load a new LBL in LCode the "new extra infos" from the LBL before is still be displayed, even if the new LBL don't include them. Only exit and restart LCode help. Seem like loading a new LBL needs something like a memory clear ?

 

[NEtech]

I hope it is better now.

 

[NEtech]

@NEtech it would be helpful to highlight the Byte in "String" to see in which place the actual byte ist placed. Like in older Lcode V1.
This is one of the things why iam actual using old Version. Its hard to find correct place in newer cars with coding with a lot of byte

You see the current Byte number of the "String" and the Byte value in hex and binary under the "String"
I have not used the old version for many years and will never use it.

How do use long coding, do you know what Byte you want to check/change?
If so, then Arrow Up, End, Home, change the the number to the number you want check/change.
Also you can click somewhere on the "String" where you think the Byte is you are searching, and then use key up/down/end/home etc..
I don't see that is difficult, much easier as trying to click on a box and hope it is right.
I use it many times every day.

The old lcode is to big in my opinion with long codings.

 

[etz2k]

I also use only 2.0 because it's much better, but if you can highlight the actual selected byte in the string again, would sometimes give a better/easier oriention, especially for the longer byte strings. If i switch between different windows i think sometimes "where was i at last", so a "bookmark" would be nice for my little brain.

 

[AINils]

Totally agree with user @etz2k
In longer codings like ABS, MLBevo A5 and some other it's quite terrible to come back to last point. Wrote a lot of label by myself but only using old Lcode one in this case as I have a better orientation.

 

[etz2k]

@AINils and @NEtech, i don't know why i haven't realized the green bar under the coding string, that shows the actual position, maybe i'm blind

 

[etz2k]

Hi NEtech,
i found a smal glitch in LCode (used latest ver.) as i writing my own label for a ABS, if there is only 1 option for a pull down menu and a red info line for a byte.

works not:

;
LC,03,0~7,8D,|  "V"
LC,03,1=,        8th VIN digit
;

works not:

;
LC,03,1=,        8th VIN digit
LC,03,0~7,8D,|  "V"
;

works:

;
LC,03,0~7,8D,|  "V"
LC,03,0~7,FF,|  any second option
LC,03,1=,        8th VIN digit
;

works also ( if the info line is disabled):

;
LC,03,0~7,8D,|  "V"
;LC,03,1=,        8th VIN digit
;

There is also another glitch that was not there before.
Till your release version from 28.02.2023 my own (beta) LBL for TT ABS works fine, but since the releases from 05.03. there is a problem. I now always get the "access violation" message if i made any changes on byte 8 and above by activate or deactivate the small Bit fields and go to next byte. If i made the changes in the binary field the problem don't occure. Maybe the problem is my lable, but it worked w/o a problem before
If you have some time maybe you can take a look

Here is my lable:

8S0-907-379.lbl

drive.google.com

 

[NEtech]

Maybe this one is better.

Just for info, these text are normally´this way:

LC,02,0+,Breakdown of manufacturer gearbox codes:e.g.: MQ350-6F
LC,02,1+,M    Manual gearbox
LC,02,2+,D    Double-clutch gearbox
LC,02,3+,Q    Transverse mounting
LC,02,4+,350    Rated torque capacity
LC,02,5+,6    Number of gears
LC,02,6+,F    Front-wheel drive
LC,02,7+,A    All-wheel quattro drive

LC,05,0~7,99,- VIN Byte (13th Digit): 0
LC,05,0~7,9A,- VIN Byte (13th Digit): 1
LC,05,0~7,9B,- VIN Byte (13th Digit): 2
LC,05,0~7,9C,- VIN Byte (13th Digit): 3

 

[etz2k]

The new version seems to work fine

Just for info, these text are normally´this way:

LC,02,0+,Breakdown of manufacturer gearbox codes:e.g.: MQ350-6F
LC,02,1+,M Manual gearbox
LC,02,2+,D Double-clutch gearbox
LC,02,3+,Q Transverse mounting
LC,02,4+,350 Rated torque capacity
LC,02,5+,6 Number of gears
LC,02,6+,F Front-wheel drive
LC,02,7+,A All-wheel quattro drive

Yes, i'm aware that i don't use it like intended by you. I only tried to use more lines then 8 in the info window. Maybe you can extend the number of possible lines a bit and activate the scrollbar on the right side of the window?


I just tried to make the VIN-Byte selection a bit more short and clearly, without show the info/describtion for every possible letter/number, because it's always the same for every selection of this byte.

 

[etz2k]

Hi NEtech,
it's me again
It seems like that a fix in the last version creates a new glitch.
Now the red info line ( LC,0x,x=, ) seems to work only if for this byte is also a pull down menu, without the pull down menu it doesn't display the red info line.

 

[NEtech]

Please test latest download.

 

[etz2k]

Hi Nils,
there seems to be a small glitch in the last version, that was not there before.
I tried to pinpoint the glitch a bit.

If there is a pull down menu for any byte and in the scripts following byte is a info line, the info line will not be displayed.

In this example the "This is only info line of Byte X" will not be dispayed.

;
LC,03,0~7,04,   Option 1
LC,03,0~7,08,   Option 2
;
LC,08,0=,This is only info line of Byte X
LC,09,0=,This is only info line of Byte Y
;

different bytes, but still the same problem

;
LC,08,0~7,04,   Option 1
LC,08,0~7,08,   Option 2
;
LC,15,0=,This is only info line of Byte X
LC,16,0=,This is only info line of Byte Y
;

 

[NEtech]

Yes, I saw your PM and have tested for some time, but after the change for "experimental pulldown", it is to easy a new bug is coming up.
And I have not had so much time, have been sandblasting old car, make a painting cabin, paint car, engine etc..
I have started making a bigger change, I will see if I should get time this weekend.

 

[etz2k]

Sorry, i'm not trying to push you (i don't know if you read my PM)
I only tried to pinpoint the problem a bit, because i send you a whole ABS Label.

 

[NEtech]

Please test latest download here.
I will test more this week.

{2.1.0.0 25.Jun.2023}
{If no ini then file left top of window is 20,30}
{Changed two procedures into one}
{More correct red info messages or new bugs?}

 

[etz2k]

Hi Nils,
i'm sorry, but it seems like the latest fix/workaround greates a new glitch

If i additionally insert a pull down menu in byte 6, the glitch is gone.

Above the new version with the glitch at bit 0 line, below the previos version w/o this glitch

 

[NEtech]

I have no time for testing right now, but you can test a new update, if you want.

 

[etz2k]

Hi Nils,
the previous glitches seems to be fixed,
but since version 2.1.0 it's not possible to load a different lable, if LCode is started in VCDS. If i start only LCode, the loading of a lable is no problem.

 

[NEtech]

Please test latest download here.
{2.1.1.0 12.Jul.2023}
{Changed label file read procedure completely}

 

[NEtech]

@etz2k has done some more testing
Please test latest download here.
{2.1.3.0 24.Jul.2023}
{If load label file is canceled, current label file data was deleted}
{Fix if label file load is canceled and then label file is loaded}