Toyopuc PC3, PC2 User Manual
Toyopuc PC3/PC2 Ethernet Driver
© 2016 PTC Inc. All Rights Reserved.
Toyopuc PC3/PC2 Ethernet Driver
Table of Contents
2
Toyopuc PC3/PC2 Ethernet Driver
Table of Contents
Toyopuc PC3/PC2 Ethernet Driver
Overview
Setup
Channel Properties - General 6
Channel Properties - Ethernet Communications 7
Channel Properties - Write Optimizations 8
Channel Properties - Advanced 9
Device Properties - General 9
Device Properties - Scan Mode 11
Device Properties - Timing 12
Device Properties - Communications Parameters 13
Device Properties - Redundancy 13
Diagnostics Tags
Multi-Point Read Support
Data Type Description
1
2
4
4
5
14
15
19
Address Descriptions
PC2/PC2 Interchange Mode Address Descriptions
PC3 Address Descriptions
PC10G Address Descriptions
Error Descriptions
Address Validation
Missing address. 31
Device address <address> contains a syntax error. 31
Address <address> is out of range for the specified device or register 31
Data Type <type> is not valid for device address <address>. 32
Device address <address> is read only. 32
Array size is out of range for address <address>. 32
Array support is not available for the specified address: <address>. 32
Device Status Messages
Device <device name> is not responding. 33
Unable to write to <address> on device <device name>. 33
Device Error Codes
20
20
22
26
31
31
33
34
Error Response Data: Error Code Table 34
Appendix: Configuring Modules
www. kepware.com
36
3
Toyopuc PC3/PC2 Ethernet Driver
Configuring the PC10G-CPU for Ethernet Communications
Configuring the FL/ET-T-V2 Ethernet Module
Configuration Ladder for EN-I/F Ethernet Module
Index
36
41
46
48
www. kepware.com
Toyopuc PC3/PC2 Ethernet Driver
Toyopuc PC3/PC2 Ethernet Driver
Help version 1.042
CONTENTS
Overview
What is the Toyopuc PC3/PC2 Ethernet Driver?
Device Setup
How do I configure a device for use with this driver?
Data Types Description
What data types does this driver support?
Address Descriptions
How do I address a data location on a Toyopuc PC3/PC2 Ethernet device?
Error Descriptions
What error messages does the Toyopuc PC3/PC2 Ethernet Driver produce?
4
Overview
The Toyopuc PC3/PC2 Ethernet Driver provides a reliable way to connect Toyopuc PC3/PC2 Ethernet devices
to OPC client applications; including HMI, SCADA, Historian, MES, ERP, and countless custom applications. It
is intended for use with Toyopuc PC3, PC2 and PC10G series PLCs using the Ethernet communications
interface. The Toyopuc PC3/PC2 Ethernet Driver supports extensive diagnostics tags and the Toyopuc
PC3/PC2 multi-point read features. For more information, refer to Diagnostics Tags and Multi-Point Read
Support .
www. kepware.com
5
Toyopuc PC3/PC2 Ethernet Driver
Setup
Supported Devices
Toyopuc PC3, PC2 and PC10G series
The PC2 model selection can be used with PC3 > PLCs operating in the PC2 Interchange mode.
Note: This driver is limited to 1024 devices.
Communication Protocol
Toyopuc PC3/PC2 Ethernet Computer Link Protocol
Connection Timeout
This property specifies the time that the driver will wait for a connection to be made with a device.
Depending on network load, the connect time may vary with each connection attempt. The default setting is
5 seconds. The valid range is 1 to 30 seconds.
Note: Making a connection with a device can be very time consuming. When connecting with multiple
devices located at different IP addresses or port numbers, define an additional Toyopuc Ethernet channel in
the OPC Server project for this unique device. Connecting to multiple devices using the Relay Command
through a single IP and port number will not cause a new connection to be opened and will not incur a
connection delay.
Port Number
This property specifies the port number that will be used to connect to the Toyopuc PLC. The Toyopuc EN-I/F
Ethernet PC3/PC2 module supports eight ports for communications. Each port must be dedicated to a single
connection. When specifying a port number, ensure that no other Ethernet node will attempt to use this port
number on the target Toyopuc PLC. The same port number can be used when communicating with multiple
Toyopuc PLCs.
Device IDs
The Device ID, specified as YYY.YYY.YYY.YYY[P1,L1, S1, L2, S2, P3, L3, S3], is used to specify the Device IP
address along with Relay Command Link/Exchange information on the Ethernet network. YYY designates the
Device IP address: each YYY byte should be in the range of 0 to 255.
Note: A request can be relayed through one device to another device configured with the same link
module, such as HPC-Link or FL-net. This relay connection is established by appending a link/exchange path
to the device IP address. The following image illustrates the use of the routing path between HPC-linked
devices:
www. kepware.com
Toyopuc PC3/PC2 Ethernet Driver
6
A routing command can only be issued through a maximum of four devices. Routing allows the Ethernet
driver to request data from non-Ethernet devices. To request data from Device 3, the driver can route a
command through Device 1 onto Device 2 then to Device 3.
Examples
1. Defining a Device ID to request data from Device 1. Device ID: 205.167.7.101.
2. Defining a Device ID to request data from Device 3. Device ID: 205.167.7.101[L1,S1,L2,S2].
Note: Lx and Sx represent the Link/Station numbers assigned to a device. . Consult the Toyopuc PC2 EN-I/F
manual, HPC Link manual, or FL/ET-T-V2H manual for more information on link/station numbers.The L and S
must be included as part of the Relay routing information when specifying a Device ID. The Px represents the
program number for PC3J systems. The Px value should precede the link variable on each layer of the route.
Example
Device ID: 205.167.7.101[P2,L1,S1,P1,L2,S2].
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.
www. kepware.com
7
Toyopuc PC3/PC2 Ethernet Driver
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 OPCserver'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.
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 - Ethernet Communications
Ethernet Communication can be used to communicate with devices.
Ethernet Settings
www. kepware.com
Toyopuc PC3/PC2 Ethernet Driver
Network Adapter:Specify the network adapter to bind. When Default is selected, the operating system
selects the default adapter.
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
OptimizationMethod: controls how write data is passed to the underlying communications driver. The
options are:
8
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.
www. kepware.com
9
Toyopuc PC3/PC2 Ethernet Driver
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-aNumber (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:
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.
l Unmodified:This option allows a driver to transfer IEEE-754 denormalized, normalized, non-
number, 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 - 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.
www. kepware.com
Toyopuc PC3/PC2 Ethernet Driver
Identification
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.
10
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
www. kepware.com
11
Toyopuc PC3/PC2 Ethernet Driver
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
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.
Scan Mode: specifies how tags in the device are scanned for updates sent to subscribed clients.
Descriptions of the options are:
l Respect Client-Specified Scan Rate:This mode uses the scan rate requested by the client.
l 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.
www. kepware.com
Toyopuc PC3/PC2 Ethernet Driver
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.
l 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.
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.
12
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.
www. kepware.com
13
Toyopuc PC3/PC2 Ethernet Driver
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.
Device Properties - Communications Parameters
Port Number: Specify the port number to be used to connect to the Toyopuc PLC. The Toyopuc EN-I/F
Ethernet PC3/PC2 module supports eight ports for communications. Each port must be dedicated to a single
connection. When specifying a port number, ensure that no other Ethernet node will attempt to use this port
number on the target Toyopuc PLC. The same port number can be used when communicating with multiple
Toyopuc PLCs.
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.
www. kepware.com
Toyopuc PC3/PC2 Ethernet Driver
Diagnostics Tags
Diagnostics Tags provide information on how the Toyopuc PC3/PC2 Ethernet Driver is performing at both
the channel level and device level. At the channel level, diagnostics tags provide information that covers all
operations performed by the driver when communicating with any PLC on the network. At the device level,
diagnostics tags provide information that pertains only to the device under which the diagnostic tags have
been requested.
Channel-Level Diagnostics Tags
Tag Name Functional Description
ChannelReadTime Contains the amount of time in milliseconds required to read all currently
active data for all devices on this channel. This value is a signed long.
ChannelHighTime Contains the amount of time in milliseconds of longest read cycle. This value
is a signed long.
ChannelLowTime Contains the amount of time in milliseconds of shortest read cycle. This value
is a signed long.
ChannelReadsPerformed Contains a count of the reads performed on this channel for all devices. This
is a signed long and will roll over.
ChannelWritesPerformed Contains a count of the writes performed on this channel for all devices. This
is a signed long and will roll over.
ChannelTimeouts Contains a count of the number of timeout/message failures that have
occurred for all devices. The _ChannelTimeouts count is for any error that
may occur on a message attempt. The value does not necessarily indicate
how many messages failed to be sent altogether. It should be used to
diagnose possible communication issues with specific devices. This is a
signed long and will roll over.
14
Device-Level Diagnostics Tags
Tag Name Functional Description
DeviceReadTime Contains the amount of time in milliseconds required to read a block of data
from the specified device. This value is a signed long.
DeviceHighTime Contains the longest amount of time in milliseconds required to read a block of
data from the specified device. This value is a signed long.
DeviceLowTime Contains the shortest amount of time in milliseconds required to read a block
of data from the specified device. This value is a signed long.
DeviceReadsPerformed Contains a count of the reads performed on this device. This is a signed long
and will roll over.
DeviceWritesPerformed Contains a count of the writes performed on this device. This is a signed long
and will roll over.
DeviceTimeouts Contains a count of the number of timeout/message failures that have
occurred on the specified device. The _ DeviceTimeouts count is for any error
that may occur on a message attempt. The value does not necessarily indicate
how many messages failed to be sent altogether. It should be used to diagnose
possible communication issues with this specific device. This is a signed long
and will roll over.
DeviceMultiPointReads Contains a count of the number of multi-point read requests that are currently
being used to acquire all data that is marked for multi-point operation. This tag
can be used to tune multi-point read operation. The goal of course being to
limit the number of multi-point reads being done to the lowest count possible,
www. kepware.com
15
Toyopuc PC3/PC2 Ethernet Driver
Tag Name Functional Description
preferably 1. This is a signed long and will roll over.
Note: All diagnostics tags are Read/Write. The only value that can be written to the tags is zero (which will
clear or reset them).
Multi-Point Read Support
The Toyopuc PLC supports the ability to read data spread randomly throughout the PLC using a single
command. By using this command, users can read crucial data items quickly and efficiently. The Toyopuc
PC3/PC2 Ethernet Driver automatically attempts to make the use of the multi-point command both easy and
efficient. Any memory type that can be acquired by the Toyopuc PC3/PC2 Ethernet Driver can be part of a
multi-point read command. To mark a particular data item to be part of a multi-point request, place the '#'
character in front of any current address. The table below is shown with the addition of the '#' character to
each address. For information on the maximum data that can be read with a multi-point command, refer to
Multi-Point Limitations.
There are some things that should be considered when using the multi-point read functions. The multi-point
command can increase the speed of the data acquisition but if overused, it will need to make multiple multipoint commands to read all the requested data. When this occurs, the overall performance of the driver will
be reduced. The key is to use the multi-point command wisely.
The driver will automatically group data from memory types like bit memory into 16 bit values. For example,
for the PC3 model, if P1-X1, P1-X3, P1-X4, P1-X6, P1-X9, P1-XA, P1-XB are marked as part of a multi-point
read using the '#', users would enter an address of #P1-X1, #P1-X3, #P1-X4, #P1-X6, #P1-X9, #P1-XA, #P1XB. These seven items would be placed into a single 16 bit value; therefore, users would use only one of the
128 16 bit values available in a single multi-point read command. The 7 items were grouped together
because the address of each bit fell within a single 16 bit word value of X memory. If 7 items like #P1-X1,#P1X20,#P1-X55,#P1-X77,#P1-X99,#P1-XAA,#P1-XBB are entered as part of a multi-point read, each bit in this
case would require an entire 16 bit value in the multi-point read command to receive the data. Plan the data
usage in the controller. If possible, make sure that the bits being read are grouped closely. This prudent
planning applies primarily to the bit memory types. Register memory requires a single 16 bit value (two 16
bit values in the case of DWords) for each register that is added to the multi-point read.
By using this information, users can plan the multi-point reads. The Toyopuc PC3/PC2 Ethernet Driver can
perform as many multi-point reads as are needed to acquire all the data that has been marked for multipoint operation. Remember, however, that the driver will run slower when there are many read being run. To
determine how many multi-point read requests the Toyopuc Ethernet PC3PC2 driver is using to acquire all
currently defined multi-point data, use the special diagnostic tag "_DeviceMultiPointReads". For more
information on this tag, refer to Diagnostics.
The multi-point read operation can be combined with the normal data reads of the Toyopuc PC3/PC2
Ethernet Driver. For example, if a block of 50 D registers consecutively ordered is being read, it may be
more efficient to read the 50 D registers as part of a normal block read and save the space in the multi-point
read function for data that is spread more randomly throughout the PLC memory. Use the diagnostics tags
to help determine the most efficient way of acquiring the data for the application.
Multi-Point Limitations
For tags belonging to device models PC3 Device and PC10G Device, the maximum data requested for the
data types are as follows:
Boolean: 1024*
www. kepware.com
Toyopuc PC3/PC2 Ethernet Driver
Byte: 128
Word: 64
DWord: 32
*If contiguous Booleans are requested, the request will be done in one multi-point read.
Combination of any of the above data types in a single multi request has to be within the following limit:
(No. of Booleans/16) + (No. of Bytes/2) + No. of Words + (No. of DWords * 2) <= 64
For tags belonging to device model PC2/PC2 Interchange, the maximum data requested for the data types
are as follows:
Boolean: 2048*
Byte: 256
Word: 128
DWord: 64
*If contiguous booleans are requested, the request will be done in one multi-point read.
Combination of any of the above data types in a single multi request has to be within the following limit:
(No. of Booleans/16) + (No. of Bytes/2) + No. of Words + (No. of DWords * 2) <= 128
16
Memory Types Shown with the Multi-Point Marker
Memory Type Syntax Data Types Access
Edge Relay (P) #P0000-#P01FF
#P000-#P01F
#P000-#P01E
Keeping Relay (K) #K0000-#K02FF
#K000-#K02F
#K000-#K02E
Specific Relay (V) #V0000-#V00FF
#V000-#V0F
#V000-#V0E
Timer Bits (T) #T0000-#T01FF
#T000-#T01F
#T000-#T01E
Count Bits (C) #C0000-#C01FF
#C000-#C01F
#C000-#C01E
Link Relay (L) #L0000-#L07FF
#L000-#L07F
#L000-#L07E
I/O Relay (X) #X0000-#X07FF
#X000-#X07F
#X000-#X07E
I/O Relay (Y) #Y0000-#Y07FF
#Y000-#Y07F
#Y000-#Y07E
Internal Relay (M) #M0000-#M07FF
#M000-#M07F
#M000-#M07E
Boolean
Byte, Word, Short, BCD DWord, Long,
LBCD
Boolean
Byte, Word, Short, BCD DWord, Long,
LBCD
Boolean
Byte, Word, Short, BCD DWord, Long,
LBCD
Boolean
Byte, Word, Short, BCD
DWord, Long, LBCD
Boolean
Byte, Word, Short, BCD DWord, Long,
LBCD
Boolean
Byte, Word, Short, BCD DWord, Long,
LBCD
Boolean
Byte, Word, Short, BCD DWord, Long,
LBCD
Boolean
Byte, Word, Short, BCD DWord, Long,
LBCD
Boolean
Byte, Word, Short, BCD DWord, Long,
LBCD
Read/Write
Read/Write
Read/Write
Read/Write
Read/Write
Read/Write
Read/Write
Read/Write
Read/Write
www. kepware.com
Loading...