PROFINET Forum

S.Ogura wrote: ↑24 Feb 2026, 02:04 Thank you for your assistance.

Our company has already applied for testing.
We are currently developing PROFINET IRT-compatible (Encoder Profile compatible) devices.
We have obtained all the test equipment specified in the PROFINET certification test specifications and are currently in the process of setting it up.

Please advise us about the SPIRTA tester (CP1616).

<Question 1>
I started the SPIRTA tester, read the GSDML of the target DUT, and set the module configuration.
Next, I would like to set the network configuration to be tested.
It appears that the IP addresses can be set in the "Spirta IP Settings" and "Device Settings" settings on the "Project Settings" - "General Settings" tab in SPIRTA.
Can the IP address setting of the target DUT be reflected using just these settings? Is a separate network configurator or something similar necessary?

<Question 2>
I don't understand the relationship between the IP address variable displays "Sp_Deviceip: 192.168.0.50" and "Sp_CP1616p: 192.168.0.28" displayed on the "Project Settings" - "Project Variables" tab in Spirta.
Does Spirta test using a fixed IP address setting?

<Question 3>
In the setup instructions (page 4 of the SPIRTA IRT Tester manual (Sprirta_V2_46_0_003)), there is a section that reads, "Disable new requirements for drivers introduced in Windows 10."
It states the following:
"Check security settings via Start -> Settings -> Update & Security. Click on "Windows security" -> Device Security. Click on "Core isolation details" and uncheck "Memory integrity" and "Memory access protection", if possible. Restart the computer."

The setting option for the part of this instruction that appears is missing:
"Windows security" -> Device Security. Click on "Core isolation details" and uncheck "Memory integrity" and "Memory access protection", ..."

As a result, this setting is not possible.

I then performed the next setting, "Another way is to enable test-signing boot configuration."

The PC I am using is a SIMATIC Industrial PC IPC847E.

However, when I restart the PC with this setting, a warning "!" appears on the device in SPIRTA in Windows Device Manager (attached file: DeviceManager.jpg).
DeviceManager.jpg

The warning disappears when I reset the "Another way is to enable test-signing boot configuration." setting, but the warning "!" appears again when I restart the PC again.

Could this be because the "Windows security" -> Device Security" settings haven't been configured?
I'm having trouble.

Thank you in advance for your help.

Raik.Zachmann wrote: ↑24 Feb 2026, 14:41

S.Ogura wrote: ↑24 Feb 2026, 02:04 Thank you for your assistance.

Our company has already applied for testing.
We are currently developing PROFINET IRT-compatible (Encoder Profile compatible) devices.
We have obtained all the test equipment specified in the PROFINET certification test specifications and are currently in the process of setting it up.

Please advise us about the SPIRTA tester (CP1616).

<Question 1>
I started the SPIRTA tester, read the GSDML of the target DUT, and set the module configuration.
Next, I would like to set the network configuration to be tested.
It appears that the IP addresses can be set in the "Spirta IP Settings" and "Device Settings" settings on the "Project Settings" - "General Settings" tab in SPIRTA.
Can the IP address setting of the target DUT be reflected using just these settings? Is a separate network configurator or something similar necessary?

<Question 2>
I don't understand the relationship between the IP address variable displays "Sp_Deviceip: 192.168.0.50" and "Sp_CP1616p: 192.168.0.28" displayed on the "Project Settings" - "Project Variables" tab in Spirta.
Does Spirta test using a fixed IP address setting?

<Question 3>
In the setup instructions (page 4 of the SPIRTA IRT Tester manual (Sprirta_V2_46_0_003)), there is a section that reads, "Disable new requirements for drivers introduced in Windows 10."
It states the following:
"Check security settings via Start -> Settings -> Update & Security. Click on "Windows security" -> Device Security. Click on "Core isolation details" and uncheck "Memory integrity" and "Memory access protection", if possible. Restart the computer."

The setting option for the part of this instruction that appears is missing:
"Windows security" -> Device Security. Click on "Core isolation details" and uncheck "Memory integrity" and "Memory access protection", ..."

As a result, this setting is not possible.

I then performed the next setting, "Another way is to enable test-signing boot configuration."

The PC I am using is a SIMATIC Industrial PC IPC847E.

However, when I restart the PC with this setting, a warning "!" appears on the device in SPIRTA in Windows Device Manager (attached file: DeviceManager.jpg).
DeviceManager.jpg

The warning disappears when I reset the "Another way is to enable test-signing boot configuration." setting, but the warning "!" appears again when I restart the PC again.

