Latest LCode version

[hadez16]

I don't need no knowledge of all contexts for trying to make the best out of the applications in order to help people and the community.

A huge part of the VCDS community is held together, and new fans and buyers are aquired, because there exist people who solve complex problems because of the ability of doing offline coding.
Not everyone has ODIS-E where a complete HTML car backup includes all the TXT coding values coming from the datasets, besides the adaptation channels. That's no secret stuff anymore really.

According steps for you: Understand, that "power-using" is not a bad thing.

 

[NEtech]

Latest download here.
{2.1.12.0 - 5.Mar.2024}
{Small corrections}

 

[hadez16]

Thank you very much Niels! The topic above is fixed in that version, great stuff.

 

[Paskal]

Thank you Niels
Good work. The CZ language is already there.

 

[AINils]

@NEtech
Got a small issue during label creation in LCode. If I use a such Synthax it will end in loosing select Box.
Bug is in 2.1.12.0 and also in LCode Classic. Is there any workaround for this?
If I remove the "LC,19,(x)=" line, then it will show correctly

LC,19,0~1,01,A3, S3, RS3 [Standard]
LC,19,1=,RDZ VL
LC,19,2~3,04,A3, S3, RS3 [Standard]
LC,19,3=,RDZ VR
LC,19,4~5,10,A3, S3, RS3 [Standard]
LC,19,5=,RDZ HL
LC,19,6~7,40,A3, S3, RS3 [Standard]
LC,19,7=,RDZ HR

 

[NEtech]

Latest 2.1.13.0 download here.
{After very long coding, left startup was not the old normal location}
{Bug with many multibyte and many red info text lines}

This did work, but there was also another little bug.

LC,00,0~1,01,A3 - S3 - RS3 [Standard]
LC,00,2~3,04,A3 - S3 - RS3 [Standard]
LC,00,4~5,10,A3 - S3 - RS3 [Standard]
LC,00,6~7,40,A3 - S3 - RS3 [Standard]
LC,00,1=,RDZ VL
LC,00,3=,RDZ VR
LC,00,5=,RDZ HL
LC,00,7=,RDZ HR

The testing I done so far looked good, but there many combinations.

 

[NEtech]

Test version 2.1.14.0 download here.
For new 200 Byte Audi 2024+ [09] Coding.
If standalone (not from VCDS), one can press Ctrl V with the 200 Byte Coding, after LCode is started.
Or start LCode, when 200 Byte Coding is in Windows paste buffer, as normal.

{2.1.14.0 - 13.Jan.2025}
{Now remove VIN from 15 Byte long}
{Support for 200 Byte Coding}
{64bit version}
{PageDown/PageUp jump 10 Bytes}

 

[AINils]

Have a small issue in latest Lcode 2.1.14.0. First thought it is a problem with my computer, but this issue is on all computer which are VCDS used in my sphere.

https://imgur.com/a/bpW8OdV

If I use older 2.1.12.0 issue is solved. Doesn't matter if I use VCDS or load a custom label

 

[Sebastian]

By "small issue" are you referring to the displayed items not being in sync/aligned with the individual bits on the screen?

When describing issues, supposed bugs etc. please make sure whoever your reports are adressed to, has a workable and clear description of the problem to go with. While some things may be obvious (to you), precision is key to fix these.

 

[NEtech]

Yes there are problems with the 2.1.14 test version for 130+ Byte.
I have not had time to debug the last month.

 

[hadez16]

How did that test version make it into the release version?

 

[Vdub]

indeed.. its very buggy

 

[NEtech]

Test version as stated.

 

[Dana]

Right and 2.1.14 was in the final Beta dataversion update. It accidentally made it to *an internal testing Release 25.3 version* in late February but that was short lived. We realized the mistake and pulled it out before the end of the month. I believe it was online like that for less than 24 hours.

If you guys have VCDS set to check for updates make sure to let that run. It has a fix for basic settings, tweak related to the MyAutoScan file limits and would correct this LCode issue for anyone that *ran an internal test version* before Release 24.7 expired.


Edit: *Indicate corrections. The only release version this made it into was for internal testing.

 

[Uwe]

I believe it was online like that for less than 24 hours.

I don't think it was ever in the published Release, only in some RC installer builds..?

-Uwe-

 

[Vdub]

everytime VCDS says update i'll update because the Beta often doesn't recognise the dongle if the version is outdated.. and i use it 6 days a week..

 

[hadez16]

I don't think it was ever in the published Release, only in some RC installer builds..?

-Uwe-

It is, or was, in the german DRV release.

 

[Sebastian]

@hadez16 All current versions should include 2.1.13.0, this applies for the English Release as well as other non-English Releases as well.

@Vdub It is extremely unlikely, that an update is offered "every time" you use VCDS. The update check only queries for a new version once a day. There were some relevant issues with the first published Release 25.3 and it's dataset which led us to push the automated/online update here, in order to make sure you do not run into any known problems, while heavily relying on VCDS during your 6 day work week.

 

[Uwe]

It is extremely unlikely, that an update is offered "every time" you use VCDS.

Nor do I read that into what he wrote. My interpretation of what he wrote is that he does any update every time one is offered by VCDS, whenever it does offer him one.

because the Beta often doesn't recognise the dongle if the version is outdated..

Yes, that is correct. Beta versions stop working at some point. But Release versions never do. They will only nag you that there should be a newer version available, but if you dismiss that nag, they will continue to work.

-Uwe-

 

[NEtech]

Test version 2.1.15.0 download here.
{2.1.15.0 - 11.Mar.2025}
{Bugs corrected for support of 200 Byte Coding}