We are facing issues connecting to the device on EtherCat port XF50, its showing as connection state not connected. Even though everything is physically wired. When I move it to XF52 it is showing as connected.

The dashboard runs continuously in a browser without any problem initially. However, after approximately 24–48 hours, the active session suddenly disconnects and the browser shows:

“Your connection is not private”

Error: NET::ERR_CERT_AUTHORITY_INVALID

I can access the PLC, HMI, and other devices on my local machine network, just not the robot. I have the controller’s WAN on my local network, and can access it when I’m directly connected to the machine’s local network.

I'm using the method where XF10 is connected to the internet and XF51 is my local machine network. I have XF51's IP set as the gateway on my devices, and this works for everything except the robot.

Thanks!

I can access the SafeX locally through EoE, so I know that the EoE connection is working correctly. It would be helpful to access or troubleshoot the SafeX remotely. Please advise if anyone has a solution for this.

Thanks!

We are making an IoT application for one of our customers (this also applies to the service Indicator App) and in their older machines they are using double axes IndraDrives.

We are connecting to drives that are connected to a MTX so we are using a user defined connections file:

[
    {
        "driver": "SIP",
        "properties": {
            "family": "IndraDrive",
            "ip": "192.168.143.1"
        }
    },
    {
        "driver": "SIP",
        "properties":{
            "ip": "192.168.143.3"
        }
    }
]

(note however that the example in the documentation is incorrect)

https://docs.automation.boschrexroth.com/doc/3473811139/feature-browsing-and-device-creation/latest/en/

But in our tests it doesn't seem that the drive connect cant connect to both drives, only the first one.

Sure the V3 documentation doesn't say that it supports IndraDrive, but it works fine for single axis devices (And V2 documentation says it works).

I also know that the SIP that's used in the drive connect app supports connecting to subdevices (Called SlaveIndex in SIP Read request).

Any chance to add support for subdevices for user defined connections, for instance like this:

[
    {
        "driver": "SIP",
        "properties": {
            "family": "IndraDrive",
            "ip": "192.168.143.1",
	        "index":1
        }
    },
    {
        "driver": "SIP",
        "properties": {
            "family": "IndraDrive",
            "ip": "192.168.143.1",
	        "index":2
        }
    },
    {
        "driver": "SIP",
        "properties":{
            "ip": "192.168.143.3"
        }
    }
]

We're totally fine if it doesnt work for auto detecting drives as that's probably a much bigger change.

My background is with PLC/HMI/MOTION and I have no experience with IOT/ database apps on the core but from research it looks like Node Red is the most common / preferred method of handling SQL.

1. As far as I can tell there are no standard CtrlX OS Apps that provide an option for providing a local SQL database on the core? The customer would have to create their own snap to handle this as described in Connect to MySQL Server using Node-red and run MySQL locally on ctrlX CORE or maybe PostgreSQL on ctrlX CORE ? If either of these are recommended are there more simple step by step instructions for users without snap knowledge?

2. A simpler method could be just to write to a local file and when network back on line read contents of the file and update remote SQL database?

3. Would there be any examples of how a network outage can be detected in Node Red?

Any support/advice would be greatly appreciated, Many Thanks!

I intent to connect multiple datalayers across different subnets/networks in a factory. Is it possible to reliably connect and access Data Layers across different IP subnets or network segments in ctrlX OS? Currently, I have reliability issues with the most basic setup:

• X5, X3 and X3 connected via switch (XF11, XF51 set to xxx.xxx.2.x)

• The datalayers can be found under "remotes" of X5

• After boot, the last remote node is unreachable

I have a customer who is having a problem with getting their Core to connect to the Telegraf app. The error message is 'Failed to reach server: Get 'https://localhost': tls: failed to verify certificate: x509 certificate is not valid for any names, but wanted to match localhost'

The API key has been regenerated, and the username and password are correct. Any ideas of how to resolve this?

I have attached a system report.

I am using the latest ctrlX Node Red v4.4.0 app.

Node red dashboard version 1 has been deprecated. Default node red dashboard version 2 is installed.

When i demonstrate the ctrlX node red app to customer i will use the node red datalayer node example. but however the example provided is for node red dashboard version 1. Will there be an update to the node red datalayer node for dashboard version 2 examples?