Uploaded image for project: 'PROFINET IO-Device V4'
  1. PROFINET IO-Device V4
  2. PSPNSV4-816

wrong byteorder for AM_Location used in AssetManagment record

          Details

          • Type: Bug
          • Status: Closed
          • Priority: Minor
          • Resolution: Fixed
          • Affects Version/s: V4.3.1.0
          • Fix Version/s: V4.4.0.1
          • Labels:
            None
          • Sprint:
            PI Sprint 2018 KW 11/12
          • Account:
            SPC Profinet Slave (SPCPROFINE)

            Description

            Due to a bug in Wireshark and a clarification for 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 Wireshark up to 2.4.4, 2.2.12 and 2.5.0 have wrong decoding.

            If Wireshark shows a correct AssetManagment dataset field "AM_Location" than the implementation in protocol stack is wrong.

              Attachments

                Issue Links

                blocks

                Bug - A problem which impairs or prevents the functions of the product. PSPNCORE-206 Wrong definition of Asset Management Location Structure

                • 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-826 Update PSPNCORE to V1.7.0.2

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

                Bug - A problem which impairs or prevents the functions of the product. PSPNS-2713 Wrong encoding of AM_Location field inside AssetManagment record object

                • 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: