FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
06-08-2023 06:33 AM
I am successfully able to establish connection with ctrlX DRIVE plus when drive master communication setting is kept SoE.
I am refering below steps during communication establishment.
But when i change drive master communication to CoE and follow the same steps. Drive is not showing in scan. Please refer the attachement.
ctrlX DRIVE: XMS2-W0023AN-02AX3T0NNET-S0316N3NNNS0NN
Runtime: FWA-XD1-AXS-V-0316N-NN-00.fwa
App: EtherCAT Master 1.20.0
ctrlX DRIVE Engineering: 01V22.0
Solved! Go to Solution.
06-13-2023 11:44 AM
For the connection way via the "Control Unit" tab you do not need to set up EoE. Only if you like to use the "IP address search". I will check the guide.
Could you
We will do some tests and answer here again.
06-20-2023 09:53 AM - edited 06-27-2023 08:39 AM
We could reproduce the behaviour that drives cannot be found via the "Control unit" tab when the fieldbus communication used is set to CoE.
EDIT: For your information the connection method "Control unit" is based on SERCOS IDs and so is not available when drives are in CoE communication mode.
EoE is working fine for all usecases so feel free to use the "IP address search" or use the "ctrlX AUTOMATION" tab in combination with the DriveConnectApp.