Netload Robustness for Security test

[rottava]

Hello,

I have some questions regarding this test.

1. A PC with Ubuntu to run the SL1-Tester was prepared and it's working fine. Followed the instructions given by the document "How to install and to run the security level 1 tester V2.43.0.0_V1.0.pdf". This is sorted now.

2. Using "normal_d_V2.43.0_RT_CU_POF_V19.zap19" PLC program as example, changed 'dut' and 'd' devices to match mine.

But...

- My 'dut' (a 2-port device) is set to exchange 1 input and 1 output words for cyclic data. This is what I've done for all tests. However, PLC shows in the HMI an error message related to IO data. How should I proceed in this case?

- According to Figure 5-7 from document "Testspec-PN_2572", a switch "R" is required to connect all devices. Is it ok to use a Scalance XC208, the so called 'b' device for other tests?

- Should I add this 'b' device to my PLC program as well?

- I am not including information about topology, as already done for MRP Inter. Am I right?

Please let me know your comments about these points.

Best Regards,
Luciano.

[galtech]

Hello,

I have some questions regarding this test.

1. A PC with Ubuntu to run the SL1-Tester was prepared and it's working fine. Followed the instructions given by the document "How to install and to run the security level 1 tester V2.43.0.0_V1.0.pdf". This is sorted now.

2. Using "normal_d_V2.43.0_RT_CU_POF_V19.zap19" PLC program as example, changed 'dut' and 'd' devices to match mine.

But...

- My 'dut' (a 2-port device) is set to exchange 1 input and 1 output words for cyclic data. This is what I've done for all tests. However, PLC shows in the HMI an error message related to IO data. How should I proceed in this case?

- According to Figure 5-7 from document "Testspec-PN_2572", a switch "R" is required to connect all devices. Is it ok to use a Scalance XC208, the so called 'b' device for other tests?

- Should I add this 'b' device to my PLC program as well?

- I am not including information about topology, as already done for MRP Inter. Am I right?

Please let me know your comments about these points.

Best Regards,
Luciano.

Hi Luciano,

1. What exactly does the error message from the PLC say?

2. The Scalance X208 will not work for netload testing because it is a managed switch. An unmanaged "dumb" switch is needed for netload testing so the maximum network traffic is transmitted to the dut. The unmanaged switch won't need to be added to the TIA portal project.

You're correct that topology is not necessary for netload testing.

Best,
Maddie

[rottava]

Hello,

I have some questions regarding this test.

1. A PC with Ubuntu to run the SL1-Tester was prepared and it's working fine. Followed the instructions given by the document "How to install and to run the security level 1 tester V2.43.0.0_V1.0.pdf". This is sorted now.

2. Using "normal_d_V2.43.0_RT_CU_POF_V19.zap19" PLC program as example, changed 'dut' and 'd' devices to match mine.

But...

- My 'dut' (a 2-port device) is set to exchange 1 input and 1 output words for cyclic data. This is what I've done for all tests. However, PLC shows in the HMI an error message related to IO data. How should I proceed in this case?

- According to Figure 5-7 from document "Testspec-PN_2572", a switch "R" is required to connect all devices. Is it ok to use a Scalance XC208, the so called 'b' device for other tests?

- Should I add this 'b' device to my PLC program as well?

- I am not including information about topology, as already done for MRP Inter. Am I right?

Please let me know your comments about these points.

Best Regards,
Luciano.

Hi Luciano,

1. What exactly does the error message from the PLC say?

2. The Scalance X208 will not work for netload testing because it is a managed switch. An unmanaged "dumb" switch is needed for netload testing so the maximum network traffic is transmitted to the dut. The unmanaged switch won't need to be added to the TIA portal project.

You're correct that topology is not necessary for netload testing.

Best,
Maddie

Hi Maddie,

Concerning first question, looks like PLC is unable to find the dut since it shows "IO device not found" (screenshots attached). As mentioned before, I've loaded the example program "normal_d_V2.43.0_RT_CU_POF_V19.zap19" and simply swapped the dut already there with mine. Didn't touch program blocks. And in terms of connection, it's exactly according to Figure 5-7.

