I am using the PROFINET Device App on ctrlX CORE. The ctrlX CORE is used as a PROFINET IO Device connected to an external PROFINET IO Controller.

The documentation states a cyclic process data limit of 1440 bytes INPUTS and 1440 bytes OUTPUTS.

Is there any officially supported way to extend this limit (1440/1440 bytes) or handle a larger amount of data with the PROFINET Device App?

I also tried to add a second PROFINET Device instance on another port. It appears in the UI, but the status is “License not available”. Would an additional license allow a second instance to run, or is only one instance supported regardless of licensing?

I am trying to establish secure HTTPS communication from my PLC(sigmatek) to a ctrlX CORE X3. Unfortunately, I keep running into Error 35 (SSL/TLS handshake failure) and could use some guidance to see if I'm missing something in my certificate setup.

Here is what I have done so far:

1. CA Certificate: I created a ca.crt file and uploaded it to both the PLC and the ctrlX CORE.

2. Device Certificates: I generated a ctrlX.crt and a ctrlX.key.

3. SAN Config: I explicitly added the IP address/hostname of the ctrlX CORE X3 as a subjectAltName (SAN) in the certificate.

4. ctrlX Setup: I uploaded the ctrlX.crt and ctrlX.key to the Web Server tab in the ctrlX CORE web interface.

   

Despite this, whenever the PLC attempts to initiate the HTTPS connection, it fails and returns Error 35.

Am I overlooking a specific configuration step for the ctrlX web server, or is there a common pitfall with how the X3 handles custom CA-signed certificates?

Any help or insight would be greatly appreciated!

Hi everyone,

We're excited to introduce a new format for keeping ctrlX OS users informed: a regular newsletter covering what's new across ctrlX OS, apps, how-tos, SDK updates, and ecosystem news — curated and concise.

Issue #1 is out now. If you're using ctrlX OS and would like to receive future issues directly in your inbox, just reach out to us.

Got feedback on the format or content? We'd love to hear it — just reply to this post. We're building this together.

Read the first issue online: ctrlX OS Product Updates - May 2026

Inscribe: https://www.ctrlx-os.com/en/product-updates

— The ctrlX OS Ecosystem Team

However, they are using this license, and they will likely have a need for it in the future, for example in failure situations.

The versions they are using in this testing are the latest ones, i.e., ctrlX OS 4.6, Motion App 4.6, etc.

Motion for 10 axes worked, but the extension to 20 axes did not.

This is not yet a major issue, but later in the year, when customer deliveries begin, it will be required.

Could this still be an issue related to the prototype versions, or does the problem also occur with the current versions?

Br, Marko

• Is it supported to configure two IP addresses (one per Ethernet interface) on the device?

• Can the Web UI be accessed via both interfaces/IPs?

• Specifically, is Web UI access supported through XF50 or XF51, or only through XF10?
  If supported, are there any prerequisites (routing, interface mode, or service binding settings) required to enable Web UI access on the secondary interface?

I have a CSV file that stores the data from each cycle on the microSD card. The problem is that when the card is removed, the PLC does not detect its absence, and I need an error to be generated in that situation.

I am using the "CXA_FileAsync" library, but it does not return any error. How can I fix this problem? If possible, could you provide an example?

we are currently facing an issue with HTTPS configuration on a ctrlX device.
We use a CA‑signed custom webserver certificate (webserver_custom_cert.pem + webserver_custom_key.pem) with a DNS name matching the certificate.

Uploading the certificate and key under Certificates / Keys, using the correct filenames, and rebooting works initially. However, after reboot the system recreates and uses the default Bosch Rexroth certificate instead of the custom one.

This setup worked before with an older (now expired) certificate. The new certificate was re‑issued by our corporate CA based on the existing private key.
No PKI is configured on the ctrlX.

Has anyone experienced a similar issue or can confirm additional requirements (e.g. PKI settings, CSR generation constraints, certificate format) to ensure the custom certificate is persistently used?

Thanks in advance!

I tried to update the system image on a CtrlX Core X7 from 3.6 to 4.6. I used an USB stick formatted in FAT32 with the system image, mounted on the XF01C usb port (as described in the manual). I tried several times but it was unsuccessful every time. I also tried with version 4.4. It seems that the update doesn't happen at all, when I boot again the CtrlX is still in 3.6.

When we connect to the CtrlX webpage during the process, we see this screen:

rexroth-arch01.tar is the name of the file we can find in the "rescue" folder of the 3.6 .zip system image file.

In version 4.X, the file is called rexroth-arch02.ova.

Could this be the problem? Am I using the right method for updating CtrlX to 4.6?

Thank you

The device repeatedly shows:

• 080F0550: Error in license management

• 080E0550: License manager warning

• detailed diagnostic 0C7A0092: ctrlX OS System License - *** - Standard Runtime missing

Additionally, I also see a health warning:

• 080F0540: Warning detected during health monitoring

• detailed diagnostic 0C66003A: High control temperature

The problem is that, as far as I can see, there is no such license on the device, and the documentation for this error does not really explain the root cause.

We already tried several times to reinstall the firmware completely with a fresh system image, following the official reset and restore instructions. The installation itself works, but after some time the same error comes back again.

Has anyone seen this issue before, or can suggest what else should be checked?