Reply to thread

Message

<blockquote data-quote="Michael John" data-source="post: 106776" data-attributes="member: 830">Re: Lake Controller 5.8 with 6.1 configured PLMHi Bodo,LC&#039;s do allow opening modules with newer firmware, even if one shouldn&#039;t, and there&#039;s currently no indication in the LC that the module might be &quot;newer.&quot;I&#039;m not sure I understand what is meant by &quot;downgrade.&quot; I&#039;m fairly familiar with the module data structures used by both the LC and the DSP in code, but I&#039;m not so familiar with the LC&#039;s process to display the modules. My understanding is that when the LC views a module, all it is doing is querying for parameters and displaying what it can. Hopefully it&#039;s not sending change commands to the PLM (or LM). If it is, then it may be worth designing out of the LC over time. If the PLM is changing its state in response to information query requests from the LC, then maybe the PLM can be made more robust.In general, I think the ability to open newer firmware in older LC&#039;s is generous. <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f642.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=":-)" title="Smile&nbsp; &nbsp; :-)"&nbsp; data-smilie="1"data-shortname=":-)" /> Maybe the LC can discreetly indicate that the module has newer firmware than the LC knows about, so that a user knows not to change anything.I guess I need to brush up on my networking knowledge. It would be nice to still use the same WAP.</blockquote>

[QUOTE="Michael John, post: 106776, member: 830"] Re: Lake Controller 5.8 with 6.1 configured PLM Hi Bodo, LC's do allow opening modules with newer firmware, even if one shouldn't, and there's currently no indication in the LC that the module might be "newer." I'm not sure I understand what is meant by "downgrade." I'm fairly familiar with the module data structures used by both the LC and the DSP in code, but I'm not so familiar with the LC's process to display the modules. My understanding is that when the LC views a module, all it is doing is querying for parameters and displaying what it can. Hopefully it's not sending change commands to the PLM (or LM). If it is, then it may be worth designing out of the LC over time. If the PLM is changing its state in response to information query requests from the LC, then maybe the PLM can be made more robust. In general, I think the ability to open newer firmware in older LC's is generous. :-) Maybe the LC can discreetly indicate that the module has newer firmware than the LC knows about, so that a user knows not to change anything. I guess I need to brush up on my networking knowledge. It would be nice to still use the same WAP. [/QUOTE]

Verification