Mitsubishi Fx Manual

Mitsubishi FX Driver

© 2016 PTC Inc. All Rights Reserved.


Table of Contents

Mitsubishi FX Driver

Table of Contents


Overview

Setup

Channel Properties

Channel Properties - General

Channel Properties - Serial Communications

Channel Properties - Write Optimizations

Channel Properties - Advanced

Device Properties

Device Properties - General

Device Properties - Scan Mode

Device Properties - Timing

Device Properties - Auto-Demotion

Device Properties - Redundancy

Modem Setup

Data Types Description

Address Descriptions

FX Addressing

FX0 Addressing

FX0N Addressing

FX2N Addressing

FX3U Addressing

Event Log Messages

Received block length does not match expected length. | Received block length = <number>,

Expected block length = <number>.

Error Mask Definitions

Appendix: Ethernet Encapsulation Examples

Index

14

16

17

17

18

19

20

3

3

4

10

10

12

13

14

14

6

8

9

5

5

21

24

1

2

24

24

25

31

2

www. kepware.com

3


Mitsubishi FX Driver

Help version 1.034

CONTENTS

Overview

What is the Mitsubishi FX Driver?

Device Setup

How do I configure a device for use with this driver?


What data types does this driver support?


How do I address a data location on a Mitsubishi FX series device?

Error Descriptions

What messages does the Mitsubishi FX Driver produce?

Overview

The Mitsubishi FX Driver provides a reliable way to connect Mitsubishi FX devices to OPC client applications; including HMI, SCADA, Historian, MES, ERP, and countless custom applications. It is intended for use with

Mitsubishi FX series devices.

www. kepware.com


Setup

Supported Device Models

FX

FX0

FX0N

FX2N

FX3U

Note: FX3U is not supported in Windows CE.

Communication Protocol

Direct Serial

Supported Communication Parameters

Baud Rate: 9600

Parity: Even

Data Bits: 7

Stop Bits: 1

Ethernet Encapsulation

This driver supports Ethernet Encapsulation, which allows the driver to communicate with serial devices attached to an Ethernet network using a terminal server. It may be invoked through the COM ID dialog in

Channel Properties. For more information, refer to the OPC server's help file.

When used directly with a serial port, this driver supports only a single connection to a single controller per serial port. When operating in the Ethernet Encapsulation mode, the driver supports up to 100 controllers per channel. In this mode, a single controller can be paired with a terminal server (device server) to form a single node. For more information, refer to

Appendix: Ethernet Encapsulation Examples

.

Note: Ethernet Encapsulation is not supported by the FX3U model.

Maximum Number of Channels and Devices

The maximum number of channels supported by this driver is 256. The maximum number of devices per channel is 100.

Device IDs

This protocol does not support simultaneous communication with multiple devices.

Flow Control

When using an RS232/RS485 converter, the type of flow control required depends on the needs of the converter. Some converters do not require any flow control whereas others require RTS flow. Consult the converter's documentation in order to determine its flow requirements. An RS485 converter that provides automatic flow control is recommended.

Note: When using the manufacturer's supplied communications cable, it is sometimes necessary to choose a flow control setting of RTS or RTS Always in the channel properties.

Channel Properties

Device Properties

4

www. kepware.com

5


Channel Properties

This server supports the use of simultaneous multiple communications drivers. Each protocol or driver used in a server project is called a channel. A server project may consist of many channels with the same communications driver or with unique communications drivers. A channel acts as the basic building block of an OPC link.

The properties associated with a channel are broken in to logical groupings. While some groups are specific to a given driver or protocol, the following are the common groups:

General

Ethernet

or

Serial Communications

Write Optimization

Advanced

Channel Properties - General

This server supports the use of simultaneous multiple communications drivers. Each protocol or driver used in a server project is called a channel. A server project may consist of many channels with the same communications driver or with unique communications drivers. A channel acts as the basic building block of an OPC link. This group is used to specify general channel properties, such as the identification attributes and operating mode.

Identification

Name: User-defined identity of this channel. In each server project, each channel name must be unique.

Although names can be up to 256 characters, some client applications have a limited display window when browsing the OPC server's tag space. The channel name is part of the OPC browser information.

For information on reserved characters, refer to "How To... Properly Name a Channel, Device, Tag, and Tag

Group" in the server help.

Description: User-defined information about this channel.

Many of these properties, including Description, have an associated system tag.

Driver: Selected protocol / driver for this channel. This property specifies the device driver that was selected during channel creation. It is a disabled setting in the channel properties.

Note: With the server's online full-time operation, these properties can be changed at any time. This includes changing the channel name to prevent clients from registering data with the server. If a client has already acquired an item from the server before the channel name is changed, the items are unaffected. If, after the channel name has been changed, the client application releases the item and attempts to reacquire using the old channel name, the item is not accepted. With this in mind, changes to the properties should not be made once a large client application has been developed. Utilize the User Manager to prevent operators from changing properties and restrict access rights to server features.

www. kepware.com


Diagnostics

Diagnostics Capture: When enabled, this option makes the channel's diagnostic information available to

OPC applications. Because the server's diagnostic features require a minimal amount of overhead processing, it is recommended that they be utilized when needed and disabled when not. The default is disabled.

For more information, refer to "Communication Diagnostics" in the server help.

Not all drivers support diagnostics. To determine whether diagnostics are available for a particular driver, open the driver information and locate the "Supports device level diagnostics" statement.

Channel Properties - Serial Communications

Serial communication properties are available to serial drivers and vary depending on the driver, connection type, and options selected. Below is a superset of the possible properties.

Click to jump to one of the sections:

Connection Type

,

Serial Port Settings

or

Ethernet Settings

, and

Operational Behavior

.

Note: With the server's online full-time operation, these properties can be changed at any time. Utilize the User Manager to restrict access rights to server features, as changes made to these properties can temporarily disrupt communications.

6

Connection Type

Physical Medium: Choose the type of hardware device for data communications. Options include

COM Port, None, Modem, and Ethernet Encapsulation. The default is COM Port.

l l

None: Select None to indicate there is no physical connection, which displays the

Operation with no

Communications

section.

COM Port: Select Com Port to display and configure the


section.

l

Modem: Select Modem if phone lines are used for communications, which are configured in the

Modem Settings

section.

l

Ethernet Encap.: Select if Ethernet Encapsulation is used for communications, which displays the


section.

l

Shared: Verify the connection is correctly identified as sharing the current configuration with another channel. This is a read-only property.

www. kepware.com

7



COM ID: Specify the Communications ID to be used when communicating with devices assigned to the channel. The valid range is 1 to 9991 to 16. The default is 1.

Baud Rate: Specify the baud rate to be used to configure the selected communications port.

Data Bits: Specify the number of data bits per data word. Options include 5, 6, 7, or 8.

Parity: Specify the type of parity for the data. Options include Odd, Even, or None.

Stop Bits: Specify the number of stop bits per data word. Options include 1 or 2.

Flow Control: Select how the RTS and DTR control lines are utilized. Flow control is required to communicate with some serial devices. Options are: l

None: This option does not toggle or assert control lines.

l l l

DTR: This option asserts the DTR line when the communications port is opened and remains on.

RTS: This option specifies that the RTS line is high if bytes are available for transmission. After all buffered bytes have been sent, the RTS line is low. This is normally used with RS232/RS485 converter hardware.

RTS, DTR: This option is a combination of DTR and RTS.

l

RTS Always: This option asserts the RTS line when the communication port is opened and remains on.

l

RTS Manual: This option asserts the RTS line based on the timing properties entered for RTS Line

Control. It is only available when the driver supports manual RTS line control (or when the properties are shared and at least one of the channels belongs to a driver that provides this support).

RTS Manual adds an RTS Line Control property with options as follows: l

Raise: This property specifies the amount of time that the RTS line is raised prior to data transmission. The valid range is 0 to 9999 milliseconds. The default is 10 milliseconds.

l

Drop: This property specifies the amount of time that the RTS line remains high after data transmission. The valid range is 0 to 9999 milliseconds. The default is 10 milliseconds.

l

Poll Delay: This property specifies the amount of time that polling for communications is delayed. The valid range is 0 to 9999. The default is 10 milliseconds.

Tip: When using two-wire RS-485, "echoes" may occur on the communication lines. Since this communication does not support echo suppression, it is recommended that echoes be disabled or a RS-485 converter be used.

Operational Behavior

l

Report Comm. Errors: Enable or disable reporting of low-level communications errors. When enabled, low-level errors are posted to the Event Log as they occur. When disabled, these same errors are not posted even though normal request failures are. The default is Enable.

l

Close Idle Connection: Choose to close the connection when there are no longer any tags being referenced by a client on the channel. The default is Enable.

l

Idle Time to Close: Specify the amount of time that the server waits once all tags have been removed before closing the COM port. The default is 15 seconds.


www. kepware.com


Ethernet Encapsulation provides communication with serial devices connected to terminal servers on the

Ethernet network. A terminal server is essentially a virtual serial port that converts TCP/IP messages on the

Ethernet network to serial data. Once the message has been converted, users can connect standard devices that support serial communications to the terminal server. The terminal server's serial port must be properly configured to match the requirements of the serial device to which it is attached. For more

information, refer to "How To... Use Ethernet Encapsulation" in the server help.

l

Network Adapter: Indicate a network adapter to bind for Ethernet devices in this channel. Choose a network adapter to bind to or allow the OS to select the default.

Specific drivers may display additional Ethernet Encapsulation properties. For more information, refer to Channel Properties - Ethernet Encapsulation.

8

Modem Settings

l

Modem: Specify the installed modem to be used for communications.

l

Connect Timeout: Specify the amount of time to wait for connections to be established before failing a read or write. The default is 60 seconds.

l

Modem Properties: Configure the modem hardware. When clicked, it opens vendor-specific modem properties.

l

Auto-Dial: Enables the automatic dialing of entries in the Phonebook. The default is Disable. For

more information, refer to "Modem Auto-Dial" in the server help.

l

Report Comm. Errors: Enable or disable reporting of low-level communications errors. When enabled, low-level errors are posted to the Event Log as they occur. When disabled, these same errors are not posted even though normal request failures are. The default is Enable.

l

Close Idle Connection: Choose to close the modem connection when there are no longer any tags being referenced by a client on the channel. The default is Enable.

l

Idle Time to Close: Specify the amount of time that the server waits once all tags have been removed before closing the modem connection. The default is 15 seconds.

Operation with no Communications

l

Read Processing: Select the action to be taken when an explicit device read is requested. Options include Ignore and Fail. Ignore does nothing; Fail provides the client with an update that indicates failure. The default setting is Ignore.

Channel Properties - Write Optimizations

As with any OPC server, writing data to the device may be the application's most important aspect. The server intends to ensure that the data written from the client application gets to the device on time. Given this goal, the server provides optimization properties that can be used to meet specific needs or improve application responsiveness.

Write Optimizations

www. kepware.com

9


Optimization Method: controls how write data is passed to the underlying communications driver. The options are: l

Write All Values for All Tags: This option forces the server to attempt to write every value to the controller. In this mode, the server continues to gather write requests and add them to the server's internal write queue. The server processes the write queue and attempts to empty it by writing data to the device as quickly as possible. This mode ensures that everything written from the client applications is sent to the target device. This mode should be selected if the write operation order or the write item's content must uniquely be seen at the target device.

l

Write Only Latest Value for Non-Boolean Tags: Many consecutive writes to the same value can accumulate in the write queue due to the time required to actually send the data to the device. If the server updates a write value that has already been placed in the write queue, far fewer writes are needed to reach the same final output value. In this way, no extra writes accumulate in the server's queue. When the user stops moving the slide switch, the value in the device is at the correct value at virtually the same time. As the mode states, any value that is not a Boolean value is updated in the server's internal write queue and sent to the device at the next possible opportunity. This can greatly improve the application performance.

Note: This option does not attempt to optimize writes to Boolean values. It allows users to optimize the operation of HMI data without causing problems with Boolean operations, such as a momentary push button.

l

Write Only Latest Value for All Tags: This option takes the theory behind the second optimization mode and applies it to all tags. It is especially useful if the application only needs to send the latest value to the device. This mode optimizes all writes by updating the tags currently in the write queue before they are sent. This is the default mode.

Duty Cycle: is used to control the ratio of write to read operations. The ratio is always based on one read for every one to ten writes. The duty cycle is set to ten by default, meaning that ten writes occur for each read operation. Although the application is performing a large number of continuous writes, it must be ensured that read data is still given time to process. A setting of one results in one read operation for every write operation. If there are no write operations to perform, reads are processed continuously. This allows optimization for applications with continuous writes versus a more balanced back and forth data flow.

Note: It is recommended that the application be characterized for compatibility with the write optimization enhancements before being used in a production environment.

Channel Properties - Advanced

This group is used to specify advanced channel properties. Not all drivers support all properties; so the

Advanced group does not appear for those devices.

Non-Normalized Float Handling: Non-normalized float handling allows users to specify how a driver handles non-normalized IEEE-754 floating point data. A non-normalized value is defined as Infinity, Not-a-

Number (NaN), or as a Denormalized Number. The default is Replace with Zero. Drivers that have native float handling may default to Unmodified. Descriptions of the options are as follows: www. kepware.com

Mitsubishi FX Driver l l

Replace with Zero: This option allows a driver to replace non-normalized IEEE-754 floating point values with zero before being transferred to clients.

Unmodified: This option allows a driver to transfer IEEE-754 denormalized, normalized, nonnumber, and infinity values to clients without any conversion or changes.

Note: This property is disabled if the driver does not support floating point values or if it only supports the option that is displayed. According to the channel's float normalization setting, only real-time driver tags

(such as values and arrays) are subject to float normalization. For example, EFM data is not affected by this setting.lin

For more information on the floating point values, refer to "How To ... Work with Non-Normalized Floating

Point Values" in the server help.

Inter-Device Delay: Specify the amount of time the communications channel waits to send new requests to the next device after data is received from the current device on the same channel. Zero (0) disables the delay.

Note: This property is not available for all drivers, models, and dependent settings.

Device Properties

Device properties are organized into the following groups. Click on a link below for details about the properties in that group.

Identification

Operating Mode

Scan Mode

Communication Timeouts

Auto-Demotion

Redundancy

Device Properties - General

A device represents a single target on a communications channel. If the driver supports multiple controllers, users must enter a device ID for each controller.

10

Identification

www. kepware.com

11


Name: This property specifies the name of the device. It is a logical user-defined name that can be up to

256 characters long, and may be used on multiple channels.

Note: Although descriptive names are generally a good idea, some OPC client applications may have a limited display window when browsing the OPC server's tag space. The device name and channel name become part of the browse tree information as well. Within an OPC client, the combination of channel name and device name would appear as "ChannelName.DeviceName".

For more information, refer to "How To... Properly Name a Channel, Device, Tag, and Tag Group" in server help.

Description: User-defined information about this device.

Many of these properties, including Description, have an associated system tag.

Channel Assignment: User-defined name of the channel to which this device currently belongs.

Driver: Selected protocol driver for this device.

Model: This property specifies the specific type of device that is associated with this ID. The contents of the drop-down menu depends on the type of communications driver being used. Models that are not supported by a driver are disabled. If the communications driver supports multiple device models, the model selection can only be changed when there are no client applications connected to the device.

Note: If the communication driver supports multiple models, users should try to match the model selection to the physical device. If the device is not represented in the drop-down menu, select a model that conforms closest to the target device. Some drivers support a model selection called "Open," which allows users to communicate without knowing the specific details of the target device. For more information, refer to the driver help documentation.

ID: This property specifies the device's driver-specific station or node. The type of ID entered depends on the communications driver being used. For many communication drivers, the ID is a numeric value. Drivers that support a Numeric ID provide users with the option to enter a numeric value whose format can be changed to suit the needs of the application or the characteristics of the selected communications driver.

The ID format can be Decimal, Octal, and Hexadecimal.

Note: If the driver is Ethernet-based or supports an unconventional station or node name, the device's

TCP/IP address may be used as the device ID. TCP/IP addresses consist of four values that are separated by periods, with each value in the range of 0 to 255. Some device IDs are string based. There may be additional properties to configure within the ID field, depending on the driver. For more information, refer to the driver's help documentation.

Operating Mode

Data Collection: This property controls the device's active state. Although device communications are enabled by default, this property can be used to disable a physical device. Communications are not attempted when a device is disabled. From a client standpoint, the data is marked as invalid and write operations are not accepted. This property can be changed at any time through this property or the device system tags.

Simulated: This option places the device into Simulation Mode. In this mode, the driver does not attempt to communicate with the physical device, but the server continues to return valid OPC data. Simulated stops physical communications with the device, but allows OPC data to be returned to the OPC client as valid data.

While in Simulation Mode, the server treats all device data as reflective: whatever is written to the simulated www. kepware.com

Mitsubishi FX Driver device is read back and each OPC item is treated individually. The item's memory map is based on the group

Update Rate. The data is not saved if the server removes the item (such as when the server is reinitialized).

The default is No.

Notes:

1. This System tag (_Simulated) is read only and cannot be written to for runtime protection. The System tag allows this property to be monitored from the client.

2. In Simulation mode, the item's memory map is based on client update rate(s) (Group Update Rate for

OPC clients or Scan Rate for native and DDE interfaces). This means that two clients that reference the same item with different update rates return different data.

Simulation Mode is for test and simulation purposes only. It should never be used in a production environment.

Device Properties - Scan Mode

The Scan Mode specifies the subscribed-client requested scan rate for tags that require device communications. Synchronous and asynchronous device reads and writes are processed as soon as possible; unaffected by the Scan Mode properties.

12

Scan Mode: specifies how tags in the device are scanned for updates sent to subscribed clients.

Descriptions of the options are: l l

Respect Client-Specified Scan Rate: This mode uses the scan rate requested by the client.

Request Data No Faster than Scan Rate: This mode specifies the maximum scan rate to be used.

The valid range is 10 to 99999990 milliseconds. The default is 1000 milliseconds.

Note: When the server has an active client and items for the device and the scan rate value is increased, the changes take effect immediately. When the scan rate value is decreased, the changes do not take effect until all client applications have been disconnected.

l

Request All Data at Scan Rate: This mode forces tags to be scanned at the specified rate for subscribed clients. The valid range is 10 to 99999990 milliseconds. The default is 1000 milliseconds.

l l

Do Not Scan, Demand Poll Only: This mode does not periodically poll tags that belong to the device nor perform a read to get an item's initial value once it becomes active. It is the client's responsibility to poll for updates, either by writing to the _DemandPoll tag or by issuing explicit device reads for individual items. For more information, refer to "Device Demand Poll" in server help.

Respect Tag-Specified Scan Rate: This mode forces static tags to be scanned at the rate specified in their static configuration tag properties. Dynamic tags are scanned at the client-specified scan rate.

Initial Updates from Cache: When enabled, this option allows the server to provide the first updates for newly activated tag references from stored (cached) data. Cache updates can only be provided when the new item reference shares the same address, scan rate, data type, client access, and scaling properties. A device read is used for the initial update for the first client reference only. The default is disabled; any time a client activates a tag reference the server attempts to read the initial value from the device.

www. kepware.com

13


Device Properties - Timing

The device Communications Timeouts properties allow the driver's response to error conditions to be tailored to fit the application's needs. In many cases, the environment requires changes to these properties for optimum performance. Factors such as electrically generated noise, modem delays, and poor physical connections can influence how many errors or timeouts a communications driver encounters.

Communications Timeouts properties are specific to each configured device.

Communications Timeouts

Connect Timeout: This property (which is used primarily by Ethernet based drivers) controls the amount of time required to establish a socket connection to a remote device. The device's connection time often takes longer than normal communications requests to that same device. The valid range is 1 to 30 seconds. The default is typically 3 seconds, but can vary depending on the driver's specific nature. If this setting is not supported by the driver, it is disabled.

Note: Due to the nature of UDP connections, the connection timeout setting is not applicable when communicating via UDP.

Request Timeout: This property specifies an interval used by all drivers to determine how long the driver waits for a response from the target device to complete. The valid range is 50 to 9,999,999 milliseconds

(167.6667 minutes). The default is usually 1000 milliseconds, but can vary depending on the driver. The default timeout for most serial drivers is based on a baud rate of 9600 baud or better. When using a driver at lower baud rates, increase the timeout to compensate for the increased time required to acquire data.

Retry Attempts: This property specifies how many times the driver retries a communications request before considering the request to have failed and the device to be in error. The valid range is 1 to 10. The default is typically 3, but can vary depending on the driver's specific nature. The number of retries configured for an application depends largely on the communications environment.

Timing

Inter-Request Delay: This property specifies how long the driver waits before sending the next request to the target device. It overrides the normal polling frequency of tags associated with the device, as well as one-time reads and writes. This delay can be useful when dealing with devices with slow turnaround times and in cases where network load is a concern. Configuring a delay for a device affects communications with all other devices on the channel. It is recommended that users separate any device that requires an interrequest delay to a separate channel if possible. Other communications properties (such as communication serialization) can extend this delay. The valid range is 0 to 300,000 milliseconds; however, some drivers may limit the maximum value due to a function of their particular design. The default is 0, which indicates no delay between requests with the target device.

Note: Not all drivers support Inter-Request Delay. This setting does not appear if it is not supported by the driver.

www. kepware.com


Device Properties - Auto-Demotion

The Auto-Demotion properties can temporarily place a device off-scan in the event that a device is not responding. By placing a non-responsive device offline for a specific time period, the driver can continue to optimize its communications with other devices on the same channel. After the time period has been reached, the driver re-attempts to communicate with the non-responsive device. If the device is responsive, the device is placed on-scan; otherwise, it restarts its off-scan time period.

14

Demote on Failure: When enabled, the device is automatically taken off-scan until it is responding again.

Tip: Determine when a device is off-scan by monitoring its demoted state using the _AutoDemoted system tag.

Timeouts to Demote: Specify how many successive cycles of request timeouts and retries occur before the device is placed off-scan. The valid range is 1 to 30 successive failures. The default is 3.

Demotion Period: Indicate how long the device should be placed off-scan when the timeouts value is reached. During this period, no read requests are sent to the device and all data associated with the read requests are set to bad quality. When this period expires, the driver places the device on-scan and allows for another attempt at communications. The valid range is 100 to 3600000 milliseconds. The default is 10000 milliseconds.

Discard Requests when Demoted: Select whether or not write requests should be attempted during the off-scan period. Disable to always send write requests regardless of the demotion period. Enable to discard writes; the server automatically fails any write request received from a client and does not post a message to the Event Log.

Device Properties - Redundancy

Redundancy is available with the Media-Level Redundancy Plug-in.

Consult the website, a sales representative, or the user manual for more information.

Modem Setup

This driver supports modem functionality. For more information, please refer to Modem Support in the server help.

www. kepware.com

15

Mitsubishi FX Driver www. kepware.com



The Mitsubishi FX Driver supports the following data types.

Data

Type

Description

Boolean Single bit

Word Unsigned 16-bit value

Short

Long bit 0 is the low bit bit 15 is the high bit

Signed 16-bit value bit 0 is the low bit bit 14 is the high bit bit 15 is the sign bit

DWord Unsigned 32-bit value bit 0 is the low bit bit 31 is the high bit

Signed 32-bit value

Float bit 0 is the low bit bit 30 is the high bit bit 31 is the sign bit

32-bit Floating point value

String

The driver interprets two consecutive registers as a single precision value by making the last register the high word and the first register the low word.

Null terminated ASCII string

Support includes HiLo LoHi byte order selection and string lengths up to 64 bytes.

16

www. kepware.com

17



Address specifications vary depending on the model in use. Click on a link from the following list to obtain specific address information for the model of interest.

FX Addressing

FX0 Addressing

FX0N Addressing

FX2N Addressing

FX3U Addressing

FX Addressing

The default data types for dynamically defined tags are shown in bold.

Device

Type

Inputs

Outputs

Auxiliary

Relays

Special Aux.

Relays

States

Timer

Contacts

Counter

Contacts

Range

X000-X377*

Y000-Y377*

M0000-M1535

M8000-M8255

S000-S999

TS000-TS255

CS000-CS255

Timer Reset TR000-TR255

Counter

Reset

CR000-CR255

Timer Value T000-T255

Counter

Value

C000-C199

C200-C255 32-bit

Counter

Value**

Data

Registers**

D000-D999

D000-D998

DSH0000.02-DSH0967.64

Data

Registers

String

Access HiLo

Byte

Ordering

Data

Registers

String

The string length may also be specified using a colon. The string length can range from 2 to 64 bytes, and must be an even number.***

DSL0000.02-DSL0967.64

The string length may also be specified using a colon. The

Data Type

Boolean

Boolean

Boolean

Boolean

Boolean

Boolean

Boolean

Boolean

Boolean

Read/Write

Read/Write

Short, Word Read/Write


Long, DWord Read/Write

Access

Read Only

Read/Write

Read/Write

Read/Write

Read/Write

Read Only

Read Only

Short, Word,

Long, DWord,

Float

String

Read/Write

Read/Write

String

Read/Write www. kepware.com


Device

Type

Access LoHi

Byte

Ordering

Special

Data

Registers**

Range

string length can range from 2 to 64 bytes, and must be an even number.***

D8000-D8255

D8000-D8254

Data Type Access

Short, Word,

Long, DWord,

Float

Read/Write

*Octal.

**Users can specify a Long data type by appending a space and an "L" to the address. For example, "D000" would be entered as "D000 L". This does not apply to arrays or bit accessed registers.

***For example, a string with HiLo byte ordering at D10 for a length of 12 bytes would be DSH10.12.

FX0 Addressing


Device

Type

Range

Inputs

Outputs

X000-X017*

Y000-Y15*

Auxiliary

Relays

Special Aux.

Relays

States

M0000-M0511

M8000-M8255

Timer

Contacts

S00-S63

TS00-TS55

Counter

Contacts

CS00-CS15

CS235-CS254


Counter

Reset

CR00-CR15

CR235-CR254

Timer Value T00-T55

Data

Type

Access

Boolean Read Only

Boolean Read/Write








Counter

Value

32-bit

Counter

Value**

Data

Registers**

C00-C15

C235-C254

D00-D31

D00-D30

Data

Registers

String

Short,

Word

Short,

Word

Long,

DWord

Read/Write

Read/Write

Read/Write

DSH0000.02–DSH30.62

The string length may also be specified using a colon. The string

Short,

Word

Long,

DWord,

Float

String

Read/Write

Read/Write

18

www. kepware.com

19


Device

Type

Access HiLo

Byte

Ordering

Data

Registers

String

Access LoHi

Byte

Ordering

Special Data

Registers**

Range

length can range from 2 to 62 bytes, and must be an even number.***

DSL0000.02–DSL30.62


D8000-D8069

D8000-D8068

Data

Type

Access

String

Read/Write

Short,

Word

Long,

DWord,

Float

Read/Write

*Octal.



FX0N Addressing


Device

Type

Range

Inputs

Outputs

X000-X177*

Y000-Y177*

Auxiliary

Relays

Special Aux.

Relays

States

M0000-M0511

M8000-M8255

Timer

Contacts

Counter

Contacts

S000-S127

TS00-TS63

CS00-CS31

CS235-CS254


Counter

Reset

CR00-CR31

CR235-CR254

Timer Value T00-T63

Data

Type

Access










Counter

Value

32-bit

Counter

Value**

C00-C31

C235-C254

Short,

Word

Short,

Word

Long,

DWord

Read/Write

Read/Write



Device

Type

Data

Registers**

Range

D000-D255

D000-D254

Data

Type

Short,

Word

Long,

DWord,

Float

String

Access

Read/Write

Read/Write Data

Registers

String

Access HiLo

Byte

Ordering

Data

Registers

String

Access LoHi

Byte

Ordering

DSH0000.02-DSH223.64


DSL0000.02-DSL223.64


Special Data

Registers**

D8000-D8255

D8000-D8254

String

Read/Write

Short,

Word

Long,

DWord,

Float

Read/Write

*Octal.



FX2N Addressing


Device

Type

Range

Inputs

Outputs

X000-X377*

Y000-Y377*

Auxiliary

Relays

Special Aux.

Relays

States

M0000-M3071

M8000-M8255

Timer

Contacts

Counter

Contacts

S000-S999

TS000-TS255

CS000-CS255



Boolean

Boolean

Boolean

Read Only

Read/Write

Read/Write

Boolean

Boolean

Boolean

Boolean

Boolean

Read/Write

Read/Write

Read Only

Read Only

Read/Write

20

www. kepware.com

21


Device

Type

Range

Counter

Reset

32-bit

Counter

Value**

Data

Registers**

CR000-CR255


Counter

Value

C000-C199

C200-C255

D000-D7999

D000-D7998

Data

Registers

String

Access HiLo

Byte

Ordering

Data

Registers

String

Access

LoHi Byte

Ordering

Special

Data

Registers**

DSH0000.02-DSH7967.64


DSL0000.02-DSL7967.64


D8000-D8255

D8000-D8254


Boolean

Read/Write




Short, Word,

Long, DWord,

Float

String

Read/Write

Read/Write

String

Read/Write

Short, Word,

Long, DWord,

Float

Read/Write

*Octal.



FX3U Addressing


Note: The FX3U model is not supported in Windows CE. It also does not support Ethernet Encapsulation.

Device

Type

Inputs

Outputs

Auxiliary

Relays

Special Aux.

Relays

States

Range

X000-X377*

Y000-Y377*

M0000-M7679

M8000-M8511

S000-S4095


Boolean

Boolean

Boolean

Read Only

Read/Write

Read/Write

Boolean

Boolean

Read/Write



Device

Type

Range

Timer

Contacts

Counter

Contacts

TS000-TS511

CS000-CS255


Counter

Reset

CR000-CR255


Counter

Value

C000-C199

C200-C255 32-bit

Counter

Value**

Data

Registers**

D000-D7999

D000-D7998

Data

Registers

String

Access HiLo

Byte

Ordering

Data

Registers

String

Access LoHi

Byte

Ordering

File

Registers**

DSH0000.02-DSH7967.64


DSL0000.02-DSL7967.64


R000-R32767

R000-R32766

File

Registers

String

Access

HiLo Byte

Ordering

File

Registers

String

Access LoHi

Byte

Ordering

Special

Data

Registers**

RSH0000.02-RSH32735.64


RSL0000.02-RSL32735.64


D8000-D8511

D8000-D8510


Boolean

Read Only

Boolean

Boolean

Boolean

Read Only

Read/Write

Read/Write




Short, Word,

