not enough memory for command

[CristianERuiz]

Hello collegues im having a problem in PLC program when im trying to start a continous motion the the ctrlX report me the next image

and all Cores fromCPU go to 100% of processing.

in this situacion i cant open the ethercat server and the follow screen come when this happn, just response the ctlX plc Engeneering. 

[CristianERuiz]

Adding more information i have this Core

and this drives

working under Ethercat.

and im using this Function

[CodeShepherd]

Could you please tell us which version of the system apps and specially ctrlX MOTION is used? Also ctrlX PLC Engineering and used CXA_MOTION library are interesting.

Please keep in mind that this is function and will be executed each time the PLC code will get to it. So after executing once you have to make sure it will not be again in the next cycle. Otherwise you will start it with each cycle again and load up the CPU and RAM utilisation depending on your cycle time of the PLC.

[CristianERuiz]

Hello!... its strange cuz i was using this same code with 2 Drives HCS01 ands was working perfect the application... when i exchange for the new drives starting this problems... im not in argentina now but maybe in few days ill give you that information!... ty so much for the fast answer.

[CristianERuiz]

[CodeShepherd]

I still cannot see the system apps (would be really nice to have) but only the application apps. And what I first see is that there is strange mixture of 1.12, 1.20 and also 2.02 apps. I generally suggest to use apps of the same version. And also you should use the latest released patch.

Did you check if code is called each cycle and spamming the ctrlX CORE? Could you send me your program via a private message?

In general there is no difference in the ctrlX MOTION between using HCS and ctrlX DRIVE. Did you both add via SoE? Could you add the firmware versions of the drives?

[CristianERuiz]

Sure ill send you all to private ty!

[CodeShepherd]

Just to clarify in you did not use the HCS connected to a ctrlX CORE? I guess you used a MLD solution and directly wrote to drive parameter right, is that correct? Could you a little be more describe your former setup and used commands?

In the ctrlX MOTION the command command ML_AxsVelocity is not designed to be called each cycle. But you could try using it as unbuffered command thst will overwrite old commands (see documentation).

Currently you could do a cyclic velocity commanding of the drives by hand (see this documentation) or use a cyclic position command (see this documentation).

[CristianERuiz]

Hello, yes i use the same ctrlX core... but with 2 hcs01... in this case i just exchange the 2 hcs01 for ctrx drives.

im writing this parameters every cicle

ill see the documentation ty!.

[CodeShepherd · Accepted solution]

Is there a reason, that you insert the velocity after calling the function? I would suggest to do it the other way around. And like mentioned add "buffered":

Write_Vel1.In.AxisName := 'Axis_1';
Write_Vel1.In.Velocity := r_X_Final;
Write_Vel1.In.Buffered := FALSE;
ML_AxsVelocity(Data:=Write_Vel1);

[CodeShepherd]

@CristianERuiz Are there any news? Is this still an issue? Or can this topic be closed?