About tommorassini

This fixed the problem for me.  Thank you!! ... View more

I'm having the same problem as reported here.  My symptoms seemed to be exactly the same as bclapperton.  I had first followed the document posted by JordiLaboria.  I had a red triangle by the axis (see below). But then followed the other link explaining the setup of the Task in the Scheduler.  After setting up the Scheduler the red triangle has gone away although I'm not sure I completely set it up correctly as I don't see what I entered displayed anywere, plus it seemed to error the first time I tried it??? Unfortunately I still can't get it to work as the MC_Power Function Block still shows "Busy" as bclapperton has posted. I feel like something is missing.  I don't see one consise explanation of all the steps needed to get this to work. I haven't seen anywere talking about the Rexroth Motion App.  My control originally had this setup along with the Axes with the Profiles set up.  I assumed this could cause some conflicts so at first I removed the Axes and then Uninstalled the Motion App.  I'm assuming we don't need the Rexroth Motion App???     ... View more

I just ran into this issue too.   Can settings like this please be left alone and stop changing things trying to assume what someone may or may not want!!!   ... View more

I haven't tried an Asynchronous motor without Encoder, but I have been successful running a drive with only Velocity Mode using the PLC Program by manually writing to S-0-0036.  In this case there was no need to use the Motion App (meaning no need to set it up in the web interface).  The key as pointed out with the Startup Parameters is to redefine or remove the S-0-0032 value since it's set for Position Mode Lagless as stated. If you don't redefine S-0-0032 or remove it from the list every time the drive transitions to OM S-0-0032 will switch back to Position Mode. I'm not sure of a further limitation regarding an Encoder otherwise that wouldn't allow you to run an Asynch motor without feedback.     ... View more

I reported this issue a while back.  The issue was confirmed and was to be fixed in RM21.11 at least for ctrlX DRIVE.  I did request it to be fixed for IndraDrive too, but don't know what if anything was done for either drive. I believe the issue is due to the C0600 Command taking over the Position Control and once finished it turns it back over ot the ctrlX CORE.  So the CORE last had the prior Position Command value from before the C0600 Command and when it gets control back after C0600 completes it wants to instantly repopulate the Position Command with the old position hence the big jump which causes the error. ... View more