Adding/Parameterizing AS-i Gateways in EcoStruxure Machine Expert

 

This topic describes how to add AS-i Gateway devices to the bus struc­ture in EcoStruxure Machine Expert and parameterize them. It contains the following information:

• Preparations

• Adding an AS-i Gateway and inserting the '8 Bytes Safe Sercos Data' device object

• Parameterizing the AS-i Gateways

• Mapping AS-i I/O safety-related data to standard (non-safety-related) variables (mirrored bits)

• Download of parameterization data to the AS-i Gateway

Preparations for integrating the AS-i Gateway

For the described integration procedure, the following should apply to your EcoStruxure Machine Expert application project:

• A Safety Logic Controller is already inserted in the Devices tree.

  Example:

  

• The IP addresses of LMC and SLC are set in the respective 'Parameters' editor (section 'General' for the LMC and section 'Identification' for the SLC).

• The value 'LMC2SLCNumberOfBOOLs' is set to '8 Bool / 1' in the 'IO Configuration' section of the SLC 'Parameters'. This value defines the non-safety-related communication between standard (non-safety-related) LMC controller and safety-related SLC. It defines the number of Boolean data items that are transferred between LMC and SLC. In EcoStruxure Machine Expert - Safety, each of these Boolean data items will be available as standard input signal under the SLC node in the 'Devices' window.

  Example

  

• Communication between LMC and SLC via the Sercos bus has been successfully established.

Adding an AS-i Gateway and inserting the '8 Bytes Safe Sercos Data' device object

Assuming that the preparations mentioned above are done, proceed as follows:

1. Add an AS-i Gateway.

   1. In the 'Devices' tree, right-click 'SercosIII (Sercos Master)' and select 'Add Device...' from the contextual menu.

      (Alternative: use 'Insert device...'. Refer to the EcoStruxure Machine Expert online help for details.)

   2. In the 'Add Device' dialog, select 'Bihl+Wiedemann' from the 'Vendor' drop-down list.

      Select the 'AS-i/Sercos III Gateway'.

      (Select the correct device version. Select the 'Display all version' checkbox, if necessary.)

   3. Click the 'Add Device' button to confirm the selection and insert the AS-i Gateway device into the 'Devices' tree.

      Close the 'Add Device' dialog.

   The AS-i Gateway is now visible under the Sercos_Master node in the tree like a usual Sercos bus device.

   The gateway node contains:

   • One slot referred to as 'No_Safety_Data' into which the '8 Bytes Safe Sercos Data' device object must be inserted. This device object represents the safety-related extension of the Bihl+Wiede­mann system and will be used in the PacDrive 3 system to access the input/output data bits read from/written to the AS-i Gateway. See section "AS-i/Sercos Data Exchange..." for details.

   • 30 'EmptyModule' slots for inserting standard (non-safety-related) AS-i slaves. The 'Empty_Module' slots are not for safety-related AS-i slaves. See step 5 in this procedure.

   Example:

   

2. Insert the '8 Bytes Safe Sercos Data' device object

   1. Right-click the 'No_Safety_Data' node and select 'Plug Device...' from the contextual menu.

   2. In the 'Plug Device' dialog, select 'Bihl+Wiedemann GmbH' from the 'Vendor' drop-down list.

      Select the entry '8 Bytes Safe Sercos Data'.

      (Make sure that the correct device version is selected for insertion. Select the 'Display all version' checkbox, if necessary.)

   3. Click the 'Plug Device' button to confirm the selection and insert the device object into the 'Devices' tree.

      Close the 'Plug Device' dialog.

   The node is renamed to '8 Bytes Safe Sercos Data'. This device object is handled like a safety-related 64 bit I/O module, inde­pendently of what AS-i data are mapped to it.

   Result of the insertion of the '8 Bytes Safe Sercos Data' device object...

   • ... in the EcoStruxure Machine Expert - Safety project: the AS-i Gateway is integrated into the list of safety-related devices. The data bits provided by the device object are then available as safety-related input and output bits. These bits can be inserted into the safety-related application.

   • ... in the EcoStruxure Machine Expert project: these bits are avail­able as mirrored bits of the safety-related data bits with read-only access. They are represented as 8*8 bytes input data and 8*8 bytes output data. By mapping these mirrored bits to standard (non-safety-related) variables in the standard application, the LMC is informed about the safety-related operations of the SLC and the AS-i Gateway. See section "Mapping AS-i I/O safety-related data to standard (non-safety-related) variables (mirrored bits)" for an example.

3. Parameterize the AS-i Gateway device and the '8 Bytes Safe Sercos Data' device object as described in the procedure below.

4. In EcoStruxure Machine Expert, you can map the AS-i input/output bits (mirrored bits) to standard (non-safety-related) variables as described below.

5. Optional: insert standard (non-safety-related) AS-i I/O slaves or other device objects into the empty module slots. Refer to the section "Integrating standard AS-i slaves" for details.

   NOTE:

   Do not use the communication telegram bits of safety-related slaves in EcoStruxure Machine Expert.

   According to the AS-i standard, AS-i slaves communicate using tele­grams composed of 4 bits of user data. Safety-related AS-i slaves only use one data bit which is derived from the AS-i telegram (4 bits) by means of a special, device-specific algorithm. This resulting (safety-related) data bit can be mapped to the '8 Bytes Safe Sercos Data' device object and is available as mirrored bit in the standard (non-safety-related) application.

   Nevertheless, all 4 bits of a safety-related slave are visible in the I/O Mapping table in EcoStruxure Machine Expert. Do not use these 4 tele­gram bits of safety-related AS-i slaves in the slave I/O Mapping because none of these single bits represents the derived safety-related bit mentioned above. Instead, only use the data bit of the safety-related slave which is available as mirrored bit in the '8 Bytes Safe Sercos Data' device object.

   WARNING

   UNINTENDED EQUIPMENT OPERATION

   Do not use the 4 bits of the safety-related communication telegram for any other purposes in your application.

   Failure to follow these instructions can result in death, serious injury or equipment damage.

Parameterizing the AS-i Gateways

Set the Sercos parameters of the AS-i Gateway as follows:

1. In the EcoStruxure Machine Expert 'Devices' tree, double-click the AS-i Gateway device to be parameterized.

   The editors of the device are opened in the editors area.

2. Click the 'Sercos III Parameters' editor.

3. Expand the structure in the editor grid and locate the parameters to be set.

4. Double-click into a 'Value' field to be edited and enter a value or, if applicable, select one after clicking the browse button '...'.

Then, parameterize the device object '8 Bytes Safe Sercos Data' as follows:

1. In the EcoStruxure Machine Expert 'Devices' tree, double-click the '8 Bytes Safe Sercos Data' device object.

   The editors of the device are opened in the editors area.

2. Click the 'Sercos Module I/O Mapping' editor.

3. Expand the byte structure in the editor grid and locate the mirrored bit to be mapped.

4. Double-click into the grid field (in the 'Mapping' column) and enter a variable name or select an already declared variable with the browse button '...'.

Mapping AS-i I/O safety-related data to standard (non-safety-related) variables (mirrored bits)

After having inserted the '8 Bytes Safe Sercos Data' device object, mirrored bits of the safety-related data bits are available in the standard (non-safety-related) application. By mapping these mirrored bits to stan­dard variables in the standard application in EcoStruxure Machine Expert, the LMC is informed about the safety-related operations of the SLC and the AS-i Gateway. In EcoStruxure Machine Expert, these mirrored bits of AS-i data are organized as 8*8 bytes input data and 8*8 bytes output data (unlike to the representation in EcoStruxure Machine Expert - Safety, where the bits are grouped as input and output bits).

Proceed as follows:

1. In the EcoStruxure Machine Expert 'Devices' tree, double-click the '8 Bytes Safe Sercos Data' device object.

   The editors of the device are opened in the editors area.

2. Click the 'sercos Module I/O Mapping' editor.

3. Expand the byte structure in the editor grid and locate the mirrored bit to be mapped.

4. Double-click into the grid field (in the 'Mapping' column) and enter a variable name or select an already declared variable with the browse button '...'.

After mapping an input/output bit to a Boolean variable in EcoStruxure Machine Expert, the safety-related project is updated accordingly by entering the name of the mapped variable in the column 'SOMM Vari­able' in EcoStruxure Machine Expert - Safety. See topic "Evaluating and Writing to AS-i I/O Devices in EcoStruxure Machine Expert - Safety".

Optional: integrating standard AS-i slaves

Standard (non-safety-related) slaves connected to the AS-i field bus can be inserted into the 'EmptyModule' slots under the AS-i Gateway. This way, their process data can be accessed in the non-safety-related LMC application. These standard slots/devices are not relevant for the safety-related aspect covered by this documentation. Therefore, their use is not part of this documentation.

1. To insert standard slaves into the empty modules slot, proceed in the same way as for inserting the safety-related device object. See section "Adding an AS-i Gateway and inserting the '8 Bytes Safe Sercos Data' device object" for details.

2. To parameterize an inserted standard AS-i slave, double-click its tree node in the 'Devices' tree and select the desired editor.

   

3. To map the I/O data of a standard AS-i slave:

   1. In the EcoStruxure Machine Expert 'Devices' tree, double-click the slave to edited. The editors of the device are opened in the editors area.

   2. Click the 'sercos Module I/O Mapping' editor.

   3. Expand the data structure in the editor grid and locate the signal to be mapped.

   4. Double-click into the grid field (in the 'Mapping' column) and enter a variable name or select an already declared variable with the browse button '...'.

   

Download of parameterization data to the AS-i Gateway

After having inserted and parameterized the AS-i Gateway as described above, the related data are part of the EcoStruxure Machine Expert project. Therefore, they are included into the usual project download and then transferred from the LMC to the AS-i Gateway; no separate down­load to the AS-i Gateway is required.

The AS-i application configuration developed using ASIMON has to be commissioned separately as described in the ASIMON user documen­tation.

Observe the following safety notes before commissioning the system including the coupled AS-i field bus: