I have a problem with axis profile. I use CANopen over Ethercat stepper drivers. I encountered no difficulties in defining the axis. When defining the signals, I have entered the minimum requirements for the profile to be defined.
Unfortunately after trying to start my axis throws an error which can be seen in the picture below.
When checking the Data layer, I noticed that the data in the scaling-information is not correct, and I tried several times to enter the correct data, but without success. Every time I make some corrections and write them, it shows me a message that the new data has been saved and after the message disappears, the corrected data goes back to its previous state.
Bifore add data:
After add data:
I try to download also the configuration file, to adjust these parameters and upload it again. But without success.
Can you tell me how I can change this data?
Solved! Go to Solution.
Seems that there is something wrong with your axisprofile json
the last entries should be like this
You can try to write this in your json or delete the axis profile and add it again.
Unfortunately, I'm still struggling to get rid of the error I get when launching the Motion app. I also asked other colleagues for assistance, but to no avail. No one can tell me why I get this error. Entercat is working as I can see through CtrlX Engineering that I have signal exchange, I even managed to manually enable the motor, but in CtrlX Core it doesn't see the motor driver and there is no signal exchange, which is very strange. Unfortunately, I'm not very familiar with CtrlX Core, and due to the lack of information, what exactly is the problem with the axis profile, I don't know what to do to start a motion app (it will be much easier for me to write the program later)
Hello, i tried CoE with my testset (but only IndraDrive with CoE) an this is working.
In my case i had to change the scaling strategy to COE_CALC_DRIVE and scalingType ROTARY in my JSON for the axisprofile.
If you have still problems
- set the traces for axisprofile (as decribed from Linhan)
-try to switch the axisprofile to running
-if you run into your problem generate a system report and add it here
Hi, the axisprofile tries to read out the drive operation mode (first line)
Is it possible that there is a problem with the parameters of your drive, especially the operation mode?
|Name: Profile_1; Type: CoE; Addr: 1001; current drive operation mode: Unknown, which is not supported|
|Name: Profile_1; Type: CoE; Addr: 1001; CoE-Read (SYNC): Object Index=6060dh, SubIndex = 0000dh, Address: fieldbuses/ethercat/master/instances/ethercatmaster/device_access/coe/sdo|
|Name: Profile_1; Type: CoE; Addr: 1001; New acceleration data scaling LSB weight = 1.000000|
|Name: Profile_1; Type: CoE; Addr: 1001; New torque data scaling LSB weight = 1.000000|
Name: Profile_1; Type: CoE; Addr: 1001; New velocity data scaling LSB weight = 1.00000
In my IndraDrive there is a startup parameter configured
Can you check if in your device a parameter like this exists?
Or add the configuration of your project (inlc. IO-Project).
Hi, please trying the set blow:
1. As Linhan said above, plese don't mapping the item other than status-/control word, position. Because the PDOs in red box are currently not available for CoE profile:
2. According to the trace error, the error is clearly points to that the operation mode is unknow, currently, only operation mode 8(Cyclic sync position mode) is available for CoE profile, therefore, the operation mode should be 8, as the red box(0x6061) in the figure blow:
The 0x6060 could be set here:
After set the value as 8 here, download to ctrlX Core is also necessary(red box). But I suggest to set in drive software.
3. I checked the IO configuration, because I don't have the hardware, so only part information are available for me:
The receive PDO2 - 4 and transmit PDO 2 looks strange on my side. Please try to create a new IO project for configuration and please do not add PDOs other than status-/control word, position.
4. Another tip is: Axisprofile does not supports profile type change after profile has been created. So please always select CANopen_over_Ethercat, if you need a CoE profile.
The parameters in figure above also needs to modify, but it may not leads to booting error in motion.
I tried the step by step instruction you suggested but without any result.
The situation is the same.
Ethercat is working as I check it.
I did an experiment and got another servo controller from a colleague that I'm sure works with CtrlX Core and wired it to my system. It turned out that the result is the same, which makes me think that the problem is with the Motion app, and not with the servo driver I'm using. I HAVE A QUESTION. Will resetting my CtrlX Core to factory settings fix it? The other option is to upgrade to a higher version.
Thanks to Michael_A Problem solved.
It turned out to be a bad installation of the Motion app - for some reason all the tools didn't load, which is why the Motion app didn't start at all.
We uninstalled the app and reinstalled it until the installation was done correctly and all the tools were loaded.
Thanks again to Michael_A for his assistance.