Latest LCode version

   #181  

NEtech

VCDS Distributor
VCDS Distributor
Joined
Feb 7, 2014
Messages
3,646
Reaction score
5,803
Location
Denmark
VCDS Serial number
C?ID=56995
So we agree on removing "Expert user" :confused:
 
   #182  

Sebastian

Ross-Tech Employee
Staff member
Ross-Tech Employee
Joined
Feb 13, 2014
Messages
2,789
Reaction score
3,142
Location
Magdeburg, Germany
VCDS Serial number
HN0-nnnnnn
No, but the standard behavior when being started externally (w/o VCDS) should be to allow bit selection.

If this was a first release of a new assist/tool, I'd agree of this being an expert view/functionality but since both LCode 1 & 2 have always behaved this way, it's IMO not good practice to change this behavior - especially w/o notice.
 
Last edited:
   #183  

Boki Ar

VCDS Distributor
VCDS Distributor
Joined
Oct 27, 2014
Messages
3,109
Reaction score
2,921
Location
Arandjelovac, Serbia
VCDS Serial number
C?ID=57300
Thank You! :thumbs:
Then you see a button [Remove VIN
1150600F492A00FB880E06E792220041BF0C00
11666066496600668866066692660041BF0C00 insert 66 VIN
11__60__49__00__88__06__92__0041BF0C00 w/o VIN

I like it :cool:
 
   #187  

hadez16

Verified VCDS User
Verified
Joined
Jun 19, 2017
Messages
826
Reaction score
703
Location
Germany
VCDS Serial number
C?ID=289891
I finally pushed myself discarding the old LCode and start using the new LCode....
Excerpt from label file:

LC,09,0,Market,0=ECE / 1=NAR
LC,09,4~7,headlamp_coding_word (HEX)

Why is LCode not displaying that placeholder label "headlamp_coding_word (HEX)" ?
It only says "none found".

eecminq.png


EDIT: I just tried 2.1.11.0, same behaviour.
 
   #188  

Sebastian

Ross-Tech Employee
Staff member
Ross-Tech Employee
Joined
Feb 13, 2014
Messages
2,789
Reaction score
3,142
Location
Magdeburg, Germany
VCDS Serial number
HN0-nnnnnn
Because the syntax in your example is incorrect.
 
   #189  

hadez16

Verified VCDS User
Verified
Joined
Jun 19, 2017
Messages
826
Reaction score
703
Location
Germany
VCDS Serial number
C?ID=289891
The syntax comes from the label file which was not created by myself, it's a grabbed experimental label from Unit 4B (3Q0-907-338).
The old LCode does show it:

EaXOhT8.png
 
   #190  

NEtech

VCDS Distributor
VCDS Distributor
Joined
Feb 7, 2014
Messages
3,646
Reaction score
5,803
Location
Denmark
VCDS Serial number
C?ID=56995
I can look at it, but experimental data is loaded in experimental "mode" (yellow screen).
Is it not loading okay, when it is standard label format file?
 
   #191  

Sebastian

Ross-Tech Employee
Staff member
Ross-Tech Employee
Joined
Feb 13, 2014
Messages
2,789
Reaction score
3,142
Location
Magdeburg, Germany
VCDS Serial number
HN0-nnnnnn
IMO LCode behaves as expected here, the input data is incorrect due to VW supplying incorrect data. This is why "experimental data" should not be used as a standard, only as a fallback.
 
   #192  

hadez16

Verified VCDS User
Verified
Joined
Jun 19, 2017
Messages
826
Reaction score
703
Location
Germany
VCDS Serial number
C?ID=289891
IMO LCode behaves as expected here, the input data is incorrect due to VW supplying incorrect data. This is why "experimental data" should not be used as a standard, only as a fallback.
VW datasets incorporate the translation to LCode label files? Didn't know about that.... :facepalm:

I can look at it, but experimental data is loaded in experimental "mode" (yellow screen).
Is it not loading okay, when it is standard label format file?
Does the "yellow mode" read label files different to "normal mode"?
It is just a label file with a description of a bit-range that worked in old LCode but not in new LCode :)
 
   #193  

Uwe

Benevolent Dictator
Administrator
Joined
Jan 29, 2014
Messages
50,562
Reaction score
34,500
Location
USA
VCDS Serial number
HC100001
the input data is incorrect due to VW supplying incorrect data.
Is it incorrect, or just incomplete?

I would guess the newer LCode wants at least some values for the bit field?

@hadez16, try:

LC,09,4~7,00,Headlight Type 1
LC,09,4~7,10,Headlight Type 2
... and so on.

-Uwe-
 
   #194  

hadez16

Verified VCDS User
Verified
Joined
Jun 19, 2017
Messages
826
Reaction score
703
Location
Germany
VCDS Serial number
C?ID=289891
I try to clarify again: this is *not* a custom label file created by one individual, it comes like this out of VCDS for the experimantal coding!
So there is either some issue with LCode by having changed the expected syntax for bit-ranges, or some issue with VCDS because it does not follow that new syntax ;)
 
   #195  

NEtech

VCDS Distributor
VCDS Distributor
Joined
Feb 7, 2014
Messages
3,646
Reaction score
5,803
Location
Denmark
VCDS Serial number
C?ID=56995
To clarify, that label file is not public available.

Does the "yellow mode" read label files different to "normal mode"?
Yes, "yellow mode" data is "Machine made".
It is just a label file with a description of a bit-range that worked in old LCode but not in new LCode :)
Is a bug in old LCode:)
 
Last edited:
   #196  

AINils

VCDS Distributor
VCDS Distributor
Joined
Apr 3, 2020
Messages
1,075
Reaction score
937
Location
Germany (AIB)
VCDS Serial number
C?ID=56975
I have access to a car (my own) with this ECU tomorrow in the evening. Can try different things if some help is needed
 
   #197  

NEtech

VCDS Distributor
VCDS Distributor
Joined
Feb 7, 2014
Messages
3,646
Reaction score
5,803
Location
Denmark
VCDS Serial number
C?ID=56995
And as Sebastian wrote incorrect syntax.
What should LCode show, for that string, HEX, 00, 10, 20, 80 etc. !
 
   #199  

hadez16

Verified VCDS User
Verified
Joined
Jun 19, 2017
Messages
826
Reaction score
703
Location
Germany
VCDS Serial number
C?ID=289891
I just tested this at my car.

"Yellow mode" does it correct:

d8ePG5U.png


Why the hell does "yellow mode" read that piece:
LC,09,4~7,headlamp_coding_word (HEX)
...differently compared to "normal mode"?

Some reason for switching back to buggy old LCode :D
 
   #200  

Sebastian

Ross-Tech Employee
Staff member
Ross-Tech Employee
Joined
Feb 13, 2014
Messages
2,789
Reaction score
3,142
Location
Magdeburg, Germany
VCDS Serial number
HN0-nnnnnn
Step 1: Understand, that you do not know all context.
Step 2: Understand, that you are using data in a way it was never meant to be used.
Step 3: Understand, that this is not a problem a regular user would ever see/experience.
 
Back
Top