[version en cours de rédaction]

Version du 18 mars 2025 à 15:22

Overcoming an issue with the DS402 protocol on the AMI8121-3100-0F21 motor

Auteur Gareth Green | Dernière modification 18/03/2025 par Gareth Green en cours de rédaction ⧼frevu-button-review-label⧽

Overcoming an issue with the DS402 protocol on the AMI8121-3100-0F21 motor

Sommaire

[masquer]

1 Problem
2 Solution
- 2.1 Update EEPROM Driver
- 2.2 Commentaires

Problem

The specification of the GY and GZ motors on A2032 and A2033 included a TwinSAFE system, which makes it difficult to operate within a non-TwinSAFE environment.

Beckhoff have a solution to this, which is to use the TwinSAFE logic controller contained inside the AMI motor / drive to control its own STO "always on"

However

There is a problem with the particular spec of the AMI8121-3100-0F21 - the 2 denotes a DS402 communication interface profile. This profile needs a firmware update to enable the TwinSAFE communication.

Solution

...The safety project defined in the following steps is saved on the Software Updates board. The following steps are for reference and for recreating this project - IT DOES NOT NEED TO BE DONE EVERY TIME

The solution takes the following steps:

Ensure the TwinCAT environment is up to date
Ensure the latest ESI (device description tables) are downloaded
Ensure the latest Drive Manager 2 Installed

Update EEPROM Driver

Device
Online Tab
Right click on the AMI->Write EEProm
Pick AMI8000-0100-0018
Activate Configuration
PowerCycle the AMI Motor
Device Manager may need changing to the new type
Drive Manager needs to detect changes

en none 0

Commentaires

Draft

@@ Ligne 32 : / Ligne 32 : @@
 *Online Tab
 *Right click on the AMI->Write EEProm
-*Pick AMI8000-0100-0020
+*Pick AMI8000-0100-0018
 *Activate Configuration
 *PowerCycle the AMI Motor
 *Device Manager may need changing to the new type
-*Drive Manager needs to detect changes
+*Drive Manager needs to detect changes</translate>
-==Create the Safety Project==
-*Add new Safety Project with preconfigured Input
-*Target System - Link to safety PLC on correct axis
-*Alias Devices->Add AM891x
-*Create the safeOr in TwinSafeGroup
-*Connect back on itself as per diagram
-{{#annotatedImageLight:Fichier:Preparing a C0001401B for TwinSAFE Project OrOut.png|0=436px|hash=|jsondata=|mediaClass=Image|type=frameless|align=center|src=https://stuga.dokit.app/images/4/4f/Preparing_a_C0001401B_for_TwinSAFE_Project_OrOut.png|href=./Fichier:Preparing a C0001401B for TwinSAFE Project OrOut.png|resource=./Fichier:Preparing a C0001401B for TwinSAFE Project OrOut.png|caption=|size=436px}}
-*OrIn1 is a break contact
-*Assign the variable name AlwaysTrue to orOut
-*Change the linking mode of the AMI to "Local"
-==Variable Mapping==
-<br />{{#annotatedImageLight:Fichier:Preparing a C0001401B for TwinSAFE Project Image Variable Mapping.png|0=964px|hash=|jsondata=|mediaClass=Image|type=frameless|align=center|src=https://stuga.dokit.app/images/5/58/Preparing_a_C0001401B_for_TwinSAFE_Project_Image_Variable_Mapping.png|href=./Fichier:Preparing a C0001401B for TwinSAFE Project Image Variable Mapping.png|resource=./Fichier:Preparing a C0001401B for TwinSAFE Project Image Variable Mapping.png|caption=|size=964px}}
-*AlwaysTrue to AMI891x as diagram
-*PLC Outputs
-**bErrAck -> ErrorAcknowledgement.sds
-**bSafetyRun->Run.sds
-{{#annotatedImageLight:Fichier:Preparing a C0001401B for TwinSAFE Project Image Link to PLC.png|0=1007px|hash=|jsondata=|mediaClass=Image|type=frameless|align=center|src=https://stuga.dokit.app/images/2/25/Preparing_a_C0001401B_for_TwinSAFE_Project_Image_Link_to_PLC.png|href=./Fichier:Preparing a C0001401B for TwinSAFE Project Image Link to PLC.png|resource=./Fichier:Preparing a C0001401B for TwinSAFE Project Image Link to PLC.png|caption=|size=1007px}}
-Activate and download the safety project - remenbering the Administrator username, serial number of target and password "TwinSAFE"</translate>
 {{PageLang
 |Language=en

Preparing a C0001401B for TwinSAFE Project : Différence entre versions