Showing results for 
Search instead for 
Did you mean: 

CtrlX Motion Scaling information

CtrlX Motion Scaling information


Hi, when I configure the ACS2 axis with CtrlX Motion CoE Communication, I have to manually change the profile scaling information in the data layer and I have to change the information again every time I configure it, can it be mapped automatically?




Community Moderator
Community Moderator

To specify your problem, you add one ACS2 axis and configure it. Now you add another one an like that it is automatically configured? This is not possible as our system does not know which sort of 3rd party drive is connected and how it should be set up.

In the CiA402 standard there can be an object added to the drive (must be done by supplier) so that control can read out the necessary information with the strategy "COE_CALC_DRIVE". That is e.g. the case for crlX DRIVE.

I Configure one ACS2 axis, and Configure another, after mapping data in the axisProfile, switch to “running” mode. then I get tow axes error as below:



then, I open datalayer Axisprofile, and find both axes scalling information are:


and I need to change "strategy" "COE_CALC_DRIVE" to "COE_CALC_CONTROL",  "scalingType" "UNDEFINED" to "LINEAR" or "ROTARY", and "numerator", "denominator", "resolution" need to modified as actual situation. after these modification, refresh Core UI, then I could switch UI to "RUNNING" mode successful.

The question is I have to change these scalling information manually everytime, when I configure axis again, or when I download devices to core from IO Engineering.

Does the scalling information could mapping with device automatically, or I could configure them as attribute value in UI?





Community Moderator
Community Moderator

You have to insert this value once in each axisprofile you are creating in the ctrlX CORE web UI. Independent of inserting drives in the IO configuration or updating it. The connection to the drive is done via the EtherCat address and the parameter mapping also done in the axisprofile.

Beware of storing the configuration to make it persistent after reboot:

ctrlX CORE web UI data layer viewer save axisprofile configurationctrlX CORE web UI data layer viewer save axisprofile configuration