Setup required to pre-test a two-port PROFINET device with redundancy S2

[rottava]

Hello,

I am currently working to pre-test a 2-port PROFINET device which supports System Redundancy S2. The 10m cables go straight from the IF1 and IF2 from the ETS to ports 1 and 2 of the DUT. With this basic setup I am able to run most of the tests the ART presents. However, those that involve redundancy are skipped, of course. I'm checking the documentation that came with the test bundle, mainly "Testspec-PN_2572_V245_Jun24", but I am not sure how to organize my test setup to run the required S2 tests.

Could you please clarify the topology and the required equipment to pre-test, in house, our DUT?

Thanks.

[galtech]

Hello,

I am currently working to pre-test a 2-port PROFINET device which supports System Redundancy S2. The 10m cables go straight from the IF1 and IF2 from the ETS to ports 1 and 2 of the DUT. With this basic setup I am able to run most of the tests the ART presents. However, those that involve redundancy are skipped, of course. I'm checking the documentation that came with the test bundle, mainly "Testspec-PN_2572_V245_Jun24", but I am not sure how to organize my test setup to run the required S2 tests.

Could you please clarify the topology and the required equipment to pre-test, in house, our DUT?

Thanks.

The S2 tests using ETS do not require a special topology. They use the connections you describe. Test cases are skipped based on device characteristics in the GSDML file. Does the device's GSDML file include the attribute DeviceTypes with a value of "S2"?

There are additional interoperability tests for S2 redundancy. They require expensive hardware, so they are not usually done outside of a PI test lab.

[rottava]

Hello,

I am currently working to pre-test a 2-port PROFINET device which supports System Redundancy S2. The 10m cables go straight from the IF1 and IF2 from the ETS to ports 1 and 2 of the DUT. With this basic setup I am able to run most of the tests the ART presents. However, those that involve redundancy are skipped, of course. I'm checking the documentation that came with the test bundle, mainly "Testspec-PN_2572_V245_Jun24", but I am not sure how to organize my test setup to run the required S2 tests.

Could you please clarify the topology and the required equipment to pre-test, in house, our DUT?

Thanks.

The S2 tests using ETS do not require a special topology. They use the connections you describe. Test cases are skipped based on device characteristics in the GSDML file. Does the device's GSDML file include the attribute DeviceTypes with a value of "S2"?

There are additional interoperability tests for S2 redundancy. They require expensive hardware, so they are not usually done outside of a PI test lab.

Hi,

Of course, that was missing in my GSDML file! Fixed and now all S2 tests are running successfully. Thank you very much.

Now my next question refers to MRC Interop - Client test. I guess the setup I would have to put together is the one shown in section 5.2.6.6, figure 5-21. If so, what do I do if I don't have those additional equipment (listed under 5.2.2 section)?

[galtech]

Hello,

I am currently working to pre-test a 2-port PROFINET device which supports System Redundancy S2. The 10m cables go straight from the IF1 and IF2 from the ETS to ports 1 and 2 of the DUT. With this basic setup I am able to run most of the tests the ART presents. However, those that involve redundancy are skipped, of course. I'm checking the documentation that came with the test bundle, mainly "Testspec-PN_2572_V245_Jun24", but I am not sure how to organize my test setup to run the required S2 tests.

Could you please clarify the topology and the required equipment to pre-test, in house, our DUT?

Thanks.

The S2 tests using ETS do not require a special topology. They use the connections you describe. Test cases are skipped based on device characteristics in the GSDML file. Does the device's GSDML file include the attribute DeviceTypes with a value of "S2"?

There are additional interoperability tests for S2 redundancy. They require expensive hardware, so they are not usually done outside of a PI test lab.

Hi,

Of course, that was missing in my GSDML file! Fixed and now all S2 tests are running successfully. Thank you very much.

Now my next question refers to MRC Interop - Client test. I guess the setup I would have to put together is the one shown in section 5.2.6.6, figure 5-21. If so, what do I do if I don't have those additional equipment (listed under 5.2.2 section)?

Yes Figure 5-21 is the correct setup for that testcase. I can't say whether the test would pass with different equipment. Some developers choose to have partial pre-tests done at PI test labs to cover the testcases that require additional equipment (S2 Interoperability, MRP-Interop, Netload, etc.). This is optional. Other developers only test the testcases which use the normal ETS setup before moving on to a full certification test at a PI test lab.

[rottava]

The S2 tests using ETS do not require a special topology. They use the connections you describe. Test cases are skipped based on device characteristics in the GSDML file. Does the device's GSDML file include the attribute DeviceTypes with a value of "S2"?

There are additional interoperability tests for S2 redundancy. They require expensive hardware, so they are not usually done outside of a PI test lab.

Hi,

Of course, that was missing in my GSDML file! Fixed and now all S2 tests are running successfully. Thank you very much.

Now my next question refers to MRC Interop - Client test. I guess the setup I would have to put together is the one shown in section 5.2.6.6, figure 5-21. If so, what do I do if I don't have those additional equipment (listed under 5.2.2 section)?

Yes Figure 5-21 is the correct setup for that testcase. I can't say whether the test would pass with different equipment. Some developers choose to have partial pre-tests done at PI test labs to cover the testcases that require additional equipment (S2 Interoperability, MRP-Interop, Netload, etc.). This is optional. Other developers only test the testcases which use the normal ETS setup before moving on to a full certification test at a PI test lab.

Right. I will try my fortune anyway. Have a CPU 1516-3 (station 'a') and a Scalance XC208 (station 'b'). For station 'd' I'm going to use an AC drive.
By the way, is there a standard TIA program to be loaded to the controller? Or should I simply create one?
Read document "MRP_Pdev", starting at page 10, but it's not very clear to me how to perform this test.

[benja_m]

Hi,

Of course, that was missing in my GSDML file! Fixed and now all S2 tests are running successfully. Thank you very much.

Now my next question refers to MRC Interop - Client test. I guess the setup I would have to put together is the one shown in section 5.2.6.6, figure 5-21. If so, what do I do if I don't have those additional equipment (listed under 5.2.2 section)?

Yes Figure 5-21 is the correct setup for that testcase. I can't say whether the test would pass with different equipment. Some developers choose to have partial pre-tests done at PI test labs to cover the testcases that require additional equipment (S2 Interoperability, MRP-Interop, Netload, etc.). This is optional. Other developers only test the testcases which use the normal ETS setup before moving on to a full certification test at a PI test lab.

Right. I will try my fortune anyway. Have a CPU 1516-3 (station 'a') and a Scalance XC208 (station 'b'). For station 'd' I'm going to use an AC drive.
By the way, is there a standard TIA program to be loaded to the controller? Or should I simply create one?
Read document "MRP_Pdev", starting at page 10, but it's not very clear to me how to perform this test.

The testbundle contains example projects. See PN-Test\engineering