[version en cours de rédaction] | [version en cours de rédaction] |
Ligne 24 : | Ligne 24 : | ||
*Ensure the latest ESI (device description tables) are downloaded | *Ensure the latest ESI (device description tables) are downloaded | ||
*Ensure the latest Drive Manager 2 Installed | *Ensure the latest Drive Manager 2 Installed | ||
− | |||
− | |||
==Update EEPROM Driver== | ==Update EEPROM Driver== | ||
Ligne 33 : | Ligne 31 : | ||
*Right click on the AMI->Write EEProm | *Right click on the AMI->Write EEProm | ||
*Pick AMI8000-0100-0018 | *Pick AMI8000-0100-0018 | ||
− | * | + | |
+ | *Allow download | ||
*PowerCycle the AMI Motor | *PowerCycle the AMI Motor | ||
− | *Device Manager may need | + | *Enter Config mode |
− | * | + | *Scan boxes ->Device Manager may need motors replacing with the new type to make the configuration identical |
+ | *Activate configuration | ||
+ | |||
+ | <br /></translate> | ||
{{PageLang | {{PageLang | ||
|Language=en | |Language=en |
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
Preparing_a_C0001401B_for_TwinSAFE_Project_Screenshot_2025-03-14_151730.jpg
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.
The solution takes the following steps:
en
none
0
Draft
Vous avez entré un nom de page invalide, avec un ou plusieurs caractères suivants :
< > @ ~ : * € £ ` + = / \ | [ ] { } ; ? #