PROFINET Forum

15:03:20 - Starting Testcase: IP_UDP_RPC_I&M_EPM - SCENARIO 1 (CLRPC)
15:03:20 - Initializing Power Outlet
15:03:21 - First Scenario Part 1: First Scenario: Checking of RPC, IP and UDP Part 1
15:03:22 - First Scenario Part 1: Test step 1: Prepare the DUT for the test run.
15:03:32 - First Scenario Part 1: Test step 2: Sending and validating ICMP ping.
15:03:35 - First Scenario Part 1: Test step 3: Read and validate the I&M0FilterData from the dut.
15:03:35 - First Scenario Part 1: Test step 4: Establish an IOC-AR with 'little endianess'.
15:03:35 - ERROR: DCE/RPC Layer: Fragment number does not match Serial. Requirement: 0x00000000. Data: 0x00000001
15:03:35 - ERROR: First Scenario Part 1: Test step 5: Failed to establish an IOC-AR with little endianess.
15:03:47 - First Scenario Part 2: First Scenario: Checking of RPC, IP and UDP Part 2
15:03:48 - First Scenario Part 2: Test step 1: Prepare the DUT for the test run.
15:03:48 - First Scenario Part 2: Test step 2: Read and validate the I&M0FilterData from the dut.
15:03:48 - First Scenario Part 2: Test step 3: Establish an IOC-AR with 'little endianess'.
15:03:49 - First Scenario Part 2: Test step 4: Validate the ModuleDiffBlock and IOPS.
15:03:49 - First Scenario Part 2: Test step 5: Start sending of manipulated packages.
15:03:49 - First Scenario Part 2: Test step 6: Sending a read request with a wrong IP checksum
15:03:50 - First Scenario Part 2: Test step 7: Sending a read request with a wrong UDP checksum
15:03:52 - First Scenario Part 2: Test step 8: Sending a read request with a wrong IP and UDP checksum
15:03:54 - First Scenario Part 2: Test step 9: Sending a read request with a too big IP length value.
15:03:55 - First Scenario Part 2: Test step 10: Sending a manipulated read request. (IP Length is as big as UDP Length).
15:03:57 - First Scenario Part 2: Test step 11: Sending a manipulated read request. (IP Length too small).
15:03:58 - First Scenario Part 2: Test step 12: Sending a manipulated read request. (UDP Length too small).
15:04:00 - First Scenario Part 2: Test step 13: Release IOC-AR established with a fragmented connect request.
15:04:19 - Finished test case IP_UDP_RPC_I&M_EPM - SCENARIO 1 (CLRPC).
15:04:21 - Test execution finished.

• Has anyone else encountered similar fragment mismatch errors in ETS/ART tests? If so, any advice on specific configuration settings to check or debugging steps to try?

• Could this issue be related to the DUT’s handling of little-endian formatting or RPC sequences, and are there particular configurations I should try adjusting?

yasiralismb1 wrote: ↑29 Oct 2024, 17:23 Hi Profinet Experts,
I am currently testing a PROFINET device using the Embedded Test System (ETS) and Automated Real-Time Tester (ART), and I ran into an issue that I am hoping to get some insights on.

The device setup includes standard PROFINET configurations, and I am specifically running the IP_UDP_RPC_I&M_EPM - SCENARIO 1 (CLRPC) test case. During the test I encountered the following error while establishing an IOC-AR (Input-Output Connection - Application Relationship) connection with little-endian encoding:

15:03:20 - Starting Testcase: IP_UDP_RPC_I&M_EPM - SCENARIO 1 (CLRPC)
15:03:20 - Initializing Power Outlet
15:03:21 - First Scenario Part 1: First Scenario: Checking of RPC, IP and UDP Part 1
15:03:22 - First Scenario Part 1: Test step 1: Prepare the DUT for the test run.
15:03:32 - First Scenario Part 1: Test step 2: Sending and validating ICMP ping.
15:03:35 - First Scenario Part 1: Test step 3: Read and validate the I&M0FilterData from the dut.
15:03:35 - First Scenario Part 1: Test step 4: Establish an IOC-AR with 'little endianess'.
15:03:35 - ERROR: DCE/RPC Layer: Fragment number does not match Serial. Requirement: 0x00000000. Data: 0x00000001
15:03:35 - ERROR: First Scenario Part 1: Test step 5: Failed to establish an IOC-AR with little endianess.
15:03:47 - First Scenario Part 2: First Scenario: Checking of RPC, IP and UDP Part 2
15:03:48 - First Scenario Part 2: Test step 1: Prepare the DUT for the test run.
15:03:48 - First Scenario Part 2: Test step 2: Read and validate the I&M0FilterData from the dut.
15:03:48 - First Scenario Part 2: Test step 3: Establish an IOC-AR with 'little endianess'.
15:03:49 - First Scenario Part 2: Test step 4: Validate the ModuleDiffBlock and IOPS.
15:03:49 - First Scenario Part 2: Test step 5: Start sending of manipulated packages.
15:03:49 - First Scenario Part 2: Test step 6: Sending a read request with a wrong IP checksum
15:03:50 - First Scenario Part 2: Test step 7: Sending a read request with a wrong UDP checksum
15:03:52 - First Scenario Part 2: Test step 8: Sending a read request with a wrong IP and UDP checksum
15:03:54 - First Scenario Part 2: Test step 9: Sending a read request with a too big IP length value.
15:03:55 - First Scenario Part 2: Test step 10: Sending a manipulated read request. (IP Length is as big as UDP Length).
15:03:57 - First Scenario Part 2: Test step 11: Sending a manipulated read request. (IP Length too small).
15:03:58 - First Scenario Part 2: Test step 12: Sending a manipulated read request. (UDP Length too small).
15:04:00 - First Scenario Part 2: Test step 13: Release IOC-AR established with a fragmented connect request.
15:04:19 - Finished test case IP_UDP_RPC_I&M_EPM - SCENARIO 1 (CLRPC).
15:04:21 - Test execution finished.

After this error, the test continues with manipulated packet tests, but I am concerned this fragment mismatch might impact the entire test outcome.

Device Details:
Device Type: PROFINET I/O device (PCI card)
Testing Environment: ETS with ART for real-time testing

Questions:

• Has anyone else encountered similar fragment mismatch errors in ETS/ART tests? If so, any advice on specific configuration settings to check or debugging steps to try?

• Could this issue be related to the DUT’s handling of little-endian formatting or RPC sequences, and are there particular configurations I should try adjusting?

Any suggestions or experiences would be greatly appreciated. Thanks in advance for the assistance