Details

    • Type: Change
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: V3.5.0.6, V3.5.3.0
    • Fix Version/s: V3.6.2.0, V3.7.0.0
    • Component/s: Core
    • Labels:
      None
    • Account:
      SPC EthernetIp Core (SPCETHERNET)

      Description

      There are a few interesting class attributes which are mostly implemented statically in the stack:

      usMaxInstance
      usNumInstance
      usMaxClassAttr
      usMaxInstanceAttr

      These values in fact have to be dynamic. For instance, usNumInstance has to increase with each new instance creation and the usMaxInstance has to increment when this creation leads to a higher maximum instance ID of the object class. Correspondingly, when an instance is deleted, the values have to be lowered eventually. This is mostly implemented, but might be better abstracted.

      For the usMaxClassAttr and usMaxInstanceAttr attributes, we should respect the attribute flags, ignoring disabled attributes, and adapting the class attributes accordingly. Such a mechanism is currently missing mostly, so the host would have to set the maximum values explicitly. An exception is the ID object which already implements this dynamics. So just maybe consolidate this mechanism. See CipId_UpdateClassAttributes().

        Attachments

          Expenses

            Activity

              Status Description

                People

                • Reporter:
                  MBommert Marc Bommert
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: