SoMachine\CoDeSys motion question

Hopefully I can articulate this correctly. I'm using SoMachine from Schneider but hopefully this translates to anyone that can help me.

I'm trying to have a motor follow an analog signal from a Banner laser distance marker for feedback. Using the motion function block "MC_MoveVelocity" the motor will indeed run at the integer from the laser but it not execute the block again until the "execute" input of the function block is toggled again on the raising edge. So if this laser integer value changes the motor will not immediately follow the laser until you toggle the input again.

This is silly to me mostly because I'm an analog guy

Should I put a "Blink" or "Oscillator" input onto the execute input to just toggle the input at an insane speed?

There is an bool output of the block that gives an indication that the input speed has been met. Is there some sort of compare from this I can drive the execute input?

Being new to this and by myself I'm getting more confused and getting scatter brained the more I think about it. I can make it work I'm sure but what is the normal practice?

I am using a GE RX3i PAC Motion module and using an MC_MoveVelocity command which receives the target velocity from a PID instruction and in order to make it adjust the velocity on the fly, I do exactly what you mentioned and use a .1 sec timer to enable/disable the MC_MoveVelocity command. I suspect that you will probably need to do this to lock in the new target velocity.

Regards

KP_EENG said:

I do exactly what you mentioned and use a .1 sec timer to enable/disable the MC_MoveVelocity command.
Regards

Click to expand...

I checked my code this morning and I am actually updating the MC_MoveVelocity Commanded velocity every 10 mS, not every 100 mS as I mentioned in the previous post.

Sorry

KP_EENG said:

I checked my code this morning and I am actually updating the MC_MoveVelocity Commanded velocity every 10 mS, not every 100 mS as I mentioned in the previous post.

Sorry

Click to expand...

No problem and thanks for the input. I'm using a blink function to drive it now like yourself. You'd think there would be a more real time motor control...

If you are using the same platform as me what is the syntax for the time of the block? The help file is worthless and if I use .010 I get compile errors. I've also tried t#010 and other stuff like that and it still hates me.

Thanks for the help.

You may use velocity setpoint compare
MC_MoveVelocity.exe := CurrentVeloSetpoint <> MemoryVeloSetpoint;
MC_MoveVelocity();
MemoryVeloSetpoint := CurrentVeloSetpoint;

Every time your velocity setpoint change, your execute will be trigger.

I've also tried t#010

Click to expand...

try the iec time format t#10ms