Long, DWord,

Float

String

Read/Write

Read/Write

String

String

Read/Write

Short, Word,

Long, DWord,

Float

String

Read/Write

Read/Write

Read/Write

Short, Word,

Long, DWord,

Float

Read/Write

22

www. kepware.com

23


*Octal.


***For example, a string with HiLo byte ordering at D10 for a length of 12 bytes would be DSH10.12

www. kepware.com


Event Log Messages

The following information concerns messages posted to the Event Log pane in the main user interface.

Consult the server help on filtering and sorting the Event Log detail view. Server help contains many common messages, so should also be searched. Generally, the type of message (informational, warning) and troubleshooting information is provided whenever possible.

24

Received block length does not match expected length. | Received block length = <number>, Expected block length = <number>.

Error Type:

Warning

Possible Cause:

The data type maximum length or the length dictated in the address definition set a range that the results do not fit.

Possible Solution:

Verify the data type is correct and check the address definition for a length definition and correct or update.

Error Mask Definitions

B = Hardware break detected

F = Framing error

E = I/O error

O = Character buffer overrun

R = RX buffer overrun

P = Received byte parity error

T = TX buffer full www. kepware.com

25


Appendix: Ethernet Encapsulation Examples

Note: The following is provided for convenience only. Refer to the manufacturer's documentation for current and official instructions.

Click on a link below for a specific Ethernet encapsulation example.

Using COM-ET10-T Ethernet Module

Using the FX2NC-ENET-ADP Ethernet Module

Using the FX3U-ENET Ethernet Module

Writing Network Parameters to the PLC

Note: Ethernet Encapsulation is not supported by the FX3U device model.

Using COM-ET10-T Ethernet Module

Mitsubishi Electric has an Ethernet module that allows peer-to-peer Ethernet connection to FX1S, FX1N,

FX2NC or FX2NC model controllers. The COM-ET10-T module connects to the controller via the FX1N-CNV-

BD or the FX2N-CNV-BD communications adapter. For equipment information, refer to the FX hardware manual.

Example Parameters

The Module ID is Fixed at ET10

E = 45

T = 54

1 = 31

0 = 30

IP Address: 192.168.108.10

192 = C0

168 = A8

108 = 6C

10 = 0A

Subnet Mask: 255.255.255.0

255 = FF

255 = FF

255 = FF

0 = 00

Gateway IP Address: 192.168.108.01

192 = C0

168 = A8

108 = 6C

1 = 01

UPD Port: 1024

TCP Port1: 1025

TCP Port2: 1026

The module currently supports only connecting to TCP Port 1025.

Mitsubishi FX 2N() Series Ladder

Ladder Logic for initializing the module. The configuration parameters are stored in data registers. Any thousand range with the D register area beginning with D0, D1000, D2000 and etc can be used.

|---| M8002 |--------------[ MOV H81 D8120 ] 'Set communication register

| |--------[ DMOV H45543130 D1000 ] 'Module ID ET10 (Fixed)

| |-------[ DMOV H0C0A86C0A D1002 ] 'Module IP Address

| |-------[ DMOV H0FFFFFF00 D1004 ] 'Subnet Mask

| |-------[ DMOV H0C0A86C01 D1006 ] 'Gateway IP Address www. kepware.com


| |-------------[ MOV K1024 D1008 ] 'UDP Port Number

| |-------------[ MOV K1025 D1009 ] 'TCP Port Number 1

| |-------------[ MOV K1026 D1010 ] 'TCP Port Number 2

| |----------------[ MOV K0 D1011 ] 'System Area Default Value 0



| |----------------[ 'System Area Default Value 0


Note: This information has been taken from the Mitsubishi Electric Ethernet Communications Module COM

ET10-T manual.

Using the FX2NC-ENET-ADP Ethernet Module

Mitsubishi has an Ethernet module that allows peer to peer Ethernet connection to FX1S, FX1N, FX2NC or

FX2NC model controllers. The FX2NC-ENET_ADP module connects to the controller via the FX1N-CNV-BD or the FX2N-CNV-BD communications adapter. For equipment information, refer to the FX hardware manual.

Example Parameters

The Module ID is Fixed at ENET

E = 45

N = 4E

E = 45

T = 54

IP Address: 192.168.108.10

192 = C0

168 = A8

108 = 6C

10 = 0A

Subnet Mask: 255.255.255.0

255 = FF

255 = FF

255 = FF

0 = 00

Gateway IP Address: 192.168.108.01

192 = C0

168 = A8

108 = 6C

1 = 01

TCP Port: 1024

Mitsubishi FX1s Series Ladder

Ladder Logic for initializing the module on a FX1s. Set the Ethernet parameters in 9 data registers starting from D128 to D136.

|---| M8002 |-----------[ DMOV H454E4554 D128 ] 'Module ID ENET (Fixed)



| |-------[ DMOV H0C0A86C01 D134 ] 'Gateway IP Address

| |-------------[ MOV K1024 D136 ] 'TCP Port Number

Mitsubishi FX1N/2N/2NC Series Ladder

Ladder Logic for initializing the module on a FX1s. Set the Ethernet parameters in 9 data registers starting from D1000 to D1008. If these registers are used for other purposes, set to 9 data registers starting at

D2000, D3000, D4000, D5000, D6000 or D7000.

|---| M8002 |-----------[ DMOV H454E4554 D1000 ] 'Module ID ENET (Fixed)



| |-------[ DMOV H0C0A86C01 D1006 ] 'Gateway IP Address

| |-------------[ MOV K1024 D1008 ] 'TCP Port Number

26

www. kepware.com

27


Note: This information has been taken from the Mitsubishi FX2NC-ENET-ADP Ethernet Adapter Users manual.

Using the FX3U-ENET Ethernet Module

To connect to the FX3U PLC via the FX3U-ENET Ethernet module, use Ethernet Encapsulation. In order to do so, the FX3U-ENET module must be configured using the Mitsubishi GX Developer-FX software. For more information, follow the instructions below.

1. To start, create a new GX Developer project for a FX3U model.

2. Then, select Tools | FX special functions utility | FX Configurator-EN.

www. kepware.com


3. The FX Configurator-EN dialog should appear as shown below.

28

4. Next, fill in the minimum required configuration information for the FX3U-ENET block. Select a module from the first drop-down list, and then click Operational Settings. The settings should be similar to those shown in the image below.

www. kepware.com

29


5. Click End to continue.

6. In the FX Configurator-EN dialog window, click Open Settings.

Writing Network Parameters to the PLC

After the network parameters have been specified, they must be written to the PLC. To do so, click Write from the FX-Configurator-EN window.

www. kepware.com


There must be a serial connection to the FX3U PLC because the configuration settings are written to the PLC via this serial link. Make sure that the communication parameters are correct by using the Transfer setup button above or by clicking Online | Transfer setup from the main menu.

After the parameters have been written, cycle the power on the PLC for the network parameter changes to take effect. Now, the FX3U PLC can be communicated with using Ethernet encapsulation via the FX3U-ENET

Ethernet module. Use the following parameters: l

IP Address: 10.10.110.107 (or the IP address used above) l l

Port Number: 5551

Protocol: TCP/IP

30

www. kepware.com

31

Index

A

Address Descriptions 17

Address specifications 17

Advanced Channel Properties 9

Appendix

Ethernet Encapsulation 25

Auto Dial 8

Auxiliary Relays 17-21

B

Baud Rate 7

Boolean 16

Buffer full 24

Buffer overrun 24

C

Channel Assignment 11

Channel Properties 5

Channel Properties - General 5

Channel Properties - Write Optimizations 8

Close Idle Connection 7-8

COM-ET10-T Module 25

COM ID 7

Communication Protocol 4

Communications Timeouts 13

Connect Timeout 13

Connection Type 6

Counter 17-20, 22

D

Data Bits 7

Data Collection 11

www. kepware.com



Data Registers 17-18, 20-22

Data Types Description 16

Demote on Failure 14

Demotion Period 14

Description 11

Device ID 4

Device Properties 10

Device Properties - Auto-Demotion 14

Device Properties - General 10

Diagnostics 6

Discard Requests when Demoted 14

Do Not Scan, Demand Poll Only 12

Driver 5, 11

Duty Cycle 9

DWord 16

E

Error Mask Definitions 24

Ethernet Encapsulation 4

Event Log Messages 24

F

Float 16

Flow Control 4, 7

Framing 24

FX Addressing 17

FX0 Addressing 18

FX0N Addressing 19

FX2N Addressing 20

FX2NC-ENET-ADP Module 26

FX3U-ENET Module 27

FX3U Addressing 21

H

Hardware break 24

www. kepware.com

32

33

I

I/O error 24

ID 11

Idle Time to Close 7-8

IEEE-754 floating point 9

Initial Updates from Cache 12

Inputs 17-21

Inter-Request Delay 13

L

Long 16

M

Mitsubishi FX 2N() Series Ladder 25

Mitsubishi FX1N/2N/2NC Series Ladder 26

Mitsubishi FX1s Series Ladder 26

Model 11

Modem 8

Modem Setup 14

N

Name 11

Network 4

Network Adapter 8

Non-Normalized Float Handling 9

O

Operational Behavior 7

Optimization Method 9

Outputs 17-21

Overrun 24

Overview 3

www. kepware.com



P

Parity 7, 24

Physical Medium 6

R

Read Processing 8

Received block length does not match expected length. | Received block length = <number>, Expected

block length = <number>. 24

Redundancy 14

Registers 17

Report Comm. Errors 7-8

Request All Data at Scan Rate 12

Request Data No Faster than Scan Rate 12

Request Timeout 13

Reset 17-20, 22

Respect Client-Specified Scan Rate 12

Respect Tag-Specified Scan Rate 12

Retry Attempts 13

S

Scan Mode 12

Serial Communications 6

Serial Port Settings 7

Setup 4

Short 16

Simulated 11

Special Aux. Relays 17-21

States 17-21

Stop Bits 7

String 16

Supported Communication Parameters 4

Supported Devices 4

T

Timeouts to Demote 14

www. kepware.com

34

35

Timer 17-20, 22

W

Word 16

Write All Values for All Tags 9

Write Only Latest Value for All Tags 9

Write Only Latest Value for Non-Boolean Tags 9

Write Optimizations 8

Mitsubishi FX Driver www. kepware.com

No results