Clarification on port requirement in IP_DUP_RPC_I&M_EPM - Scenario 2

[sbsprofi]

I am failing IP_DUP_RPC_I&M_EPM - Scenario 2 because my udp port number is not being set correctly. When I look at the documentation for this test it says it is checking for "RPCPortNumber <= 0xC000". When I look at the failure message from the Automated RT Tester software it says "EPM/Floors: Port for PNIO service is invalid. Requirement: >= 0xC000".

Should the RPCPortNumber be >= or <= 0xC000?

[Raik.Zachmann]

I am failing IP_DUP_RPC_I&M_EPM - Scenario 2 because my udp port number is not being set correctly. When I look at the documentation for this test it says it is checking for "RPCPortNumber <= 0xC000". When I look at the failure message from the Automated RT Tester software it says "EPM/Floors: Port for PNIO service is invalid. Requirement: >= 0xC000".

Should the RPCPortNumber be >= or <= 0xC000?

The implementation of the test case is correct you have to deliver a port number >= 0xC000. The TCIS (Test Case Implementation Specification) needs to be changed. Many thanks for bringing up this issue.

[sbsprofi]

I am failing IP_DUP_RPC_I&M_EPM - Scenario 2 because my udp port number is not being set correctly. When I look at the documentation for this test it says it is checking for "RPCPortNumber <= 0xC000". When I look at the failure message from the Automated RT Tester software it says "EPM/Floors: Port for PNIO service is invalid. Requirement: >= 0xC000".

Should the RPCPortNumber be >= or <= 0xC000?

The implementation of the test case is correct you have to deliver a port number >= 0xC000. The TCIS (Test Case Implementation Specification) needs to be changed. Many thanks for bringing up this issue.

Thank you for the clarification! I think I found another issue in this test. The device information from the I&M0 record read is compared with the device information provided by the EPM request. If you have a mismatch between the software revision prefix ('p' or 'v' for most devices) found in these separate requests, then the ART will report that failure correctly but then incorrectly report the Hardware Revision number as the at-fault value. It confused me for a minute so I figured it would be good to report for the readers of this forum. Please let me know if there is a better place for ART bug reports.

Here is what it looks like (my HW Revision is 4):

Code: Select all

"ERROR: The SwRevisionPrefix value retrieved from EPM and the I&M0 data differ... Requirement: 4. Data: 4"