Could this be because the "Windows security" -> Device Security" settings haven't been configured?
I'm having trouble.

Thank you in advance for your help.

Hello,

following the answers to your questions:

Question 1:
There is no need to adapt the IP settings, the default values are fine. Within the test cases the DUT gets the IP settings automatically assigned.

Question 2:
Spirta IP settings are used by the controller (CP1616)
Device IP settings (DUT) are set during the test case sequence using DCP set.

Question 3:
On our System the settings can be found as mentioned.
You can search via windows search for “Device Security” and you should find it.
If not it needs to be checked if you are using the correct windows version:
Windows 10 64 Bit Professional, Version 22H2.
Do you have installed the correct driver for the CP1616?
Use the batch file which is delivered within the testbundle.
Please note, that for SPIRTA the official SIMATIC NET driver shall not be used and deleted if installed on the system.

S.Ogura wrote: ↑25 Feb 2026, 02:54

Raik.Zachmann wrote: ↑24 Feb 2026, 14:41

S.Ogura wrote: ↑24 Feb 2026, 02:04 Thank you for your assistance.

Our company has already applied for testing.
We are currently developing PROFINET IRT-compatible (Encoder Profile compatible) devices.
We have obtained all the test equipment specified in the PROFINET certification test specifications and are currently in the process of setting it up.

Please advise us about the SPIRTA tester (CP1616).

<Question 1>
I started the SPIRTA tester, read the GSDML of the target DUT, and set the module configuration.
Next, I would like to set the network configuration to be tested.
It appears that the IP addresses can be set in the "Spirta IP Settings" and "Device Settings" settings on the "Project Settings" - "General Settings" tab in SPIRTA.
Can the IP address setting of the target DUT be reflected using just these settings? Is a separate network configurator or something similar necessary?

<Question 2>
I don't understand the relationship between the IP address variable displays "Sp_Deviceip: 192.168.0.50" and "Sp_CP1616p: 192.168.0.28" displayed on the "Project Settings" - "Project Variables" tab in Spirta.
Does Spirta test using a fixed IP address setting?

<Question 3>
In the setup instructions (page 4 of the SPIRTA IRT Tester manual (Sprirta_V2_46_0_003)), there is a section that reads, "Disable new requirements for drivers introduced in Windows 10."
It states the following:
"Check security settings via Start -> Settings -> Update & Security. Click on "Windows security" -> Device Security. Click on "Core isolation details" and uncheck "Memory integrity" and "Memory access protection", if possible. Restart the computer."

The setting option for the part of this instruction that appears is missing:
"Windows security" -> Device Security. Click on "Core isolation details" and uncheck "Memory integrity" and "Memory access protection", ..."

As a result, this setting is not possible.

I then performed the next setting, "Another way is to enable test-signing boot configuration."

The PC I am using is a SIMATIC Industrial PC IPC847E.

However, when I restart the PC with this setting, a warning "!" appears on the device in SPIRTA in Windows Device Manager (attached file: DeviceManager.jpg).
DeviceManager.jpg

The warning disappears when I reset the "Another way is to enable test-signing boot configuration." setting, but the warning "!" appears again when I restart the PC again.

Could this be because the "Windows security" -> Device Security" settings haven't been configured?
I'm having trouble.

Thank you in advance for your help.

Hello,

following the answers to your questions:

Question 1:
There is no need to adapt the IP settings, the default values are fine. Within the test cases the DUT gets the IP settings automatically assigned.

Question 2:
Spirta IP settings are used by the controller (CP1616)
Device IP settings (DUT) are set during the test case sequence using DCP set.

Question 3:
On our System the settings can be found as mentioned.
You can search via windows search for “Device Security” and you should find it.
If not it needs to be checked if you are using the correct windows version:
Windows 10 64 Bit Professional, Version 22H2.
Do you have installed the correct driver for the CP1616?
Use the batch file which is delivered within the testbundle.
Please note, that for SPIRTA the official SIMATIC NET driver shall not be used and deleted if installed on the system.

Dear Raik,

Thank you for your reply.

Regarding questions 1 and 2, I understand that there is no need to specify an IP address, as it will be automatically set to a unique address specified by SPIRTA.

The problem is question 3.
The PC we procured for authentication is a SIEMENS SIMATIC IPC847E.
The selected OS edition is "Windows 10 Enterprise 2016 LTSB, (En, Ger, Fr, It, Sp), 64-bit (for Core i7, Xeon)."

