About Drelax21

The tool on the screenshot is called UAExpert. See this external link. This configuration can be done via any OPC UA client as long as our OPC UA server is running on the ctrlX CORE. On the data layer, like mentioned, enter e.g. following: { "name": "Test", "endpointUrl": "opc.tcp://192.168.1.1:4840", "sessionConfiguration": { "userToken": { "userIdentityToken_type": "TokenUserPassword", "userIdentityToken": { "username": "boschrexroth", "password": "***" } }, "messageSecurityMode": { "messageSecurityMode": "BESTAVAILABLE" }, "securityPolicy": { "securityPolicy": "BESTAVAILABLE" }, "localeIds": ["en-US"] }, "timeoutConfiguration": { "browseCallTimeout": 10000, "discoveryTimeout": 60000, "publishTimeout": 60000, "readCallTimeout": 10000, "sessionTimeout": 1200000, "watchdogTimeout": 5000, "writeCallTimeout": 10000, "callCallTimeout": 10000 }, "persistent": true } ctrlX CORE Web UI data layer viewer add OPC UA client In the actual version 1.20 you can also use the ctrlX CORE Web UI directly: ctrlX CORE Web UI add OPC UA client ... View more

You could send the system report without the app data then it should be small enough. Otherwise we could open an adhoc data exchange. Is this still an issue or can the topic be closed? ... View more

In a ctrlX CORE the the standard scheduler for PLC tasks is working in 1ms cycle time at the moment, so the tasks cannot be set faster. You could use another event to trigger you task faster created directly in the ctrlX COREs scheduler. But at the moment also there is minimum time of 500µs. Could you explain what you need such low cycle times? As e.g. EtherCat is 2ms minimum in X3 so IO data could also not get updated faster. ... View more

Hi, due to the possible support issues by our side, the CoDeSys licensing is not supported by our ctrlX CORE. You can buy the MQTT license at our ctrlX Store (CODESYS - IIoT Libraries (boschrexroth.com)). Please check if CoDeSys takes back the license, you've bought. kind regards ... View more