Académique Documents
Professionnel Documents
Culture Documents
for FactoryLink
Contents
1 Overview......................................................................................................1
1.1 Software License.....................................................................................................1
1.2 Introduction.............................................................................................................1
1.3 Historical Note........................................................................................................1
1.4 Software Installation...............................................................................................1
2.5.3PLC Name..............................................................................................12
2.5.4 Device Type..........................................................................................12
2.5.5 Connect Status Tag Name.....................................................................13
2.5.6 Comment...............................................................................................13
3 Appendices................................................................................................14
3.1 Appendix A: (Reserved).....................................................................................14
3.2 Appendix B: (Reserved).......................................................................................15
3.3 Appendix C: (Reserved).......................................................................................16
3.4 Appendix D: Software Installation-Windows 95/NT..........................................17
3.4.1 Before Starting Installation - (Windows 95/NT version).....................17
3.4.2 Driver Installation Instructions (Windows 95/NT)...............................17
3.4.3SoftKey Protection Validation...............................................................19
3.5 Appendix E: (Reserved).......................................................................................20
3.6 Appendix F: Driver Status Codes........................................................................21
3.6.1 Application startup errors.....................................................................21
3.6.2 Run-time startup errors.........................................................................23
3.6.3 SoftKey protection errors......................................................................24
3.6.4 Run-time errors.....................................................................................24
3.7 Appendix G: HCT SRX Error Codes...................................................................26
3.7.1 Invalid Parameter Errors.......................................................................26
3.7.2 System Errors........................................................................................26
3.7.3 Communications Stack Errors..............................................................26
3.7.4 Connect Errors......................................................................................27
3.7.5Transfer Errors.......................................................................................27
3.7.6 Invalid State Errors...............................................................................28
3.7.7 PLC CPU Error Codes..........................................................................28
3.8 Appendix H: Data Types and Conversions..........................................................30
3.9 Appendix I: Series 90 Addressing........................................................................32
3.9.1Bit Addressing Regions (Examples)......................................................32
3.9.2Word Addressing Regions (Examples)..................................................34
3.10 Appendix J: Logical Station Commands...........................................................35
3.10.1 SNPX Logical Stations.......................................................................35
3.10.2 Logical Station Commands.................................................................35
3.11 Appendix K: FactoryLink Version Upgrade Procedures...................................37
3.12 Appendix L: Samp.............................................................................................38
4 Glossary.....................................................................................................39
5 Contact information:.................................................................................41
This document is based on information available at the time of its publication. While efforts have been made
to be accurate, the information contained herein does not purport to cover all details or variations in hardware
or software, nor to provide for every possible contingency in connection with installation, operation, or
maintenance. Features may be described herein which are not present in all hardware and software systems.
Axisware assumes no obligation of notice to holders of this document with respect to changes subsequently
made.
Axisware makes no representation or warranty, expressed, implied, or statutory with respect to, and assumes
no responsibility for the accuracy, completeness, sufficiency, or usefulness of the information contained
herein. No warranties of merchantability or fitness for purpose shall apply.
All trademarks are the property of their respectve owners. All trademarks acknowledged.
1 Overview
This product uses a SoftKey protection method. Please consult the SoftKey manual for a discussion of the
procedures to validate the SoftKey for this product.
1.2 Introduction
This manual describes the installation and configuration of the Axisware GE Fanuc SNPX Driver for
FactoryLink. This driver allows FactoryLink to communicate with multiple GE Fanuc Programmable Logic
Controllers. The driver currently supports the built-in serial port on GE Fanuc 90-20, and 90-30 PLCs. It also
currently supports the CMM module on 90-30 and 90-70 PLCs. Unsolicited messages are not supported.
In the appendix section are appendices describing the software installation for this product on specific
platforms. Please read the appropriate appendix before installing this product.
Platform Appendix
Windows NT/95 D
When the driver software installation is completed, please refer to the SoftKey Manual for the instructions on
running the Validate program. Failure to run Validate by the end of the 15-day grace period will result in a non-
functioning driver.
After this communications driver has been installed, updating to a newer version of FactoryLink may appear to
cause operational problems. Please refer to Appendix P before updating FactoryLink.
Access this table by selecting External Device Definition from the Configuration Manager main menu. This is
one of the five configuration tables that must be configured The other tables are accessed by selecting Axisware
GE SNPX Driver from the Configuration Manager main menu.
This table identifies the computer’s ports and I/O cards through which the devices will communicate with
FactoryLink. In this table identifiers are declared which make the external devices recognizable to FactoryLink.
This panel contains seven fields. Use the Tab key to move among the fields.
Number assigned by the user to indicate a particular communication path. This number must be unique
for each EDI driver used in the application.
2.1.5 Function
2.1.6 Memory
The amount of memory in K-bytes used for the block storage size of the read and write information
entered by the user. This entry refers only to the memory used by the driver for data storage for the
related Logical Port.
2.1.7 Comment
(Optional) Description for the current Logical Port. Used only for application documentation.
After these fields have been configured, select "Next" or Ctrl-N to edit the Read/Write Information Table
corresponding to the Control table selected by the cursor.
Allows you to select whether the current table will be considered in the processing of an unsolicited
message received from the PLC..
Option determining whether or not a specific tag in the related Read/Write Information Table is written
to the selected logical station whenever the real-time database value for that tag changes.
Yes A change of status of any element in the table generates a write of that
element's value.
No No exception processing.
Priority influencing the order in which the EDI task handles the queuing of block read requests. If two
requests are received simultaneously by EDI, the request with the highest priority (lowest number) is
processed first.
Digital tag whose value, when forced to 1 (ON), initiates a block read of the values specified in the
related Read/Write Information Table. This trigger allows the block read operation to be initiated by
some other task.
Digital tag used to determine whether or not a block read table will be processed. If the tag value is 0,
the table is permitted to function normally; however, if the value is 1, the table will not respond to the
Block Read Trigger defined above.
Digital tag whose value is force written to 1 (ON) by the EDI task whenever any block read operation for
this table is completed. If this tag is specified then when the EDI task initializes, its value is force
written to 1 (ON).
Note: Block Read Complete tags are valid only if a different table is used for each logical port.
Digital tag whose value is 0 (OFF) when a block read of the tags specified in this table is in progress and
1 (ON) otherwise. If this tag is specified then when the EDI task initializes, its value is force written to 1
(ON).
Note: Block Read State tags are valid only if a different table is used for each logical port.
Priority influencing the order in which the EDI task handles the queuing of block write and exception
write requests. If two requests are received simultaneously by EDI, the request with the highest priority
(lowest number) is processed first.
Dgital tag whose value, when forced to 1 (ON), initiates a block write of the values specified in the
related Read/Write Information Table. This trigger allows the block write operation to be initiated by
some other task.
Dgital tag used to determine whether or not a block write table will be processed. If the tag value is 0,
the table is permitted to function normally; however, if the value is 1, the table will not respond to the
Block Write Trigger defined above.
Dgital tag whose value is force written to 1 (ON) by the EDI task whenever any block write operation
for this table is completed. If this tag is specified then, when the EDI task initializes, its value is force
written to 1 (ON).
Note: Block Write Complete tags are valid only if a different table is used for each logical port.
Dgital tag whose value is 0 (OFF) when a block write of the tags specified in this table is in progress and
1 (ON) otherwise. If this tag is specified then, when the EDI task initializes, its value is force written to
1 (ON).
Note: Block Write State tags are valid only if a different table is used for each logical port.
These tables are sometimes referred to as overlay panels, or ovr panels. Each table has one entry (line) for it
in the Read/Write Control Table.
Note: Please verify that the table name displayed at the bottom of the panel correctly shows the table to be
modified.
After these fields have been completed, select "Next" or Ctrl-N to edit the Logical Station Control Table.
Name of the FactoryLink tag to be updated as a result of the read operation or the tag from which
information is taken to be written to the device.
Number from the Logical Station Table identifying the particular combination of physical attributes that
will define and govern the data transfer to and from the real-time tag.
2.3.4 Element
Numeric portion of device address; may be word or bit address depending on the entry selected for the
Data Region.
If a digital tag is used and a word oriented data region has been selected, this field is used to specify the
bit offset in the selected word. If a message tag is used, the field specifies the number of bytes that are to
be transferred between the message tag and the Logical Station.
Type of data representation in PLC for information being read/written from/to the Logical Station.
2.3.7 Comment
After completing these fields, select "Next" or Ctrl-N to edit the Logical Station Information Table
corresponding to the table selected by the cursor.
Number specified in the External Device Definition Table which represents a particular communications
path.
This number must also be referenced in the External Device Definition panel.
(Optional) Message tagto which a text string will be written if an error is encountered in the
processing of an EDI request.
Determines the speed at which data will be transmitted over the network. All devices on the network
must be configured for the same baudrate.
2.4.4 Parity
Selects the desired parity for the serial communications between FactoryLink and the PLC. The
parity must be the same for all devices on the network.
Number representing the desired number of data bits for the serial communications between
FactoryLink and the PLC. The specified number of data bits must be the same for all devices on the
network.
Valid entry: 8
Number representing the desired number of stop bits for the serial communications between
FactoryLink and the PLC. The specified number of stop bits must be the same for all devices on the
network.
Valid entries: 1 or 2
Valid entries: Actual value in tenths of seconds (3 - 4 seconds for most applications)
Note: Please verify that the table name displayed at the bottom of the panel is showing the table to be
modified.
After these fields have been completed, "Exit" or F3 will allow you to return to the Configuration Manager
main menu.
(Optional) Analog tag to which all error codes for this logical station are to be written.
Number entered by user to represent a particular combination of a logical port (PCIM card) and physical
device (PLC). This number is referenced in the Read/Write Information Table to correlate specific
addresses and tags with a physical device (PLC). This number must be unique for each four-letter
device ID (SNPX).
2.5.3PLC Name
Name of ANALOG tag that indicates the current status of the logical station.
2.5.6 Comment
(Optional) Description for the current Logical Station. Used only for application documentation.
3 Appendices
If the driver software is an update from an older version, the following procedures must be followed for the
software to be properly installed. First, the operator must exit from both the Run Manager and the Configuration
Manager. Second, a multiplatform save file should be created. Third, the driver should be installed as described
below. Fourth, restore the multiplatform save file created in step 2. Fifth, update the Configuration Manager
tables for the SNPX driver (Logical Station Information).
The install command file relies upon the environment variable $FLINK to complete the installation process.
($FLINK is used to refer to the environment variable “FLINK”, which points to the FactoryLink directory.)
Before starting the install program you may want to manually set $FLINK if you want to have the files
copied to a directory other than the default of C:\FLWIN (or C:\FLNT).
If $FLINK has not been defined when the install is started, you will be requested to exit and assign a value
to $FLINK, and then restart the install program. $FLINK can be assigned a parameter by using the SET
command (example: set flink=d:\flnt). Be sure to include the drive letter.
During the installation, two ASCII text files will be modified by the installation program. The original copies
of both files will be copied to a file with the same filename but a .NVA extension. The first file to be modified
is $FLINK\AC\TITLES (where $FLINK is the FactoryLink directory). This file is used by the Configuration
Manager to determine which tasks to list and also the order in which they are to be listed. The following line
will be added to the TITLES file. (The line may be different, depending on your FactoryLink version.)
If you have a backup file named $FLINK\AC\TITLES.NVA (possibly created by a previous install), the
program will warn you during the install that it is about to be overwritten and will ask you if you want to exit,
and manually save the .NVA file.
The second file to be modified is $FLINK\CTGEN\CTLIST. This file is used by the CTGEN utility in the
creation of the binary CT (configuration table) files used at run-time by FactoryLink. The following line will
be added to the CTLIST file.
If you have a backup file named $FLINK\CTGEN\CTLIST.NVA (possibly created by a previous install), the
program will ask you during the install if you wish to exit, and manually save a copy of this .NVA file before
it is overwritten.
The driver software is loaded by inserting the driver diskette in drive A or B. At a command prompt, make
the drive containing the diskette the current working drive, type INSTALL and then press Enter.
Note: A source other than drive A or B can be used; e.g., from a directory on a hard drive, or across a
network.
If a message is displayed stating that the INSTALL program is having difficulty finding the directory
containing the FactoryLink program files, press a key to exit and use the set command to reset the $FLINK
environment variable. The problem may be resolved by clearly stating the drive letter. At a command
prompt type set FLINK= followed by the drive letter (a-z), a colon (:), a backslash (\) and the directory name
(s) giving the path to the FactoryLink program files. Examples: set FLINK=d:\work1\flos2 or set
FLINK=t:\sect2\factory. Make sure that the only space in this command is between “set” and “FLINK”.
After the “Axisware” screen appears the FactoryLink Path and FactoryLink Release Version are displayed.
Press y and then the Enter (Return) key if the information is correct.
The driver Serial Number and Release Type are then displayed. Press y and then the Enter (Return) key to
continue.
The install program checks for a backup file named $FLINK\AC\TITLES.NVA. If found, the following
message is displayed:
The install program will then go through the same procedure before updating the file
$FLINK\CTGEN\CTLIST. The install program checks for a backup file named
$FLINK\CTGEN\CTLIST.NVA. If found, this message appears:
The messages
are briefly displayed while the backup (.NVA) versions are being created and the $FLINK\AC\TITLES and
$FLINK\CTGEN\CTLIST files are updated.
the lines to be added to these files can be typed in manually using a text editor. Refer to the section “Before
Starting Installation” (above) for the specific lines and where they are to be added.
Please notice any additional messages displayed on the screen. When all of the necessary files have been
copied the following message will appear:
.....Installation Program Completed.
Please refer to the SoftKey Manual and run the program Validate to ensure that your product does not
expire at the end of the grace period. Specific steps are included in the SoftKey Manual.
Warning: The installation of this product is not complete until the Validate program is run.
The following error codes (alphabetized) may be reported to FactoryLink while the driver tables are being
processed at startup.
The following error messages (alphabetized) which are preceded by “gehc:“ are followed by a location
indicating where the problem likely originated (Logical Station, Region Element, Bit):
gehc: Bit writes to word regions not supported: (Logical Station: Region: Element: Bit/Length: )
Bits cannot be written to regions R, AI, or AQ as these regions use word addressing.
gehc: Message Tags in word regions must have even byte length:
Check the Bit or Length field in the Read/Write Information Table.
There is a limit of 1024 FactoryLink tags in any one packet. Break up the tags into more than
one table.
The following errors (alphabetized) may be reported when the EDI task is started after all tables have been
processed. All the following errors are immediately fatal.
Maximum requests for platform exceeded. Reduce Max Concurrent Requests field in
Logical Station Information table.
Messages relating to SoftKey protection may appear after the driver has been initialized by the EDI task.
Please refer to the SoftKey manual if they appear. If SoftKey does not detect a problem the following
message will be displayed.
The following errors may be reported while the driver is processing application requests. The text represents
the error message returned to the message tag defined in the Logical Station Control Table. The number in
parentheses is returned to the analog tag defined in the Logical Station Information Table. While the following
errors are not immediately fatal, recurring errors should be evaluated and eradicated to maintain the integrity of
the network.
(1) Timeout
(2) SRX Error
(3) Inactive Station
(4) Disabled Station
(5) Unknown Status from HCT
The following (alphabetized) error messages are unlikely to appear. Their purpose is to provide useful
information for Axisware technical support personnel.
If one of the following error messages appear, please record (write down) the entire message before
contacting Axisware. (Each message begins with a module name followed by a function name.)
These error codes are returned from the HCT package. Refer back to the section on runtime errors in
Appendix F (Driver Status Codes).
Error codes in this group indicate that a parameter in a call from the Toolkit to the underlying
communications driver was invalid.
Error codes in this group indicate that a basic system error of some kind occurred.
Value Description of Error Condition
(hex)
7 Some resource other than buffer allocation could
not be obtained.
8 The maximum number of SRX Driver users are
already active.
9 Attempt to allocate a buffer failed.
A SRX Driver timed out waiting for an event to occur.
Error codes in this group indicate that an error has occurred when attempting to establish a session to the
remote PLC.
3.7.5Transfer Errors
Error codes in this group indicate that an error has occurred when attempting to transfer data between the
local user application and the remote PLC.
Error codes in this group indicate that a request from the Toolkit was made while the Finite State Machine
(FSM) for the underlying communications driver was in a state that does not allow that kind of request.
DIGITAL
ANALOG
LONG ANALOG
FLOATING POINT
MESSAGE
When DEF is used, the PLC data type is determined and set automatically by the tag type:
Valid PLC data types for each of the FactoryLink tag types:
PLC memory regions are divided into two functionally distinct addressing
types: bit addressing regions, and word addressing regions.
Global Data
The global data regions are denoted by %G, %GA, %GB, %GC, %GD, and %GE. This
data region is accessed by bit addressing rather than word addressing.
Examples:
Region Element Description
G 1 %G0001
GA 14 %GA0014
GE 100 %GE0100
Discrete Inputs
The discrete input data region is denoted by %I. This data region is accessed by bit
addressing rather than word addressing.
Examples:
Region Element Description
I 1 %I0001
I 14 %I0014
I 100 %I0100
Discrete Internals
The discrete internal data region is denoted by %M. This data region is accessed by bit
addressing rather than word addressing.
Examples:
Region Element Description
M 1 %M0001
M 14 %M0014
M 100 %M0100
Discrete Outputs
The discrete output data region is denoted by %Q. This data region is accessed by bit
addressing rather than word addressing.
Examples:
Region Element Description
Q 1 %Q0001
Q 14 %Q0014
Q 100 %Q0100
Examples:
Region Element Description
S 1 %S0001
SA 14 %SA0014
SC 32 %SC0032
Discrete Temporaries
The discrete temporary data region is denoted by %T.
Examples:
Region Element Description
T 1 %T0001
T 14 %T0014
T 100 %T0100
Analog Inputs
The analog input data region is denoted by %AI.
Examples:
Region Element Description
AI 1 %AI0001
AI 14 %AI0014
AI 50 %AI0050
Analog Outputs
The analog output data region is denoted by %AQ.
Examples:
Region Element Description
AQ 1 %AQ0001
AQ 14 %AQ0014
AQ 50 %AQ0050
Registers
The register data region is denoted by %R.
Examples:
Region Element Description
R 1 %R00001
R 14 %R00014
R 150 %R00150
When the GEHC protocol module is running, each logical station is an object which controls solicited
operation access to its mapped physical device. The logical station runs in one of six states. The current state
of any logical station can be monitored by the FactoryLink application by specifying an analog tag in the
Connect Status Tag Name field of the Logical Station Information Panel. Following is a description of
each state. The number in parentheses() is the value written to the analog tag.
Logical Station Disabled (-2): The logical station has been disabled by the logical station enable/disable
command, please refer to the logical station command section later in this appendix. In this state all requests
received by the logical station are aborted with a status code of 4. The logical station will remain in this state
until receipt of a logical station enable command or the EDI task is terminated.
Logical Station Disconnected (-1): The logical station has been disconnected for some reason and is
waiting the station reconnect wait period. In this state all requests received by the logical station will be
aborted with a status code of 3. The logical station will remain in this state until the time period has expired
(at which time it will enter the inactive state), receipt of a logical station enable command, or until the EDI
task is terminated.
Logical Station Inactive (0): Initial logical station state. In this state the logical station remains idle using
minimal system resources until a request is received. Upon receipt of a request the logical station will
attempt to connect to the physical station by entering the connecting state.
Logical Station Connecting (1): In this state the logical station is attempting to connect to the physical
station (PLC). The logical station will remain in this state until the connection attempt is successful or fails.
Logical Station Active or Running (2): In this state the logical station is connected to the physical station
(PLC) and is processing requests. The logical station will remain in this state until 1) a communications
error forces a disconnect, or 2) a logical station enable/disable command is received to disable the station.
Logical Station Disconnecting (3): In this state the logical station is disconnecting from the physical
station. The logical station will remain in this state until disconnected and will then move to either the
Disabled or Disconnected state depending on the reason for the disconnection.
The Logical Stations Command (LS) data region allows for the FactoryLink application to modify certain
elements of a runtime logical station’s configuration. This data region is write only as it commands the
logical station object. To specify a logical station command in the Read/Write Information Panel enter
“LS” in the Data Region field, enter the logical station number to receive the command in the Logical
Station field, and the command code in the Element field. Let the remaining fields default by leaving them
blank. Following are descriptions of the possible logical station commands. The number preceding the
command description is the command code (element).
1 Logical Station Enable/Disable: This command will either enable or disable the logical station
depending on the value of the digital tag written to the logical station. If the value of the digital tag
is zero the logical station is disabled, if the value of the digital tag is one the logical station is
enabled. This command takes effect immediately upon receipt.
2 Logical Station Set Station Name: This command will replace the physical station name specified
in the PLC Name field of the Logical Station Information Panel with the string contained in the
message tag written to the logical station. This name change will not take effect until the logical
station is disconnected and reconnected. Use the Logical Station Enable/Disable command to force
disconnect and reconnect.
3 Included for compatibility with other Axisware GE Fanuc drivers..This command has no effect on
SNPX protocol.
After installing this communications driver, upgrading to a newer version of FactoryLink may appear to
cause operational problems. This is due to the modifications to certain text files made by installing this
product being overwritten during the install of the new FactoryLink version. However, these files can be
reconfigured using a text editor
After installing the FactoryLink upgrade, the following steps should be done before restoring the
multiplatform save file of your application:
The SAMPLE directory of the nstall cd-rom includes compressed multiplatform save files of a sample
application for this driver. The sample application can be used to test communications, as well as serve as an
example of how to prepare a FactoryLink application to use the driver. The sample application has examples of
block reads, block writes, exception writes and unsolicited reads from a single PLC. Please refer to the
"README.TXT" file in the SAMPLE directory for instructions on how to use this application.
4 Glossary
Configuration Tables
Where you establish the communication path and specify elements in the database. These tables work
together to allow FactoryLink to exchange information from the tag database with the device.
Logical Port
Number specified in the External Device Definition table which represents a particular communication path.
Logical Station
Number entered by the user to represent a particular combination of a logical port and a physical device
(PLC). Correlates specific addresses and tags with a physical device (PLC).
Proof of License
An 8 1/2 by 11 certificate that must accompany the software indicated by its unique serial number when that
product is sold or transferred to another company or entity.
SoftKey
Axisware software protection system where no hardware key (dongle) is required.
Validate
The program run after the software is installed that checks for improper use of the product and enables the
software to function past the grace period.
5 Contact information:
Axisware LLC
support@axisware.com
http://www.axisware.com
T: 1-(214)-764-1876
F: 1-(214)-764-1878