No more communication with axes after update to 1.8

[AndroidzZ]

I updated the core from 1.6.0 to 1.8.0, updating went well. I am trying to control 2 axes via 2 Indra drives (HSC01.1E-W0018-A-03-A-ET-EC-NN-L3-NN-FW & HSC01.1E-W0013-A-02).

the core can communicate with the drives via ethercat and also gives green check marks as normal, everything is ready for operation. When I try to rotate the axes, axis commissioning has indicated that the axes are rotating but again the drives are in mode AB and remain in mode AB, so the are not turning. It seems that the axis profile is not being forwarded properly or at all and the axes in axis commissioning are the virtual axes.

what have i tried:
* reset the axes
* Used a complete new configuration file
* Turning axes directly via the ctrlX DRIVE ( this does work )
* Turning traces on but no error whatsoever are popping up

Any idea what could cause this?
ctrlX CORE back to 1.6.0?

[CodeShepherd]

Please check first that in the version 1.8 now are units known by the motion but there is no automatic alignment to the drive or vise versa:

Did you already check your AxisProfiles?

Do you use the otion interface in the PLC? There are some small changes to do for updating to 1.8.

 

[AndroidzZ]

The drive units and axis configuration units come across. I have double checked the axis profiles and reset them once. I do use the motion interface but for this test I am not using a PLC program nor the motion interface. I am trying to run the axes via axis commissioning only at this time.

[CodeShepherd]

I already contacted you directly. We will have a look on this.

[AndroidzZ]

The solution was quite simple... Completely forgot that the axis profile must also be linked in the configuration. Thanks to

CodeShepherd for pointing that out and for the quick response!

[CodeShepherd · Accepted solution]

In a session we found that the axisprofiles were not selected in the axis configuraion: