Details

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

      Description

      Incorrect order of function calls prevents the TimeSync object to get the actual IP address. 

      In the callback function EipTcp_NetIfStatusChange_Callback_Job, Eip_NotifyTimeSyncAboutIpAddressChange is called before the IP assignment to ptRsc->tObjData.atInstance[0].tNV.tInterfaceConfig.ulIpAddr which always delivers the IP address zero. 

        Attachments

          Expenses

            Activity

              Status Description

                People

                • Reporter:
                  OKompani Omid Kompani
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: