Part Number: AM3359
Hi,
does the PRU change the APDU status or other areas of the cyclic PN frame in certain cases?
Thank you.
Best Regards
MT
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: AM3359
Hi,
does the PRU change the APDU status or other areas of the cyclic PN frame in certain cases?
Thank you.
Best Regards
MT
MT,
The document
briefly describes the Profinet firmware architecture. I don't think the APDU status or other fields in the cyclic PN frame is modified by the PRU.
Any background about the question? Do you see unexpected APDU status?
Regards,
Garrett
Hi,
yes, in some Automated RT Tester (Testbundle Sept 2018) test cases the IOPS and part of the APDU status are wrong. We use the TMG Profinetstack in shared memory mode and for test purposes the DataStatus is set to 0x35 and the IOPS are set to 0x80. On the fieldbus the value 0x25 for the data status and 0x00 for the IOPS can be seen.
Have you tested the current PRU firmware with the September 2018 test bundle (PNIO version V2.33) and passed the tests positively?
Regards,
MT
MT,
Which release of Profinet are you testing? Is it the latest – PRU_ICSS_PROFINET_Slave 1.0.3.4?
Regards,
Garrett
Hi MT,
I confirmed the Data status is updated by PN stack in PPM buffer. The Cycle counter and Transfer status in APDU status is updated by the firmware though.
We use TMG Profinetstack in shared memory mode too, and have no such APDU issue per my discussion with system test team.
Regards, Garrett