Main Steps for Gateway Integration

 

The integration of AS-i Gateway devices into a Schneider Electric Embedded Safety System (e.g., PacDrive 3 application) has to be performed in the following main steps:

1. Development of the ASIMON application including

   • implementation of control functionality of the AS-i Gateway

   • mapping of AS-i data to the '8 Bytes Safe Sercos Data' device object.

   The present documentation is predicated on the best practice of a 1:1 data mapping application. This means the address of each AS-i slave corresponds to the input/output bit number in the '8 Bytes Safe Sercos Data' device object. No offset must be added to deter­mine the data bit relating to an AS-i slave. Besides this straight 1:1 mapping, each user-definable mapping of AS-i data to the data bits in the device object is possible. However, keep the mapping as clear as possible to help avoiding incorrect data assignments in the safety-related application.

   The AS-i Gateway provides one diagnostic status signal for each of its both AS-i circuits. Map these status signals to the input bits 0 and 32 of the '8 Bytes Safe Sercos Data' device object and then evaluate the bits 0 and 32 in the safety-related application. Also evaluate the SafeGatewayOK signal in the safety-related applica­tion. This signal which is also provided by the AS-i Gateway indi­cates the status of the communication between SLC and the AS-i Gateway via openSafety over Sercos.

   Moreover, provide two separate signals generated in the safety-related SLC application as enable signals for each of the output AS-i circuits. Map these enable (or release) signals to the output bits 0 and 32 of the '8 Bytes Safe Sercos Data' device object and process them accordingly in the ASIMON application. If you do not need the bits 0 and 32 then they are free to be configured for other purposes.

   Further Information

   Refer to the topic "Configuration of the AS-i functionality in ASIMON" for details.

   An AS-i application is verified by a checksum called ConfigID which is generated in ASIMON. This ConfigID has to be entered in EcoStruxure Machine Expert - Safety as safety-related 'ConfigID' parameter in the Device Parameterization Editor. Each modifica­tion of the AS-i application in ASIMON results in a new ConfigID. After having completed the project in ASIMON and commissioned the AS-i Gateway, note down the new ASIMON ConfigID.

2. In EcoStruxure Machine Expert:

   1. Add AS-i Gateway device(s) to the bus structure ('Devices' window).

   2. Insert an '8 Bytes Safe Sercos Data' device object under each added gateway node.

   3. Parameterize each AS-i Gateway device and its '8 Bytes Safe Sercos Data' device object.

   4. Assign the input/output data bits of the device object (I/O data of AS-i devices) to standard (non-safety-related) EcoStruxure Machine Expert variables, if needed. This has to be done in the 'I/O Mapping' editor of the respective device object.

   5. Optional: insert standard (non-safety-related) AS-i I/O slaves or other device objects into the EmptyModule slots under the gateway node.

   Refer to the topic "Adding/Parameterizing AS-i Devices in EcoStruxure Machine Expert" for details.

3. In EcoStruxure Machine Expert - Safety:

   Set the safety-related parameters of the integrated AS-i Gateways and their device objects. The AS-i I/O slaves cannot be parameter­ized in EcoStruxure Machine Expert - Safety.

   Refer to the topic "Parameterizing AS-i I/O slaves in EcoStruxure Machine Expert - Safety" for details.

4. In EcoStruxure Machine Expert - Safety:

   Use the input/output bits provided by the device object in the safety-related application. At least one input or output has to be used in the safety-related application to be able to compile the project.

   • Read and evaluate the SafeGatewayOK status signal coming from the AS-i Gateway which indicates the status of the communication between SLC and AS-i Gateway.

   • Read and evaluate the diagnostic status signals for the AS-i circuits 1 and 2 of the AS-i Gateway mapped to the bits 0 and 32 of the '8 Bytes Safe Sercos Data' device object.

   • Generate and write one separate signal as enable signal for each of the output AS-i circuits (mapped to the output bits 0 and 32 of the '8 Bytes Safe Sercos Data' device object).

   • Read the input bits (status of AS-i sensors), or other safety-related data and evaluate them in the safety-related application.

   • Write the output bits (control of AS-i actuators) in the safety-related logic depending on the evaluated status information.