About giustola69

giustola69 · ‎03-20-2023

Hi, in attached file you'll find a guide relative to a test we did connection out C15 to a Profisafe PLC ( our MLC safelogic in the test ) to control via the SafeLink bus our CtrlX safety motion functions. I hope it will usefull to somebody else. This document describes how to connect to a Profisafe PLC a C15. At this purpose the test was performed using a SafeLogic safety plc functional module mounted on an MLC75 as simulation of what could be a possible connection with a Siemens Profisafe PLC The purpose of the test is to verify the operation and communication between a Profisafe machine safety PLC, for example Siemens, and our C15 safety PLC, this in order to provide a possible configuration of use of the Safety Motion functions of our CtrlX drive through precisely the use of a C15 safety PLC this to remedy the current absence of the Profisafe protocol within the CtrlX using the SafetyLink connection from C15 to the drives and the Profisafe connection between the C15 and the machine safety plc

giustola69 · ‎03-14-2023

Hi, I found it in the C15 firmware zip file . Many Thanks Giuseppe

giustola69 · ‎03-14-2023

Hi, where could I download the C15 GSDML configuration file to confiure the safety control with a Profisafe Siemens master or with our XM Safelogic ?? Many Thanks Giuseppe

giustola69 · ‎02-27-2023

Hi, is thers any way to delete the drive residual path from CtrlX core immediatelly ? What we need is a command to set the drive commanded position = to the drive feedback position immediately when a following error has been accumulated. In my opinion this job should be performed automatically by the FB MC_Stop: after an MC_Stop execution the axis should not move until a new command is performed. Up to now if the drive has a residual path with a following error generated using the C1300 procedure, the axis moves even after a MC_STOP command Many Thanks Giuseppe

giustola69 · ‎02-24-2023

Hi, I'm using a Move_Absolute FB and the C1300 commad togheter to avoid the eccessive deviation because the assi stop on a machanical point while moving ( is a tapper ) and whe the torque reach the tapper value the axis shoud stop and delete the following error whiout moving. We did a lot of this application wiht MLC/XM and Indradrive and using the MC_Stop the axis went is stopping mode and releasing the stop command in AH ( according to the PlcOpen machine state rules ). Now with Ctrlx seems that that behavior has changed. So Ho could we delete the following error if the MC_Stop is non working anymore ? As I said we found two workaroud but we wanted to be sure that hese are the right ways of doing the job now with CtrlX core and drive. Regards, Giuseppe

About giustola69

C15 Profisafe -> SafeLink -> SafetyMotion settings example

Re: C15 GSDML Profinet Configuration file

C15 GSDML Profinet Configuration file

Re: Axis residual commad position path (following err )not deleted after MC_STOP and axis ...

Re: Axis residual commad position path (following err )not deleted after MC_STOP and axis ...