Thank you!
Below is code for servo driven press section of machine.
The program doesn't have a MAM anywhere to be found. Coincidentally, the 19 parameters between ( ) are the same number (19) as a MAM instruction.
MOV on the other hand oly has (10 parameters)?
This press moves two servos at once A416 and A416.
I omitted A416 at the bottom (duplicate of Positioner A415)
// PRESSORI MOTORIZZATI //
MOV_GUIDE(A415_MoveGuide,CICLO_PRESSORE1mot,A415_Posizionamento_ok,A415_Errore,Marcia_Assi,RESET_ASSI,TIME_CLOCK,Errore_Guide_PRESSmot1,A415_Start,A415_MoveGuideDurata);
MOV_GUIDE(A416_MoveGuide,CICLO_PRESSORE2mot,A416_Posizionamento_ok,A416_Errore,Marcia_Assi,RESET_ASSI,TIME_CLOCK,Errore_Guide_PRESSmot2,A416_Start,A416_MoveGuideDurata);
Positioner(A415_Motion,
A415Axis,
A415_TARGET_POS,
A415_LIM_MIN,
A415_LIM_MAX,
0,
A415_Start,
RESET_ASSI,
Immediate_ESTOP_F,
Delayed_ESTOP_F,
0,
A415_Velocity,
A415_Acc,
A415_Dec,
A415_Posizionamento_ok,
A415_Homed,
A415_Locked,
A415_Errore,
A415_ErrCode);
No one answered this so I will and as I noted I know very little RSLogix..anything.
I think this needs knowledge of RSLogix5000 platform, RSLogix motion control and Structured Text in general. Why I think that:
Whatever that "Positioner" is should've been recognized by your right away if you are familiar with the platform,ADD_ON meaning it is either a call to routine (sub routine or whatever it is called) or it maybe some motion control datatype which would've bee declared as a tag/variable somewhere or actual native instruction (I couldn't find it).
Since this is way beyond me I will answer your original post with links that I think should be helpful:
Motion control video tutorials (look for RSLogix ones in the list)
RSLogix structured text.
RSLogix motion control instructions.
Structured text video tutorial (way too basic but search their playlist they may just have more.
The instructions should look same whether in LADDER or ST, that is the instruction will have the same input, output and Input_Output formal parameters whether in ST or LADDER, the difference is in LADDER it is graphical and in ST it is not so much, they are between parenthesis. In other platforms we get context help to show us the parameters as we are typing them in and if we do not provide all the *required* parameters the compiler would produce and error.
Again depending on the platform (I think) I may have to write the formal parameter name then assign a tag to it, I can not just list the tag in between the parenthesis, and in any case it is good practice to do so even though it stretches the code quite a bit.
So the call would like MAM(Axis:=myAxis, MotionControl:=myMOT_CTRL, MoveType:=diMove_Type, Position:=myRealPosition,*****etc all the way to the end);
Outputs are assigned this way (myTag => Formal_Parameter)
It is quite the learning curve so take your time is the quickest way to get where you want.
