From ed84fa26e3fbedba8eca6873e3ef7e8375569bf8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Anders=20Sandstr=C3=B6m?= Date: Wed, 28 Feb 2024 13:47:17 +0100 Subject: [PATCH] Rename addAxisToGroup.cmd to addAxisToSafetyGroup.cmd WIP --- README.md | 30 +++++++++++++------ ...isToGroup.cmd => addAxisToSafetyGroup.cmd} | 0 2 files changed, 21 insertions(+), 9 deletions(-) rename scripts/{addAxisToGroup.cmd => addAxisToSafetyGroup.cmd} (100%) diff --git a/README.md b/README.md index fc6a7f7..bed2599 100644 --- a/README.md +++ b/README.md @@ -22,8 +22,8 @@ Basically the safey system is interfaced with two binary signals (ethercat I/O): If, for instance, an safety event is triggerd by the safety system, it will immediately command this plugin to rampdown velocity of all axes (that a configured to stop). When all axes, that are configured to rampdown, have stopped then this plugin will disable the axes and set an ethercat output informing the safety system that the axes are standstill. After a certain timout the safety system will make sure power is removed from the motion axes by triggering an STO or removing power. The removal of power or triggering of STO will made regardless if the axes are at rest or not. A reset of the safety system, allowing power to the drives, will only be possible once the safety system gets a confirmation that all axes are at rest. The configuration is made by two commands: -1. ecmcAddSS1SafetyGroup() -2. ecmcAddAxisToSafetyGroup() +1. ecmcAddSS1SafetyGroup() wrapped into addSS1Group.cmd +2. ecmcAddAxisToSafetyGroup() wrapped in snippet addAxisToSafetyGroup.cmd ## ecmcAddSS1SafetyGroup() @@ -38,9 +38,22 @@ ecmcAddSS1SafetyGroup(, , ,