Uploaded image for project: 'PROFINET IO-Device'
  1. PROFINET IO-Device
  2. PSPNS-2713

Wrong encoding of AM_Location field inside AssetManagment record object

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Minor
          • Resolution: Fixed
          • Affects Version/s: V3.12.0.0
          • Fix Version/s: V3.12.0.11, V3.12.2.0, V3.13.0.0
          • Component/s: None
          • Labels:
            None
          • Sprint:
            PI Sprint 2018 KW 11/12
          • Account:
            SPC Profinet Slave (SPCPROFINE)

            Description

            Due to a clarification of the Profinet specification it is now clear that the field "AM_Location" inside the AssetManagment record is filled with wrong byteorder by protocol stack.

            Note that all Wireshark versions up to 2.5.x have also wrong decoding implemented. Starting with Wireshark 2.6.0 the decoding in Wireshark is correct.

              Attachments

                Issue Links

                relates to

                Bug - A problem which impairs or prevents the functions of the product. PSPNS-2874 Wrong coding of AM_DeviceIdentification in asset management block

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. PSPNSV4-816 wrong byteorder for AM_Location used in AssetManagment record

                • Minor - Minor loss of function, or other problem where easy workaround is present.
                • Closed
                mentioned in

                Page Loading...

                  Expenses

                    Activity

                      Status Description

                        People

                        • Reporter:
                          BMeyer Benjamin Meyer
                        • Votes:
                          0 Vote for this issue
                          Watchers:
                          0 Start watching this issue

                          Dates

                          • Created:
                            Updated:
                            Resolved: