Uploaded image for project: 'EtherNet/IP Core V2'
  1. EtherNet/IP Core V2
  2. PSEIPCORE-298

Ethernet Link and TCP/IP Object do not behave correctly when only one Ethernet port is available

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: V2.7.0.1, V2.7.1.0 (open)
    • Labels:
      None
    • Account:
      SPC EthernetIp Core (SPCETHERNET)

      Description

      In case there is only one physical Ethernet port available,

      the Ethernet Link Object behaves incorrectly:

      • Get Attribute All service request to instance 2 (which is not available) is rejected with status "Service not supported" (0x08), instead of "Path destination unknown" (0x05)
      • Get Attribute request to attribute 10 "Interface Label" is rejected with "Attribute not supported " (0x14), but should be accepted.
      • Set attribute single request to attribute 10 is rejected with "Attribute Not Supported" instead of "Attribute not settable".
      • Interface Counters (attribute 4) are not filled properly.
      • Status (attribute 2) not filled properly.
      • Attributes are not initialized properly on startup.

       

      the TCP/IP Interface Object behaves incorrectly:

      • Get attribute single to Physical Link Object Path (attribute 4) delivers wrong attribute value (all zero).
        It is expected to see the path to the Ethernet Link instance 1, in case only 1 Ethernet port is available.
        All zero can be delivered in case more than one Ethernet Port is available.

        Attachments

          Expenses

            Activity

              Status Description

                People

                • Reporter:
                  KMichel Kai Michel
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: