Omron Driver Installation and Users Guide

SAFETY PRECAUTIONS
(Always read these instructions before using this equipment.)
Before using this product, please read this manual and the relevant manuals introduced in this manual carefully and pay full attention to safety to handle the product correctly. The instructions given in this manual are concerned with this product. For the safety instructions of the programmable controller system, please read the CPU module user's manual. In this manual, the safety instructions are ranked as "DANGER" and "CAUTION".

DANGER CAUTION

Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury. Indicates that incorrect handling may cause hazardous conditions, resulting in medium or slight personal injury or physical damage.

Note that the ! CAUTION level may lead to a serious consequence according to the circumstances. Always follow the instructions of both levels because they are important to personal safety.

Please save this manual to make it accessible when required and always forward it to the end user.

[Design Instructions]

DANGER
When performing data changes or status control from the personal computer to the running PLC, configure up an interlock circuit outside the PLC system to ensure that the whole system will operate safely. In addition, predetermine corrective actions for the system so that you can take measures against any communication error caused by a cable connection fault or the like in online operations performed from the peripheral device to the PLC.

CAUTION
Read the manual carefully before performing the online operations (especially forced output and operating status change) which will be executed with the personal computer connected to the running CPU module. Not doing so can damage the machine or cause an accident due to misoperation.

REVISIONS
* The manual number is given on the bottom left of the back cover.

Print Date Jul., 2009 Apr., 2010

* Manual Number BAD-804Q012-A0 BAD-804Q012-A1

Revisions First edition Correction Chapter 2 Chapter 3 Chapter 5 Chapter 7 Correction Chapter 2 Chapter 3 Chapter 4

Jun., 2011

BAD-804Q012-A2

This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.

2011 ILS Technology, Licensed to Mitsubishi Electric Corporation

This book applies to the Mitsubishi Electric Corporation MESInterface IT product components and to all subsequent releases and modifications until otherwise indicated in new editions. Make sure you are using the correct edition for the level of the product.

MITSUBISHI ELECTRIC CORPORATION PROVIDES THIS BOOK "AS IS," WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions therefore, this statement may not apply to you.

This book could contain technical inaccuracies or typographical errors. Changes are made periodically to the information herein. Mitsubishi Electric Corporation. May make improvements and changes at any time to the product(s) and/or program(s) described in this book.

When you send information to Mitsubishi Electric Corporation, you grant Mitsubishi Electric Corporation a nonexclusive right to use or distribute the information in any way it believes appropriate, without incurring any obligation to you.

TableofContents
Preface...............................................................................................................................................ii Assumptions...................................................................................................................................ii Who should read this book.............................................................................................................ii How this book is organized ........................................................................................................... iii Related documentation ................................................................................................................. iii Terminology used in this book.......................................................................................................iv Chapter 1: Introduction ..................................................................................................................... 1 Chapter 2: Supported Hardware ....................................................................................................... 2 Supported PLCs and communication interfaces ........................................................................... 2 Overall system configuration ..................................................................................................... 3 Chapter 3: Installing the License and Driver ..................................................................................... 4 Obtaining and installing the license keys ...................................................................................... 4 Installing the Omron driver package.............................................................................................. 7 Verifying Omron PLC device support is licensed and installed ..................................................... 9 Chapter 4: Device Definition ........................................................................................................... 10 Using the Workbench to define Omron devices .......................................................................... 10 Defining an Omron CJ1 or CS1 PLC device........................................................................... 11 Verifying a Device configuration.................................................................................................. 14 Displaying a devices runtime status ........................................................................................... 15 Displaying a devices attributes ................................................................................................... 16 Using the Variables window to access device variables ............................................................. 17 Chapter 5: Supported Access ......................................................................................................... 19 Variables ..................................................................................................................................... 19 Data types, data conversion and addressing .............................................................................. 19 Omron unsolicited command 090 and 098.................................................................................. 20 Configuring an Omron network send/recv instruction in the PLC ............................................ 20 Defining a trigger for a unsolicited event ................................................................................. 21 Example Trigger with Omron Unsolicited Event .......................................................................... 22 Chapter 6: Performance Considerations......................................................................................... 23 Chapter 7: Troubleshooting ............................................................................................................ 24 Common tasks and problems...................................................................................................... 24 Verify the proper license keys are installed. ............................................................................ 24 Unable to define a device for an Omron PLC .......................................................................... 25 Unable to Validate or communicate with an Omron PLC device ............................................. 25 MESInterface IT reboots when the device starts ..................................................................... 25 Error Codes ................................................................................................................................. 25 Index ............................................................................................................................................... 26 i

