PRONETA Profile Tester Configuration

Owned by Nico Mäding
2024-05-23
8 min read

1. PC Specs

1.1. Software

OS:

Edition: Windows 10 Pro
Version: 20H2
OS Build: 19042.804
Experience: Windows Feature Experience Pack 120.2212.551.0

SIMATIC.NET(CP1616 firmware):

V02.08.01.00_00.01.00.00

PRONETA:

PROFINET_Profile_Tester_v5.2.0.24

2. IO Device Configuration

The configuration of the IO device is described at PDMC V1.1/V4.1.0.0 Configuration.

3. Profile Tester Installation

1. Install SIMATIC.NET CP16XX

2. Load the firmware into the CP1616

The firmware is part of the SIMATIC.NET CP16XX cd. The application, FWLoad, used to load it is part of the installation package and located in "C:\Program Files\Siemens\SIMATIC.NET\CP1616\inst_bin" 

3. Disable Windows10 Driver Signing feature. 

The Testing software uses a driver that is not signed, so in order to be properly installed, the signing feature has to be disabled. To do this open a shell with administrative privileges and type:

bcdedit /set TESTSIGNING ON.



At this point, if you receive the following error:

"The value is protected by Secure Boot policy and cannot be modified or deleted."

you may have to disable the "Secure Boot" feature from the BIOS.

How to check Secure Boot state: https://learn.microsoft.com/en-us/mem/intune/user-help/you-need-to-enable-secure-boot-windows

The particular procedure depends on the BIOS utility. For ASUS, for example, follow this article: https://www.technorms.com/45538/disable-enable-secure-boot-asus-motherboard-uefi-bios-utility

4. Restart the PC. After restarting a watersign will appear at the bottom right corner, notifying the user that Windows is in Test mode.

5. Install the PRONETA Software

The installer will automatically install CP1616 driver (the device is named SPIRTA CP1616).

6. To disable the Winodows Test Mode, run again Command Prompt as an Administrator and type:

bcdedit /set TESTSIGNING OFF.

7. Reboot after installation.

8. Launch PRONETA software with Admin elevation

9. PRONETA shows error TTIF open failed 0xA200 = (Application Error). According to the User Manual this is a driver issue.

To resolve this issue I had to disable and re-enable the SPIRTA CP1616 Driver in the Device Manager:

This step has to be reapplied after each reboot or shutdown (or reboot with the Advanced options described in step 7 of this guide).

4. Configuration via TIA Portal

Using TIA Portal V16

Configuration Procedure, done according to PTv5_SP2_User_Guide.pdf, section 6.2.3:

1) Create a new project in TIA portal

2) Drag and drop a PC Station from the hardware catalog into the Network view panel.

3) Double Click onto the added device.

4)Step 3 will open the Device view. Drag and drop the 6GK1 161-6AA00 module from the Hardware catalog onto the previously added PC Station. The Proneta guide recommends using this module regardless of which hardware model is actually used.

5) Double-click on the CP1616 module and select the Ethernet addresses dialogue. Here you can set the IP address of the controller.

6) Now import the GSDML of the PN Device. If the GSDML-file of your device has not been installed yet, go to ‘Options’ → ‘Manage general station description files (GSD)’. The following window will open (see Figure 6-29 of Proneta Guide): adapt the source path, select the GSDML file you want to install and select ‘Install’.

7) Add the newly imported device to network view. 

8) Assign the device to the CP1616 PROFINET Interface

9) Insert the Profidrive PAP and the intended "Standard Telegram" submodule (Standard Telegram 1, 2 or 3. AC4 needs Standard Telegram 3). Double-click the device to open it in device view. Drag and drop the PROFIdrive module from the hardware catalog to the Device Overview.

Application Class 4 (IRT mode is required):

10) [From the Poneta guide]Switch back to ‘Network overview’, click on the device icon and switch to the tab ‘Properties’ in the bottom window. Select ‘PROFINET interface’ → ‘Ethernet addresses’: here the IP-address, PROFINET device name and device number have to be adapted (has to match actual setting of the device: can be checked and edited in section ‘Online access’ of the project tree → [used network adapter] → ‘Update accessible devices’

11) If IRT-communication shall be configured the following steps have to be executed: - Open the properties of the CP1616 → ‘PROFINET interface (X1)’ → ‘Advanced options’ → ‘Real time settings’ and select ‘Sync master’ as synchronization role. If necessary, the "Send clock" can be adapted here as well - Open the properties of the device under test → ‘PROFINET interface [X150]’ → ‘Advanced options’ → ‘Isochronous mode’ - Check the ‘Isochronous mode’ box and the module which shall run in isochronous mode (e.g. Standard telegram 3) 

12)  Now the settings can be compiled: mark the PC station and select ‘Compile’ in
the top toolbar → successful compiling is signaled by the output ‘Compiling finished
(errors: 0; warnings: 0)

13) Afterwards select ‘Download to device’ → choose the network adapter and PN interface → ‘Start search’ → select the CP1616 and click ‘Load’ → hardware configuration will be downloaded to the CP1616

5. Profile Tester Usage

1) Upon completing the above steps the Profile Tester will detect the change in configuration, will issue a notification, and will update the configuration.

2)Configure the tester. If you have already created a project, click the home button in the top-left corner and select 'Settings'. First select which Ethernet adapter to use.

In the GSDLM manager add the GSDML file for your device. This is done so the tester can later recognize the modules on the device.

3) Configure the Application Class and  type of the IO Device

4) In the Project View go to Device Access and find your device. After clicking on it the tester should be able to recognize it's modules. However In this case, the tester is only able to recognize the DAP and not the PROFIDrive Module, even though it's described in the GSDML and configured in TIA portal.

Device Parameter End Indication:

Device Parameter End Response:

In this scenario there is no PNS_IF_CHECK_IND send from the device's stack.

5.1.1. Network capture

The following network capture is made after switching the IO device to Operate mode from the Profile Tester:

PronetaOperateNetworkCapture.pcapng

5.1.2. Using a custom script to attempt to read records from the device

5.1.2.1. Read PROFINET Record

In order for that script to execute successfully, the tester has to be in "Operate" Mode

Script

set_verbose_mode() read_data_record_controller(0x2)

Output:

Wireshark:

There is no Read Record Request sent from the master to the device.

5.1.2.2. Read a PROFIdrive Parameter Using the controller

set_verbose_mode() read_value_controller(1)

Write Parameter Indication received by the firmware:

Wireshark:

5.1.2.3. Read a PROFIdrive Parameter Using Device Access

set_verbose_mode() connection1 = establishConnectionDA(get_current_line) connection1.read_value(1)

Write Parameter Indication received by the firmware:

Wireshark:

6. CifX PNMv3 Master Network Capture

For reference here's a network capture with the same device connected to a cifx PNMv3. Configuration is done using Sycon.

Master:

Device:

In this connection sequence, cyclic exchange starts immediately after connection is established. 

7. Establishing communication using a PLC

PLC model: SIMATIC S7-1200

CPU: 1214C DC/DC/DC

Tia Ladder Diagram:

Wireshark trace:

SiemensPLC_Comm.pcapng

Read Record Indication in the device firmware: