[TheNine90]

The flm data for right and left is always the same. It might be the wiring that differentiates them.
For the sweeping right to left, does coding using ECE typecode do anything?

[yamanote]

Originally Posted by TheNine90

The flm data for right and left is always the same. It might be the wiring that differentiates them.
For the sweeping right to left, does coding using ECE typecode do anything?

Coding US headlights with ECE typekey results in the DRLs no longer working, so no animation at all. The only thing that lights up are the light strips under the main beam.

[TheNine90]

Is there a G20 with US headlights that have sweeping right to left lights?

[yamanote]

Originally Posted by TheNine90

Is there a G20 with US headlights that have sweeping right to left lights?

No, the US welcome animation just briefly pulses brighter then back to normal brightness.

[TheNine90]

So it might be a hardware limitation? Or there might be some more coding in the BDC?

[MichaelNRW]

Originally Posted by TheNine90

So it might be a hardware limitation? Or there might be some more coding in the BDC?

Probably something like that.

Can someone provide me a G20 LCI US ncd via PM?
I´ll compare it to the files i got.

[Ghostsf30]

Originally Posted by MichaelNRW

Probably something like that.

Can someone provide me a G20 LCI US ncd via PM?
I´ll compare it to the files i got.

Do you still need the US LCI files?

[MichaelNRW]

Originally Posted by Ghostsf30

Do you still need the US LCI files?

Yes

[Ghostsf30]

Originally Posted by MichaelNRW

Yes

Could you tell me which files / what data you need exactly so I can send it over

[MichaelNRW]

Originally Posted by Ghostsf30

Could you tell me which files / what data you need exactly so I can send it over

It´s the FLM2 called CAFD_00006DF0_XYZ_XYZ_XYZ.ncd
XYZ represent the version of the software on your FLM2 ECU.

[Ghostsf30]

Originally Posted by MichaelNRW

It´s the FLM2 called CAFD_00006DF0_XYZ_XYZ_XYZ.ncd
XYZ represent the version of the software on your FLM2 ECU.

Hopefully I did this right lol. Here’s the link with the ncd file:

https://mega.nz/file/fEEHzbzS#1AAt0S...3IgGRXv6M5GhrY

[mrpingu]

Just chiming in with a suggestion, did anyone take a look what the data contains?

I have been looking at a older FLM / FLE module and I found the following matrix. Maybe it is kind of the same matrix?

LedChannel follows a sequence with intensities for a period of time


LedChannel
Intensity
TimeDelta
RampType???


I have a older vehicle but it might be something that gives some understanding for the data in the staging arrays

[Hyperion42]

I am also trying to make sense of the data, but am stuck. For example, the pre LCI G20 data seems to have 5 individual transitions, while in the video I can only see 4 different ones:
1. HB and LB onat low brightness
2. DRL on
3. HB and LB high brightness
4. HB and LB to medium brightness
Can someone identify a 5. transition?

@Michael, for the videos that you posted, did you only change the Staging1 amd Staging2 values to the other models, or the entier data of the ecu? I am wondering where the mapping in the data to the modules are...

[MichaelNRW]

Originally Posted by Hyperion42

@Michael, for the videos that you posted, did you only change the Staging1 amd Staging2 values to the other models, or the entier data of the ecu? I am wondering where the mapping in the data to the modules are...

I only changed the Staging1 and Staging2 values.
The rest of the data isn´t compatible to the PreLCI because the LCI and G8x have more controllable parts of the headlights.
e.g. the tubes can be controlled independently while the PreLCI can only control them together.

[Hyperion42]

I want to share my findings, not because they are a particularly breakthrough in decoding the data, but to maybe get someone else to think along with me, and because no one else posted anything in this direction.

To start with something easy/small, I looked at the Pre-LCI G20 data first. Here is the data structure I could come up with to parse the entire staging data (1 and 2 combined):

struct data
{
    u8 a;
    u8 b;
};

