FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
- About Wsson
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About Wsson
since
12-12-2023
09-12-2024
Wsson
New Poster
6
Posts
0
Likes
0
Solutions
03-26-2024
11:47 AM
Yes, this issue was solved by upgrading to 2.4 and the topic can be closed. In my case it seems to work with COE_CALC_DRIVE. I did changed to COE_CALC_CONTROL but notice no difference.
... View more
03-12-2024
08:29 AM
Reseting the scheduler configuration using the linked methode did not solve the problem unfortunately.
... View more
03-11-2024
12:33 PM
Hello, Yes, we did a reset first, then a reboot. Then loaded the IO Config from IO engineering. Then we made a backup that we called EmptywIO. And loaded the motion config to it. Loaded EmptywIO to the core and then downloaded the PLC code from PLC engineering. We have updated our core from V1.20 to V2.4 (Using USB and reboot) We will try again with the method that you mentioned above.
... View more
03-11-2024
11:47 AM
Hello, We are having some issues when rebooting the core. We get Error on configuration. I have searched the forum and found some similare cases, but not a solution that has worked for us. The error happens some times, but not every time we restart the core and causes us to not reach operation. Note that we are using V2.4 I have activated trace for the scheduler and set the logbook to persistent before restarting the core and getting the error. We also tried to load a empty configuration, then redownload the I/O config, and loading our motion config from an archived config. Then downloading the PLC code. This did not solve the problem. Thankfull for any help on this issue!
... View more
- Tags:
- ctrlxmotion
- update
01-04-2024
02:50 PM
Hi Thanks for your reply! When we mapped the controlword within the PLC we set the Motionapp in Configurationmode. We did a trace in the Festodrive of the Controlword and Statusword. Here are the results PowerOn from MotionApp Ready for power on Controlword = 134 (Bit 1,2,7) Statusword = 33329 (Bit 0,4,5,9,15) Then we pressed "PowerOn" Controlword = 15 (Bit 0,1,2,3) Statusword = 33329 (Bit 4,5,6,9,15) The drive does not power up and Motion app throws fault after 2s, no errors in festodrive Motionapp switch the Controlword to = 6 (Bit 1,2) Statusword = 33329 (Bit 0,4,5,9,15) Then we press "Reset error" Controlword = 134 (Bit 1,2,7) Statusword = 33329 (Bit 0,4,5,9,15) Forcing the controlword from PLC Ready for power on Controlword = 134 (Bit 1,2,7) Statusword = 33329 (Bit 0,4,5,9,15) Power on Controlword = 15 (Bit 0,1,2,3) Statusword = 33331 (Bit 0,1,4,5,9,15) The drive powers on and change the statusword Statusword = 37431(Bit 0,1,2,4,5,9,12,15) So we tried to do exactly like the motionapp, but when we force the Controlword from PLC it works.... When we send 15 from PLC the answer in the statusword differs from when we send from Motionapp. Any ideas?? Regards,
... View more
Latest Tags
No tags yet
OK
OK