OS options for the SIEMENS SIMATIC IPC847E are limited to the following:
1. Windows 10 Enterprise 2016 LTSB, 64-bit (for Core i3, Core i5)
2. Windows 10 Enterprise 2016 LTSB, 64-bit (for Core i7, Xeon)
3. Windows 10 IoT Enterprise 2019 LTSC, 64-bit (for Core i3, Core i5)
4. Windows 10 IoT Enterprise 2019 LTSC, 64-bit (for Core i7, Xeon)
5. Windows 10 IoT Enterprise 2021 LTSC, 64-bit (for Core i3, Core i5)
6. Windows 10 IoT Enterprise 2021 LTSC, 64-bit (for Core i7, Xeon)
7. Windows Server 2016 Standard Edition 64-bit, 5 clients
8. Windows Server 2019 Standard Edition 64-bit, 5 clients
9. Windows Server 2022 Standard Edition 64-bit, 5 clients

So, I'd like to somehow run this on my current Enterprise OS. Is there a way to work around this issue?

Currently, when I run "install.bat" at the end of the setup, the warning mark "!" for the CP1616 card displayed in Windows Device Manager disappears.
Also, if I run the SPIRTA test as is, the test seems to run successfully.
However, when I power the PC back on, the warning mark "!" for the CP1616 reappears.
Running "install.bat" again clears the warning mark "!" for the CP1616.

In other words, I have to run "install.bat" every time I power it on.
It's a bit inconvenient, but is this the only option?

Thank you in advance.

Raik.Zachmann wrote: ↑26 Feb 2026, 09:50

S.Ogura wrote: ↑25 Feb 2026, 02:54

Raik.Zachmann wrote: ↑24 Feb 2026, 14:41

Hello,

following the answers to your questions:

Question 1:
There is no need to adapt the IP settings, the default values are fine. Within the test cases the DUT gets the IP settings automatically assigned.

Question 2:
Spirta IP settings are used by the controller (CP1616)
Device IP settings (DUT) are set during the test case sequence using DCP set.

Question 3:
On our System the settings can be found as mentioned.
You can search via windows search for “Device Security” and you should find it.
If not it needs to be checked if you are using the correct windows version:
Windows 10 64 Bit Professional, Version 22H2.
Do you have installed the correct driver for the CP1616?
Use the batch file which is delivered within the testbundle.
Please note, that for SPIRTA the official SIMATIC NET driver shall not be used and deleted if installed on the system.

Dear Raik,

Thank you for your reply.

Regarding questions 1 and 2, I understand that there is no need to specify an IP address, as it will be automatically set to a unique address specified by SPIRTA.

The problem is question 3.
The PC we procured for authentication is a SIEMENS SIMATIC IPC847E.
The selected OS edition is "Windows 10 Enterprise 2016 LTSB, (En, Ger, Fr, It, Sp), 64-bit (for Core i7, Xeon)."

OS options for the SIEMENS SIMATIC IPC847E are limited to the following:
1. Windows 10 Enterprise 2016 LTSB, 64-bit (for Core i3, Core i5)
2. Windows 10 Enterprise 2016 LTSB, 64-bit (for Core i7, Xeon)
3. Windows 10 IoT Enterprise 2019 LTSC, 64-bit (for Core i3, Core i5)
4. Windows 10 IoT Enterprise 2019 LTSC, 64-bit (for Core i7, Xeon)
5. Windows 10 IoT Enterprise 2021 LTSC, 64-bit (for Core i3, Core i5)
6. Windows 10 IoT Enterprise 2021 LTSC, 64-bit (for Core i7, Xeon)
7. Windows Server 2016 Standard Edition 64-bit, 5 clients
8. Windows Server 2019 Standard Edition 64-bit, 5 clients
9. Windows Server 2022 Standard Edition 64-bit, 5 clients

So, I'd like to somehow run this on my current Enterprise OS. Is there a way to work around this issue?

Currently, when I run "install.bat" at the end of the setup, the warning mark "!" for the CP1616 card displayed in Windows Device Manager disappears.
Also, if I run the SPIRTA test as is, the test seems to run successfully.
However, when I power the PC back on, the warning mark "!" for the CP1616 reappears.
Running "install.bat" again clears the warning mark "!" for the CP1616.

In other words, I have to run "install.bat" every time I power it on.
It's a bit inconvenient, but is this the only option?

Thank you in advance.

Unfortunately I cannot give you an answer on this, because for other OS than the specified no support can be given.
As I understood you found a workaround and can run the tests. That's great.