FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
- About Hugues
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About Hugues
since
03-02-2023
2 weeks ago
Hugues
Member
9
Posts
0
Likes
0
Solutions
Hello, Using simply DL_ReadNode() works perfectly. Thanks
... View more
Hello, I'm trying to get a string from the datalayer at 'fieldbuses/modbustcp/client/devices/EFC1/info/status' which would return a drive status. I've been using some other forum topics to make the following code : I understood that I have to use the type written in References from Metadata, so uint16 in that case. But I got the DL_Type_mismatch error : Is my problem about wrong type variable type ? Or did I implement some code error ? Thanks in advance
... View more
12-11-2023
08:33 AM
UPDATE : I tried an other Modbus communication using function blocks in PLC Engineering. The problem remains the same. I also observed that the sequence of booting the Core with the drive being off first (and then power it right after) works just fine. Is it possible that there is a conflict in some way between the booting and the Modbus communication ?
... View more
12-07-2023
11:37 AM
Hello, I'm having two similar problems about a CtrlX Core X3 communicating with a speed variator drive (EFC5610) by the Modbus TCP App. So in the first case, the CtrlX won't boot properly while having a Modbus communication plugged on its XF51 port. The indicator lights vary between red and blue so it means that it activated the rescue system (from the status displays document). Nothing changes unless I unplug the cable on the XF51 port. The CtrlX then boots normally and works correctly after I plug again on the XF51 port. Same configuration with a different CtrlX Core X3, this time the CtrlX boots and starts properly. But the Modbus communication doesn't start unless I unplug and then re-plug the XF51 port. So that makes two very similar situation and it is quite disturbing having to physically interact with the system everytime it restarts. So I'm wondering what could be the cause of it ? Could it be an app version issue or else ? I'm using a CtrlX Core X3 in 1.20 version and the Modbus TCP app in 1.20.1 version. I also don't think that the problem comes from the bus configuration because the bus works well after the quick cable handling. Thank you in advance.
... View more
07-25-2023
01:43 PM
So I went through all steps from A to I but at step J, clicking on Drive Engineering only opens an empty window doing nothing. Or using CMD then the ping at 172.31.254.1 adress doesn't respond. Using Drive Engineering, I can connect on the drive (picture 1) but it only opens another empty window (picture 2). I've seen older tutorials about EoE and it was said that on the Network Interfaces, eth1 port or EthercatMaster port which should correspond to XF50 also has to be IP forwarding enabled. But this port in non-apparent on the page. Did it change because of the Core version ?
... View more
OK
OK