[veyslaurens]

Hello,

I executed the LCI tail light retrofit and as expected, the inner blinkers don't work.
I used the official wiring harness and want to keep it that way (don't want to tap the outer blinkers)
I added HELC and VO coded the REM module but it still doesn't work.
I did not try it with bimmercode as the HO-WORT didn't work.
Looks like I have to update the i-step of the REM.
Can somebody help me with what psdzdata I need (I would also like to keep the 5 time blinker) and where I can find this.
I also would rather not update any other modules if that is possible.
I currently have esys 3.27.1

Thank you!

[atzebmw]

I sent you a PM.

[psyki]

When I did the LCI taillight retrofit I chose the latest version of the psdzdata that would allow for the 5 blinks and also retain the last used backup/surround view camera mode when putting the car in reverse. The version number I used is 4.03.30 (F020-16-11-503). I would share it with you but it's 70GB uncompressed and my internet is quite possible the worst around. My understanding is that 2016 models were the last to have these features so I looked for the latest 2016 version I could find, I used this chart: https://www.dropbox.com/s/vcz5mb4xa8...RVIEW.pdf?dl=0

Honestly try googling the version numbers, I believe when I did it (a couple years back) I found a random torrent online.

[veyslaurens]

Originally Posted by psyki

When I did the LCI taillight retrofit I chose the latest version of the psdzdata that would allow for the 5 blinks and also retain the last used backup/surround view camera mode when putting the car in reverse. The version number I used is 4.03.30 (F020-16-11-503). I would share it with you but it's 70GB uncompressed and my internet is quite possible the worst around. My understanding is that 2016 models were the last to have these features so I looked for the latest 2016 version I could find, I used this chart: https://www.dropbox.com/s/vcz5mb4xa8...RVIEW.pdf?dl=0

Honestly try googling the version numbers, I believe when I did it (a couple years back) I found a random torrent online.

Hi!
Thanks to the kindness of atzebmw I already got access to various different versions of the psdzdata.
He recommended to at a minimum use version 3.55 so that is the one I downloaded and will try.
How long does the update take?
Would you risk it without a PSU, because I don't have one.

[psyki]

Originally Posted by veyslaurens

Hi!
Thanks to the kindness of atzebmw I already got access to various different versions of the psdzdata.
He recommended to at a minimum use version 3.55 so that is the one I downloaded and will try.
How long does the update take?
Would you risk it without a PSU, because I don't have one.

I updated my entire car i-step when I flashed and all I did was jump it to my running F15 X5. I want to say it took about 45 minutes or so? It was about 2 years ago so I don't remember exactly. Flashing NBT took by far the longest and the idrive screen showed all sorts of weird stuff during the process, just be patient and let it finish.

If you're only flashing REM you probably don't need to jump it as it should only take a few minutes.

[veyslaurens]

Originally Posted by psyki

I updated my entire car i-step when I flashed and all I did was jump it to my running F15 X5. I want to say it took about 45 minutes or so? It was about 2 years ago so I don't remember exactly. Flashing NBT took by far the longest and the idrive screen showed all sorts of weird stuff during the process, just be patient and let it finish.

If you're only flashing REM you probably don't need to jump it as it should only take a few minutes.

I got this error when trying to connect.
I used psdz 3.55, is it to old?

[atzebmw]

Originally Posted by veyslaurens

I got this error when trying to connect.
I used psdz 3.55, is it to old?

Your E-Sys is too new for this psdzdata.
I think 3.27 could be the right one for this.

[veyslaurens]

Originally Posted by atzebmw

Your E-Sys is too new for this psdzdata.
I think 3.27 could be the right one for this.

Hi!
I got past this error by trying psdzdat v4.03.30. I'm using esys 3.27.
However I got a new error when trying to calculate the SVT target that I cannot figure out. Got any idea?
Thanks

[atzebmw]

Originally Posted by veyslaurens

Hi!
I got past this error by trying psdzdat v4.03.30. I'm using esys 3.27.
However I got a new error when trying to calculate the SVT target that I cannot figure out. Got any idea?
Thanks

I have no direct idea.
But maybe you can post the full list of errors here?

[veyslaurens]

Originally Posted by atzebmw

I have no direct idea.
But maybe you can post the full list of errors here?

OutOfMemoryError: Java heap space


__________________________________________________ ___
com.bmw.esys.domain.psdz.PsdzException: Generating target SVT with strategy complete flash and integration level "F020-16-11-503" (target) and "F020-13-03-502" (shipment) failed. [C324]
at com.bmw.esys.domain.psdz.Psdz.generateSollverbauun gGesamtflash(Psdz.java:758)
at com.bmw.esys.domain.svt.SvtLogic.generateSvtTarget FromModel(SvtLogic.java:269)
at com.bmw.esys.gui.svt.SvtCompareController.generate Svt(SvtCompareController.java:627)
at com.bmw.esys.gui.svt.SvtTargetView$GenerateTargetS vtAction.doActionPerformed(SvtTargetView.java:408)
at com.bmw.esys.gui.AbstractView$AbstractGuiProgressA ction$1.init(AbstractView.java:425)
at com.bmw.esys.gui.component.DialogProgress$2.constr uct(DialogProgress.java:152)
at com.bmw.esys.gui.component.SwingWorker$2.run(Swing Worker.java:145)
at java.lang.Thread.run(Thread.java:744)
Caused by: There was a problem while PSdZ tried to access KIS
Timestamp: Tue Jul 27 20:48:26 CEST 2021
ErrorCategory: not set ID: 1966
Class: com.bmw.psdz.kis.adapter.facade.SollverbauungBF
ExecutionContext={category=UNDEFINED, ecuid=(UNKNOWN,?)}
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash_aroundBody21$advice (SollverbauungBF.java:95)
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash_aroundBody22(Sollve rbauungBF.java:1)
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash_aroundBody23$advice (SollverbauungBF.java:44)
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash(SollverbauungBF.jav a:1)
at com.bmw.psdz.vehicle.softwarelogistik.kis.Sollverb auungGenerator.generateSollverbauungGesamtflash(So llverbauungGenerator.java:592)
at com.bmw.psdz.vehicle.softwarelogistik.bf.Sollverba uungsGeneratorBF.generateSollverbauungGesamtflash( SollverbauungsGeneratorBF.java:68)
at com.bmw.psdz.logic.facade.LogicImpl.generateSollve rbauungGesamtflash(LogicImpl.java:710)
at com.bmw.psdz.facade.LogicBF.generateSollverbauungG esamtflash_aroundBody72(LogicBF.java:324)
at com.bmw.psdz.facade.LogicBF.generateSollverbauungG esamtflash_aroundBody73$advice(LogicBF.java:55)
at com.bmw.psdz.facade.LogicBF.generateSollverbauungG esamtflash(LogicBF.java:1)
at com.bmw.esys.domain.psdz.Psdz.generateSollverbauun gGesamtflash(Psdz.java:752)
... 7 more
Caused by: java.lang.OutOfMemoryError: Java heap space
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java: 133)
at java.io.OutputStreamWriter.write(OutputStreamWrite r.java:220)
at java.io.Writer.write(Writer.java:157)
at org.apache.log4j.helpers.CountingQuietWriter.write (CountingQuietWriter.java:45)
at org.apache.log4j.WriterAppender.subAppend(WriterAp pender.java:310)
at org.apache.log4j.RollingFileAppender.subAppend(Rol lingFileAppender.java:276)
at org.apache.log4j.WriterAppender.append(WriterAppen der.java:162)
at org.apache.log4j.AppenderSkeleton.doAppend(Appende rSkeleton.java:251)
at org.apache.log4j.helpers.AppenderAttachableImpl.ap pendLoopOnAppenders(AppenderAttachableImpl.java:66 )
at org.apache.log4j.Category.callAppenders(Category.j ava:206)
at org.apache.log4j.Category.forcedLog(Category.java: 391)
at org.apache.log4j.Category.debug(Category.java:260)
at com.bmw.kis.awl.kennungsblock.TestkennungsBlock.ma tchBlock(TestkennungsBlock.java:223)
at com.bmw.kis.awl.kennungsblock.TestkennungsBlock.id entifyIst(TestkennungsBlock.java:203)
at com.bmw.kis.awl.kennungsblock.TestkennungsBlock.<i nit>(TestkennungsBlock.java:106)
at com.bmw.kis.awl.domain.SollverbauungsBerechnung.te stverbauungsPartition(SollverbauungsBerechnung.jav a:190)
at com.bmw.kis.awl.domain.SollverbauungsBerechnung.pr epare(SollverbauungsBerechnung.java:157)
at com.bmw.kis.awl.facade.methods.SollverbauungBF.exe cute(SollverbauungBF.java:303)
at com.bmw.kis.awl.facade.methods.AuswertelogikMethod .executeMethod(AuswertelogikMethod.java:225)
at com.bmw.kis.awl.facade.AuswertelogikBF.berechneSol lverbauungGesamtflash(AuswertelogikBF.java:144)
at com.bmw.psdz.kis.adapter.esi.impl.KisAuswertelogik Bmw.berechneSollverbauungGesamtflash(KisAuswertelo gikBmw.java:89)
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash_aroundBody20(Sollve rbauungBF.java:81)
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash_aroundBody21$advice (SollverbauungBF.java:65)
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash_aroundBody22(Sollve rbauungBF.java:1)
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash_aroundBody23$advice (SollverbauungBF.java:44)
at com.bmw.psdz.kis.adapter.facade.SollverbauungBF.be rechneSollverbauungGesamtflash(SollverbauungBF.jav a:1)
at com.bmw.psdz.vehicle.softwarelogistik.kis.Sollverb auungGenerator.generateSollverbauungGesamtflash(So llverbauungGenerator.java:592)
at com.bmw.psdz.vehicle.softwarelogistik.bf.Sollverba uungsGeneratorBF.generateSollverbauungGesamtflash( SollverbauungsGeneratorBF.java:68)
at com.bmw.psdz.logic.facade.LogicImpl.generateSollve rbauungGesamtflash(LogicImpl.java:710)
at com.bmw.psdz.facade.LogicBF.generateSollverbauungG esamtflash_aroundBody72(LogicBF.java:324)
at com.bmw.psdz.facade.LogicBF.generateSollverbauungG esamtflash_aroundBody73$advice(LogicBF.java:55)
at com.bmw.psdz.facade.LogicBF.generateSollverbauungG esamtflash(LogicBF.java:1)

