[Node]

BCO ncds seemed ok. Kombi ones you can immediately see ncd file is much smaller after saving in ESysUltra. I don't know if it's a bug of ESys or ESysUltra, but there definitely is a problem somewhere. I just did a single test with ESys 22.10 and Ultra (I think).

IMHO BU is much better product. At least it's not the first time I have problems with Ultra. While with BU I can't complain about yet (except crashing, but that was some time ago). Well, except license transfer

[NIGHT2000]

esys 22_10&22_06 Tried and tested.
Simply name and save the ncd without messing with anything and Sigunature will be 00. The size also decreases.
Reported to ultra.

---

It was confirmed that Sigunature is 00 even with ESYS 22_10 & 22_06 & 3.40 without ULTRA.
What is strange is that some of the past data shows that even after coding, some of them are not 00.
I don't know now which data it is because I used both BU and ULTRA.

Is this something specific to Motorrad?
It is unclear whether this is due to esys settings.

Does anyone know where the Sigunature 00 affects?

[Kordoff]

You guys understand that once you edit and save an NCD the signature gets zeroed out on ALL ESys versions no matter ESysUltra, BU or whatever, this can be observed if you reload the file in the FDL-Editor. The signature is calculated when the NCD gets written so both of you are just pointing fingers at nothing

[NIGHT2000]

I received a similar response from ESysUltra.
It seems that the fact that the signature value is 00 has nothing to do with it.

What was the cause of the TFT blackout after all?

I don't know if it is a problem with the istep file, as I don't have the latest information on BMW's TIS, etc.

Does anyone have a similar case or can identify the cause of the glitch?

[Node]

Just try to flash to 23-07 and code ncd made with BU. IMHO you will see.

[NIGHT2000]

I haven't connected it to the vehicle yet, but on my PC
In addition to esysultra, if you save with plain esys23_06 & 22_10 & 22_06 etc., the signature will be all 00.
I don't own it now, but I'm curious about how it works with launcher pro, etc.

Will all Signatures be 00 for vehicles other than motorcycles?
I don't have any NCD files for anything other than the bike, so I don't know.

Is it because the Signature values are all 00?
Do you know where the Signature value is affected?

I'll update again on the weekend on 23_07 and check it out.

[NIGHT2000]

to Node
I have not yet updated to 23-07-5XX,
I tried FDL coding with esysultra on the current 23-03-501.

1) I extracted the NCD from the vehicle.
(at this point the signatures were random numbers)
2) Edited and coded in esysultra with the FDL editor.
3) Save.
(Checking the saved NCD, the signatures were all 00)
4) NCD coded to the vehicle in esysultra.
5) When the NCD is extracted from the vehicle, the signature is not 00, but a random number.
6) I rode the vehicle in this condition, but no TFT abnormality was observed.

As esysultra support and kordoff say,
Isn't the 00 value of the signature automatically rewritten to a random number when the NCD is written to the vehicle?

I will do a software update after this and ride the bike tomorrow with no coding to see if there is anything wrong with the TFT.