Preface
The MESInterface IT Omron driver is a MESInterface IT software driver that provides communication support for Omron PLCs. This book describes how to use the MESInterface IT Omron driver (referred to as the Omron driver) in conjunction with the MESInterface IT runtime and the MESInterface IT Workbench (referred to as the Workbench).

Assumptions
It is assumed that the reader has experience with the following: Omron PLC architecture Omron PLCs Omron naming conventions Omron CX-Programmer software MESInterface IT MESInterface IT Workbench.

Before using information in this book, the following should have occurred: MESInterface IT was installed in its operating environment The Workbench was installed on a computer that has TCP network connectivity to the MESInterface IT node The Omron PLCs have been setup and have network connectivity.

Whoshouldreadthisbook
This book is intended for process engineers and device programmers who will be defining device access and control solutions using MESInterface IT and the Workbench. This book is also intended for people who manage device interface systems.

ii MESInterface IT Omron Driver

Howthisbookisorganized
This book contains the following chapters: Chapter 1: Introduction provides an introduction to MESInterface IT and the Omron driver. Chapter 2: Supported Hardware describes the hardware that is supported by the Omron driver. Chapter 3: Installing the License and Driver describes the process of installing the license and driver package. Chapter 4: Device Definition describes the steps used to define the different types of devices. Chapter 5: Supported Access describes the data elements, data types and unsolicited events supported by the driver. Chapter 6: Performance Considerations provides information about device access performance. Chapter 7: Troubleshooting describes common problem scenarios and their resolutions and lists the extended status codes returned by the Omron driver.

Relateddocumentation
This book assumes you have access to the following MESInterface IT documentation: MESInterface IT Users Guide MESInterface IT Enterprise Connectivity Users Guide MESInterface IT System Administration Users Guide MESInterface IT Trigger Actions Guide and Reference MESInterface IT Troubleshooting Guide MESInterface IT Quick Start - TCP MESInterface IT Quick Start Database Insert MESInterface IT Quick Start WebSphere MQ MESInterface IT Quick Start MELSEC

Each of these books provides its specific information for the MESInterface IT product.

iii

Terminologyusedinthisbook
This section is your starting point and as such provides the terminology associated with the MESInterface IT environment. Use this terminology as a reference for the rest of this book. Term access privileges Description Permissions set by an administrator that allow or deny users access to certain features of the Workbench, such as changing the value of a device variable. By setting access privileges, the administrator controls user access to restricted data and functions. The development tool used to configure Omron PLCs and create and manage programs that run in the Omron PLCs. In MESInterface IT, a representation of a physical controller, such as a PLC. A named area of a devices memory where data is stored. The MESInterface IT product includes the following: MESInterface IT runtime, which provides the device management and access logic The MESInterface IT Workbench, which provides the view into a MESInterface IT nodes configuration and resource definition. The Workbench also provides access and control over those resources Individual device drivers, which provide the specific communication support for a device. Refers to an organizations systems that run high-end business applications such as an enterprise resource planning (ERP) application. Pertains to a trigger. An event is a condition that defines when a trigger should execute. Some common examples of events would be: data changing in a PLC a message instruction sent from a ladder program a time schedule a message sent from an enterprise system. A key that allows access to functions in the MESInterface IT node. Media Access Control (MAC) is a hardware address. The number is assigned by the manufacturer. MAC addresses uniquely identify a hardware unit on a network. A software component that provides a specific portion of MESInterface IT capability. A device driver can be implemented as a package. Programmable logic controller. The periodic automatic reading of a device variable. A set of rules for transferring data. In MESInterface IT, a predefined event and response item that is monitored by MESInterface IT. The event is the condition that defines when a trigger should execute. The response contains one or more actions that are executed when the event occurs. An Omron PLC unsolicited event. In a ladder logic program, a construct that allows the programmer to send to or receive data from a MESInterface IT trigger. The MESInterface IT Workbench provides the view into a MESInterface IT installations configuration and resource definition and provides access to those resources.

CX-Programmer device device variable MESInterface IT

enterprise system event

license key MAC address

package PLC polling protocol trigger

unsolicited event Command 090 and 098 Workbench

iv MESInterface IT Omron Driver

Chapter 1: Introduction
The MESInterface IT product is a software framework that provides intelligent and secure connectivity from your plant floor devices to your enterprise. This allows you to provide connectivity to any device in a vendor neutral methodology to your enterprise level allowing you to make business decisions based on real time data. The MESInterface IT runtime is the software that runs in a MESInterface IT Node. It allows you to: Define logical devices that represent the physical devices installed throughout your business. Define the data gathering and mapping solutions you need to share and convert data from one device to another device. Define connections and transactions between the MESInterface IT application logic and your enterprise applications, such as Database Management Systems, Enterprise Resource Planning Systems, and messaging systems. MESInterface IT manages the logical device definition, data access, data mapping and application logic that make up your specific business solution. The MESInterface IT Workbench is the common user interface used to configure all MESInterface IT products. The MESInterface IT Omron driver (Omron driver) is the software that enables communication between MESInterface IT and Omron PLCs. The combination of MESInterface IT and the manufacturer specific device drivers give businesses the ability to gather and map data from their variety of devices and generate real-time business events to their enterprise systems. See the MESInterface IT Users Guide for more information about the capabilities and usage of MESInterface IT and the Workbench.

Chapter 2: Supported Hardware

The driver is supported on all supported MESInterface IT operating environments. The supported operating environments for MESInterface IT include: Mitsubishi Q12DCCPU-V (CCPU)

The Omron driver is the extension of MESInterface IT that contains the protocol specific logic to communicate with the Omron PLCs.

SupportedPLCsandcommunicationinterfaces
The following Omron PLCs and communication interfaces are supported: Series SYSMAC CS1 SYSMAC CJ1 Model CS1G-CPU**H CS1H-CPU**H CJ1G-CPU4*H CJ1H-CPU6*H-R/6*H CJ1M-CPU1* Network Unit CS1W-ETN21 CJ1W-ETN21

MESInterface IT Omron Driver

Overallsystemconfiguration
This section shows the overall system configuration when using the MESinterface IT with C Controller Module.

Q12DCCPU-V
RUN CF CARD CH3 SD/RD MODE ERR. USER

USB

Chapter 3: Installing the License and Driver

Obtainingandinstallingthelicensekeys
MESInterface IT requires licenses to activate the functions and support that will be available in each MESInterface IT node. The specific license requirement for Omron PLC support varies depending on your MESInterface IT product operating environment. Refer to your license provider for the specific license requirement for your environment. The following sections assume that you have installed MESInterface IT and the Workbench in your network environment. Refer to the appropriate MESInterface IT Installation document for your operating environment for information on: Installing the MESInterface IT runtime Installing the MESInterface IT Workbench Using the Workbench to Scan for active MESInterface IT nodes.

Once you have used the Scan action to connect to one or more MESInterface IT nodes, you can view and configure the resources in the MESInterface IT Node. The examples shown in the following sections may appear different than your environment, depending on your MESInterface IT operating environments and the MESInterface IT product that you have installed. These examples assume a MESInterface IT Enterprise Edition node with a node name of Acme Products and IP address of 192.168.2.96. There may be differences between your Workbench panels and the example panels shown here, but the functional capabilities and logic flow will be similar.

MESInterface IT Omron Driver

To use the Workbench to view the licenses that are installed in a MESInterface IT node, follow these steps: 1. From the Workbench left pane, expand the MESInterface IT node you want to view.

2. Select the Administration icon. The Administration window appears as the right pane.

3. Select the Licenses tab. The Licenses tab will display a table showing the licenses for this MESInterface IT node. As each row in the table is selected, the detailed information for the license is displayed. The table has the following columns: License Key the license key code provided by your license provider Product a description name of the license Features the features activated by the license Expiration the expiration date of the license Status the status of the license. A blank field indicates that the license expiration date has not passed. 4. To add additional license support, such as for access to Omron PLCs, you can use: New to add a single license key Import to add one or more license keys in a license file.

For more information, see Key-based licensing and activation process in the MESInterface IT System Administration Users Guide.

MESInterface IT Omron Driver

InstallingtheOmrondriverpackage
Some MESInterface IT operating environments may have the Omron driver already installed. Verification of device support can continue with the section Verifying Omron PLC device support is licensed and installed. For MESInterface IT operating environments that do not have the Omron driver already installed, the Omron driver is installed as a package in the MESInterface IT environment. The administration steps to view and add packages are similar to those for licenses. To use the Workbench to view installed packages on a MESInterface IT node, follow these steps: 1. From the Workbench left pane, expand the MESInterface IT node you want to view. 2. Select the Administration icon. The Administration window appears as the right pane. 3. Select the Packages tab.

The Packages tab provides a table that displays the installed packages. As each row in the table is selected, detailed information for the package appears. The table has the following columns: Name the name of the package 7

Type the type of the package. A driver package will display the string Driver Version the version number of the package Publisher the provider of the package. When a row is selected, additional information may be provided for that package, such as the publishers Web site URL, phone number and email address.

To install a new package, follow these steps: 1. Select Add at the bottom of the window. The Package File Location dialogue window appears. 2. Navigate to the location of the package file, enter the file name and click Select. An Add Package confirmation window appears with the detailed information for the package. (The version of the installed package file should be the same as MESInterface IT core.) 3. Select Yes to add the package. An Add Package information window appears, indicating that the package is being added and a Node restart may occur. 4. Select OK to clear the information window. The new package will be listed in the Packages tab and its additional information will be displayed when its row in the table is selected. Depending on your operating environment, MESInterface IT might automatically restart or you might have to manually restart MESInterface IT in order to have the support in the package become available to define and access Omron PLC devices.

MESInterface IT Omron Driver

VerifyingOmronPLCdevicesupportislicensedandinstalled
The available device types in a MESInterface IT node are determined by the device support that is installed in the MESInterface IT node. You can verify that support for Omron PLCs is configured in this MESInterface IT node by doing the following: 1. From the Workbench left pane, expand the MESInterface IT node you want to verify. 2. Select the Devices icon. The Devices window appears as the right pane. 3. Select New at the bottom of the pane. The Device window appears. 4. Select the Type drop down list to view the supported device types. You should see the supported Omron PLC types under the Omron group.

5. This verifies that you have the correct license and driver package needed to communicate with Omron PLCs.

Chapter 4: Device Definition

The task of device definition fits into the overall sequence of steps as follows: 1. Installing your hardware. Your device and network installation will determine the MESInterface IT devices that must be defined. The detailed installation of your hardware is beyond the scope of this document. 2. Configuring your hardware using the CX-Programmer programming and maintenance tool. The entire capability and usage of the CX-Programmer is beyond the scope of this document. 3. Installing the MESInterface IT runtime and Workbench. Refer to the appropriate MESInterface IT Installation document for installation information. 4. Using the Workbench to define devices. This task is described in the following sections. There may be differences between your Workbench panels and the example panels shown here, but the functional capabilities and logic flow will be similar.

UsingtheWorkbenchtodefineOmrondevices
The Workbench provides the view into a MESInterface IT installations configuration and resource definition. The Workbench also provides access and control over those resources. In MESInterface IT, a device is a resource that represents a physical controller. Some examples of a device would be an Omron PLC, a bar code reader and a RFID tag reader. A device can also be defined in one MESInterface IT node to represent a device that is defined and supported in another MESInterface IT node. This allows your application solution to have access to devices and their data independent of their location or connectivity details. The following devices can be defined in MESInterface IT with the Omron driver: Omron CJ1 Omron CS1

10

MESInterface IT Omron Driver

DefininganOmronCJ1orCS1PLCdevice
To define a device that represents one of the Omron PLC types, follow these steps: 1. From the Workbench left pane, expand the MESInterface IT node where you want to define a device.

2. Select the Devices icon. The Devices window appears as the right pane.

The Devices window provides a table format that lists the previously defined devices.

11

3. To define a new device, select New at the bottom of the pane. The Device window appears. 4. Use the Type down-arrow, to select CJ or CS1 under the Omron group.

5. The Device window changes to accommodate the selected device type.

12

MESInterface IT Omron Driver

6. To define a device that represents an Omron CJ1 or CS1 PLC, set this new devices fields as follows: Field Name Type Protocol IP Address Port Source Node Description Enter a name for the Omron PLC device. Select CJ1 or CS1. Select TCP or UDP protocols. Enter the IP Address of the device. Enter the port number used by the device. The default is 9600, but may be changed. If using TCP, then this field should be set to 0, otherwise refer to your CX-Programmer manual and device configuration for this parameter. If using TCP, then this field should be set to 0, otherwise refer to your CX-Programmer manual and device configuration for this parameter.

Destination Node

You can also specify advanced settings for the Omron CJ1 or CS1 device. Select the Advanced Properties checkbox. Field Source Network Source Unit Destination Network Destination Unit Per Variable Security Description Refer to your CX-Programmer manual and device configuration for this parameter. Refer to your CX-Programmer manual and device configuration for this parameter. Refer to your CX-Programmer manual and device configuration for this parameter. Refer to your CX-Programmer manual and device configuration for this parameter. Select False to disable the allocation of additional memory to track User to Variable access for all Variables in this Device. Select True to enable this feature if required. See Setting up Read Write per device variable in the MESInterface IT Systems Administration Users Guide for more information.

7. Select Validate to have MESInterface IT validate the fields and connect to the Omron PLC. If there is a problem connecting to the Omron PLC, an error code will be displayed. 8. Select Save to save the device definition. The device will appear in the Device window list of devices. 9. You can now control the device (Start, Stop), access the devices variables by using the Variables window and build solutions that use the devices resources.

13

VerifyingaDeviceconfiguration
As you define your devices, you can verify that the configuration of the device is correct and that the communication path to the device is working in several ways. 1. When defining a new device or editing an existing device definition, the Validate function verifies the values in the devices fields and performs a communication connection to the physical device. 2. After using Validate, you use the Save function to save the current device definition. 3. Select Devices in the left pane to view the devices defined for this MESInterface IT node. The devices that are defined in this MESInterface IT node will be listed in the Devices window. The State column shows the current state of the device, Stopped when first defined and Started after a successful start of the device. There are other states that a device can have: Starting, Stopping and Disabled when the device is transitioning between the Started and Stopped states or when recovering from a communication problem. The example below shows a CS1 PLC device defined in the MESInterface IT node. The device is in the Started state.

14

MESInterface IT Omron Driver

The Start function can be used to change a devices state from Stopped to Started. When a device is started, MESInterface IT: Establishes a communication connection to the physical device Sets up the internal structures to keep track of the device connection Places the device in the Started state, which allows the device to be accessed (read and write) by your applications.

Displayingadevicesruntimestatus
The Devices window displays the devices that are defined in MESInterface IT. Runtime statistics will be maintained for each device that is in the Started state. To display the runtime statistics: 1. Select a device in the list of devices. The devices operational statistics are displayed in the Status tab.

2. Select the Status tab. The following example displays the status panel associated with an Omron CS1 device.

15

Runtime Status Fields

Attribute Start Time (ms): Stop Time (ms): Avg Queue Wait (ms): Queue Depth: Last Read: Avg Read (ms): Last Write: Avg Write (ms): Last Occurrence First Occurrence Variable Status Ext. Status Repeats Value Millisecond length of time needed to start the device. Millisecond length of time needed to stop the device. Millisecond length of time device read/write requests spent in a queue waiting processing. Average number of items in the queue. Timestamp of the last read request. Average Millisecond length of time needed to perform a device read. Timestamp of the last write request. Average Millisecond length of time needed to perform a device write. Most recent time the error occurred. Initial time the error occurred. The Variable associated with the error occurrence. The MESInterface IT error code that was encountered. An error code that was returned by the device. The number of times the error has occurred between the Last and First occurrence.