Regarding the second, fair enough. Replaced the XC208 by a dumb unmanaged switch which was laying over here.

Thank you very much for your inputs.

Best Regards,
Luciano.

[galtech]

Hello,

I have some questions regarding this test.

1. A PC with Ubuntu to run the SL1-Tester was prepared and it's working fine. Followed the instructions given by the document "How to install and to run the security level 1 tester V2.43.0.0_V1.0.pdf". This is sorted now.

2. Using "normal_d_V2.43.0_RT_CU_POF_V19.zap19" PLC program as example, changed 'dut' and 'd' devices to match mine.

But...

- My 'dut' (a 2-port device) is set to exchange 1 input and 1 output words for cyclic data. This is what I've done for all tests. However, PLC shows in the HMI an error message related to IO data. How should I proceed in this case?

- According to Figure 5-7 from document "Testspec-PN_2572", a switch "R" is required to connect all devices. Is it ok to use a Scalance XC208, the so called 'b' device for other tests?

- Should I add this 'b' device to my PLC program as well?

- I am not including information about topology, as already done for MRP Inter. Am I right?

Please let me know your comments about these points.

Best Regards,
Luciano.

Hi Luciano,

1. What exactly does the error message from the PLC say?

2. The Scalance X208 will not work for netload testing because it is a managed switch. An unmanaged "dumb" switch is needed for netload testing so the maximum network traffic is transmitted to the dut. The unmanaged switch won't need to be added to the TIA portal project.

You're correct that topology is not necessary for netload testing.

Best,
Maddie

Hi Maddie,

Concerning first question, looks like PLC is unable to find the dut since it shows "IO device not found" (screenshots attached). As mentioned before, I've loaded the example program "normal_d_V2.43.0_RT_CU_POF_V19.zap19" and simply swapped the dut already there with mine. Didn't touch program blocks. And in terms of connection, it's exactly according to Figure 5-7.

Regarding the second, fair enough. Replaced the XC208 by a dumb unmanaged switch which was laying over here.

Thank you very much for your inputs.

Best Regards,
Luciano.

Hi Luciano,

Can you record the network traffic when you disconnect and connect the dut from the network? The network capture should show why the device isn't connecting. For example, if the name and IP of the device aren't set (double-checking that the device has a name set is always a good first step), it won't answer DCP Ident and ARP requests from the PLC, so the PLC can't find it. If the device is rejecting Connect Requests from the PLC, there may be something wrong with the device configuration in the engineering project.

Best,
Maddie

[rottava]

Hi Luciano,

1. What exactly does the error message from the PLC say?

2. The Scalance X208 will not work for netload testing because it is a managed switch. An unmanaged "dumb" switch is needed for netload testing so the maximum network traffic is transmitted to the dut. The unmanaged switch won't need to be added to the TIA portal project.

You're correct that topology is not necessary for netload testing.

Best,
Maddie

Hi Maddie,

Concerning first question, looks like PLC is unable to find the dut since it shows "IO device not found" (screenshots attached). As mentioned before, I've loaded the example program "normal_d_V2.43.0_RT_CU_POF_V19.zap19" and simply swapped the dut already there with mine. Didn't touch program blocks. And in terms of connection, it's exactly according to Figure 5-7.

Regarding the second, fair enough. Replaced the XC208 by a dumb unmanaged switch which was laying over here.

Thank you very much for your inputs.

Best Regards,
Luciano.

Hi Luciano,

Can you record the network traffic when you disconnect and connect the dut from the network? The network capture should show why the device isn't connecting. For example, if the name and IP of the device aren't set (double-checking that the device has a name set is always a good first step), it won't answer DCP Ident and ARP requests from the PLC, so the PLC can't find it. If the device is rejecting Connect Requests from the PLC, there may be something wrong with the device configuration in the engineering project.

Best,
Maddie

Hello Maddie,

That was it! IP address and station name were wrong. I remember double checking these settings every time I start a new test (with PRONETA), but this time apparently I missed; or a leftover from previous tests, don't know for sure.

Anyway, after fixing this configuration, performing the test was easy and everything went well.

Once again, thank you very much for the heads up.

Regards,
Luciano