About jacaré

NoRisk4Project · ‎12-07-2023

The problem is, as I mentioned before, the NodeId "ns=2;s=Methods/sqrt(x)" of the method and the interpretation of it inside the OPC UA Client app. Inside the DataLayer (I named my client "Milo") it's "opcuaclient/Milo/i=85/ns=2;s=Methods/sqrt(x)" and when you connect via our OPC UA server it's "ns=6;s=opcuaclient/Milo/i=85/ns=2;s=Methods/sqrt(x)" And in both cases it doesn’t work, because the Id doesn’t fit. I just tested a development version of the OPC UA Client app with a bugfix and now the NodeId inside the DataLayer is "opcuaclient/Milo/i=85/ns=2;s=Methods/ns=2;s=Methods/sqrt(x)" and "ns=6;s=opcuaclient/Milo/i=85/ns=2;s=Methods/ns=2;s=Methods/sqrt(x)" inside our OPC UA server. And now it runs ... The bug will be fixed with RM24.03 (version 2.06). If you use the OPC UA Client app inside the PLC, you don't need to wait for the bugfix. You can call the method by using the right NodeId ("ns=6;s=opcuaclient/Milo/i=85/ns=2;s=Methods/ns=2;s=Methods/sqrt(x)") right now.

CodeShepherd · ‎12-07-2023

Together we found following: The axis were not visible in the EoE tab of the EtherCat master in the ctrlX CORE web UI and master configuration was missing: ctrlX CORE web UI - EtherCat master - EoE setting missing Further more when clicking on a slave the Protocols EoE and SoE were not available: ctrlX CORE web UI - EtherCat slave information - missing protocols As a result the ctrlX MOTION was not able to read out and check the scaling settings of the drive while booting up. Everything was correctly configured in the ctrlX IO Engineering project. The reason seemed to be a problem with the installation of ctrlX WORKS. After uninstalling their current version and installing the latest LTS version 1.20.5 the IO project was again loaded to the ctrlX CORE and the machine was working like expected.

jacaré · ‎11-30-2023

You don't need any additional ESI files to Scan the Ethercat Network and to find your devices. I hope a reboot will do the job 🙂

jacaré · ‎11-10-2023

This issue is known and is fixed with the Version 2.02. For the Version 1.20 it will be fixed with the Release Milestone 24.03 (2024 March)

jacaré · ‎10-17-2023

For SSH access you need a root-user for your ctrlX Core. This is only provided by the Rexroth Support and only for development purposes. If you need one, please contact the support via: service@boschrexroth.de or your local sales rep

Search in community

About jacaré

Re: Cannot use OPC UA Method with OPC UA App

Re: Error scaling AxisProfile 091F0007/0C580401

Re: Where can I find device description files for the axes?

Re: I/O Engineering - Slave to Slave connection can't be saved

Re: Connect ctrlX CORE to a VNC Server using noVNC (MobaXterm)