If you take a look at the trace files provided by wyccka in 2013 ( link) you'll see that "OFFSET_HI_LI" and "OFFSET_HI_RE" do match the predefined values. However in this case I don't think it should. Some parameter values can diverge from the predefined ones during normal usage. This by itself is not an issue or cause for alarm. When loading the nettodata trace file in NCS Dummy you'll see it selects "" () which is just a placeholder for undefined values. The reason for this is because their (nettodata) data values do not match any of the predefined parameters in the module description file. As you may have noticed these functions are missing from your FSW/PSW trace files. I must admit I'm also a bit confused about the content of "OFFSET_HI_LI" and "OFFSET_HI_RE" in your trace files. For an E39 touring parameter "e39_ab_sensor" should be the right one. Nevertheless if you want to recode the module and include "EHC_KENNFELD" I would keep only one parameter. So you probably can't alter "EHC_KENNFELD" at all. ![]() ![]() Given the fact that NCS Expert cannot read the underlying nettodata value, I doubt it can write it. Jduffett: To be honest, I don't know what would happen if you try to code the module with the FSW/PSW trace file containing conflicting entries for "EHC_KENNFELD".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |