Term definition: In the following, the term 'x Bytes Safe Sercos Data' designates both, the 8 and 12 bytes object, depending on the gateway type. (x = 8 for the BWU2984 and x = 12 for the ASi-5/ASi-3 Gateway.)
The ASi Gateway does not only enable the communication between SLC/LMC and the ASi devices, it may also implement control functionality by executing the ASi application configured with the Bihl+Wiedemann configuration, programming, and diagnostic tool ASIMON360. The use of ASIMON360 and the steps to adapt/develop the configuration project is not part of this documentation. Refer to the ASIMON360 documentation provided by Bihl+Wiedemann for information.
The user-definable mapping of safety-related ASi data to the bits of the 'x Bytes Safe Sercos Data' device object has also to be done in ASIMON360. These safety-related ASi data are generated as follows: by means of a special, device-specific algorithm, the ASi communication telegram of each connected safety-related ASi device is permuted into one safety-related data bit per ASi device. This safety-related data bit can be mapped to the 'x Bytes Safe Sercos Data' device object in ASIMON360 (see below). Standard (non-safety-related) ASi devices cannot be mapped to the device object.
The present documentation is predicated on the best practice of a 1:1 data mapping application. This means, the address of an ASi device corresponds to the input/output bit number in the 'x Bytes Safe Sercos Data' device object which is exchanged between the ASi Gateway, SLC and LMC (via Sercos). ASi device 1 connected to ASi circuit 1 is mapped to bit 1, ASi device 2 is mapped to bit 2, and so on.
Besides this straight 1:1 mapping, each user-definable mapping of ASi data to the 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 following applies to the '8 Bytes Safe Sercos Data' device object (that is to say, for the BWU2984 ASi-3 Gateway). For the ASi-5/ASi-3 Gateway with its '12 Bytes Safe Sercos Data' device object, other values for the device object size, bit numbers etc. apply accordingly.
In ASIMON360, map each connected ASi device to the '8 Bytes Safe Sercos Data' device object. Use a straight 1:1 mapping.
In ASIMON360, configure the application logic.
Implementing ASi circuit diagnostics:
If configured in ASIMON360, the ASi Gateway provides diagnostic status signals for both ASi circuits (similar to the SafeModuleOK signal from TM5/TM7 modules). These bits indicate the status of the respective ASi circuit and of the communication between the ASi Gateway and the SLC, and therefore, from safety-related application perspective, the ASi Gateway status itself.
Make sure that ASIMON360 is setup in a way that the diagnostic status signals for the ASi circuits 1 and 2 are generated and output.
Map the diagnostic status signals for the ASi circuits 1 and 2 in ASIMON360 to the input bits 0 and 32 of the '8 Bytes Safe Sercos Data' device object. Input data bit 0 then represents the status of ASi circuit 1, and input bit 32 represents circuit 2.
When developing the safety-related SLC application in EcoStruxure Machine Expert™ – Safety, you have to evaluate the input bits 0 and 32 in a way that the signals coming from the ASi devices are considered as invalid if the circuit status signal is SAFEFALSE. Refer to the topic "Reading and Writing ASi Data Bits in EcoStruxure Machine Expert™ – Safety" for details. In particular observe the information given in section "Description of the ASi input/output bits".
Implementing enable output signals to control the ASi output circuits:
Use suitable Boolean output variables generated in the safety-related SLC application as enable output signals for each of the output ASi circuits.
Map these enable output signals to the output bits 0 and 32 of the '8 Bytes Safe Sercos Data' device object.
Process the output bits 0 and 32 accordingly in the ASIMON360 application using logical AND combinations in a way that a device may only activate its output if the enable signal is SAFETRUE.
In doing so, the output bits 0 and 32 of the '8 Bytes Safe Sercos Data' device object can be used for enabling the circuits 1 and 2 (similar to the ReleaseOutput signal known from TM5/TM7 modules). Setting an enable bit to SAFETRUE means that the related ASi devices may activate their outputs.
Refer to the topic "Reading and Writing ASi Data Bits in EcoStruxure Machine Expert™ – Safety" for details. In particular, observe the information given in section "Description of the ASi input/output bits".
Each modification in the ASi application results in a newly calculated ConfigID value (see section below).
Each ASi application is verified by a unique checksum which is generated in ASIMON360 before copying the configuration data to the ASi Gateway and commissioning the ASi application. In ASIMON360, this checksum is called ConfigID.
Each modification in the ASi application results in a newly calculated unique ConfigID.
In EcoStruxure Machine Expert™ – Safety, this ConfigID has to be entered as safety-related 'ConfigID' parameter in the Device Parameterization Editor. This checksum is used to verify that the configuration and application loaded in the ASi Gateway is valid and corresponds to the ASi configuration entered in EcoStruxure Machine Expert™ – Safety.
Refer to the ASIMON360 documentation, how to determine the ConfigID checksum value.
(Also observe the possibility of displaying the ConfigID at the device as described below.)
Note down the ConfigID generated by ASIMON360. It has to be entered as 'ConfigID' parameter in EcoStruxure Machine Expert™ – Safety.
You can also display the ConfigID at the ASi Gateway device. Press the 'OK' button at the device to enter the menu and select 'Safety > Safe Sercos > Config IDs (Node and Manager)' to display the ConfigID.
The 'Node' entry on the displayed screen outputs the ConfigID configured on the ASi Gateway device.
The 'Manager' entry displays the ConfigID which is entered in the safety-related device ASi Gateway parameters in EcoStruxure Machine Expert™ – Safety.
If the value is 0, either no communication connection is established between EcoStruxure Machine Expert™ – Safety and the ASi Gateway, or communications will be unsuccessful because of the invalid ConfigID.