Displayingadevicesattributes
The Devices window displays the devices that are defined in MESInterface IT. The Omron PLC devices will display additional attributes when they are in the Started state. To display these attributes: 1. From the Devices panel, select the appropriate Omron PLC device in the list of devices. The Omron PLC devices attributes are displayed in the Attributes tabs. 2. Select the Attributes tab. The Attributes tab for the Omron PLC will display the attributes and their current values for the selected device: Attribute Controller Model Controller Version Destination Node Source Node Structure Count Value The model information for the Omron PLC. The version information for the Omron PLC. Device specific network configuration information. Device specific network configuration information. The number of SINFO objects associated with the device. These are the registered structures, they may not all be in use. The number of VINFO objects associated with all SINFO objects. This is the sum of all members attached to all structures. The number of all VINFO objects associated with the device. If the VINFO is a structure, then also count the children, however counts arrays as individual items. The number of VINFO objects associated with the device. These can be primitives, arrays or structures, but they only count as 1 item in the tree.

Structure Member Count

Total Variable Count

Variable Count

16

MESInterface IT Omron Driver

UsingtheVariableswindowtoaccessdevicevariables
Once you have defined your devices, you can use the Workbench to access the variables that reside in those devices. 1. From the Workbench left pane, select the Variables icon. The Variables window appears as the right pane.

The Variables window provides a tree format that lists the started devices in the MESInterface IT node. The devices must be in the Started state to be included in the Variables window. Each device can be expanded to show the variables that reside in that device. 2. You can expand or collapse the tree format to zoom in or out on a devices variables. When you get to an individual data element, you have access to the Read and Write functions to read a devices data element or write a devices data element. For information on data types and data conversion supported by the Omron driver. Refer to Chapter 5: Supported Access. 3. You must ensure that the appropriate levels of security access privileges are in place to restrict the access to data elements to those personnel who have the proper knowledge and understanding when reading or writing device data elements. See Controlling user access in 17

the MESInterface IT System Administration Users Guide for more information. Some of the data elements may also be configured to be read only within the device using the devices programming tools.

18

MESInterface IT Omron Driver

Chapter 5: Supported Access

Variables
The Omron driver supports the following Omron PLC registers as MESInterface IT variables: Variable Description CIO Standard I/O points that are usually tied to physical IO on the system. This area of memory can only be read by MESInterface IT and cannot be written. DM Standard WORD-based memory space. This data region is volatile and values will be lost when the power is recycled. It can be accessed as WORDS, DWORDS, STRINGs, or FLOATS (REAL, LREAL). EM Extended WORD-based memory space. This data region is volatile and values will be lost when the power is recycled. It can be accessed as WORDS, DWORDS, STRINGs, or FLOATS (REAL, LREAL).

Datatypes,dataconversionandaddressing
The Omron driver and MESInterface IT support the Omron PLC data types and the MESInterface IT data types as follows: Omron data type MESInterface IT data type Word INT2 DWord INT4 Real FLOAT4 String STRING Bit BOOL The Omron PLC data types are supported in the MESInterface IT environment wherever a variable is accessed and the variable is associated with an Omron PLC device. Some examples are: Workbench Variables window Read as and Write as functions Transport map data type fields Trigger data type fields Trigger action variable data type fields.

The data representations in the Omron PLC, MESInterface IT and the Workbench are supported by the necessary data conversion functions (e.g. Real and Float4). The variable addressing supports the assignment of a variable of one data type into a variable with a different data type at the correct starting address location. One way to see this variable addressing support is to use the Workbench Variables windows Read as and Write as functions by right clicking on a data element and reading or writing as a type different than the data element.

19

Omronunsolicitedcommand090and098
Omron PLCs are able to send to and receive data from MESInterface IT using two commands. Command 090 can be used to allow an Omron PLC to send data to MESInterface IT. Command 098 can be used to request data from MESInterface IT and allows the user to initiate the execution of a MESInterface IT trigger from the ladder logic in an Omron PLC. This can take the place of having a MESInterface IT trigger constantly polling an Omron PLC variable to see if an event has occurred. For more information on triggers and actions, see the MESInterface IT Trigger Actions Guide and Reference.

ConfiguringanOmronnetworksend/recvinstructioninthePLC
The following screen shows the Omron CX-Programmer software and an example of a rung of a ladder that can send an event notification to a MESInterface IT trigger. Refer to the CXProgrammers guide for more information about how to use these function blocks.

20

MESInterface IT Omron Driver

Definingatriggerforaunsolicitedevent
To define a trigger that executes when an Omron unsolicited executes, follow these steps: 1. From Workbench left pane, expand the MESInterface IT node where you want to define a trigger. 2. Select the Projects icon. The Projects window appears as the right pane. 3. To add a trigger to a new project, first create a project by selecting New from the bottom of the Projects window. Enter a name for the new project and select OK. After the project is created, select the project to display the Triggers window. 4. To add a trigger to an existing project, select the existing project from the Projects list to display the Triggers window. The Triggers window appears as the right pane. 5. To define a new trigger, select New at the bottom of the pane. The New Trigger window appears. To define a trigger that executes when an Omron unsolicited executes, set this new triggers fields as follows: Field Name Reporting Description Enter a name that for the trigger. Enter the reporting option for the trigger. See Setting trigger reporting options in the MESInterface IT Users Guide for information. Under PLC Logic Events group, select Omron. Pick the name of an existing (started) Omron PLC device. If you want to send data from the PLC to MESInterface IT , use command 090 (Send). If you want the PLC to receive data, use command 098 (Recv). The address can be any positive integer. It is a unique (user defined) number for unsolicited message identification. It is used to match the packets and allows multiple triggers to be on the same PLC. The expected number of words to be sent in the request (applies to command 090). (098) is used for the response. The expected number of words to be sent in the request (applies to command 090). (098) is used for the response. Enter the maximum number of instances of the trigger that can execute concurrently. 21

Trigger Event Type Device Name Command Code

Address

Requested Word Count Requested Data Type Max Pending

Max Exec Time (ms)

Actions

Enter the maximum execution time for the trigger. If this time is exceeded, a warning message is written to the Exceptions log (even if Reporting is off). Add the trigger actions required to implement the response desired for this Omron PLC unsolicited event.

ExampleTriggerwithOmronUnsolicitedEvent

22

MESInterface IT Omron Driver

Chapter 6: Performance Considerations

The MESInterface IT Troubleshooting Guide has system-wide information pertaining to MESInterface IT, including performance considerations. The Workbench provides execution information that can be used to understand the performance characteristics of your solution, including device access.

Trigger definition fields

The trigger Max Pending field defines the number of trigger instances that can execute concurrently. The trigger Max Exec Time (ms) field defines the maximum execution time of the trigger, which when exceeded will result in a warning message written to the Exceptions Log file.

Triggers window fields

The Triggers window displays the state and status of each trigger, including fields to understand the execution characteristics of the trigger as it is developed, tuned and monitored during operations: Successes, Failures, In Progress, Overflow, and Avg Time (ms).

Devices window fields

The Devices window displays the state of each device, including fields to understand the read and write access of the device. A list of the latest errors encountered in accessing the device is also displayed.

23

Chapter 7: Troubleshooting
The Omron driver troubleshooting procedures should begin with the information in the MESInterface IT Troubleshooting Guide. The Troubleshooting Guide has system-wide information pertaining to MESInterface IT. For Omron driver-specific problems, the following section lists common tasks and problems.

Commontasksandproblems
The following are common tasks and problems when accessing Omron PLCs.

Verifytheproperlicensekeysareinstalled.
The features and functions available in a MESInterface IT node are controlled by the licenses that are installed in the node. To verify that the Omron driver license is installed: 1. From the Workbench left pane, expand the node whose license you want to check, and then select the Administration icon. 2. From the Administration window, select the Licenses tab. 3. Select the appropriate license. Details of the license appear on the tab. 4. View the Features field to identify the device driver. If you do not see the correct license, or if the license is expired, you must request a license from your license key provider. For information on how to install a license, refer to the MESInterface IT System Administration Users Guide.

24

MESInterface IT Omron Driver

