Runtime Commands execution speed / Load Home Counter

5 years 7 months ago #29529995 by Herman
I tried to set the speed with !S 1 1000 or !S 1000 but nothing happens.
The controller acknowledge the command but the motor speed is not set. With !G the motor runs.

The manual says that !S is only accepted in closed loop position relative and count position mode. I have the controller in closed loop speed mode


So to answer your question: I get different behaviour, I cannot control the speed with !S


Still having the "short spinning" problem, I will do experiments to determine what command in the sequence causes the motor to spin shortly.

Or you must have a brilliant idea, that would be nice


Herman

Please Log in or Create an account to join the conversation.

5 years 7 months ago #29529997 by TechSupport
The !S is for speed mode as a motor command. In the position mode relative, the !S will change the value of the velocity parameter which will have a change in behavior. Which firmware are you using? The latest should be 11/21/14

Please Log in or Create an account to join the conversation.

5 years 7 months ago #29530000 by Herman
I think I have a 2013 firmware version, I will update it tonight

My application uses speed mode:

I don't understand why I should test with S! as it is for speed mode as a the motor command. ?

Please Log in or Create an account to join the conversation.

5 years 7 months ago #29530001 by TechSupport
You can use the !G command as you see fit. I figured if you were trying to tell a motor to go a a specific speed using the speed mode, you would like to be able to drive that speed a command using the !S rather than trying to guess a speed command using the !G.

Please Log in or Create an account to join the conversation.

5 years 7 months ago #29530002 by Herman
I read your answer several times but I don't understand what it has to do with my initial problem.

Please Log in or Create an account to join the conversation.

5 years 7 months ago #29530003 by TechSupport
Both commands should tell the motor to not move. Therefore if the !S 1 0 after going from the open loop to closed move causes the motor to do nothing, then that tells you that the !G is somehow causing the problem. Both in a sense when you go from open loop mode, send !G 1 0 and then reset counter, and go to closed loop mode, the motor should be at rest. When you said after going back to closed loop mode and sending the !G 1 0 and the motor moves, then in a sense you should possibly see the problem occur with the !S command. If it doesn't have the same behavior, then there is a problem.
The following user(s) said Thank You: Herman

Please Log in or Create an account to join the conversation.

Moderators: tonysantoni
Time to create page: 0.100 seconds