0% found this document useful (0 votes)

98 views71 pages

Ge SNPX Manual

Uploaded by

Garcia

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

98 views71 pages

Ge SNPX Manual

Uploaded by

Garcia

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 71

GE SNPX Driver

© 2020 PTC Inc. All Rights Reserved.

GE SNPX Driver 2

Table of Contents
GE SNPX Driver 1

Table of Contents 2

GESNPX Driver 6

Overview 6

Setup 6
Channel Properties — General 7
Channel Properties — Serial Communications 8
Channel Properties — Write Optimizations 10
Channel Properties — Advanced 11
Channel Properties — Communication Serialization 12
Device Properties — General 13
Operating Mode 14
Device Properties — Scan Mode 15
Device Properties — Timing 16
Device Properties — Auto-Demotion 17
Device Properties — Tag Generation 17
Device Properties — Redundancy 19
Device Properties — Variable Import Settings 20

Data Types Description 21

Address Descriptions 22
GE Micro 22
311 Addressing 23
313 Addressing 24
331 Addressing 25
341 Addressing 26
350 Addressing 27
360 Addressing 28
731 Addressing 29
732 Addressing 29
771 Addressing 30
772 Addressing 31
781 Addressing 32
782 Addressing 33
GE OPEN Addressing 34
Advanced Addressing 35

Automatic Tag Database Generation 36

www. ptc.com
3 GE SNPX Driver

Tag Hierarchy 37

Import File-to-Server Name Conversions 37

Importing VersaPro Tags 38

VersaPro Import Preparation: VersaPro Steps 39
VersaPro Import Preparation: OPC Server Steps 40
Highlighting VersaPro Variables 40
VersaPro Array Tag Import 41

Importing LogicDeveloper Tags 42

LogicDeveloper Import Preparation: LogicDeveloper Steps 42
LogicDeveloper Import Preparation: OPC Server Steps 44
Highlighting LogicDeveloper Variables 45
LogicDeveloper Array Tag Import 45

Importing Proficy Logic Developer Tags 45

Proficy Logic Developer Import Preparation: Logic Developer Steps 46
Proficy Logic Developer Import Preparation: OPC Server Steps 47
Highlighting Proficy Logic Developer Variables 48
Proficy Logic Developer Array Tag Import 48

Error Descriptions 49
Missing address 51
Device address '<address>' contains a syntax error 51
Address '<address>' is out of range for the specified device or register 51
Device address '<address>' is not supported by model '<model name>' 52
Data Type '<type>' is not valid for device address '<address>' 52
Device address '<address>' is Read Only 52
Array size is out of range for address '<address>' 52
Array support is not available for the specified address: '<address>' 53
COMn does not exist 53
Error opening COMn 53
COMn is in use by another application 53
Unable to set comm parameters on COMn 54
Communications error on '<channel name>' [<error mask>] 54
Device '<device name>' not responding 54
Unable to write to '<address>' on device '<device name>' 55
Invalid tag in block starting at <address> on device <device name>. Block deactivated 55
Unable to write to tag '<tag address>' on device '<device name>'. The service requested is either
not defined or not supported 56
Unable to write to tag '<tag address>' on device '<device name>'. The user does not have suf-
ficient privileges to process the request. Minor status error code = '<hexadecimal error code>' 56
Unable to write to tag '<tag address>' on device '<device name>'. The CPU has received a mes- 56

www. ptc.com
GE SNPX Driver 4

sage that is out of order

Unable to write to tag '<tag address>' on device '<device name>'. Service request error. Minor
status error code = '<hexadecimal error code>' 56
Unable to write to tag '<tag address>' on device '<device name>'. The PLC CPU's service request
queue is full: please wait a minimum of 10 ms before sending another service request 57
Unable to write to tag '<tag address>' on device '<device name>'. A framing error has occurred 57
Unable to write to tag '<tag address>' on device '<device name>'. Device returned major error
code '<hexadecimal error code>' and minor error code '<hexadecimal error code>' 57
Unable to read ' <number of bytes>' bytes starting at address '<tag address>' on device '<device
name>'. The service requested is either not defined or not supported 58
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device
name>'. The user does not have sufficient privileges to process the request. Minor status error
code = '<hexadecimal error code>' 58
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device
name>'. The CPU has received a message that is out of order 58
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device
name>'. Service request error. Minor status error code = '<hexadecimal error code>' 59
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device
name>'. The PLC CPU's service request queue is full: please wait a minimum of 10 ms before
sending another service request 59
Unable to read '<byte count>' bytes starting at address '<start tag>' on device '<device name>'. A
framing error has occurred 59
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device
name>'. Device returned major error code '<hexadecimal error code>' and minor error code
'<hexadecimal error code>' 60
Unable to read tag '<tag address>' on device '<device name>'. The service requested is either not
defined or not supported 60
Unable to read tag '<tag address>' on device '<device name>'. The user does not have sufficient
privileges to process the request. Minor status error code = '<hexadecimal error code>' 60
Unable to read tag '<tag address>' on device '<device name>'. The CPU has received a message
that is out of order 60
Unable to read tag '<tag address>' on device '<device name>'. Service request error. Minor
status error code = '<hexadecimal error code>' 61
Unable to read tag '<tag address>' on device '<device name>'. The PLC CPU's service request
queue is full: please wait a minimum of 10 ms before sending another service request 61
Unable to read tag '<tag address>' on device '<device name>'. A framing error has occurred 61
Unable to read tag '<tag address>' on device '<device name>'. Device returned major error code
'<hexadecimal error code>' and minor error code '<hexadecimal error code>' 62
Unable to generate a tag database for device <device name>. Reason: Low memory resources 62
Unable to generate a tag database for device <device name>. Reason: Import file is invalid or cor-
rupt 62
Database Error: Tag '<orig. tag name>' exceeds 256 characters. Tag renamed to '<new tag
name>' 63

www. ptc.com
5 GE SNPX Driver

Database Error: Array tags '<orig. tag name><dimensions>' exceed 256 characters. Tags
renamed to '<new tag name><dimensions>' 63
Database Error: Datatype '<type>' for tag '<tag name>' is currently not supported. Tag not cre-
ated 63
Database Error: Datatype '<type>' for tag '<tag name>' not found in import file. Setting to default 64
Database Error: Logic Developer Variable Arrays are currently not supported. Array Tag(s)
'<array tag name>' not created 64
Database Error: No Reference Address found for tag '<tag name>' in import file. Tag not created 64
Database Error: Only variables with Data Source '<data source name>' are imported. Data
Source '<data source name>' is not supported. Tag '<tag name>' not created 65
Database Error: Data type '<type>' arrays are currently not supported. Tag '<array tag name>'
not created 65

Index 66

www. ptc.com
GE SNPX Driver 6

GE SNPX Driver
Help version 1.031

CONTENTS

Overview
What is the GE SNPX Driver?

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

Dat a Types Descript ion

What data types does this driver support?

Address Descript ions

How do I address a data location on a GE SNPX device?

Aut omat ic Tag Dat abase Generat ion

How can I easily configure tags for the GE SNPX Driver?

Error Descript ions

What error messages does the GE SNPX Driver produce?

Overview
The GE SNPX Driver provides a reliable way to connect GE SNPX controllers to OPC Client applications,
including HMI, SCADA, Historian, MES, ERP and countless custom applications. This driver is intended for use
with GE Programmable Logic Controllers.

Set up
Supported Devices
Series GE Micro
Series 90-30 311/313, 331/341, 350,360
Series 90-70 731/732, 771/772, 781/782
GE-OPEN Wide range model support

Communication Protocol
GE SNPX

Supported Communication Parameters

Baud Rate: 300, 600, 1200, 2400, 9600 and 19200
Parity: Odd, None
Data Bits: 8
Stop Bits: 1
N ote: Not all devices support the listed configurations.

Channel and Device Limits

www. ptc.com
7 GE SNPX Driver

The maximum number of channels supported by this driver is 100. The maximum number of devices sup-
ported by this driver is 128 per channel.

Device IDs
Series 90-30 PLCs support up to 6-character strings (such as 1 and Ge3).
Series 90-70 PLCs support up to 7-character strings (such as 1, Ge7 and Ge).
N ote: For peer-to-peer communications an empty string is a valid Node ID.

Flow Control
When using an RS232/RS485 converter, the type of flow control that is 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 to determine its flow requirements. An RS485 converter that provides automatic
flow control is recommended.
N ote: Peer-to-peer communications requires RTS-Always flow control.

Automatic Tag Database Generation

For more information, refer to Variable Im port Settings.

Cabling
Follow the manufacturer's suggested cabling for the communications port and communications module.

Channel Propert ies — 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 com-
munications 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

N am e: 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. The prop-
erty is required for creating a channel.
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. The property is required for cre-
ating a channel.

www. ptc.com
GE SNPX Driver 8

N ote: 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 re-
acquire 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 pro-
cessing, it is recommended that they be utilized when needed and disabled when not. The default is dis-
abled.
N ote: This property is not available if the driver does not support diagnostics.
For more information, refer to "Communication Diagnostics" and "Statistics Tags" in the server help.

Channel Propert ies — Serial Com m unicat ions

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.

N ote: 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 tem-
porarily disrupt communications.

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 N one: Select None to indicate there is no physical connection, which displays the Operation with no
Com m unications section.
l COM Port: Select Com Port to display and configure the Serial Port Settings section.

www. ptc.com
9 GE SNPX Driver

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
Ethernet Settings section.
l Shared: Verify the connection is correctly identified as sharing the current configuration with another
channel. This is a read-only property.

Serial Port Settings

COM ID: Specify the Communications ID to be used when communicating with devices assigned to the chan-
nel. 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 N one: This option does not toggle or assert control lines.

l DTR: This option asserts the DTR line when the communications port is opened and remains on.
l RTS: This option specifies that the RTS line is high if bytes are available for transmission. After all buf-
fered bytes have been sent, the RTS line is low. This is normally used with RS232/RS485 converter
hardware.
l 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 com-
munication does not support echo suppression, it is recommended that echoes be disabled or a RS-485 con-
verter be used.

Operational Behavior

www. ptc.com
GE SNPX Driver 10

l Report Com m unication 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 ref-
erenced by a client on the channel. The default is Enable.
l Idle Tim e 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.

Ethernet Settings
N ote: Not all serial drivers support Ethernet Encapsulation. If this group does not appear, the functionality
is not supported.

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 prop-
erly configured to match the requirements of the serial device to which it is attached. For more information,
refer to "Using Ethernet Encapsulation" in the server help.

l N etwork 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.

M odem Settings
l Modem : Specify the installed modem to be used for communications.
l Connect Tim eout: 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 Com m unication 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 Tim e 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 w ith 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 fail-
ure. The default setting is Ignore.

Channel Propert ies — Writ e Opt im izat ions

As with any 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,

www. ptc.com
11 GE SNPX Driver

the server provides optimization properties that can be used to meet specific needs or improve application
responsiveness.

Write Optimizations

Optim ization 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 applic-
ations 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 N on-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.
N ote: 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 optim-
ization for applications with continuous writes versus a more balanced back and forth data flow.
N ote: It is recommended that the application be characterized for compatibility with the write optimization
enhancements before being used in a production environment.

Channel Propert ies — 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.

www. ptc.com
GE SNPX Driver 12

N on-N orm alized Float Handling: 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. Non-normalized float handling allows users to specify how a driver handles non-nor-
malized IEEE-754 floating point data. Descriptions of the options are as follows:

l Replace with Zero: This option allows a driver to replace non-normalized IEEE-754 floating point val-
ues with zero before being transferred to clients.
l Unm odified: This option allows a driver to transfer IEEE-754 denormalized, normalized, non-num-
ber, and infinity values to clients without any conversion or changes.

N ote: This property is not available 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.

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.

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

Channel Propert ies — Com m unicat ion Serializat ion

The server's multi-threading architecture allows channels to communicate with devices in parallel. Although
this is efficient, communication can be serialized in cases with physical network restrictions (such as Eth-
ernet radios). Communication serialization limits communication to one channel at a time within a virtual net-
work.

The term "virtual network" describes a collection of channels and associated devices that use the same
pipeline for communications. For example, the pipeline of an Ethernet radio is the master radio. All channels
using the same master radio associate with the same virtual network. Channels are allowed to communicate
each in turn, in a "round-robin" manner. By default, a channel can process one transaction before handing
communications off to another channel. A transaction can include one or more tags. If the controlling chan-
nel contains a device that is not responding to a request, the channel cannot release control until the trans-
action times out. This results in data update delays for the other channels in the virtual network.

Channel-Level Settings

www. ptc.com
13 GE SNPX Driver

Virtual N etwork: This property specifies the channel's mode of communication serialization. Options
include None and Network 1 - Network 500. The default is None. Descriptions of the options are as follows:

l N one: This option disables communication serialization for the channel.

l N etwork 1 - N etwork 500: This option specifies the virtual network to which the channel is
assigned.

Transactions per Cycle: This property specifies the number of single blocked/non-blocked read/write trans-
actions that can occur on the channel. When a channel is given the opportunity to communicate, this is the
number of transactions attempted. The valid range is 1 to 99. The default is 1.

Global Settings
l N etwork Mode: This property is used to control how channel communication is delegated. In Load
Balanced mode, each channel is given the opportunity to communicate in turn, one at a time. In Pri-
ority mode, channels are given the opportunity to communicate according to the following rules
(highest to lowest priority):
l Channels with pending writes have the highest priority.
l Channels with pending explicit reads (through internal plug-ins or external client interfaces)
are prioritized based on the read's priority.
l Scanned reads and other periodic events (driver specific).
The default is Load Balanced and affects all virtual networks and channels.

Devices that rely on unsolicited responses should not be placed in a virtual network. In situations where
communications must be serialized, it is recommended that Auto-Demotion be enabled.

Due to differences in the way that drivers read and write data (such as in single, blocked, or non-blocked
transactions); the application's Transactions per cycle property may need to be adjusted. When doing so,
consider the following factors:

l How many tags must be read from each channel?

l How often is data written to each channel?
l Is the channel using a serial or Ethernet driver?
l Does the driver read tags in separate requests, or are multiple tags read in a block?
l Have the device's Timing properties (such as Request timeout and Fail after x successive timeouts)
been optimized for the virtual network's communication medium?

Device Propert ies — 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. ptc.com
GE SNPX Driver 14

Identification

N am e: 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.

N ote: 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 Assignm ent: 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.
N ote: If the communication driver supports multiple models, users should try to match the model selec-
tion to the physical device. If the device is not represented in the drop-down menu, select a model that con-
forms 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 format is set by the driver by default. Options include Decimal, Octal, and Hexadecimal.
N ote: 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 M ode

www. ptc.com
15 GE SNPX Driver

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 attemp-
ted 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.

Sim ulated: 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.
N otes:

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 envir-
onment.

Device Propert ies — Scan M ode

The Scan Mode specifies the subscribed-client requested scan rate for tags that require device com-
munications. 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 subscribing clients. Descrip-
tions of the options are:

l Respect Client-Specified Scan Rate: This mode uses the scan rate requested by the client.
l Request Data N o Faster than Scan Rate: This mode specifies the value set as the maximum scan
rate. The valid range is 10 to 99999990 milliseconds. The default is 1000 milliseconds.
N ote: 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 sub-
scribed clients. The valid range is 10 to 99999990 milliseconds. The default is 1000 milliseconds.

www. ptc.com
GE SNPX Driver 16

l Do N ot Scan, Dem and 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 Propert ies — Tim ing

The device Timing properties allow the driver's response to error conditions to be tailored to fit the applic-
ation's needs. In many cases, the environment requires changes to these properties for optimum per-
formance. Factors such as electrically generated noise, modem delays, and poor physical connections can
influence how many errors or timeouts a communications driver encounters. Timing properties are specific
to each configured device.

Communications Timeouts
Connect Tim eout: 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 sup-
ported by the driver, it is disabled.
N ote: Due to the nature of UDP connections, the connection timeout setting is not applicable when com-
municating via UDP.

Request Tim eout: 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.

Attem pts Before Tim eout: This property specifies how many times the driver issues 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 attempts
configured for an application depends largely on the communications environment. This property applies to
both connection attempts and request attempts.

Timing

www. ptc.com
17 GE SNPX Driver

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 inter-
request 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.
N ote: Not all drivers support Inter-Request Delay. This setting does not appear if it is not available.

Device Propert ies — Aut o-Dem ot ion

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.

Dem ote 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 sys-
tem tag.

Tim eouts to Dem ote: 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.

Dem otion 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 Dem oted: 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 Propert ies — Tag Generat ion

The automatic tag database generation features make setting up an application a plug-and-play operation.
Select communications drivers can be configured to automatically build a list of tags that correspond to
device-specific data. These automatically generated tags (which depend on the nature of the supporting
driver) can be browsed from the clients.

Not all devices and drivers support full automatic tag database generation and not all support the same data
types. Consult the data types descriptions or the supported data type lists for each driver for specifics.

www. ptc.com
GE SNPX Driver 18

If the target device supports its own local tag database, the driver reads the device's tag information and
uses the data to generate tags within the server. If the device does not natively support named tags, the
driver creates a list of tags based on driver-specific information. An example of these two conditions is as fol-
lows:

1. If a data acquisition system supports its own local tag database, the communications driver uses the
tag names found in the device to build the server's tags.

2. If an Ethernet I/O system supports detection of its own available I/O module types, the com-
munications driver automatically generates tags in the server that are based on the types of I/O mod-
ules plugged into the Ethernet I/O rack.

N ote: Automatic tag database generation's mode of operation is completely configurable. For more inform-
ation, refer to the property descriptions below.

On Property Change: If the device supports automatic tag generation when certain properties change, the
On Property Change option is shown. It is set to Yes by default, but it can be set to N o to control over when
tag generation is performed. In this case, the Create tags action must be manually invoked to perform tag
generation.

On Device Startup: This property specifies when OPC tags are automatically generated. Descriptions of the
options are as follows:

l Do N ot Generate on Startup: This option prevents the driver from adding any OPC tags to the tag
space of the server. This is the default setting.
l Always Generate on Startup: This option causes the driver to evaluate the device for tag inform-
ation. It also adds tags to the tag space of the server every time the server is launched.
l Generate on First Startup: This option causes the driver to evaluate the target device for tag
information the first time the project is run. It also adds any OPC tags to the server tag space as
needed.

N ote: When the option to automatically generate OPC tags is selected, any tags that are added to the
server's tag space must be saved with the project. Users can configure the project to automatically save
from the Tools | Options menu.

On Duplicate Tag: When automatic tag database generation is enabled, the server needs to know what to
do with the tags that it may have previously added or with tags that have been added or modified after the
communications driver since their original creation. This setting controls how the server handles OPC tags
that were automatically generated and currently exist in the project. It also prevents automatically gen-
erated tags from accumulating in the server.

For example, if a user changes the I/O modules in the rack with the server configured to Always Generate
on Startup, new tags would be added to the server every time the communications driver detected a new

www. ptc.com
19 GE SNPX Driver

I/O module. If the old tags were not removed, many unused tags could accumulate in the server's tag space.
The options are:

l Delete on Create: This option deletes any tags that were previously added to the tag space before
any new tags are added. This is the default setting.
l Overwrite as N ecessary: This option instructs the server to only remove the tags that the com-
munications driver is replacing with new tags. Any tags that are not being overwritten remain in the
server's tag space.
l Do not Overwrite: This option prevents the server from removing any tags that were previously gen-
erated or already existed in the server. The communications driver can only add tags that are com-
pletely new.
l Do not Overwrite, Log Error: This option has the same effect as the prior option, and also posts an
error message to the server's Event Log when a tag overwrite would have occurred.

N ote: Removing OPC tags affects tags that have been automatically generated by the com-
munications driver as well as any tags that have been added using names that match generated tags.
Users should avoid adding tags to the server using names that may match tags that are automatically
generated by the driver.

Parent Group: This property keeps automatically generated tags from mixing with tags that have been
entered manually by specifying a group to be used for automatically generated tags. The name of the group
can be up to 256 characters. This parent group provides a root branch to which all automatically generated
tags are added.

Allow Autom atically Generated Subgroups: This property controls whether the server automatically cre-
ates subgroups for the automatically generated tags. This is the default setting. If disabled, the server gen-
erates the device's tags in a flat list without any grouping. In the server project, the resulting tags are named
with the address value. For example, the tag names are not retained during the generation process.
N ote: If, as the server is generating tags, a tag is assigned the same name as an existing tag, the system
automatically increments to the next highest number so that the tag name is not duplicated. For example, if
the generation process creates a tag named "AI22" that already exists, it creates the tag as "AI23" instead.

Create: Initiates the creation of automatically generated OPC tags. If the device's configuration has been
modified, Create tags forces the driver to reevaluate the device for possible tag changes. Its ability to be
accessed from the System tags allows a client application to initiate tag database creation.
N ote: Create tags is disabled if the Configuration edits a project offline.

Device Propert ies — 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. ptc.com
GE SNPX Driver 20

Device Propert ies — Variable Im port Set t ings

Variable Im port File: This property is used to enter the exact location of the variable import file (* .snf or
* .csv file extension) or Logic Developer variable import file (* .txt or other file extension) from which vari-
ables will be imported. It is this file that will be used when Automatic Tag Database Generation is instructed
to create the tag database. All tags will be imported and expanded according to their respective data types.

Display Descriptions: When enabled, this option will import tag descriptions. If necessary, a description will
be given to tags with long names stating the original tag name. Default setting is Enable.

Use Alias Data Type if Possible: When enabled, this option will use the data type assigned to an alias tag
in the import file. If the alias data type is incompatible with the source tag data type, the source tag data type
will be used instead. Default setting is Disable.

Dat a Types Descript ion

Dat a Descript ion

Type
Boolean Single bit
Byte Unsigned 8-bit value

bit 0 is the low bit

bit 7 is the high bit
Word Unsigned 16-bit value

bit 0 is the low bit

bit 15 is the high bit
Short 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
Long Signed 32-bit value

bit 0 is the low bit

bit 30 is the high bit
bit 31 is the sign bit
BCD Two byte packed BCD

Value range is 0-9999. Behavior is undefined for values beyond this range.
LBCD Four byte packed BCD

Value range is 0-99999999. Behavior is undefined for values beyond this range.
Float 32-bit floating point value

The driver interprets two consecutive registers as a floating point value by making the second
register the high word and the first register the low word.
String Null terminated ASCII string

Support includes HiLo LoHi byte order selection.

Double 64-bit floating point value

www. ptc.com
GE SNPX Driver 22

Address Descript ions

Address specifications vary depending on the model in use. Select a link from the following list to obtain spe-
cific address information for the model of interest.

GE M icro
311
313
331
341
350
360
731
732
771
772
781
782
GE OPEN

N ote: Each topic contains tables that display the ranges that are supported by the driver for that model;
however, the actual range may vary depending on the configuration of the device.

Device Address Range Dat a Type Access

www. ptc.com
23 GE SNPX Driver

Device Address Range Dat a Type Access

Register References R0001 to R9999 Word, Short, BCD Read/Write
R0001 to R9998 DWord, Long, LBCD, Float
R0001 to R9996 Double
Analog Inputs AI0001 to AI1024 Word, Short, BCD Read/Write
AI0001 to AI1023 DWord, Long, LBCD, Float
AI0001 to AI1021 Double
Analog Outputs AQ0001 to AQ256 Word, Short, BCD Read/Write
AQ0001 to AQ255 DWord, Long, LBCD, Float
AQ0001 to AQ253 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Array Support
The following data types support arrays: Byte, Word, Short, DWord, Long and Float. An array is a collection of
contiguous elements of a given data type. The maximum array size is 32 DWords (Longs, Floats), 64 Words
(Shorts) or 128 Bytes for a total of 1024 bits. For information on the two ways to specify an array, refer to the
table below.

Examples
Address Address Breakdown
G1 [4] includes the following byte addresses:* G1, G9, G17, G25

1 row implied = 4 bytes

4 x 8 (byte) = 32 total bits
R16 [3][4] includes the following word addresses: R16, R17, R18, R19
R20, R21, R22, R23
R24, R25, R26, R27

3 rows x 4 columns = 12 words

12 x 16 (word) = 192 total bits
P10 [5] includes the following word addresses: P10, P11, P12, P13, P14

1 rows x 5 columns = 5 words

5 x 16 (word) = 80 total bits

* G25 indicates the fourth byte beginning at bit 25.

311 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

www. ptc.com
GE SNPX Driver 24

Device Address Range Dat a Type Access

Q001 to Q497 (every 8th bit) Word, Short, BCD
Discrete Globals G0001 to G1280 Boolean* Read/Write
G0001 to G1273 (every 8th bit) Byte
G0001 to G1265 (every 8th bit) Word, Short, BCD
Internal Coils M0001 to M1024 Boolean* Read/Write
M0001 to M1017 (every 8th bit) Byte
M0001 to M1009 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S01 to S32 Boolean* Read Only
S01 to S25 (every 8th bit) Byte
(Same for SA, SB, SC) S01 to S17 (every 8th bit) Word, Short, BCD
Register References R001 to R512 Word, Short, BCD Read/Write
R001 to R511 DWord, Long, LBCD, Float
R001 to R509 Double
Analog Inputs AI01 to AI64 Word, Short, BCD Read/Write
AI01 to AI63 DWord, Long, LBCD, Float
AI01 to AI61 Double
Analog Outputs AQ001 to AQ032 Word, Short, BCD Read/Write
AQ001 to AQ031 DWord, Long, LBCD, Float
AQ001 to AQ029 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

313 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

www. ptc.com
25 GE SNPX Driver

Device Address Range Dat a Type Access

M0001 to M1009 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S01 to S32 Boolean* Read Only
S01 to S25 (every 8th bit) Byte
(Same for SA, SB, SC) S01 to S17 (every 8th bit) Word, Short, BCD
Register References R001 to R1024 Word, Short, BCD Read/Write
R001 to R1023 DWord, Long, LBCD, Float
R001 to R1021 Double
Analog Inputs AI01 to AI64 Word, Short, BCD Read/Write
AI01 to AI63 DWord, Long, LBCD, Float
AI01 to AI61 Double
Analog Outputs AQ001 to AQ032 Word, Short, BCD Read/Write
AQ001 to AQ031 DWord, Long, LBCD, Float
AQ001 to AQ029 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

331 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

www. ptc.com
GE SNPX Driver 26

Device Address Range Dat a Type Access

(Same for SA, SB, SC) S01 to S17 (every 8th bit) Word, Short, BCD
Register References R0001 to R2048 Word, Short, BCD Read/Write
R0001 to R2047 DWord, Long, LBCD, Float
R0001 to R2045 Double
Analog Inputs AI001 to AI128 Word, Short, BCD Read/Write
AI001 to AI127 DWord, Long, LBCD, Float
AI001 to AI125 Double
Analog Outputs AQ01 to AQ64 Word, Short, BCD Read/Write
AQ01 to AQ63 DWord, Long, LBCD, Float
AQ01 to AQ61 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

341 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

Discrete Inputs I001 to I512 Boolean* Read/Write
I001 to I505 (every 8th bit) Byte
I001 to I497 (every 8th bit) Word, Short, BCD
Discrete Outputs Q001 to Q512 Boolean* Read/Write
Q001 to Q505 (every 8th bit) Byte
Q001 to Q497 (every 8th bit) Word, Short, BCD
Discrete Globals G0001 to G1280 Boolean* Read/Write
G0001 to G1273 (every 8th bit) Byte
G0001 to G1265 (every 8th bit) Word, Short, BCD
Internal Coils M0001 to M1024 Boolean* Read/Write
M0001 to M1017 (every 8th bit) Byte
M0001 to M1009 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S01 to S32 Boolean* Read Only
S01 to S25 (every 8th bit) Byte
(Same for SA, SB, SC) S01 to S17 (every 8th bit) Word, Short, BCD
Register References R0001 to R9999 Word, Short, BCD Read/Write
R0001 to R9998 DWord, Long, LBCD, Float
R0001 to R9996 Double
Analog Inputs AI0001 to AI1024 Word, Short, BCD Read/Write
AI0001 to AI1023 DWord, Long, LBCD, Float

www. ptc.com
27 GE SNPX Driver

Device Address Range Dat a Type Access

AI0001 to AI1021 Double
Analog Outputs AQ0001 to AQ256 Word, Short, BCD Read/Write
AQ0001 to AQ255 DWord, Long, LBCD, Float
AQ0001 to AQ253 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

350 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

Discrete Inputs I0001 to I2048 Boolean* Read/Write
I0001 to I2041 (every 8th bit) Byte
I0001 to I2033 (every 8th bit) Word, Short, BCD
Discrete Outputs Q0001 to Q2048 Boolean* Read/Write
Q0001 to Q2041 (every 8th bit) Byte
Q0001 to Q2033 (every 8th bit) Word, Short, BCD
Discrete Globals G0001 to G1280 Boolean* Read/Write
G0001 to G1273 (every 8th bit) Byte
G0001 to G1265 (every 8th bit) Word, Short, BCD
Internal Coils M0001 to M4096 Boolean* Read/Write
M0001 to M4089 (every 8th bit) Byte
M0001 to M4081 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S01 to S32 Boolean* Read Only
S01 to S25 (every 8th bit) Byte
(Same for SA, SB, SC) S01 to S17 (every 8th bit) Word, Short, BCD
Register References R0001 to R9999 Word, Short, BCD Read/Write
R0001 to R9998 DWord, Long, LBCD, Float
R0001 to R9996 Double
Analog Inputs AI0001 to AI2048 Word, Short, BCD Read/Write
AI0001 to AI2047 DWord, Long, LBCD, Float
AI0001 to AI2045 Double
Analog Outputs AQ001 to AQ512 Word, Short, BCD Read/Write
AQ001 to AQ511 DWord, Long, LBCD, Float
AQ001 to AQ509 Double

* When an array specification is given, the default data type Boolean becomes Byte.

www. ptc.com
GE SNPX Driver 28

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

360 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

Discrete Inputs I0001 to I2048 Boolean* Read/Write
I0001 to I2041 (every 8th bit) Byte
I0001 to I2033 (every 8th bit) Word, Short, BCD
Discrete Outputs Q0001 to Q2048 Boolean* Read/Write
Q0001 to Q2041 (every 8th bit) Byte
Q0001 to Q2033 (every 8th bit) Word, Short, BCD
Discrete Globals G0001 to G1280 Boolean* Read/Write
G0001 to G1273 (every 8th bit) Byte
G0001 to G1265 (every 8th bit) Word, Short, BCD
Internal Coils M0001 to M4096 Boolean* Read/Write
M0001 to M4089 (every 8th bit) Byte
M0001 to M4081 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S01 to S32 Boolean* Read Only
S01 to S25 (every 8th bit) Byte
(Same for SA, SB, SC) S01 to S17 (every 8th bit) Word, Short, BCD
Register References R00001 to R32768 Word, Short, BCD Read/Write
R00001 to R32767 DWord, Long, LBCD, Float
R00001 to R32765 Double
Analog Inputs AI0001 to AI2048 Word, Short, BCD Read/Write
AI0001 to AI2047 DWord, Long, LBCD, Float
AI0001 to AI2045 Double
Analog Outputs AQ001 to AQ512 Word, Short, BCD Read/Write
AQ001 to AQ511 DWord, Long, LBCD, Float
AQ001 to AQ509 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

www. ptc.com
29 GE SNPX Driver

731 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

Discrete Inputs I001 to I512 Boolean* Read/Write
I001 to I505 (every 8th bit) Byte
I001 to I497 (every 8th bit) Word, Short, BCD
Discrete Outputs Q001 to Q512 Boolean* Read/Write
Q001 to Q505 (every 8th bit) Byte
Q001 to Q497 (every 8th bit) Word, Short, BCD
Discrete Globals G0001 to G1280 Boolean* Read/Write
G0001 to G1273 (every 8th bit) Byte
G0001 to G1265 (every 8th bit) Word, Short, BCD
Internal Coils M0001 to M2048 Boolean* Read/Write
M0001 to M2041 (every 8th bit) Byte
M0001 to M2033 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S001 to S128 Boolean* Read Only
S001 to S121 (every 8th bit) Byte
(Same for SA, SB, SC) S001 to S113 (every 8th bit) Word, Short, BCD
Register References R00001 to R16384 Word, Short, BCD Read/Write
R00001 to R16383 DWord, Long, LBCD, Float
R00001 to R16381 Double
Analog Inputs AI0001 to AI8192 Word, Short, BCD Read/Write
AI0001 to AI8191 DWord, Long, LBCD, Float
AI0001 to AI8189 Double
Analog Outputs AQ0001 to AQ8192 Word, Short, BCD Read/Write
AQ0001 to AQ8191 DWord, Long, LBCD, Float
AQ0001 to AQ8189 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

732 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

Discrete Inputs I001 to I512 Boolean* Read/Write
I001 to I505 (every 8th bit) Byte
I001 to I497 (every 8th bit) Word, Short, BCD

www. ptc.com
GE SNPX Driver 30

Device Address Range Dat a Type Access

Discrete Outputs Q001 to Q512 Boolean* Read/Write
Q001 to Q505 (every 8th bit) Byte
Q001 to Q497 (every 8th bit) Word, Short, BCD
Discrete Globals G0001 to G1280 Boolean* Read/Write
G0001 to G1273 (every 8th bit) Byte
G0001 to G1265 (every 8th bit) Word, Short, BCD
Internal Coils M0001 to M2048 Boolean* Read/Write
M0001 to M2041 (every 8th bit) Byte
M0001 to M2033 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S001 to S128 Boolean* Read Only
S001 to S121 (every 8th bit) Byte
(Same for SA, SB, SC) S001 to S113 (every 8th bit) Word, Short, BCD
Register References R00001 to R16384 Word, Short, BCD Read/Write
R00001 to R16383 DWord, Long, LBCD, Float
R00001 to R16381 Double
Analog Inputs AI0001 to AI8192 Word, Short, BCD Read/Write
AI0001 to AI8191 DWord, Long, LBCD, Float
AI0001 to AI8189 Double
Analog Outputs AQ0001 to AQ8192 Word, Short, BCD Read/Write
AQ0001 to AQ8191 DWord, Long, LBCD, Float
AQ0001 to AQ8189 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

771 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

www. ptc.com
31 GE SNPX Driver

Device Address Range Dat a Type Access

Internal Coils M0001 to M4096 Boolean* Read/Write
M0001 to M4089 (every 8th bit) Byte
M0001 to M4081 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S001 to S128 Boolean* Read Only
S001 to S121 (every 8th bit) Byte
(Same for SA, SB, SC) S001 to S113 (every 8th bit) Word, Short, BCD
Register References R00001 to R16384 Word, Short, BCD Read/Write
R00001 to R16383 DWord, Long, LBCD, Float
R00001 to R16381 Double
Analog Inputs AI0001 to AI8192 Word, Short, BCD Read/Write
AI0001 to AI8191 DWord, Long, LBCD, Float
AI0001 to AI8189 Double
Analog Outputs AQ0001 to AQ8192 Word, Short, BCD Read/Write
AQ0001 to AQ8191 DWord, Long, LBCD, Float
AQ0001 to AQ8189 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

772 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

www. ptc.com
GE SNPX Driver 32

Device Address Range Dat a Type Access

Status References S001 to S128 Boolean* Read Only
S001 to S121 (every 8th bit) Byte
(Same for SA, SB, SC) S001 to S113 (every 8th bit) Word, Short, BCD
Register References R00001 to R16384 Word, Short, BCD Read/Write
R00001 to R16383 DWord, Long, LBCD, Float
R00001 to R16381 Double
Analog Inputs AI0001 to AI8192 Word, Short, BCD Read/Write
AI0001 to AI8191 DWord, Long, LBCD, Float
AI0001 to AI8189 Double
Analog Outputs AQ0001 to AQ8192 Word, Short, BCD Read/Write
AQ0001 to AQ8191 DWord, Long, LBCD, Float
AQ0001 to AQ8189 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

781 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

Discrete Inputs I00001 to I12288 Boolean* Read/Write
I00001 to I12281 (every 8th bit) Byte
I00001 to I12273 (every 8th bit) Word, Short, BCD
Discrete Outputs Q00001 to Q12288 Boolean* Read/Write
Q00001 to Q12281 (every 8th bit) Byte
Q00001 to Q12273 (every 8th bit) Word, Short, BCD
Discrete Globals G0001 to G7680 Boolean* Read/Write
G0001 to G7673 (every 8th bit) Byte
G0001 to G7665 (every 8th bit) Word, Short, BCD
Internal Coils M00001 to M12288 Boolean* Read/Write
M00001 to M12281 (every 8th bit) Byte
M00001 to M12273 (every 8th bit) Word, Short, BCD
Temporary Coils T001 to T256 Boolean* Read/Write
T001 to T249 (every 8th bit) Byte
T001 to T241 (every 8th bit) Word, Short, BCD
Status References S001 to S128 Boolean* Read Only
S001 to S121 (every 8th bit) Byte
(Same for SA, SB, SC) S001 to S113 (every 8th bit) Word, Short, BCD
Register References R00001 to R16384 Word, Short, BCD Read/Write
R00001 to R16383 DWord, Long, LBCD, Float
R00001 to R16381 Double

