Related Wrike task: Add legal disclamer to automated SMM configuration https://github.com/synapticon/motion-master-client-examples/blob/main/src/fp/configure-smm.ts
User Story
As a developer,
I want all scripts that configure SMM to include the legal disclaimer provided by the SMM team,
so that users are reminded that every safety function must be verified after configuration and our team is legally protected.
Acceptance Criteria
Disclaimer
⚠️ WARNING: SAFETY-CRITICAL APPLICATION & MANDATORY COMPLIANCE
-
SCOPE OF AUTOMATION: This script is designed to automate the parameterization of Safe Motion Module. Use of this script is strictly limited to configurations where a known, valid configuration (.csv) is already available.
-
MANDATORY CHECKLIST ADHERENCE: Execution of this script does NOT bypass the requirements outlined in the “Commissioning of Joints with Known Safety Configuration” checklist. The user must ensure all physical prerequisites are met, including:
- Correct mechanical mounting per IEC 61800-5-2:2016.
- Proper encoder calibration.
- Verification that the FSoE Watchdog is correctly configured on the FSoE Master.
-
VALIDATION OF LIMITS & REACTIONS: As per standard operating procedure, the safety configuration must be manually checked by intentionally violating limits to trigger and verify the expected reaction. If safe torque values are used, they must be validated by applying specific torque and verifying the reported data.
-
SYSTEM-WIDE FUNCTIONAL TEST: Automation of individual drive parameters does not validate the safety of the machine. The user is legally required to validate the safety functions of the entire system by triggering every implemented safety function, including establishing a process for repeated testing of STO/SBC functions.
-
LIABILITY & ARCHIVING: The developer is not liable for configurations that produce violations during regular operation; safety margins must be manually adjusted. Upon completion, the user MUST export and archive the safety parameter report along with the commissioning checklists.
BY EXECUTING THIS SCRIPT, YOU ACKNOWLEDGE THAT YOU HAVE COMPLETED ALL PRE-COMMISSIONING STEPS AND WILL PERFORM ALL POST-COMMISSIONING VALIDATION TESTS LISTED IN THE PROJECT CHECKLIST.
Related Wrike task: Add legal disclamer to automated SMM configuration https://github.com/synapticon/motion-master-client-examples/blob/main/src/fp/configure-smm.ts
User Story
As a developer,
I want all scripts that configure SMM to include the legal disclaimer provided by the SMM team,
so that users are reminded that every safety function must be verified after configuration and our team is legally protected.
Acceptance Criteria
Disclaimer
SCOPE OF AUTOMATION: This script is designed to automate the parameterization of Safe Motion Module. Use of this script is strictly limited to configurations where a known, valid configuration (.csv) is already available.
MANDATORY CHECKLIST ADHERENCE: Execution of this script does NOT bypass the requirements outlined in the “Commissioning of Joints with Known Safety Configuration” checklist. The user must ensure all physical prerequisites are met, including:
VALIDATION OF LIMITS & REACTIONS: As per standard operating procedure, the safety configuration must be manually checked by intentionally violating limits to trigger and verify the expected reaction. If safe torque values are used, they must be validated by applying specific torque and verifying the reported data.
SYSTEM-WIDE FUNCTIONAL TEST: Automation of individual drive parameters does not validate the safety of the machine. The user is legally required to validate the safety functions of the entire system by triggering every implemented safety function, including establishing a process for repeated testing of STO/SBC functions.
LIABILITY & ARCHIVING: The developer is not liable for configurations that produce violations during regular operation; safety margins must be manually adjusted. Upon completion, the user MUST export and archive the safety parameter report along with the commissioning checklists.
BY EXECUTING THIS SCRIPT, YOU ACKNOWLEDGE THAT YOU HAVE COMPLETED ALL PRE-COMMISSIONING STEPS AND WILL PERFORM ALL POST-COMMISSIONING VALIDATION TESTS LISTED IN THE PROJECT CHECKLIST.