[atzebmw]

OK, I haven't found a definite error either, but there seems to be a problem with the KIS data.
In other threads with this error number I found indications that the KIS data could be damaged.
I'm afraid you'll have to download another psdzdata version again.

[adrien78]

I used this with Bimmercode to code my lci tail lights

REM_01 > LceLampMapping1 3062 > MAPPING_BLINKER_H_L_FIXED_PWM = fixed
REM_01 > LceLampMapping1 3062 > MAPPING_BLINKER_H_L_PWM_LEVEL_1 = 13.7V [Default]
REM_01 > LceLampMapping1 3062 > MAPPING_BLINKER_H_R_FIXED_PWM = fixed
REM_01 > LceLampMapping1 3062 > MAPPING_BLINKER_H_R_PWM_LEVEL_1 = 13.7V [Default]
REM_01 > LceLampMapping1 3062 > MAPPING_BRAKEFORCED_L_FIXED_PWM = fixed
REM_01 > LceLampMapping1 3062 > MAPPING_BRAKEFORCED_L_PWM_LEVEL_1 = 100% [Default]
REM_01 > LceLampMapping1 3062 > MAPPING_BRAKEFORCED_R_FIXED_PWM = fixed
REM_01 > LceLampMapping1 3062 > MAPPING_BRAKEFORCED_R_PWM_LEVEL_1 = 100% [Default]
REM_01 > LceLampMapping1 3062 > MAPPING_BREMSL_L_FIXED_PWM = fixed
REM_01 > LceLampMapping1 3062 > MAPPING_BREMSL_L_PWM_LEVEL_1 = 13.5V [Default]
REM_01 > LceLampMapping1 3062 > MAPPING_BREMSL_R_FIXED_PWM = fixed
REM_01 > LceLampMapping1 3062 > MAPPING_BREMSL_R_PWM_LEVEL_1 = 13.5V [Default]
REM_01 > LceLampMapping2 3063 > MAPPING_NEBELSCHLUSSL_L_FIXED_PWM = fixed
REM_01 > LceLampMapping2 3063 > MAPPING_NEBELSCHLUSSL_L_PWM_LEVEL_1 = 13.5V [Default]
REM_01 > LceLampMapping2 3063 > MAPPING_NEBELSCHLUSSL_R_FIXED_PWM = fixed
REM_01 > LceLampMapping2 3063 > MAPPING_NEBELSCHLUSSL_R_PWM_LEVEL_1 = 13.5V [Default]
REM_01 > LceLampMapping2 3063 > MAPPING_RUECKFAHRL_L_PWM_LEVEL_1 = 13.7V [Default]
REM_01 > LceLampMapping2 3063 > MAPPING_RUECKFAHRL_R_PWM_LEVEL_1 = 13.7V [Default]
REM_01 > LceLampMapping2 3063 > MAPPING_UNIVERSAL_6_OUTPUT = sl_2_l
REM_01 > LceLampMapping2 3063 > MAPPING_UNIVERSAL_7_OUTPUT = sl_2_r
REM_01 > LceLampMapping2 3063 > MAPPING_UNIVERSAL_8_OUTPUT = bfd_l
REM_01 > LceLampMapping2 3063 > MAPPING_UNIVERSAL_9_OUTPUT = bfd_r
REM_01 > LceOutputChannels 3061 > BFD_L_CCM = ccm_blinker_l
REM_01 > LceOutputChannels 3061 > BFD_L_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > BFD_L_UE_SPG_SCHUTZ = dimmed
REM_01 > LceOutputChannels 3061 > BFD_R_CCM = ccm_blinker_r
REM_01 > LceOutputChannels 3061 > BFD_R_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > BFD_R_UE_SPG_SCHUTZ = dimmed
REM_01 > LceOutputChannels 3061 > BL_L_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > BL_L_KALTUEBERWACHUNG = nicht_aktiv
REM_01 > LceOutputChannels 3061 > BL_L_UE_SPG_SCHUTZ = nicht_aktiv
REM_01 > LceOutputChannels 3061 > BL_R_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > BL_R_KALTUEBERWACHUNG = nicht_aktiv
REM_01 > LceOutputChannels 3061 > BL_R_UE_SPG_SCHUTZ = nicht_aktiv
REM_01 > LceOutputChannels 3061 > FRA_H_L_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > FRA_H_L_KALTUEBERWACHUNG = nicht_aktiv
REM_01 > LceOutputChannels 3061 > FRA_H_L_WARMUEBERWACHUNG = aktiv [Default]
REM_01 > LceOutputChannels 3061 > FRA_H_R_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > FRA_H_R_KALTUEBERWACHUNG = nicht_aktiv
REM_01 > LceOutputChannels 3061 > FRA_H_R_WARMUEBERWACHUNG = aktiv [Default]
REM_01 > LceOutputChannels 3061 > NSL_L_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > NSL_L_KALTUEBERWACHUNG = nicht_aktiv
REM_01 > LceOutputChannels 3061 > NSL_L_UE_SPG_SCHUTZ = aktiv [Default]
REM_01 > LceOutputChannels 3061 > NSL_L_WARMUEBERWACHUNG = nicht_aktiv
REM_01 > LceOutputChannels 3061 > NSL_R_CCM = NEW_ccm_nsl_r
REM_01 > LceOutputChannels 3061 > NSL_R_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > NSL_R_KALTUEBERWACHUNG = nicht_aktiv
REM_01 > LceOutputChannels 3061 > NSL_R_UE_SPG_SCHUTZ = aktiv [Default]
REM_01 > LceOutputChannels 3061 > NSL_R_WARMUEBERWACHUNG = nicht_aktiv
REM_01 > LceOutputChannels 3061 > RFS_L_CCM = NEW_ccm_rfs_l
REM_01 > LceOutputChannels 3061 > SL_2_L_CCM = Fxx_ccm_sl_2_l
REM_01 > LceOutputChannels 3061 > SL_2_L_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > SL_2_R_CCM = Fxx_ccm_sl_2_r
REM_01 > LceOutputChannels 3061 > SL_2_R_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > SL_L_IS_LED = aktiv
REM_01 > LceOutputChannels 3061 > SL_R_IS_LED = aktiv