www. ptc.com
33 GE SNPX Driver

Device Address Range Dat a Type Access

Analog Inputs AI0001 to AI8192 Word, Short, BCD Read/Write
AI0001 to AI8191 DWord, Long, LBCD, Float
AI0001 to AI8189 Double
Analog Outputs AQ0001 to AQ8192 Word, Short, BCD Read/Write
AQ0001 to AQ8191 DWord, Long, LBCD, Float
AQ0001 to AQ8189 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

782 Addressing
The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

www. ptc.com
GE SNPX Driver 34

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing
Default Dat a Type Override
St ring Access t o Regist ers
Array Support

GE OPEN Addressing
The GE OPEN model selection has been provided to supply support for any GE SNPX compatible device that
is not currently listed in the standard model selection menu. The data range has been expanded for each
data type so that a wide range of PLCs may be addressed. Although the address ranges shown below may
exceed the specific PLC's capability, the SNPX driver will respect all messages from the PLC regarding
memory range limits. The default data types for dynamic tags are shown in bold.

Device Address Range Dat a Type Access

Discrete Inputs I0001 to I32768 Boolean* Read/Write
I0001 to I32761 (every 8th bit) Byte
I0001 to I32753 (every 8th bit) Word, Short, BCD
Discrete Outputs Q00001 to Q32768 Boolean* Read/Write
Q00001 to Q32761 (every 8th bit) Byte
Q00001 to Q32753 (every 8th bit) Word, Short, BCD
Discrete Globals G00001 to G32768 Boolean* Read/Write
G00001 to G32761 (every 8th bit) Byte
G00001 to G32753 (every 8th bit) Word, Short, BCD
Internal Coils M00001 to M32768 Boolean* Read/Write
M00001 to M32761 (every 8th bit) Byte
M00001 to M32753 (every 8th bit) Word, Short, BCD
Temporary Coils T00001 to T32768 Boolean* Read/Write
T00001 to T32761 (every 8th bit) Byte
T00001 to T32753 (every 8th bit) Word, Short, BCD
Status References S00001 to S32768 Boolean* Read Only
S00001 to S32761 (every 8th bit) Byte
(Same for SA, SB, SC) S00001 to S32753 (every 8th bit) Word, Short, BCD
Register References R00001 to R32768 Word, Short, BCD Read/Write
R00001 to R32767 DWord, Long, LBCD, Float
R00001 to R32765 Double
Analog Inputs AI00001 to AI32768 Word, Short, BCD Read/Write
AI00001 to AI32767 DWord, Long, LBCD, Float
AI00001 to AI32765 Double
Analog Outputs AQ00001 to AQ32768 Word, Short, BCD Read/Write
AQ00001 to AQ32767 DWord, Long, LBCD, Float
AQ00001 to AQ32765 Double

* When an array specification is given, the default data type Boolean becomes Byte.

Advanced Addressing

www. ptc.com
35 GE SNPX Driver

Default Dat a Type Override

St ring Access t o Regist ers
Array Support

Advanced Addressing
Default Data Type Override
The default data types for each device type are shown in the table below. To override these defaults, append
data type indicators to the device address. The possible data type indicators are as follows:

Indicat ors Dat a Type

F Float
S Short
L Long
M String
(BCD) BCD

Examples
Address Descript ion
R100 F Access R100 as a floating point value
R300 L Access R300 as a long
R400–R410 M Access R400-R410 as a string with a length of 22 bytes.
LoHi byte order is assumed.

N ote: There must be a space between the register number and the data type indicator.

String Access to Registers

Register space can be accessed as string data by appending the "M" data type indicator. The length of the
string is based on how the device address reference is entered. Each register addressed can contain 2 char-
acters. The byte order of characters in registers can be specified by appending an optional "H" for HiLo or
"L" for LoHi after the "M" data indicator. If no byte order is specified, LoHi order is assumed.

Examples
Address Descript ion
R100-R150 M Access Register R100 as string with a length of 102 bytes.
LoHi byte order is assumed.
R400 M Access Register R400 as a string with a length of 4 bytes.
LoHi byte order is assumed.
R405-R405 M Access Register R405 as a string with a length of 2 bytes.
LoHi byte order is assumed.
R100-R150 M H Access Register R100 as string with a length of 102 bytes.
HiLo byte order is explicitly specified.
R100-R150 M L Access Register R100 as string with a length of 102 bytes.
LoHi byte order is explicitly specified.

www. ptc.com
GE SNPX Driver 36

N ote: The maximum string length is 128 bytes. For HiLo byte ordering, the string "AB" would be stored in a
register as 0x4142. For LoHi byte ordering, the string "AB" would be stored in a register as 0x4241. There
must be a space between the "M" data type indicator and the byte order indicator.

Array Support
An array is a collection of contiguous elements of a given data type. The maximum array size is 16 Doubles,
32 DWords (Longs, Floats), 64 Words (Shorts), or 128 Bytes for a total of 1024 bits. The following data types
support arrays: Byte, Word, Short, DWord, Long, Float, and Double. For information on the two ways to spe-
cify an array, refer to the table below.

Address Address Breakdown

G1 [4] includes the following byte addresses:* G1, G9, G17, G25

1 row implied = 4 bytes

4 x 8 (byte) = 32 total bits
R16 [3][4] includes the following word addresses: R16, R17, R18, R19
R20, R21, R22, R23
R24, R25, R26, R27

3 rows x 4 columns = 12 words

12 x 16 (word) = 192 total bits
P10 [5] includes the following word addresses: P10, P11, P12, P13, P14

1 rows x 5 columns = 5 words

5 x 16 (word) = 80 total bits

* G25 indicates the fourth byte beginning at bit 25.

Aut om at ic Tag Dat abase Generat ion

The GE SNPX Device Driver generates its tags offline and is based on variables imported from a text file. It is
offline in the sense that no connection to the device is required to generate tags. The text file (variables to
import) can originate from one of the following applications:

1. Cimplicity Machine Edition - Logic Developer

2. VersaPro

There are two parts to Automatic Tag Database Generation: creating a variable import file from the applic-
ation in use and generating tags based on the variable import file from the OPC server. For information on
creating variable import files, refer to Im porting VersaPro Tags or Im porting LogicDeveloper Tags. For
information on generating tags based on the import file, refer to Variable Im port Settings and Tag Gen-
eration. It is recommended that users become familiar with this second part before starting the first part.

Generating Tag Database While Preserving Previously Generated Tag Databases

Under certain circumstances, multiple imports into the server are required to import all tags of interest. This
is the case with importing VersaPro System variables and non-System variables into the same OPC server
project. In the Tag Generation property group under Device Properties, click the property On Duplicate
Tag. The options available are "Delete on create," "Overwrite as necessary," "Do not overwrite" and "Do not
overwrite, log error. " After the first OPC server import/database creation is done, check that the action is

www. ptc.com
37 GE SNPX Driver

set to "Do not overwrite" or "Do not overwrite, log error" for future imports. This will allow tags to be impor-
ted without deleting or overwriting tags that have been imported previously.

Tag Hierarchy
The tags created via automatic tag generation follow a specific hierarchy. The root level groups (or sub-
group levels of the group specified in "Add generated tags to the following group") are determined by the
variable addresses (such as R, G, M and so forth) referenced. For example, every variable that is of address
type "R" will be placed in a root level group called "R". Each array tag is provided in its own subgroup of the
parent group. The name of the array subgroup provides a description of the array. For example, an array
R10[6] defined in the import file would have a subgroup name "R10_x"; x signifies dimension 1 exists.

Im port File-t o-Server Nam e Conversions

Leading Underscores, Percents, Pound, and Dollar Signs
Leading underscores (_) in tag names will be replaced with U_. This is required since the server does not
accept tag/group names beginning with an underscore.

l Leading percents (%) in tag names will be replaced with P_. This is required since the server does not
accept tag/group names beginning with a percent sign.
l Leading pound signs (# ) in tag names will be replaced with PD_. This is required since the server
does not accept tag/group names beginning with a pound sign.
l Leading dollar signs ($) in tag names will be replaced with D_. This is required since the server does
not accept tag/group names beginning with a dollar sign.

Invalid Characters In Name

The only characters allowed in the server tag name are A-Z, a-z, 0-9, and underscore (_). As mentioned
above, a tag name cannot begin with an underscore. All other invalid characters encountered will be con-
verted to a sequence of characters that are valid. Below is a table showing the invalid character, and the
sequence of characters that it is replaced with when encountered in the import file variable name.

Invalid Character Replaced With

$ D_
% P_
+ PL_
- M_

www. ptc.com
GE SNPX Driver 38

Invalid Character Replaced With

# PD_
@ A_
< L_
> G_
= E_

Long Names
The GE SNPX Driver is limited to 256 character group and tag names. Therefore, if a tag name exceeds 256
characters, it must be clipped. Names are clipped as follows:

N on-Array

1. Determine a 5-digit Unique ID for this tag.

2. Given a tag name: ThisIsALongTagName…AndProbablyExceeds256

3. Clip tag at 256: ThisIsALongTagName…AndProbablyEx

4. Room is made for the Unique ID: ThisIsALongTagName…AndProba# # # # #

5. Insert this ID: ThisIsALongTagName…AndProba00000

Array

1. Determine a 5-digit Unique ID for this array.

2. Given an array tag name: ThisIsALongTagName…AndProbablyExceeds256_23_45_8

3. Clip tag at 256 while holding on to the element values: ThisIsALongTagName…AndPr_23_45_8

4. Room is made for the Unique ID: ThisIsALongTagName…# # # # # _23_45_8

5. Insert this ID: ThisIsALongTagName…00001_23_45_8

Im port ing VersaPro Tags

The device driver uses files generated from VersaPro called Shared Name Files (SNF) to generate the tag
database. Certain aspects of the Automatic Tag Database Generation process are specific to the application
from which variables are imported. The following topics are VersaPro specific. To import tags from an applic-
ation other than VersaPro, refer to Autom atic Tag Database Generation to see if the application is sup-
ported.

How do I create a VersaPro variable import file (* .SNF)?

See VersaPro Im port Preparation: VersaPro Steps

How do I configure the OPC Server to use this import file for Automatic Tag Data-
base Generation?
See VersaPro Im port Preparation: OPC Server Steps

How do I import System Variables since they are not included w ith All Variables?
See Generating Tag Database While Preserving Previously Generated Tag Databases

www. ptc.com
39 GE SNPX Driver

How do I highlight variables in VersaPro?

See Highlighting VersaPro Variables

How are VersaPro array variables imported?

See VersaPro Array Tag Im port

VersaPro Im port Preparat ion: VersaPro St eps

1. To start, open the VersaPro project containing the tags (variables) that will be ported over to OPC
server.

2. Open the Variable Declaration Table by clicking View | Variable Declaration Table.

3. Next, decide the Group to which the tags of interest belong. The default groups available are Global,
Local, All, System and Tem porary. The group All does not include the variables from the System
group. In order for System and Global/Local/All variables to be imported, multiple imports are
required (that is, multiple SNF files must be created).

4. Click on the group's tab to bring its variables to the front, and then highlight all tags of interest. Then
click Tools | Export Variables. For more information, refer to Highlighting VersaPro Variables.

www. ptc.com
GE SNPX Driver 40

5. When prompted, select Shared N am e File (* .snf) and then specify a name. VersaPro will export the
project's contents into this SNF file.

VersaPro Im port Preparat ion: OPC Server St eps

1. Open up the Device Properties for the device of interest for which tags will be generated.

2. Select the Variable Im port Settings property group.

3. Enter or browse for the location of the newly created VersaPro * .snf file.

4. Select the Tag Generation property group and utilize as instructed above.

5. The OPC server will state in the Event Log that it is attempting to perform a tag import. When fin-
ished, it will state that the tag import has completed. All variable exported out of VersaPro will appear
in the OPC server in the layout discussed in Tag Hierarchy.

Highlight ing VersaPro Variables

Variables can be highlighted in VersaPro using the actions.

Single Variable Selecting

www. ptc.com
41 GE SNPX Driver

Left-click on the variable of interest while pressing CTRL.

Pick-n-Choose
N/A.

Selecting a Range of Variables

Left-click on the first variable in the range of interest, and then press SHIFT and left-click on the last variable
in the range. All variables in the range will be highlighted.

Selecting All Variables

Left-click on a variable within the group of interest in the Variable Declaration Table. The variable chosen
is irrelevant. Next, click Edit | Select All. All variables will be highlighted within that target. All variables will
be highlighted in that group.

VersaPro Array Tag Im port

VersaPro variables have a length specification. Length is the number of elements for the given array vari-
able. In the driver, this element count can be used to create tags in two ways. The first is to create an array
tag with data in a row x column format. The second is an expanded group of tags, length in number. The fol-
lowing applies for variables with a length > 1.

Array Tags
Since VersaPro arrays are 1-dimensional, the number of columns is always 1. Thus, an array tag would have
the following syntax: <array variable>[# rows = Length]. This single array tag would retrieve length elements
starting at the base address defined in <array variable>. The data will come back formatted in array form for
use in HMI's that support arrays.

Individual Elements
Element tags are the base address + element number. This has the following form, where n = Length - 1.

<array variable><base address + 0>

These tags are not array tags; they are just the reference tags for the <array variable>. It may be thought of
as a listing of all the addresses being referenced in the <array variable>.

Example
Variable Im ported:
MyArrayTag, Length = 10, Address = R1

Result as Array Tag:

MyArrayTag [10]

Result as Individual Elem ents

R1
R2
R3
R4

www. ptc.com
GE SNPX Driver 42

R5
R6
R7
R8
R9
R10

N ote: Variables of type BIT array cannot be accessed as an array tag, only as an expanded group of tags.

Im port ing LogicDeveloper Tags

The device driver uses user-generated ASCII text files from Logic Developer to generate the tag database.
Certain aspects of the Automatic Tag Database Generation process are specific to the application from
which variables are imported. The following topics are LogicDeveloper specific. To import tags from an
application other than LogicDeveloper, refer to Autom atic Tag Database Generation to see if the applic-
ation is supported.

How do I create a LogicDeveloper variable import file (* .TXT)?

See LogicDeveloper Im port Preparation: LogicDeveloper Steps

How do I configure the OPC server to use this import file for Automatic Tag Data-
base Generation?
See LogicDeveloper Im port Preparation: OPC Server Steps

How do I highlight variables in LogicDeveloper?

See Highlighting LogicDeveloper Variables

How are LogicDeveloper array variables imported?

See LogicDeveloper Array Tag Im port

LogicDeveloper Im port Preparat ion: LogicDeveloper St eps

1. To start, open the FrameworX project containing the tags (variables) that will be ported over to OPC
server.

2. Open the N avigator window (Shift-F4) if it's not already open.

3. Click on Variables and select Variable List View.

www. ptc.com
43 GE SNPX Driver

Im portant: Each FrameworX project contains one or more targets. A target is essentially the
device on which the application will run. Variables are created on the target-level, so in order to spe-
cify the variables to export, the target of interest must first be decided. In order for the target vari-
ables to be imported, the variables must have GE PLC as the Data Source. This can be verified by left-
clicking on the variable and looking at its Data Source property in the Inspector window. Internal vari-
ables will not be imported.

4. Sort the variables by target. To do so, right-click on the Variable List header and select Sort | Target.

5. Highlight the tags (variables) of interest in the target of interest. For more information, refer to High-
lighting LogicDeveloper Variables.

6. Next, click Edit | Copy.

www. ptc.com
GE SNPX Driver 44

7. Open a word processing program such as Notepad or Wordpad. This will be the place where the vari-
ables will ultimately be saved for importing. Click Edit | Paste.

8. The variables on the Clipboard will now be pasted to the document, TAB delimited. Do not modify the
contents. Modifications may cause the import to fail.

9. Save this text document with the TXT extension (* .txt) in ANSI form.

10. The variables highlighted and copied in Logic Developer are now contained within this text document
to be imported into the OPC server.

LogicDeveloper Im port Preparat ion: OPC Server St eps

1. Open up the Device Properties for the device of interest for which tags will be generated.

2. Select the Variable Im port Settings property group.

3. Enter or browse for the location of the newly created Logic Developer * .txt file.

4. Select the Tag Generation property group and utilize as instructed above.

www. ptc.com
45 GE SNPX Driver

5. The OPC server will state in the Event Log that it is attempting to perform a tag import. When fin-
ished, it will state that the tag import has completed. All variables exported out of Logic Developer
will appear in the OPC server in the layout discussed in Tag Hierarchy.

Highlight ing LogicDeveloper Variables

Variables can be highlighted in Logic Developer using the following actions.

Single Variable Selecting

Left-click on the variable of interest.

Pick-n-Choose
Left-click on the first variable of interest, and then press CTRL and left-click on each successive variable of
interest. Repeat until all variables of interest are highlighted.

Selecting a Range of Variables

Left-click on the first variable in the range of interest, and then press SHIFT and left-click on the last variable
in the range. All variables in the range will be highlighted.

Selecting All Variables

Left-click on a variable within the target of interest in the Variable List View. The variable chosen is irrel-
evant. Next, click Edit | Select All. All variables will be highlighted within that target.

LogicDeveloper Array Tag Im port

Array tags (or individual element breakdowns of array variables) are not supported when importing from
Logic Developer.

Im port ing Proficy Logic Developer Tags

This driver uses import files from Proficy Logic Developer to generate the tag database. Certain aspects of
the Automatic Tag Database Generation process are specific to the application from which variables are
imported. The following topics are specific to Proficy Logic Developer. To import tags from an application
other than Proficy Logic Developer, refer to Autom atic Tag Database Generation to see if the application
is supported.

N ote: This driver supports the importing of structured data types.

How do I create a Proficy Logic Developer variable import file (* .snf or * .csv)?
See Proficy Logic Developer Im port Preparation: Logic Developer Steps

How do I configure the OPC Server to use this import file for Automatic Tag Data-
base Generation?
See Proficy Logic Developer Im port Preparation: OPC Server Steps

How do I highlight variables in Proficy Logic Developer?

www. ptc.com
GE SNPX Driver 46

See Highlighting Proficy Logic Developer Variables

How are Proficy Logic Developer array variables imported?

See Proficy Logic Developer Array Tag Im port

Proficy Logic Developer Im port Preparat ion: Logic Developer St eps

1. To start, open the Proficy Logic Developer project containing the tags (variables) that will be ported
over to the OPC server.

2. Open the N avigator and select the Variables tab.

3. In the Variable List View, sort the variables by target. To do so, right-click on the Variable List
header and then click Sort | Target.

Im portant: Each Logic Developer project contains one or more targets. A target is essentially the
device on which the application will run. Variables are created on the target-level, so in order to spe-
cify the variables to export, the target of interest must first be defined. In order for the target vari-
ables to be imported, the variables must have GE PLC as the Data Source. This can be verified by left-
clicking on the variable and looking at its Data Source properties in the Inspector window. Internal
variables will not be imported.

4. To export all of the variables, right-click on the Variable List tree root and click the Export…pop-up
menu option.

5. To export only selected variables, highlight the tags of interest in the target of interest. Then, right-
click on one of the selected variables and click Export….

www. ptc.com
47 GE SNPX Driver

6. In the Save as Type drop-down list, choose between Standard N am e Form (* .snf) or Com m a
Separated Variable (* .csv) as the export file type.

Proficy Logic Developer Im port Preparat ion: OPC Server St eps

1. Open up the Device Properties for the device of interest for which tags will be generated.

2. Select the Variable Im port Settings property group.

3. Enter or browse for the location of the newly created * .snf or * .csv export file.

4. Select the Tag Generation property group and click Create Tags in order to import variables now.
Other settings on that page may be used to automatically create the database later.

www. ptc.com
GE SNPX Driver 48

Highlight ing Proficy Logic Developer Variables

Variables can be highlighted in Logic Developer using the following actions.

Single Variable Selecting

Left-click on a variable of interest.

Pick-n-Choose
Left-click on the first variable of interest, and then press CTRL and left-click on each successive variable of
interest. Repeat until all variables of interest are highlighted.

Selecting a Range of Variables

Left-click on the first variable in the range of interest, and then press SHIFT and left-click on the last variable
in the range. All variables in the range will be highlighted.

Selecting All Variables

Proficy Logic Developer Array Tag Im port

Arrays of referenced variables and arrays of symbolic variables will be imported differently.

Referenced Variable Arrays

Arrays of referenced variables will be imported as described in VersaPro Array Tag Im port. A group will be
created for each array. Each group will contain a single array tag, plus a number of tags addressing the indi-
vidual array elements.

Sym bolic Variable Arrays

A single array tag will be generated for each symbolic variable array in the import file. All symbolic variable
array tags will be places in the Symbolic group along with all other symbolic variable tags. The driver will not
generate tags for BOOL and STRING symbolic variable arrays.

www. ptc.com
49 GE SNPX Driver

Error Descript ions

The following messages may be generated. Click on the link for a description of the message.

Address Validation
M issing address.
Device address '<address>' cont ains a synt ax error.
Address '<address>' is out of range for t he specified device or regist er.
Device address '<address>' is not support ed by model '<model name>'.
Dat a Type '<t ype>' is not valid for device address '<address>'.
Device address '<address>' is read only.
Array size is out of range for address '<address>'.
Array support is not available for t he specified address: '<address>'.

Serial Communications
COM n does not exist .
Error opening COM n.
COM n is in use by anot her applicat ion.
Unable t o set comm paramet ers on COM n.
Communicat ions error on '<channel name>' [<error mask>].

Device Status M essages

Device '<device name>' is not responding.
Unable t o writ e t o '<address>' on device '<device name>'.

Device Specific M essages

Invalid t ag in block st art ing at <address> on device <device name>. Block deact ivat ed.

Write Error Messages

Unable t o writ e t o t ag '<t ag address>' on device '<device name>'. The service request ed
is eit her not defined or not support ed.
Unable t o writ e t o t ag '<t ag address>' on device '<device name>'. The user does not have
sufficient privileges t o process t he request . M inor st at us error code = '<hexadecimal
error code>'.
Unable t o writ e t o t ag '<t ag address>' on device '<device name>'. The CPU has received a
message t hat is out of order.
Unable t o writ e t o t ag '<t ag address>' on device '<device name>'. Service request error.
M inor st at us error code = '<hexadecimal error code>'.
Unable t o writ e t o t ag '<t ag address>' on device '<device name>'. The PLC CPU's service
request queue is full: please wait a minimum of 10 ms before sending anot her service
request .
Unable t o writ e t o t ag '<t ag address>' on device '<device name>'. A framing error has
occurred.
Unable t o writ e t o t ag '<t ag address>' on device '<device name>'. Device ret urned major
error code <hexadecimal error code> and minor error code <hexadecimal error code>.

www. ptc.com
GE SNPX Driver 50

Blocked Reads Error Messages

Unable t o read '<number of byt es>' byt es st art ing at address '<t ag address>' on device
'<device name>'. The service request ed is eit her not defined or not support ed.
Unable t o read '<number of byt es>' byt es st art ing at address '<t ag address>' on device
'<device name>'. The user does not have sufficient privileges t o process t he request .
M inor st at us error code = '<hexadecimal error code>'.
Unable t o read '<number of byt es>' byt es st art ing at address '<t ag address>' on device
'<device name>'. The CPU has received a message t hat is out of order.
Unable t o read '<number of byt es>' byt es st art ing at address '<t ag address>' on device
'<device name>'. Service request error. M inor st at us error code = '<hexadecimal error
code>'.
Unable t o read '<number of byt es>' byt es st art ing at address '<t ag address>' on device
'<device name>'. The PLC CPU's service request queue is full: please wait a minimum of
10 ms before sending anot her service request .
Unable t o read '<byt e count >' byt es st art ing at address '<st art t ag>' on device '<device
name>'. A framing error has occurred.
Unable t o read '<number of byt es>' byt es st art ing at address '<t ag address>' on device
'<device name>'. Device ret urned major error code <hexadecimal error code> and minor
error code <hexadecimal error code>.

N on-Blocked Reads Error Messages

Unable t o read t ag '<t ag address>' on device '<device name>'. The service request ed is
eit her not defined or not support ed.
Unable t o read t ag '<t ag address>' on device '<device name>'. The user does not have
sufficient privileges t o process t he request . M inor st at us error code = '<hexadecimal
error code>'.
Unable t o read t ag '<t ag address>' on device '<device name>'. The CPU has received a
message t hat is out of order.
Unable t o read t ag '<t ag address>' on device '<device name>'. Service request error.
M inor st at us error code = '<hexadecimal error code>'.
Unable t o read t ag '<t ag address>' on device '<device name>'. The PLC CPU's service
request queue is full: please wait a minimum of 10 ms before sending anot her service
request .
Unable t o read t ag '<t ag address>' on device '<device name>'. A framing error has
occurred.
Unable t o read t ag '<t ag address>' on device '<device name>'. Device ret urned major
error code <hexadecimal error code> and minor error code <hexadecimal error code>.

Automatic Tag Database Generation M essages

Unable t o generat e a t ag dat abase for device <device name>. Reason: Low memory
resources.
Unable t o generat e a t ag dat abase for device <device name>. Reason: Import file is
invalid or corrupt .
Dat abase Error: Tag '<orig. t ag name>' exceeds 256 charact ers. Tag renamed t o '<new
t ag name>'.

www. ptc.com
51 GE SNPX Driver

Dat abase Error: Array t ags '<orig. t ag name><dimensions>' exceed 256 charact ers. Tags
renamed t o '<new t ag name><dimensions>'.
Dat abase Error: Dat a t ype '<t ype>' for t ag '<t ag name>' not found in import file. Set t ing
t o Default Type '<t ype>'.
Dat abase Error: Dat a t ype '<t ype>' for t ag '<t ag name>' is current ly not support ed. Tag
not creat ed.
Dat abase Error: Logic Developer Variable Arrays are current ly not support ed. Array Tag
(s) '<array t ag name>' not creat ed.
Dat abase Error: N o Reference Address found for t ag '<t ag name>' in import file. Tag not
creat ed.
Dat abase Error: Only variables wit h Dat a Source '<dat a source name>' are import ed.
Dat a Source '<dat a source name>' is not support ed. Tag '<t ag name>' not creat ed.
Dat abase Error: Dat a t ype '<t ype>' arrays are current ly not support ed. Tag '<array t ag
name>' not creat ed.

M issing address
Error Type:
Warning

Possible Cause:
A tag address that has been specified statically has no length.

Solution:
Re-enter the address in the client application.

Device address '<address>' cont ains a synt ax error

Error Type:
Warning

Possible Cause:
A tag address that has been specified statically contains one or more invalid characters.

Solution:
Re-enter the address in the client application.

Address '<address>' is out of range for t he specified device or regist er

Error Type:
Warning

Possible Cause:
A tag address that has been specified statically references a location that is beyond the range of supported
locations for the device.

www. ptc.com
GE SNPX Driver 52

Solution:
Verify that the address is correct; if it is not, re-enter it in the client application.

Device address '<address>' is not support ed by m odel '<m odel nam e>'
Error Type:
Warning

Possible Cause:
A tag address that has been specified statically references a location that is valid for the communications
protocol but not supported by the target device.

Solution:
Verify that the address is correct; if it is not, re-enter it in the client application. Also verify that the selected
model name for the device is correct.

Dat a Type '<t ype>' is not valid for device address '<address>'
Error Type:
Warning

Possible Cause:
A tag address that has been specified statically has been assigned an invalid data type.

Solution:
Modify the requested data type in the client application.

Device address '<address>' is Read Only

Error Type:
Warning

Possible Cause:
A tag address that has been specified statically has a requested access mode that is not compatible with
what the device supports for that address.

Solution:
Change the access mode in the client application.

Array size is out of range for address '<address>'

Error Type:
Warning

Possible Cause:
A tag address that has been specified statically is requesting an array size that is too large for the address
type or block size of the driver.

www. ptc.com
53 GE SNPX Driver

Solution:
Re-enter the address in the client application to specify a smaller value for the array or a different starting
point.

Array support is not available for t he specified address: '<address>'

Error Type:
Warning

Possible Cause:
A tag address that has been specified statically contains an array reference for an address type that doesn't
support arrays.

Solution:
Re-enter the address in the client application to remove the array reference or correct the address type.

COM n does not exist

Error Type:
Fatal

Possible Cause:
The specified COM port is not present on the target computer.

Solution:
Verify that the proper COM port has been selected.

Error opening COM n

Error Type:
Fatal

Possible Cause:
The specified COM port could not be opened due an internal hardware or software problem on the target
computer.

Solution:
Verify that the COM port is functional and may be accessed by other Windows applications.

COM n is in use by anot her applicat ion

Error Type:
Fatal

Possible Cause:
The serial port assigned to a device is being used by another application.

www. ptc.com
GE SNPX Driver 54

Solution:
Verify that the correct port has been assigned to the channel.

Unable t o set com m param et ers on COM n

Error Type:
Fatal

Possible Cause:
The serial parameters for the specified COM port are not valid.

Solution:
Verify the serial parameters and make any necessary changes.

Com m unicat ions error on '<channel nam e>' [<error m ask>]

Error Type:
Serious

Error M ask 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.

Possible Cause:
1. The serial connection between the device and the Host PC is bad.

2. The communications parameters for the serial connection are incorrect.

Solution:
1. Verify the cabling between the PC and the PLC device.

2. Verify that the specified communications parameters match those of the device.

Device '<device nam e>' not responding

Error Type:
Serious

Possible Cause:

www. ptc.com
55 GE SNPX Driver

1. The serial connection between the device and the Host PC is broken.

2. The communications parameters for the serial connection are incorrect.

3. The named device may have been assigned an incorrect Network ID.

4. The response from the device took longer to receive than the amount of time specified in the
"Request Timeout" device setting.

Solution:
1. Verify the cabling between the PC and the PLC device.

2. Verify the specified communications parameters match those of the device.

3. Verify that the Network ID given to the named device matches that of the actual device.

4. Increase the Request Timeout setting so that the entire response can be handled.

Unable t o writ e t o '<address>' on device '<device nam e>'

Error Type:
Serious

Possible Cause:
1. The serial connection between the device and the Host PC is broken.

2. The communications parameters for the serial connection are incorrect.

3. The named device may have been assigned an incorrect Network ID.

Solution:
1. Verify the cabling between the PC and the PLC device.

2. Verify the specified communications parameters match those of the device.

3. Verify that the Network ID given to the named device matches that of the actual device.

Invalid t ag in block st art ing at <address> on device <device nam e>. Block
deact ivat ed
Error Type:
Serious

Possible Cause:
An attempt has been made to reference a nonexistent location in the specified device.

Solution:
Verify the tags assigned to addresses in the specified range on the device and eliminate ones that reference
invalid locations.

www. ptc.com
GE SNPX Driver 56

Unable t o writ e t o t ag '<t ag address>' on device '<device nam e>'. The ser-
vice request ed is eit her not defined or not support ed
Error Type:
Warning

Possible Cause:
The requested service is either not defined or not supported.

Solution:
1. Determine whether writes are supported for the tag address.

2. Verify that the device has the latest Firmware revision.

Unable t o writ e t o t ag '<t ag address>' on device '<device nam e>'. The user
does not have sufficient privileges t o process t he request . M inor st at us
error code = '<hexadecim al error code>'
Error Type:
Warning

Possible Cause:
The user does not have sufficient privileges to complete the service request.

Solution:
For the privilege level required to complete the service request, refer to the Minor Status field.

Unable t o writ e t o t ag '<t ag address>' on device '<device nam e>'. The CPU
has received a m essage t hat is out of order
Error Type:
Warning

Possible Cause:
The CPU received a malformed message.

Solution:
Resend the write request. This will automatically resend the polled tags, as well.

Unable t o writ e t o t ag '<t ag address>' on device '<device nam e>'. Service

request error. M inor st at us error code = '<hexadecim al error code>'
Error Type:
Warning

www. ptc.com
57 GE SNPX Driver

Possible Cause:
The CPU cannot process the service request correctly.

Solution:
For the specific error code, refer to the Minor Status field.

Unable t o writ e t o t ag '<t ag address>' on device '<device nam e>'. The PLC
CPU's service request queue is full: please wait a m inim um of 10 m s
before sending anot her service request
Error Type:
Warning

Possible Cause:
The PLC CPU's service request queue is full.

Solution:
Resend the write request at a later time. This will automatically resend the polled tags, as well.

Unable t o writ e t o t ag '<t ag address>' on device '<device nam e>'. A fram -

ing error has occurred
Error Type:
Warning

Possible Cause:
1. The packets are misaligned due to the connection between the PC and the device.

2. Bad cabling connects the device and is causing noise.

Solution:
1. Place the device on a less noisy network.

2. Increase the Request Timeout and/or Retry Attempts.

Unable t o writ e t o t ag '<t ag address>' on device '<device nam e>'. Device

ret urned m ajor error code '<hexadecim al error code>' and m inor error
code '<hexadecim al error code>'
Error Type:
Warning

Possible Cause:
An unknown error has occurred.

www. ptc.com
GE SNPX Driver 58

Solution:
For the meaning of the error code, refer to the manufacturer's documentation.

Unable t o read ' <num ber of byt es>' byt es st art ing at address '<t ag
address>' on device '<device nam e>'. The service request ed is eit her not
defined or not support ed
Error Type:
Warning

Possible Cause:
The requested service is either not defined or not supported.

Solution:
1. Determine whether reads are supported for the tag address.

2. Verify that the device has the latest Firmware revision.

Unable t o read '<num ber of byt es>' byt es st art ing at address '<t ag
address>' on device '<device nam e>'. The user does not have sufficient
privileges t o process t he request . M inor st at us error code = '<hexadecim al
error code>'
Error Type:
Warning

Possible Cause:
The user does not have sufficient privileges to complete the service request.

Solution:
For the privilege level required to complete the service request, refer to the Minor Status field.

Unable t o read '<num ber of byt es>' byt es st art ing at address '<t ag
address>' on device '<device nam e>'. The CPU has received a m essage t hat
is out of order
Error Type:
Warning

Possible Cause:
The CPU received a malformed message.

Solution:
Resend the read request. This will automatically resend the polled tags, as well.

www. ptc.com
59 GE SNPX Driver

Unable t o read '<num ber of byt es>' byt es st art ing at address '<t ag
address>' on device '<device nam e>'. Service request error. M inor st at us
error code = '<hexadecim al error code>'
Error Type:
Warning

Possible Cause:
The CPU cannot process the service request correctly.

Solution:
For the specific error code, refer to the Minor Status field.

Unable t o read '<num ber of byt es>' byt es st art ing at address '<t ag
address>' on device '<device nam e>'. The PLC CPU's service request queue
is full: please wait a m inim um of 10 m s before sending anot her service
request
Error Type:
Warning

Possible Cause:
The PLC CPU's service request queue is full.

Solution:
Resend the read request at a later time. This will automatically resend the polled tags, as well.

Unable t o read '<byt e count >' byt es st art ing at address '<st art t ag>' on
device '<device nam e>'. A fram ing error has occurred
Error Type:
Warning

Possible Cause:
1. The packets are misaligned due to the connection between the PC and the device.

2. Bad cabling connects the device and is causing noise.

Solution:
1. Place the device on a less noisy network.

2. Increase the Request Timeout and/or Retry Attempts.

www. ptc.com
GE SNPX Driver 60

Unable t o read '<num ber of byt es>' byt es st art ing at address '<t ag
address>' on device '<device nam e>'. Device ret urned m ajor error code
'<hexadecim al error code>' and m inor error code '<hexadecim al error
code>'
Error Type:
Warning

Possible Cause:
An unknown error has occurred.

Solution:
For the meaning of the error code, refer to the manufacturer's documentation.

Unable t o read t ag '<t ag address>' on device '<device nam e>'. The service
request ed is eit her not defined or not support ed
Error Type:
Warning

Possible Cause:
The requested service is either not defined or not supported.

Solution:
1. Determine whether reads are supported for the tag address.

2. Verify that the device has the latest Firmware revision.

Unable t o read t ag '<t ag address>' on device '<device nam e>'. The user
does not have sufficient privileges t o process t he request . M inor st at us
error code = '<hexadecim al error code>'
Error Type:
Warning

Possible Cause:
The user does not have sufficient privileges to complete the service request.

Solution:
For the privilege level required to complete the service request, refer to the Minor Status field.

Unable t o read t ag '<t ag address>' on device '<device nam e>'. The CPU has
received a m essage t hat is out of order
Error Type:
Warning

www. ptc.com
61 GE SNPX Driver

Possible Cause:
The CPU received a malformed message.

Solution:
Resend the read request. This will automatically resend the polled tags, as well.

Unable t o read t ag '<t ag address>' on device '<device nam e>'. Service

request error. M inor st at us error code = '<hexadecim al error code>'
Error Type:
Warning

Possible Cause:
The CPU cannot process the service request correctly.

Solution:
For the specific error code, refer to the Minor Status field.

Unable t o read t ag '<t ag address>' on device '<device nam e>'. The PLC
CPU's service request queue is full: please wait a m inim um of 10 m s
before sending anot her service request
Error Type:
Warning

Possible Cause:
The PLC CPU's service request queue is full.

Solution:
Resend the read request at a later time. This will automatically resend the polled tags, as well.

Unable t o read t ag '<t ag address>' on device '<device nam e>'. A fram ing
error has occurred
Error Type:
Warning

Possible Cause:
1. The packets are misaligned due to the connection between the PC and the device.

2. Bad cabling connects the device and is causing noise.

Solution:

www. ptc.com
GE SNPX Driver 62

1. Place the device on a less noisy network.

2. Increase the Request Timeout and/or Retry Attempts.

Unable t o read t ag '<t ag address>' on device '<device nam e>'. Device

ret urned m ajor error code '<hexadecim al error code>' and m inor error
code '<hexadecim al error code>'
Error Type:
Warning

Possible Cause:
An unknown error has occurred.

Solution:
For the meaning of the error code, refer to the manufacturer's documentation.

Unable t o generat e a t ag dat abase for device <device nam e>. Reason: Low
m em ory resources
Error Type:
Warning

Possible Cause:
Memory required for database generation could not be allocated. The process is cancelled.

Solution:
Close any unused applications and/or increase the amount of virtual memory. Then, try again.

Unable t o generat e a t ag dat abase for device <device nam e>. Reason:
Im port file is invalid or corrupt
Error Type:
Warning

Possible Cause:
1. The file specified as the Tag Import File (* .snf or * .csv) is corrupt.

2. The file specified as the Tag Import File is an improperly formatted Logic Developer text file.

Solution:
Select a valid, properly formatted VersaPro/Logic Developer variable import file or retry the tag export pro-
cess in the respective application to produce a new import file.

Aut omat ic Tag Dat abase Generat ion

Dat abase Error: Tag '<orig. t ag nam e>' exceeds 256 charact ers. Tag
renam ed t o '<new t ag nam e>'
Error Type:
Warning

Possible Cause:
The name assigned to a tag originates from the variable name in the import file. This name exceeds the
256-character limitation and will be renamed to one that is valid.

Solution:
None.

See Also:
Import File-t o-Server N ame Conversions

Dat abase Error: Array t ags '<orig. t ag nam e><dim ensions>' exceed 256
charact ers. Tags renam ed t o '<new t ag nam e><dim ensions>'
Error Type:
Warning

Possible Cause:
The name assigned to an array tag originates from the variable name in the import file. This name exceeds
the 256-character limitation and will be renamed to one that is valid. <Dimensions> define the number of
dimensions for the given array tag: XXX for 1 dimension, XXX_YYY for 2. The number of Xs and Ys approx-
imates the number of elements for the respective dimensions. Since such an error will occur for each ele-
ment, generalizing with XXX and YYY implies all array elements will be affected.

Solution:
None.

See Also:
Import File-t o-Server N ame Conversions

Dat abase Error: Dat at ype '<t ype>' for t ag '<t ag nam e>' is current ly not sup-
port ed. Tag not creat ed
Error Type:
Warning

Possible Cause:
The data type <type> as specified in the import file cannot be resolved or isn't natively supported by the GE
SNPX Driver. The tag was not automatically generated.

www. ptc.com
GE SNPX Driver 64

Solution:
For applicable tags, avoid using data type <type> in the VersaPro/Logic Developer projects.

Dat abase Error: Dat at ype '<t ype>' for t ag '<t ag nam e>' not found in
im port file. Set t ing t o default
Error Type:
Warning

Possible Cause:
The definition of data type '<type>', for tag <tag name>, could not be found in the import file.

Solution:
This tag will take on the Default type for the given address type as assigned by the GE SNPX Driver.

Dat abase Error: Logic Developer Variable Arrays are current ly not sup-
port ed. Array Tag(s) '<array t ag nam e>' not creat ed
Error Type:
Warning

Possible Cause:
Array tags of 1 or 2 dimensions originating from a Logic Developer import file, are not supported at this
time. The array tag(s) were not automatically generated.

Solution:
For applicable tags, avoid using arrays in the Logic Developer projects.

Dat abase Error: No Reference Address found for t ag '<t ag nam e>' in
im port file. Tag not creat ed
Error Type:
Warning

Possible Cause:
Variables without a reference address cannot have a tag created since the reference address determines
the tag's address. The tag was not automatically generated.

Solution:
Verify that the <tag name> has a PLC as a data source and that reference address (PLC memory location)
has been assigned to it.

www. ptc.com
65 GE SNPX Driver

Dat abase Error: Only variables wit h Dat a Source '<dat a source nam e>' are
im port ed. Dat a Source '<dat a source nam e>' is not support ed. Tag '<t ag
nam e>' not creat ed
Error Type:
Warning

Possible Cause:
In Logic Developer, variables can take on a data value from a number of sources. For use in the OPC server,
the source must be a GE SNPX PLC. The tag was not automatically generated.

Solution:
Verify that the <tag name> has a PLC as a data source.

Dat abase Error: Dat a t ype '<t ype>' arrays are current ly not support ed. Tag
'<array t ag nam e>' not creat ed
Error Type:
Warning

Possible Cause:
Boolean or String array tags of 1 or 2 dimensions are not supported at this time.

Solution:
For Boolean array tags, individual array elements of the tag if specified in the import file will be generated.
Further, the driver will also automatically create individual elements for the array tag (except for bit within
word type Boolean array tags).

Note:
For String array tags, neither the array tag nor the individual elements will be generated. String data type is
currently not supported by the driver. Thus, avoid using String data type if possible.

www. ptc.com
66 GE SNPX Driver

Index

311 Addressing 23
313 Addressing 24
331 Addressing 25
341 Addressing 26
350 Addressing 27
360 Addressing 28

731 Addressing 29
732 Addressing 29
771 Addressing 30
772 Addressing 31
781 Addressing 32
782 Addressing 33

Address '<address>' is out of range for the specified device or register 51

Address Descriptions 22
Advanced Addressing 35
Allow Sub Groups 19
Array size is out of range for address '<address>' 52
Array support is not available for the specified address: '<address>' 53
Attempts Before Timeout 16
Auto-Demotion 17
Automatic Tag Database Generation 36

Boolean 21
Byte 21

www. ptc.com
GE SNPX Driver 67

Channel Assignment 14
Communications error on '<channel name>' [<error mask>] 54
Communications Timeouts 16-17
COMn does not exist 53
COMn is in use by another application 53
Connect Timeout 16
Create 19

Data Collection 15
Data Types Description 21
Database Error: Array tags '<orig. tag name><dimensions>' exceed 256 characters. Tags renamed to
'<new tag name><dimensions>' 63
Database Error: Data type '<type>' arrays are currently not supported. Tag '<array tag name>' not cre-
ated 65
Database Error: Datatype '<type>' for tag '<tag name>' is currently not supported. Tag not created 63
Database Error: Datatype '<type>' for tag '<tag name>' not found in import file. Setting to Default Type
'<type>' 64
Database Error: Logic Developer Variable Arrays are currently not supported. Array Tag(s) '<array tag
name>' not created. 64
Database Error: No Reference Address found for tag '<tag name>' in import file. Tag not created 64
Database Error: Only variables with Data Source '<data source name>' are imported. Data Source '<data
source name>' is not. . . 65
Database Error: Tag '<orig. tag name>' exceeds 256 characters. Tag renamed to '<new tag name>' 63
Delete 19
Demote on Failure 17
Demotion Period 17
Device '<device name> not responding 54
Device address '<address>' contains a syntax error 51
Device address '<address>' is not supported by model '<model name>' 52
Device address '<address>' is Read Only 52
Device ID 7
Device Properties — Tag Generation 17
Discard Requests when Demoted 17
Do Not Scan, Demand Poll Only 16
Driver 14

www. ptc.com
68 GE SNPX Driver

Error Descriptions 49
Error opening COMn 53

framing 54

GE Micro 22
GE OPEN Addressing 34
General 13
Generate 18

Highlighting LogicDeveloper Variables 45

Highlighting Proficy Logic Developer Variables 48
Highlighting VersaPro Variables 40

ID 14
Identification 13-14
Import File-to-Server Name Conversions 37
Importing LogicDeveloper Tags 42
Importing Proficy Logic Developer Tags 45
Importing VersaPro Tags 38
Initial Updates from Cache 16
Inter-Request Delay 17
Invalid tag in block starting at <address> on device <device name>. Block deactivated 55

LogicDeveloper Array Tag Import 45

www. ptc.com
GE SNPX Driver 69

LogicDeveloper Import Preparation: LogicDeveloper Steps 42

LogicDeveloper Import Preparation: OPC Server Steps 44

mask 54
Missing address 51
Model 14

Name 14

On Device Startup 18
On Duplicate Tag 18
On Property Change 18
Operating Mode 14
overrun 54
Overview 6
Overwrite 19

Parent Group 19
parity 54
Proficy Logic Developer Array Tag Import 48
Proficy Logic Developer Import Preparation: Logic Developer Steps 46
Proficy Logic Developer Import Preparation: OPC Server Steps 47

Redundancy 19
Request Timeout 16
Respect Tag-Specified Scan Rate 16

www. ptc.com
70 GE SNPX Driver

Scan Mode 15
Setup 6
Short 21
Simulated 15

Tag Generation 17
Tag Hierarchy 37
Timeouts to Demote 17

Unable to generate a tag database for device <device name>. Reason: Low memory resources 62
Unable to generate a tag database for device <device name>. Reason:Import file is invalid or corrupt 62
Unable to read '<byte count>' bytes starting at address '<start tag>' on device '<device name>'. A fram-
ing error has occurred 59
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device name>'.
Device returned major error code '<hexadecimal error code>' and minor error code '<hexa-
decimal error code>' 60
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device name>'.
Service request error. Minor status error code = '<hexadecimal error code>' 59
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device name>'.
The CPU has received a message that is out of order 58
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device name>'.
The PLC CPU's service request queue is full: please wait a minimum of 10 ms before sending
another service request 59
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device name>'.
The service requested is either not defined or not supported 58
Unable to read '<number of bytes>' bytes starting at address '<tag address>' on device '<device name>'.
The user does not have sufficient privileges to process the request. Minor status error code =
'<hexadecimal error code>' 58
Unable to read tag '<tag address>' on device '<device name>'. A framing error has occurred 61
Unable to read tag '<tag address>' on device '<device name>'. Device returned major error code '<hexa-
decimal error code>' and minor error code '<hexadecimal error code>' 62
Unable to read tag '<tag address>' on device '<device name>'. Service request error. Minor status error
code = '<hexadecimal error code>' 61
Unable to read tag '<tag address>' on device '<device name>'. The CPU has received a message that is

www. ptc.com
GE SNPX Driver 71

out of order 60
Unable to read tag '<tag address>' on device '<device name>'. The PLC CPU's service request queue is
full: please wait a minimum of 10 ms before sending another service request 61
Unable to read tag '<tag address>' on device '<device name>'. The service requested is either not
defined or not supported 60
Unable to read tag '<tag address>' on device '<device name>'. The user does not have sufficient priv-
ileges to process the request. Minor status error code = '<hexadecimal error code>' 60
Unable to set comm parameters on COMn 54
Unable to write tag '<address>' on device '<device name>' 55
Unable to write to tag '<tag address>' on device '<device name>'. A framing error has occurred 57
Unable to write to tag '<tag address>' on device '<device name>'. Device returned major error code
'<hexadecimal error code>' and minor error code '<hexadecimal error code>' 57
Unable to write to tag '<tag address>' on device '<device name>'. Service request error. Minor status
error code = '<hexadecimal error code>' 56
Unable to write to tag '<tag address>' on device '<device name>'. The CPU has received a message that
is out of order 56
Unable to write to tag '<tag address>' on device '<device name>'. The PLC CPU's service request queue
is full: please wait a minimum of 10 ms before sending another service request 57
Unable to write to tag '<tag address>' on device '<device name>'. The service requested is either not
defined or not supported 56
Unable to write to tag '<tag address>' on device '<device name>'. The user does not have sufficient priv-
ileges to process the request. Minor status error code = '<hexadecimal error code>' 56

Variable Import Settings 20

VersaPro Array Tag Import 41
VersaPro Import Preparation OPC Server Steps 40
VersaPro Import Preparation VersaPro Steps 39

Word 21

www. ptc.com

Allen-Bradley ControlLogix Ethernet Driver
100% (1)
Allen-Bradley ControlLogix Ethernet Driver
186 pages
Write Heidenhain TNC PLC Data
No ratings yet
Write Heidenhain TNC PLC Data
5 pages
Step7 ErrorCode PDF
No ratings yet
Step7 ErrorCode PDF
37 pages
Allen Bradley Ethernet Manual
100% (1)
Allen Bradley Ethernet Manual
46 pages
Spruh73c PDF
No ratings yet
Spruh73c PDF
4,593 pages
History, Disrupted: How Social Media and the World Wide Web Have Changed the Past Jason Steinhauer pdf download
100% (2)
History, Disrupted: How Social Media and the World Wide Web Have Changed the Past Jason Steinhauer pdf download
61 pages
Read Heidenhain TNC PLC Data
100% (1)
Read Heidenhain TNC PLC Data
4 pages
Xdata User Guide
No ratings yet
Xdata User Guide
197 pages
STEP7 ErrorCode Engl
No ratings yet
STEP7 ErrorCode Engl
31 pages
Technical Reference Manual: Am335X Arm Cortex™-A8 Microprocessors (Mpus)
No ratings yet
Technical Reference Manual: Am335X Arm Cortex™-A8 Microprocessors (Mpus)
4,110 pages
Acloud Get St
No ratings yet
Acloud Get St
110 pages
f
No ratings yet
f
94 pages
P60 Agile P16x: Technical Manual
No ratings yet
P60 Agile P16x: Technical Manual
552 pages
IAM Ping Engineer Resume OH - Hire IT People - We get IT done
No ratings yet
IAM Ping Engineer Resume OH - Hire IT People - We get IT done
7 pages
Ajp Manual
No ratings yet
Ajp Manual
25 pages
Sage 200 Evolution FTP Download Procedures Version Executable Fixes
No ratings yet
Sage 200 Evolution FTP Download Procedures Version Executable Fixes
9 pages
Customize Your SAP NetWeaver BPM Through APIs
0% (1)
Customize Your SAP NetWeaver BPM Through APIs
21 pages
Ge Snpx Manual
No ratings yet
Ge Snpx Manual
72 pages
STEP7 ErrorCode e
No ratings yet
STEP7 ErrorCode e
62 pages
Webinar-ABB-IPTouch-October2020 PR EN V1-0 9AKK107991A3557
No ratings yet
Webinar-ABB-IPTouch-October2020 PR EN V1-0 9AKK107991A3557
84 pages
PXE Error Codes
No ratings yet
PXE Error Codes
8 pages
IoT-Enabled Shipping Container with Environmental Monitoring and Location Tracking
No ratings yet
IoT-Enabled Shipping Container with Environmental Monitoring and Location Tracking
7 pages
Final Report WRL
No ratings yet
Final Report WRL
14 pages
allen-bradley-controllogix-ethernet-manual
No ratings yet
allen-bradley-controllogix-ethernet-manual
210 pages
Ultratech Cement Shareholders Handbook
No ratings yet
Ultratech Cement Shareholders Handbook
29 pages
PSSE Reference
No ratings yet
PSSE Reference
66 pages
Siemens S7 1200 S7 1500 Absolute Addressing Ethernet
No ratings yet
Siemens S7 1200 S7 1500 Absolute Addressing Ethernet
13 pages
Step7 PDF
No ratings yet
Step7 PDF
39 pages
TCP Congestion Control Algorithms
No ratings yet
TCP Congestion Control Algorithms
7 pages
Ride Sharing App Terms and Conditions
No ratings yet
Ride Sharing App Terms and Conditions
57 pages
STEP7 ErrorCode Engl
No ratings yet
STEP7 ErrorCode Engl
37 pages
Allen Bradley Controllogix Ethernet Manual
No ratings yet
Allen Bradley Controllogix Ethernet Manual
207 pages
Ge Ethernet Manual
No ratings yet
Ge Ethernet Manual
79 pages
Riddles
No ratings yet
Riddles
3 pages
Step 7 Err Code125936644
No ratings yet
Step 7 Err Code125936644
37 pages
Siemens S7 1200 S7 1500 Absolute Addressing Ethernet
No ratings yet
Siemens S7 1200 S7 1500 Absolute Addressing Ethernet
13 pages
Codesys Manual
No ratings yet
Codesys Manual
49 pages
List of All Free Videos PDF
No ratings yet
List of All Free Videos PDF
11 pages
IT305 Sample Final
No ratings yet
IT305 Sample Final
4 pages
Keyboarding 101
No ratings yet
Keyboarding 101
15 pages
Omni Flow Computer Manual
No ratings yet
Omni Flow Computer Manual
75 pages
IMC0x-PLC System Manual
No ratings yet
IMC0x-PLC System Manual
138 pages
Schneider PLCUSB Driver - Release Notes
No ratings yet
Schneider PLCUSB Driver - Release Notes
20 pages
GND Kayla - Google Search
No ratings yet
GND Kayla - Google Search
1 page
Usp/Nsc MICROCODE VERSION 50-09-98-00/12 RELEASED 02/21/2012 Newly Supported Features and Functions For Version 50-09-98-00/12
No ratings yet
Usp/Nsc MICROCODE VERSION 50-09-98-00/12 RELEASED 02/21/2012 Newly Supported Features and Functions For Version 50-09-98-00/12
3 pages
Digital Documentation 1 - 2022
No ratings yet
Digital Documentation 1 - 2022
2 pages
Porn 2.0 - Wikipedia
No ratings yet
Porn 2.0 - Wikipedia
9 pages
WORK - MC8V - Activate Version
No ratings yet
WORK - MC8V - Activate Version
15 pages
2019 PP 102 DataNetworking
No ratings yet
2019 PP 102 DataNetworking
6 pages
RSLogic5000 I/O Data Tag
No ratings yet
RSLogic5000 I/O Data Tag
86 pages
Configuring SQL Server 2016 Express On LAN For C# Connection String
No ratings yet
Configuring SQL Server 2016 Express On LAN For C# Connection String
8 pages
Step7 ErrorCode
No ratings yet
Step7 ErrorCode
37 pages
CPU & IO Module
No ratings yet
CPU & IO Module
48 pages
Btech Cse 7 Sem Cyber Security Pec Cs702e 2024
No ratings yet
Btech Cse 7 Sem Cyber Security Pec Cs702e 2024
1 page
Brad Templeton
No ratings yet
Brad Templeton
6 pages
W913293750801a K02 000 01
No ratings yet
W913293750801a K02 000 01
112 pages
OMRON EtherNet IP NJ NX Series
No ratings yet
OMRON EtherNet IP NJ NX Series
4 pages
Kepware UCON
No ratings yet
Kepware UCON
154 pages
PxCSE_HMI_Toolbox_1-20220119125740
No ratings yet
PxCSE_HMI_Toolbox_1-20220119125740
21 pages
PowerEdge Corrective Maintenance Module1_Participant Guide
No ratings yet
PowerEdge Corrective Maintenance Module1_Participant Guide
64 pages
IFIX Drivers
No ratings yet
IFIX Drivers
17 pages
PowerEdge Corrective Maintenance Module2_Participant Guide
No ratings yet
PowerEdge Corrective Maintenance Module2_Participant Guide
64 pages
AN12436 SE050 Configurations
No ratings yet
AN12436 SE050 Configurations
25 pages
STEP7 ErrorCode English
No ratings yet
STEP7 ErrorCode English
31 pages
1.1 AM335x Family: 1.1.1 Device Features
No ratings yet
1.1 AM335x Family: 1.1.1 Device Features
11 pages
Software - PLCNEXT ENGINEER - 1046008: Your Advantages
No ratings yet
Software - PLCNEXT ENGINEER - 1046008: Your Advantages
5 pages
Schneider PLCUSB Driver - Release Notes
No ratings yet
Schneider PLCUSB Driver - Release Notes
19 pages
Information Security Incident Report
No ratings yet
Information Security Incident Report
4 pages
EtherNetIP Error Code Decoder V2.50
No ratings yet
EtherNetIP Error Code Decoder V2.50
18 pages
PowerDeviceLibrary ReleaseNotes
No ratings yet
PowerDeviceLibrary ReleaseNotes
19 pages
Error Environmental Interface Failure
No ratings yet
Error Environmental Interface Failure
1 page
Automotive Bootloader
No ratings yet
Automotive Bootloader
58 pages
Marc Guitar - C7SlowBlues (Clapton Style) TAB
No ratings yet
Marc Guitar - C7SlowBlues (Clapton Style) TAB
3 pages
File: /home/ven0m/downloads/service-Names-Port-Numbers - CSV Page 1 of 288
No ratings yet
File: /home/ven0m/downloads/service-Names-Port-Numbers - CSV Page 1 of 288
1 page
Category Description Register Units Range Default NV User Notes Size (INT16)
No ratings yet
Category Description Register Units Range Default NV User Notes Size (INT16)
19 pages
IFIX Drivers
No ratings yet
IFIX Drivers
17 pages
Siemens S7 1200 S7 1500 Absolute Addressing Ethernet
No ratings yet
Siemens S7 1200 S7 1500 Absolute Addressing Ethernet
14 pages
Protocolo Proprietário SIW200G e SIW400G
No ratings yet
Protocolo Proprietário SIW200G e SIW400G
36 pages
Step by Step Instruction On How To Install X-TREND For 32 & 64 BIT WINDOWS
No ratings yet
Step by Step Instruction On How To Install X-TREND For 32 & 64 BIT WINDOWS
5 pages
Rockwell Automation Application Content: Power Device Library
No ratings yet
Rockwell Automation Application Content: Power Device Library
17 pages
Read Tnc Plc Data
No ratings yet
Read Tnc Plc Data
4 pages
PAC Fixed Issues
No ratings yet
PAC Fixed Issues
5 pages
HTML language complete
From Everand
HTML language complete
Hiyesh Ratee
No ratings yet
Efficient Development with Rider: Definitive Reference for Developers and Engineers
From Everand
Efficient Development with Rider: Definitive Reference for Developers and Engineers
Richard Johnson
No ratings yet
SAP Solution Manager
From Everand
SAP Solution Manager
equitypress
4/5 (10)
Beginning C# 7 Programming with Visual Studio 2017
From Everand
Beginning C# 7 Programming with Visual Studio 2017
Benjamin Perkins
No ratings yet
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
From Everand
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
Vladimir Kiselev
No ratings yet
DB2 Interview Questions, Answers, and Explanations: DB2 Database Certification Review
From Everand
DB2 Interview Questions, Answers, and Explanations: DB2 Database Certification Review
equitypress
No ratings yet
OpenGL to Vulkan: Mastering Graphics Programming
From Everand
OpenGL to Vulkan: Mastering Graphics Programming
Kameron Hussain
No ratings yet

Ge SNPX Manual

Uploaded by

Ge SNPX Manual

Uploaded by

GE SNPX Driver

© 2020 PTC Inc. All Rights Reserved.

Data Types Description 21

Automatic Tag Database Generation 36

Import File-to-Server Name Conversions 37

Importing VersaPro Tags 38

Importing LogicDeveloper Tags 42

Importing Proficy Logic Developer Tags 45

sage that is out of order

Dat a Types Descript ion

Address Descript ions

Aut omat ic Tag Dat abase Generat ion

Error Descript ions

Supported Communication Parameters

Channel and Device Limits

Automatic Tag Database Generation

Channel Propert ies — General

Description: User-defined information about this channel.

Channel Propert ies — Serial Com m unicat ions

Serial Port Settings

l N one: This option does not toggle or assert control lines.

Operation w ith no Communications

Channel Propert ies — Writ e Opt im izat ions

Channel Propert ies — Advanced

Channel Propert ies — Com m unicat ion Serializat ion

l N one: This option disables communication serialization for the channel.

l How many tags must be read from each channel?

Device Propert ies — General

Description: User-defined information about this device.

Driver: Selected protocol driver for this device.

Device Propert ies — Scan M ode

Device Propert ies — Tim ing

Device Propert ies — Aut o-Dem ot ion

Device Propert ies — Tag Generat ion

Device Propert ies — Redundancy

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

Device Propert ies — Variable Im port Set t ings

See Also: Autom atic Tag Database Generation

Dat a Types Descript ion

Dat a Descript ion

bit 0 is the low bit

bit 0 is the low bit

bit 0 is the low bit

bit 0 is the low bit

bit 0 is the low bit

Support includes HiLo LoHi byte order selection.

Address Descript ions

See Also: Advanced Addressing

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

1 row implied = 4 bytes

3 rows x 4 columns = 12 words

1 rows x 5 columns = 5 words

* G25 indicates the fourth byte beginning at bit 25.

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Device Address Range Dat a Type Access

Default Dat a Type Override