AR-ASE S2 test failed

[rottava]

Hello,

I need a helping hand concerning above mentioned test. My device is failing when I run AR-ASE S2 test, in the beginning of Scenario 1-4. Behavior 8, 9, 10 and 11, right in the sequence, are failing as well. AR-ASE and other behavior tests are ok.

Log shows the following messages:
14:40:11 - AR-ASE S2 - Scenario 1 (first run): FirstScenario : ArAsetest with DA-AR with running IOC-AR and 1.AR in Backup
14:40:12 - AR-ASE S2 - Scenario 1 (first run): Test step 1: Prepare the Dut by setting the correct Name and IP address.
14:40:17 - AR-ASE S2 - Scenario 1 (first run): Test step 2: Establish the AR_ASE System Redundancy 1AR.
14:46:05 - ERROR: No response received.
14:46:05 - ERROR: AR-ASE S2 - Scenario 1 (first run): Test step 3: Failed to establish the AR_ASE System Redundancy AR1.
14:46:12 - Finished test case AR-ASE S2 - SCENARIO 1-4 (CLRPC).
14:46:44 - Test execution finished.

When I look at the correspondent Wireshark log (attached), last message sent by the ART is a "Connect request..." that never receives an answer. Log shows previous similar messsages had a correct "Connect response..." answer. Failed behavior tests have a similar symptom.

So I am wondering what possibly could be wrong in my implementation. GSDML seems to be fine, no warning or error reported by the checker. Besides, this device "works", I mean, if I put it on a network with a PLC with S2 redundancy (S7 1513R), it works fine when cables are removed.

Appreciate any idea to fix this issue.

Thank you.

[DanielS]

Hello,

I need a helping hand concerning above mentioned test. My device is failing when I run AR-ASE S2 test, in the beginning of Scenario 1-4. Behavior 8, 9, 10 and 11, right in the sequence, are failing as well. AR-ASE and other behavior tests are ok.

Log shows the following messages:
14:40:11 - AR-ASE S2 - Scenario 1 (first run): FirstScenario : ArAsetest with DA-AR with running IOC-AR and 1.AR in Backup
14:40:12 - AR-ASE S2 - Scenario 1 (first run): Test step 1: Prepare the Dut by setting the correct Name and IP address.
14:40:17 - AR-ASE S2 - Scenario 1 (first run): Test step 2: Establish the AR_ASE System Redundancy 1AR.
14:46:05 - ERROR: No response received.
14:46:05 - ERROR: AR-ASE S2 - Scenario 1 (first run): Test step 3: Failed to establish the AR_ASE System Redundancy AR1.
14:46:12 - Finished test case AR-ASE S2 - SCENARIO 1-4 (CLRPC).
14:46:44 - Test execution finished.

When I look at the correspondent Wireshark log (attached), last message sent by the ART is a "Connect request..." that never receives an answer. Log shows previous similar messsages had a correct "Connect response..." answer. Failed behavior tests have a similar symptom.

So I am wondering what possibly could be wrong in my implementation. GSDML seems to be fine, no warning or error reported by the checker. Besides, this device "works", I mean, if I put it on a network with a PLC with S2 redundancy (S7 1513R), it works fine when cables are removed.

Appreciate any idea to fix this issue.

Thank you.

Hi,

I have checked the pcap and I cannot see that the testsystem does something wrong. The first Teststeps are working well. Within the connect.req there is nothing different than from the other IOC-AR´s. Maybe the issue is in the number of different IOC-AR and DA-AR´s. As there are many AR Establishments in short time, this might cause the issue in your device? The PROFINET Stack seems to be still running as the device is still sending LLDP´s.
Are you able to debug the device during the test run? Is the Application still running or has connection to the PROFINET stack?

BR
Daniel

[rottava]

Hello,

I need a helping hand concerning above mentioned test. My device is failing when I run AR-ASE S2 test, in the beginning of Scenario 1-4. Behavior 8, 9, 10 and 11, right in the sequence, are failing as well. AR-ASE and other behavior tests are ok.

Log shows the following messages:
14:40:11 - AR-ASE S2 - Scenario 1 (first run): FirstScenario : ArAsetest with DA-AR with running IOC-AR and 1.AR in Backup
14:40:12 - AR-ASE S2 - Scenario 1 (first run): Test step 1: Prepare the Dut by setting the correct Name and IP address.
14:40:17 - AR-ASE S2 - Scenario 1 (first run): Test step 2: Establish the AR_ASE System Redundancy 1AR.
14:46:05 - ERROR: No response received.
14:46:05 - ERROR: AR-ASE S2 - Scenario 1 (first run): Test step 3: Failed to establish the AR_ASE System Redundancy AR1.
14:46:12 - Finished test case AR-ASE S2 - SCENARIO 1-4 (CLRPC).
14:46:44 - Test execution finished.

When I look at the correspondent Wireshark log (attached), last message sent by the ART is a "Connect request..." that never receives an answer. Log shows previous similar messsages had a correct "Connect response..." answer. Failed behavior tests have a similar symptom.

So I am wondering what possibly could be wrong in my implementation. GSDML seems to be fine, no warning or error reported by the checker. Besides, this device "works", I mean, if I put it on a network with a PLC with S2 redundancy (S7 1513R), it works fine when cables are removed.

Appreciate any idea to fix this issue.

Thank you.

Hi,

I have checked the pcap and I cannot see that the testsystem does something wrong. The first Teststeps are working well. Within the connect.req there is nothing different than from the other IOC-AR´s. Maybe the issue is in the number of different IOC-AR and DA-AR´s. As there are many AR Establishments in short time, this might cause the issue in your device? The PROFINET Stack seems to be still running as the device is still sending LLDP´s.
Are you able to debug the device during the test run? Is the Application still running or has connection to the PROFINET stack?

BR
Daniel

Hi Daniel,

Thank you for looking at this issue. Yes, I am able to debug the device but, unfortunately, I don't get much information. The PROFINET ASIC takes care of almost everything regarding the communication.

Application is running even after the test failure, but the PROFINET stack seems to be faulty since most of the tests return an error after the AR-ASE S2.

Will contact the supplier of this ASIC and check if they can give me some hints. However, what I'm wondering is why the "Connect request" telegram from the test is different when it fails; 3 submodules rather than 4 (screenshots attached).

Regards,
Luciano.