UnabletodefineadeviceforanOmronPLC
The Omron driver is not part of this MESInterface IT installation. The Omron driver is installed as a package separate from the base MESInterface IT installation. You may be working with different levels of MESInterface IT nodes, each with different levels of support for devices. Ensure that this MESInterface IT node is the one with support for Omron PLCs.

UnabletoValidateorcommunicatewithanOmronPLCdevice
The Omron PLC needs to be configured using the CX-Programmer software. The complete description of this configuration is beyond the scope of this document. Ensure that the Conversion setting and the IP address table in the network settings are correctly configured for your network setup.

MESInterfaceITrebootswhenthedevicestarts
Free Memory is shortage. Stop the other device and restart the device.

ErrorCodes
This section describes the error codes that you might encounter when using MESInterface IT and the Omron driver. These error codes are available from the Devices window on the Extended Status column. The error codes are also referenced in the Exceptions Log. When the system experiences an abnormal condition (such as a device failure, disconnect from a controller, or software error), an error code and extended error code are recorded in the Exceptions Log. For more information, see the MESInterface IT Troubleshooting Guide. In the Devices window, the Status column will always be a generic error code that can tell you if the error is a communication error, a data error, or some other internal device error. The Extended Status column provides the error code from the driver. These error codes can be basic MESInterface IT error codes or specific to the Omron driver. Refer to the FINS Reference manual (page 109) for detailed protocol-specific error codes.

25

Index
A
accessprivileges,iv Administrationwindow,5,7 Attributestab,16

M
MaxExecTime,22 MaxPending,21

O
Omronunsolicitedcommand,20

C
CXprogrammersoftware,20 CXProgrammer,iv

P
package,7 Packagestab,7 polling,20

D
datatypes,19 device,iv,10 deviceattributes,16 devicevariable,iv Deviceswindow,9

R
Runtimestatistics,15

S
Scan,4 Statustab,15

E
enterprisesystem,iv event,iv EventID,21 ExceptionsLog,25 executioncharacteristics,23 ExtendedStatus,25

T
trigger,iv,21 TriggerEventType,21 troubleshootingprocedures,24

I
installalicense,24

U
unsolicitedevent,iv

L
license,iv licenses,4 Licensestab,6

V
variables,19 Variableswindow,17

W
Workbench,iv,10

26

MESInterface IT Omron Driver

"deviceWISE enabled" deviceWISE is a trademark of ILS Technology LLC. Microsoft, Windows, Windows Vista, SQL server, and Visual Studio are registered trademarks of Microsoft Corporation in the United States and other countries. Sun, Sun Microsystems, Java, J2ME and J2SE are either trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Oracle is a registered trademark of Oracle Corporation. Adobe and Acrobat are registered trademarks of Adobe Systems Incorporation. Pentium and Celeron are trademarks of Intel Corporation in the united States and other countries. Ethernet is a trademark of Xerox Co., Ltd. in the United States. CompactFlash is a trademark of SanDisk Corporation. Other company names used in this document are trademarks or registered trademarks of respective owners. The Program may contain some or all of the following third party components: EZSocket Copyright (C) 2008 Mitsubishi Electric Corporation iconv Copyright (C) 2007 Free Software Foundation javasqlite Copyright (C) 2008 Christian Werner libxml2 Copyright (C) 2008 xmlsoft.org log4j as originally developed by Apache.org OpenSSL Toolkit, Open SSL Project, OpenSSL Copyright (C) 1998-2008 the Open SSL Project; This product includes cryptographic software written by Eric Young (eay@cryptsoft.com) and by Tim Hudson (tjh@cryptsoft.com) Jamaica JVM Copyright (C) 2008 Aicas

27

Omron Driver Installation and Users Guide

MODEL MODEL CODE

BAD-804Q012-A2

MITSUBISHI ELECTRIC CORPORATION

HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN NAGOYA WORKS : 1-14, YADA-MINAMI 5-CHOME, HIGASHI-KU, NAOGYA, JAPAN

When exported from Japan, this manual does not require application to the Ministry of Economy, Trade and Industry for service transaction permission.

Specifications subject to change without notice.

28

MESInterface IT Omron Driver