[atzebmw]

Originally Posted by adrien78

I used this with Bimmercode to code my lci tail lights

But this will only work if you have a software from 07/2015 upwards installed.

[veyslaurens]

Originally Posted by atzebmw

OK, I haven't found a definite error either, but there seems to be a problem with the KIS data.
In other threads with this error number I found indications that the KIS data could be damaged.
I'm afraid you'll have to download another psdzdata version again.

I tried again with v.4.01.22, with the same kind of results. I really am getting out of options here.

[atzebmw]

Originally Posted by veyslaurens

I tried again with v.4.01.22, with the same kind of results. I really am getting out of options here.

Please can you send me your SVT_IST and FA.
Then i can make some tests.

[veyslaurens]

Originally Posted by atzebmw

Please can you send me your SVT_IST and FA.
Then i can make some tests.

Here they are.
Thanks a lot for all the help, appreciate it!

[atzebmw]

Originally Posted by veyslaurens

Here they are.
Thanks a lot for all the help, appreciate it!

OK, i already made some tests and had the same problem.
What I've found so far is that your retrofitted NBTEvo is causing the problems here.
But this problem should be possible to solve.
Unfortunately I don't have any more time today and will try again tomorrow.

[atzebmw]

Originally Posted by veyslaurens

Here they are.
Thanks a lot for all the help, appreciate it!

OK, i think i got it.
Here you get your 2 files back.
I edited the FA and deleted the 609.
Then the calculation worked for me.
So you now may not to load the FA from your car, but load my edited FA.
Then load the SVT_IST and try the calculation.
If it works use this FA only for this calculation.
After the flash you have to code the REM.
And for the coding better also not use this FA, but load again the FA from your car.

[veyslaurens]

Originally Posted by atzebmw

OK, i think i got it.
Here you get your 2 files back.
I edited the FA and deleted the 609.
Then the calculation worked for me.
So you now may not to load the FA from your car, but load my edited FA.
Then load the SVT_IST and try the calculation.
If it works use this FA only for this calculation.
After the flash you have to code the REM.
And for the coding better also not use this FA, but load again the FA from your car.

This unfortunately still results in the same error😢

[atzebmw]

Originally Posted by veyslaurens

This unfortunately still results in the same error😢

OK, i'm sorry.
I will do more tests.

[veyslaurens]

Originally Posted by atzebmw

OK, i'm sorry.
I will do more tests.

Thanks for all the help

[atzebmw]

Originally Posted by veyslaurens

Thanks for all the help

No problem.
I also find that interesting and learn something new in the process.

So i tested again.
I think i have now the same files like you.
E-Sys 3.27, psdzdata 4.01.22 Full and your SVT_IST and FA.
And again it worked for me.
So i have to ask, did you really load my edited FA?

But we can now try another thing.
Because it worked for me i could create the SVT_SOLL and SVT_TAL.
You now can skip the calculation and directly start the TAL processing if you load the SVT_SOLL and SVT_TAL.
Then only choose the REM and maybe it will work.
I also never did it that way but i think it can work.