A customer is making an application with two Axes, DriveX, Motion app, AxisInterface and Webvisu.
he is having problems with task configuration and AxisInterface initialisation.
Currently you have it configured as picture "error 1", with the 10ms FastTask task calling the AxiInterface cyclic.
The problem is that sometimes when starting the PLC or loading the program the AxisInterface does not initialise and has to do a warm reset several times (error2).
It also happens that when partially downloading the program the AxisInterface of the Axes indicates an error without the Drives are in error or the PLC, it happens during the download program (Error3).
Could it be a problem of task times, priorities or programme calls that do not initialize well?
Thanks in advance
Solved! Go to Solution.
It looks like the axes are configured correctly in the axis interface. Could you provide the error information of the TE_AxisInterfaceMainProg (ErrorID: ERROR_CODE, ErrorIdent: ERROR_STRUCT)? There is mentioned what is going wrong.
Attached image requested when the AxisInterface has not initialized.
It is strange because it does not show any error.
Anyway, the client tells me that to force the AxisInterface not to initialize, what it does is to lower the time of the task call to 4 ms. If you set it to 10ms it works correctly.
What is the recommended time for the AxisInterface task? Is it recommended to go below 10ms?
The customer is using the latest system image V1.16 and as PLC software has installed the version currently available for download in the Collaboration Room 1.16.
The software was installed 2 weeks ago.
We could not reproduce the errors as that you got. Would it possible to send me a private message with your contact data so we probably could do a meeting or share the project?