struct section
{
    u8 id;
    be u16 num_data_entries;
    data entries[num_data_entries];
};

section data[while(std::mem::read_unsigned($, 1))] @ 0x00;

I am using ImHex for this, but apart from last line it should be pretty readable for everyone. This data structure can be applied to all of the staging data I've seen here, G20 LCI for both EU and US, as well as G82, and seems to fit quite well. However, as one can easily tell, the data is not really well defined and we have still no idea what is going on here.

Going back to G20 Pre-LCI then to look at the data. There are 5 sections in total, the first section has 15 entries. The first 6 entries are as follows:

[50, 0], [50, 0] ,[25, 0], [25, 0], [25, 0], [63, 100], ...

My thinking is: As we see the same pairs repeating multiple times, the mapping to specific light modules can't be part of the data. I believe Michael already confirmed that by showing us that coding different staging data from other models, and then comparing the result with the actual model (G21 Pre-LCI with G20 LCI vs the real G20 LCI) seems to play some part of the animation on the wrong light modules.

Furthermore, in all data that has been posted here the first section for all of them has 15 entries - roughly matching the number of LM mappings Michael posted. Looking at the number of entries for all sections, we see for the G20 Pre-LCI: 1: 15, 2: 5, 3: 3, 4: 3, 5: 6

With that I believe the mapping to the light module is actually the index into the entries array. The first section initializes all 15 channels, while the other sections might only specify data for the channels that changed.

Looking then at the first 6 entries of each section we see the following:

1: [50,  0], [50,  0] ,[25,  0], [25,  0], [25,  0], [63, 100], ...
2: [50,  0], [50,  0], [25,  0], [12, 20], [60, 67]
3: [60, 43], [59, 20], [12,  0]
4: [50,   0], [12, 20], [60, 46]
5: [50, 46], [50, 46], [50, 46], [60, 43], [59, 20], [12,   0]

Could it be that the first part of each tuple is the timedelta, and the second one is the intensity? I don't know, at this point I am stuck as I can't properly match this with the video that Michael posted. Maybe someone else has an idea? Maybe this is also going into a totally wrong direction.

If someone wants to contribute, it would help to create annotations for Michaels videos: Which parts of the lights change, for how long do they change, and when do they start changing. With that we could try to make more sense of the data.

[MichaelNRW]

Awesome work!

[mrpingu]

Cool! Would be also nice to time every module so we know atleast roughly the milliseconds each module is on. Would someone be able to do a 120fps video then we can calculate the timedelta more exactly.

Edit:
LWR movement could also be part of the staging data because in older modules the stepper motors in the lights can also be controlled, with the WELL_LWR_SEQ values. In the older FLE module you have the following
LWR_SEQ_DIR - Move up(1) or down (0) for SEQ_T if no HOLD is associated
LWR_SEQ_HOLD - duration of no movement
LWR_SEQ_SPEED - Speed V1 or V0 defined in LWR_SEQ_Vx
LWR_SEQ_T - duration of sequence step

[mrpingu]

Originally Posted by TheNine90

The flm data for right and left is always the same. It might be the wiring that differentiates them.
For the sweeping right to left, does coding using ECE typecode do anything?

In older FLE modules this is addressed through different WELL_SEQ values, there is a WELL_SEQ_LE and WELL_SEQ_RE both headlights contain both values but this makes it makes it possible to have separate sequences for right and left headlight

[MichaelNRW]

Originally Posted by mrpingu

Cool! Would be also nice to time every module so we know atleast roughly the milliseconds each module is on. Would someone be able to do a 120fps video then we can calculate the timedelta more exactly.

I could try that on the weekend.

[alep85]

Originally Posted by MichaelNRW

I could try that on the weekend.

Any luck? This seems far more complex than even I initially thought, but appreciate all of the research this thread has done to-date!

[Melosium]

I'm following the thread. You guys are doing an amazing job here.

[MichaelNRW]

I´m sorry... my time is very limited currently.
I´ll try to do a recording soon.