Configuration of the AS-i functionality in ASIMON

 

The AS-i Gateway does not only enable the communication between SLC/LMC and the AS-i slaves, it may also implement control function­ality by executing the AS-i application configured with the Bihl+Wiede­mann configuration, programming, and diagnostic tool ASIMON. The use of ASIMON and the steps to adapt/develop the configuration project is not part of this documentation. Refer to the ASIMON documentation provided by Bihl+Wiedemann for information.

The user-definable mapping of safety-related AS-i data to the bits of the '8 Bytes Safe Sercos Data' device object has also to be done in ASIMON. These safety-related AS-i data are generated as follows: by means of a special, device-specific algorithm, the AS-i communication telegram of each connected safety-related AS-i slave is permuted into one safety-related data bit per AS-i slave. This safety-related data bit can be mapped to the '8 Bytes Safe Sercos Data' device object in ASIMON (see below). Standard (non-safety-related) AS-i slaves 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 AS-i slave corresponds to the input/output bit number in the '8 Bytes Safe Sercos Data' device object which is exchanged between the AS-i Gateway, SLC and LMC (via Sercos). AS-i slave 1 connected to AS-i circuit 1 is mapped to bit 1, AS-i slave 2 is mapped to bit 2, and so on.

NOTE:

Besides this straight 1:1 mapping, each user-definable mapping of AS-i 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.

Developing an ASIMON project

  1. In ASIMON, map each connected AS-i slave to the '8 Bytes Safe Sercos Data' device object. Use a straight 1:1 mapping.

  2. In ASIMON, configure the application logic.

  3. Implementing AS-i circuit diagnostics:

    If configured in ASIMON, the AS-i Gateway provides diagnostic status signals for both AS-i circuits (similar to the SafeModuleOK signal from TM5/TM7 modules). These bits indicate the status of the respective AS-i circuit and of the communication between the AS-i Gateway and the SLC, and therefore, from safety-related application perspective, the AS-i Gateway status itself.

    1. Make sure that ASIMON is setup in a way that the diagnostic status signals for the AS-i circuits 1 and 2 are generated and output.

    2. Map the diagnostic status signals for the AS-i circuits 1 and 2 in ASIMON 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 AS-i 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 AS-i slaves are considered as invalid if the circuit status signal is SAFE­FALSE. Refer to the topic "Reading and Writing AS-i Data Bits in EcoStruxure Machine Expert - Safety" for details. In particular observe the information given in section "Description of the AS-i input/output bits".

  4. Implementing enable output signals to control the AS-i output circuits:

    1. Use suitable Boolean output variables generated in the safety-related SLC application as enable output signals for each of the output AS-i circuits.

    2. Map these enable output signals to the output bits 0 and 32 of the '8 Bytes Safe Sercos Data' device object.

    3. Process the output bits 0 and 32 accordingly in the ASIMON appli­cation using logical AND combinations in a way that a slave 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 AS-i slaves may activate their outputs.

    Refer to the topic "Reading and Writing AS-i Data Bits in EcoStruxure Machine Expert - Safety" for details. In particular, observe the information given in section "Description of the AS-i input/output bits".

NOTE:

Each modification in the AS-i application results in a newly calcu­lated ConfigID value (see section below).

ConfigID in ASIMON corresponds to safety-related ConfigID parameter

Each AS-i application is verified by a unique checksum which is gener­ated in ASIMON before copying the configuration data to the AS-i Gateway and commissioning the AS-i application. In ASIMON, this checksum is called ConfigID.

NOTE:

Each modification in the AS-i application results in a newly calcu­lated 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 appli­cation loaded in the AS-i Gateway is valid and corresponds to the AS-i configuration entered in EcoStruxure Machine Expert - Safety.

You can also display the ConfigID at the AS-i 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.

EIO0000002594.01

© Copyright 2019, Schneider Electric