User guide: Studio 5000 and Mecademic Add-on instructions

CompactLogix PLC v1.0

Software

The purpose of this document is to guide the user in integrating a Mecademic Robot with Rockwell Studio 5000. This guide and the examples that are in it were done with Studio 5000 version 30.11. However, all of these instructions should work with any version higher than 20.

Installing the EDS file

After installing the EDS file, you can add a new module in your Rockwell project. To do this, right click on your Ethernet Port and select New Module.

When adding the Module, you will be prompted to select the module type. This is where you can select the Meca500 robot.

After selecting the Meca500 Robot, enter the IP address and name the instance of your robot. The revision for the module definition should be set on 1.001 with the Electronic keying set on exact match or compatible keying.

If the previous steps were done correctly, you should now be able to see the robot data structure in the controller tags of your project.

Using the Add-On Instructions

The following Add-On instructions are provided by Mecademic to simplify the usage of the Meca500 with Rockwell PLCs.

These instructions will be mirroring the commands present in the TCP/IP interface to enable ease of use and standardize the programming structure between the Web Interface and in PLC programs (Ladder/ST/SFC) for Rockwell PLCs.

Follow the steps below to use the Add-On Instructions in Studio 5000.

First, select the block that represents the command you want to send to your robot.

Populate the argument(s) field with the values you want to send for the selected command. The command will be sent to the robot on the first scan of the block or when one of the argument(s) values are modified.

If real-time updates are required, sending these instructions by updating the values should be the preferred method. However, it is recommended to update the values before enabling the blocks as this might give better control and prevent multiple instructions from being sent too rapidly if they are not all updated in the same scan.

Once the command has been sent, the sent bit from the block will become true and stay true until one of the arguments is modified or until the block is no longer enabled.

The buffered bit will become true when the MoveID (Internal or External) of the last command received by the robot equals the MoveID of the command sent by the block. When the Buffered bit becomes True it is an acknowledgment from the robot controller that it has received the command and added it to FIFO command buffer queue.

Motion Commands and MoveID

The way that the robot can identify all of the different commands is with the motion command number. Each command has it’s own unique number. The internal MoveID values of the AOIs are closely related to the motion command values. Since the MoveID needs to be changed every time a new command is being sent to the robot, the add on instruction will alternate between two MoveIDs.

These two numbers will be constructed as such :

External MoveID

The external MoveID feature can be activated by setting the ExternalStateControl value to 1. When this is enabled, the user will need to input their own MoveID in the AOI. The commands will be sent only when the external MoveID value is updated to a new value as with the internal MoveID. This feature can be useful for users who want more in-depth control of their sequence and who want to monitor the commands sent and received by the robot more closely.

It should be noted that this approach needs a careful and thorough understanding of how the MoveID is being used in the robot controller and should only be used by more advanced users. It is also important to note that the values of the external MoveID should never be the same as the internal values of the AOI. If the user tries to input the same value as an internal value the error bit will become true on the AOI.

Connect Block

Error Block

Please note that these examples are provided as-is by either Mecademic or it's Partners. These can be used as starting point for development and testing but Mecademic or it's partners are not under obligation to provide support and are not liable for any errors or unintended behavior caused by the examples. These examples could be updated over time.