Latest LCode version

   #81  

VWT6

Verified VCDS User
Verified
Joined
Jan 15, 2017
Messages
111
Reaction score
202
Location
Finland
VCDS Serial number
C?ID=295527
Hmmm... am I missing something obvious but LCode_2 (2.0.12) doesn't seem to work for me.
1. Select byte 1, click LCode_2
2. No coding - ok!
3. LCode_2 opens byte 0 - ok (certainly the preferred would have been to have byte 1 still selected).
4. Select byte 1 - individual tick boxes disappear and can't get them to show for byte 1 :banghead:


The Classic LCode 1.0.9.12 works just fine (the tick boxes).
 
   #83  

VWT6

Verified VCDS User
Verified
Joined
Jan 15, 2017
Messages
111
Reaction score
202
Location
Finland
VCDS Serial number
C?ID=295527
Thank you for quick update. Now the tick boxes work. Perhaps worth to mention that I had to delete LCode.ini to make the new version to launch.

However, then came up against another quirk not seen before.

So, I did the steps around the BCMas as before - looked good.
Exited without saving, closed the controller, etc. and moved to another controller (Battery regul.) and launched again LCode2.
(1) Interestingly the LCode2 came up with the coding from the previous controller (BCM).


(2) Probably worth to mention that after getting the leftover coding and exiting LCode2, the LCode2 won't launch again at all - not in the same module neither elsewhere, not even by restarting VCDS.
Deleting LCode.ini seems to clear this non-launch issue.
Thanks.

PS. Just in case being relevant, the laptop in question (fresh Win10) -->
 
   #84  

NEtech

VCDS Distributor
Joined
Feb 7, 2014
Messages
2,598
Reaction score
4,194
Location
Denmark
VCDS Serial number
C?ID=56995
Try to change Copy-Clip in lcode.ini to "0" if it is "1"
Copy-Clip=0
 
   #85  

VWT6

Verified VCDS User
Verified
Joined
Jan 15, 2017
Messages
111
Reaction score
202
Location
Finland
VCDS Serial number
C?ID=295527
Thanks again! Indeed the "Copy-Clip" was "1". The change to "0" did the trick :thumbs:

Clicking LCode2 back and forth discovered following feature:
(1) Launch LCode2 - it comes up nicely below the long coding helper​
(2) Exit LCode2​
(3) Launch LCode2 again - it comes up in location below where LCode2 window at (1) was.​
(4) Exit LCode2​
(5) Launch LCode2 again - it comes up in location below where LCode2 window at (3) was, thus almost falling off my screen.​
(6) Exit LCode2​
(5) Launch LCode2 again - it comes up in location below where LCode2 window at (5) was, thus now way below visible area of my screen.​
Anyways, this is not a big deal - who would launch LCode2 several times in a session within a module :D - and of course I can always use "Move Window" to drag it back up.
 
   #87  

Mork

Verified VCDS User
Verified
Joined
Dec 18, 2015
Messages
7
Reaction score
2
Location
Canada
VCDS Serial number
C?ID=30926
Here is the latest LCode version.
{2.0.14.0}
{Bug fixed from reading tod files}
{Bug long coding did not use lowercase character}
{Small improvements}

Hello, i got the following error when trying to open Lcode.

Pressing Ok doesn't allow to continue, only abort and then i'm back at the same place.

MpOY0mP.jpg
 
   #88  

Dana

Administrator
Staff member
Ross-Tech Employee
Joined
Jan 29, 2014
Messages
4,710
Reaction score
6,952
Location
Western PA, USA
That looks like a 2018 Mk7/MQB based 03-ABS module with 47 Byte coding. Does this happen on any other modules with shorter coding (01-Engine, 08-Auto HVAC, etc)?
 
   #89  

NEtech

VCDS Distributor
Joined
Feb 7, 2014
Messages
2,598
Reaction score
4,194
Location
Denmark
VCDS Serial number
C?ID=56995
By coincidence I have a similar car available right now, but I have been able to generate that error.
Do you just press [Long Coding Helper], then the error comes up?
Do you have a slower or a fast computer?
You start VCDS and go to ABS?
Why is there an Autoscan running in the rear of the picture?

lc03error.png
 
   #90  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
35,013
Reaction score
24,891
Location
USA
VCDS Serial number
HC100001
Why is there an Autoscan running in the rear of the picture?
I would guess he ran an Auto-Scan (or GVL on the Auto-Scan screen) and then double-clicked on the entry for ABS in the GVL listing.

-Uwe-
 
   #91  

Mork

Verified VCDS User
Verified
Joined
Dec 18, 2015
Messages
7
Reaction score
2
Location
Canada
VCDS Serial number
C?ID=30926
By coincidence I have a similar car available right now, but I have been able to generate that error.
Do you just press [Long Coding Helper], then the error comes up?
Do you have a slower or a fast computer?
You start VCDS and go to ABS?
Why is there an Autoscan running in the rear of the picture?

lc03error.png

Hello, Uwe is correct, I open VCDS, click auto-scan, then gateway list and double click on the module.
I have a fast computer and had actually changed the ABS coding on the exact same car (2018 GTI) with no issues a couple weeks back.
Since then there was a VCDS update as well as a firmware on the dongle.
Since the updates I get that error using the same laptop, dongle and car.
I didn't try all the modules but had no issues with at least 3-4 other modules on that car.

Luckily I had saved the full long coding that I wanted to change in ABS previously so I was able to just paste it in "new coding" and it worked.
Its really clicking on long coding helper that wouldn't work.
 
  • Informative
Reactions: Uwe
Top