axisware snpx manual: factorylink driver for ge fanuc snpx serial

GE Fanuc SNPX Driverfor FactoryLink

Version 7.2 February 2004

Axisware GE Fanuc SNPX Driver for FactoryLink 1

Contents

1 Overview......................................................................................................1

1.1 Software License.....................................................................................................11.2 Introduction.............................................................................................................11.3 Historical Note........................................................................................................11.4 Software Installation...............................................................................................1

2 Factorylink Application Configuration......................................................3

2.1 External Device Definition.....................................................................................32.1.1 Logical Port.............................................................................................32.1.2 Physical Card..........................................................................................32.1.3 Physical Port............................................................................................32.1.4 Device Name...........................................................................................32.1.5 Function...................................................................................................32.1.6 Memory...................................................................................................42.1.7 Comment.................................................................................................4

2.2 Axisware GE SNPX Read/Write Control...............................................................52.2.1 Table Name.............................................................................................52.2.2 Unsolicited Read.....................................................................................52.2.3 Exception Write......................................................................................52.2.4 Block Read Priority.................................................................................52.2.5 Block Read Trigger.................................................................................62.2.6 Block Read Disable.................................................................................62.2.7 Block Read Complete.............................................................................62.2.8 Block Read State.....................................................................................62.2.9 Block Write Priority................................................................................72.2.10 Block Write Trigger..............................................................................72.2.11 Block Write Disable..............................................................................72.2.12 Block Write Complete..........................................................................72.2.13 Block Write State..................................................................................7

2.3 Axisware GE SNPX Read/Write Information Table..............................................82.3.1 Tag Name................................................................................................82.3.2 Logical Station........................................................................................82.3.3 Data Region.............................................................................................82.3.4 Element...................................................................................................92.3.5 Bit or Length...........................................................................................92.3.6 PLC Data Type........................................................................................92.3.7 Comment.................................................................................................9

2.4 Axisware GE SNPX Logical Station Control.......................................................102.4.1 Logical Port...........................................................................................102.4.2 Status Msg Tag......................................................................................102.4.3 Baud Rate..............................................................................................102.4.4 Parity.....................................................................................................102.4.5 Data Bits................................................................................................112.4.6 Stop Bits................................................................................................112.4.7 Response Timeout 0.1 Sec....................................................................11

2.5 Axisware GE SNPX Logical Station Information................................................122.5.1 Error/Status Tag Name..........................................................................122.5.2 Logical Station (Decimal).....................................................................12

Axisware LLC [email protected] www.axisware.com


2.5.3PLC Name..............................................................................................122.5.4 Device Type..........................................................................................122.5.5 Connect Status Tag Name.....................................................................132.5.6 Comment...............................................................................................13

3 Appendices................................................................................................14

3.1 Appendix A: (Reserved).....................................................................................143.2 Appendix B: (Reserved).......................................................................................153.3 Appendix C: (Reserved).......................................................................................163.4 Appendix D: Software Installation-Windows 95/NT..........................................17

3.4.1 Before Starting Installation - (Windows 95/NT version).....................173.4.2 Driver Installation Instructions (Windows 95/NT)...............................173.4.3SoftKey Protection Validation...............................................................19

3.5 Appendix E: (Reserved).......................................................................................203.6 Appendix F: Driver Status Codes........................................................................21

3.6.1 Application startup errors.....................................................................213.6.2 Run-time startup errors.........................................................................233.6.3 SoftKey protection errors......................................................................243.6.4 Run-time errors.....................................................................................24

3.7 Appendix G: HCT SRX Error Codes...................................................................263.7.1 Invalid Parameter Errors.......................................................................263.7.2 System Errors........................................................................................263.7.3 Communications Stack Errors..............................................................263.7.4 Connect Errors......................................................................................273.7.5Transfer Errors.......................................................................................273.7.6 Invalid State Errors...............................................................................283.7.7 PLC CPU Error Codes..........................................................................28

3.8 Appendix H: Data Types and Conversions..........................................................303.9 Appendix I: Series 90 Addressing........................................................................32

3.9.1Bit Addressing Regions (Examples)......................................................323.9.2Word Addressing Regions (Examples)..................................................34

3.10 Appendix J: Logical Station Commands...........................................................353.10.1 SNPX Logical Stations.......................................................................353.10.2 Logical Station Commands.................................................................35

3.11 Appendix K: FactoryLink Version Upgrade Procedures...................................373.12 Appendix L: Samp.............................................................................................38

4 Glossary.....................................................................................................39

5 Contact information:.................................................................................41



This document contains proprietary information of Axisware LLC (Axisware). This document is based on information available at the time of its publication. While efforts have been madeto be accurate, the information contained herein does not purport to cover all details or variations in hardwareor software, nor to provide for every possible contingency in connection with installation, operation, ormaintenance. 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 subsequentlymade. Axisware makes no representation or warranty, expressed, implied, or statutory with respect to, and assumesno responsibility for the accuracy, completeness, sufficiency, or usefulness of the information containedherein. No warranties of merchantability or fitness for purpose shall apply.

All trademarks are the property of their respectve owners. All trademarks acknowledged.

Copyright 1995-1996 NOVA TechnologiesCopyright 1997-2000 Bullet SoftwareCopyright 2000-2004 Axisware LLCAll Rights Reserved



1 Overview

1.1 Software LicenseAxisware LLC grants you a non-exclusive license to use the Software programs and related documentationfor this product on a single processing unit. For each processing unit that executes the Software programs forthis product you must have a unique serial number and Proof of License statement. No one other than acurrent Axisware employee or agent is permitted to modify or tamper with in any way the executablecomputer files(s) associated with this product. This license applies solely to the software contained in thisproduct, and does not include any additional software or documentation provided by Axisware or otherparties required for the proper operation of this product. This product uses a SoftKey protection method. Please consult the SoftKey manual for a discussion of theprocedures to validate the SoftKey for this product.

1.2 Introduction

This manual describes the installation and configuration of the Axisware GE Fanuc SNPX Driver forFactoryLink. This driver allows FactoryLink to communicate with multiple GE Fanuc Programmable LogicControllers. The driver currently supports the built-in serial port on GE Fanuc 90-20, and 90-30 PLCs. It alsocurrently supports the CMM module on 90-30 and 90-70 PLCs. Unsolicited messages are not supported.

1.3 Historical Note

This product was previously a Nova Technologies product and is now an Axisware product. The manual iscorrect in all technical detail except install instructions, which are detailed in the Utilities manual. Axiswarehas assumed all responsibilities for this product; if you see a reference to Nova Technologies consider it areference to Axisware.

1.4 Software Installation

If installing over a previous version of this driver, perform a multi-platform save of the FactoryLinkapplication before the install and restore the application after installation. Please refer to FactoryLinkdocumentation for details on multi-platform save and restore.

In the appendix section are appendices describing the software installation for this product on specificplatforms. 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 onrunning 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 tocause operational problems. Please refer to Appendix P before updating FactoryLink.



2 Factorylink Application Configuration

2.1 External Device Definition

Access this table by selecting External Device Definition from the Configuration Manager main menu. This isone 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 withFactoryLink. 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.

2.1.1 Logical Port

Number assigned by the user to indicate a particular communication path. This number must be uniquefor each EDI driver used in the application.

Valid entries: 0-999

2.1.2 Physical Card

This field is not used by this driver.

2.1.3 Physical Port

PC COM port used, for example “1” for COM1

2.1.4 Device Name

The four-character device name for the driver.

Valid entry: SNPX

2.1.5 Function

This field refers to the different types of EDI communication modes.



Valid entry: SYSPRG

2.1.6 Memory

The amount of memory in K-bytes used for the block storage size of the read and write informationentered by the user. This entry refers only to the memory used by the driver for data storage for therelated Logical Port.

Valid entries: 4-63

2.1.7 Comment

(Optional) Description for the current Logical Port. Used only for application documentation.

Valid entry: 14 alphabetic or numeric characters



2.2 Axisware GE SNPX Read/Write Control

This table specifies the tags used to control the reading and writing of the values specified in the Read/Write

Information table (the controlling tags are the Read Trigger, Read Disable, Write Trigger, Write Disable). Italso defines the tags that will report the status of reads and writes (the status tags are the Read Complete,Read State, Write Complete, Write State). Each line in this table refers to one Read/Write Information

Table.

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.

2.2.1 Table Name

User assigned name of the Read/Write Information Table to be defined or modified.

Valid entry: ASCII string incorporation up to 16 of the following character set:A-Z,a-z,@,$,_, or 0-9

2.2.2 Unsolicited Read

Allows you to select whether the current table will be considered in the processing of an unsolicitedmessage received from the PLC..

Valid entries: Descriptions:

No Unsolicited reads are not processed

2.2.3 Exception Write

Option determining whether or not a specific tag in the related Read/Write Information Table is writtento the selected logical station whenever the real-time database value for that tag changes.

Valid entries: Description:

Yes A change of status of any element in the table generates a write of thatelement's value.

No No exception processing.

2.2.4 Block Read Priority



Priority influencing the order in which the EDI task handles the queuing of block read requests. If tworequests are received simultaneously by EDI, the request with the highest priority (lowest number) isprocessed first.

Valid entries: 1-4 (default = 1)

2.2.5 Block Read Trigger

Digital tag whose value, when forced to 1 (ON), initiates a block read of the values specified in therelated Read/Write Information Table. This trigger allows the block read operation to be initiated bysome other task.

Valid entry: FactoryLink digital tag

2.2.6 Block Read Disable

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 theBlock Read Trigger defined above.


2.2.7 Block Read Complete

Digital tag whose value is force written to 1 (ON) by the EDI task whenever any block read operation forthis table is completed. If this tag is specified then when the EDI task initializes, its value is forcewritten to 1 (ON).

Note: Block Read Complete tags are valid only if a different table is used for each logical port.


2.2.8 Block Read State

Digital tag whose value is 0 (OFF) when a block read of the tags specified in this table is in progress and1 (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.




2.2.9 Block Write Priority

Priority influencing the order in which the EDI task handles the queuing of block write and exceptionwrite requests. If two requests are received simultaneously by EDI, the request with the highest priority(lowest number) is processed first.

Valid entries: 1-4 (default = 1)

2.2.10 Block Write Trigger

Dgital tag whose value, when forced to 1 (ON), initiates a block write of the values specified in therelated Read/Write Information Table. This trigger allows the block write operation to be initiated bysome other task.


2.2.11 Block Write Disable

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 theBlock Write Trigger defined above.


2.2.12 Block Write Complete

Dgital tag whose value is force written to 1 (ON) by the EDI task whenever any block write operationfor this table is completed. If this tag is specified then, when the EDI task initializes, its value is forcewritten to 1 (ON).

Note: Block Write Complete tags are valid only if a different table is used for each logical port.


2.2.13 Block Write State

Dgital tag whose value is 0 (OFF) when a block write of the tags specified in this table is in progress and1 (ON) otherwise. If this tag is specified then, when the EDI task initializes, its value is force written to1 (ON).

Note: Block Write State tags are valid only if a different table is used for each logical port.




2.3 Axisware GE SNPX Read/Write Information Table

The Read/Write Information Table links FactoryLink tags to specific addresses in the PLC represented by theLogical Station. Values are either read into the tags from the device or written from the real-time database tagsto the device.

These tables are sometimes referred to as overlay panels, or ovr panels. Each table has one entry (line) for itin 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.

2.3.1 Tag Name

Name of the FactoryLink tag to be updated as a result of the read operation or the tag from whichinformation is taken to be written to the device.

Valid entry: FactoryLink tag(DIGITAL, ANALOG, LONGANA,FLOAT, MESSAGE)

2.3.2 Logical Station

Number from the Logical Station Table identifying the particular combination of physical attributes thatwill define and govern the data transfer to and from the real-time tag.


2.3.3 Data Region

Mnemonic defining area of device memory to be accessed.

Valid entries: See Appendix I (Series 90 Addressing) for examples.



2.3.4 Element

Numeric portion of device address; may be word or bit address depending on the entry selected for theData Region.

Valid entries: Range varies with PLC model

See Appendix I (Series 90 Addressing) for examples

2.3.5 Bit or Length

If a digital tag is used and a word oriented data region has been selected, this field is used to specify thebit offset in the selected word. If a message tag is used, the field specifies the number of bytes that are tobe transferred between the message tag and the Logical Station.

Valid entries: Digital tags 0-15 (Word addressing-data regions only)0-LSB 15-MSB

Message tags 1-255 Must be an even number of bytes in word regions.(1 is the default)

2.3.6 PLC Data Type

Type of data representation in PLC for information being read/written from/to the Logical Station.

Valid entries: See Appendix H (Data Types and Conversions).

2.3.7 Comment

(Optional) Comment field for application documentation.

Valid entries: 21-character alphanumeric text.



2.4 Axisware GE SNPX Logical Station Control

This table is used to configure each logical port and its associated stations in the Logical Station Information

table. It specifies which specific port is connected to the external device being defined.

After completing these fields, select "Next" or Ctrl-N to edit the Logical Station Information Table

corresponding to the table selected by the cursor.

2.4.1 Logical Port

Number specified in the External Device Definition Table which represents a particular communicationspath.

This number must also be referenced in the External Device Definition panel.


2.4.2 Status Msg Tag

(Optional) Message tagto which a text string will be written if an error is encountered in theprocessing of an EDI request.

Valid entry: FactoryLink message tag

2.4.3 Baud Rate

Determines the speed at which data will be transmitted over the network. All devices on the networkmust be configured for the same baudrate.

Valid entries: 300, 600, 1200, 2400, 4800, 9600, or 19200

2.4.4 Parity

Selects the desired parity for the serial communications between FactoryLink and the PLC. Theparity must be the same for all devices on the network.



Valid entries: ODD, EVEN, or NONE

2.4.5 Data Bits

Number representing the desired number of data bits for the serial communications betweenFactoryLink and the PLC. The specified number of data bits must be the same for all devices on thenetwork.

Valid entry: 8

2.4.6 Stop Bits

Number representing the desired number of stop bits for the serial communications betweenFactoryLink and the PLC. The specified number of stop bits must be the same for all devices on thenetwork.

Valid entries: 1 or 2

2.4.7 Response Timeout 0.1 Sec

Number of seconds in tenths permitted for the driver to process a request.

Valid entries: Actual value in tenths of seconds (3 - 4 seconds for most applications)



2.5 Axisware GE SNPX Logical Station Information

This table defines the logical station(s) accessible through a specific logical port defined in the Logical

Station Control Table. Each logical station is tied to its physical station address and device type. This logicalstation information structure allows communications to multiple devices on a network using one logical port. 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 Managermain menu.

2.5.1 Error/Status Tag Name

(Optional) Analog tag to which all error codes for this logical station are to be written.

Valid entries: FactoryLink analog tag

2.5.2 Logical Station (Decimal)

Number entered by user to represent a particular combination of a logical port (PCIM card) and physicaldevice (PLC). This number is referenced in the Read/Write Information Table to correlate specificaddresses and tags with a physical device (PLC). This number must be unique for each four-letterdevice ID (SNPX).


2.5.3PLC Name

A 8-character ASCII string that specifies the device.

Valid entry (example): myplc

2.5.4 Device Type

Type of device on the network with which communications are to be established.

Valid entries: Description:"GE9030" GE Fanuc 90-30 PLC"GE9070” GE Fanuc 90-70 PLC



2.5.5 Connect Status Tag Name

Name of ANALOG tag that indicates the current status of the logical station.

Valid entry: Any valid analog tag.

Run-time value in analog tag if specified:-2 -- disabled-1 -- disconnected 0 -- inactive 1 -- connecting 2 – running 3 - disconnecting

2.5.6 Comment

(Optional) Description for the current Logical Station. Used only for application documentation.

Valid entry: 31 alphabetic or numeric characters



3 Appendices

3.1 Appendix A: (Reserved)

This appendix is reserved for future use.



3.2 Appendix B: (Reserved)




3.3 Appendix C: (Reserved)




3.4 Appendix D: Software Installation-Windows 95/NT

3.4.1 Before Starting Installation - (Windows 95/NT version) Updating From A Previous Version:

If the driver software is an update from an older version, the following procedures must be followed for thesoftware to be properly installed. First, the operator must exit from both the Run Manager and the ConfigurationManager. Second, a multiplatform save file should be created. Third, the driver should be installed as describedbelow. Fourth, restore the multiplatform save file created in step 2. Fifth, update the Configuration Managertables 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 filescopied 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 valueto $FLINK, and then restart the install program. $FLINK can be assigned a parameter by using the SETcommand (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 copiesof both files will be copied to a file with the same filename but a .NVA extension. The first file to be modifiedis $FLINK\AC\TITLES (where $FLINK is the FactoryLink directory). This file is used by the ConfigurationManager to determine which tasks to list and also the order in which they are to be listed. The following linewill be added to the TITLES file. (The line may be different, depending on your FactoryLink version.)

snpx.ac EDI Axisware GE SNPX Driver If you have a backup file named $FLINK\AC\TITLES.NVA (possibly created by a previous install), theprogram 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 thecreation of the binary CT (configuration table) files used at run-time by FactoryLink. The following line willbe added to the CTLIST file.

snpx: snpxshdr snpxsovr snpx_hdr snpx_ovr If you have a backup file named $FLINK\CTGEN\CTLIST.NVA (possibly created by a previous install), theprogram will ask you during the install if you wish to exit, and manually save a copy of this .NVA file beforeit is overwritten.

3.4.2 Driver Installation Instructions (Windows 95/NT)



The driver software is loaded by inserting the driver diskette in drive A or B. At a command prompt, makethe 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 directorycontaining the FactoryLink program files, press a key to exit and use the set command to reset the $FLINKenvironment variable. The problem may be resolved by clearly stating the drive letter. At a commandprompt 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 setFLINK=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 tocontinue. The following message will appear

Copying configuration files to hard disk . . .

followed by a message relevant to obtaining authorization for the product, if required.

The install program checks for a backup file named $FLINK\AC\TITLES.NVA. If found, the followingmessage is displayed:

This install program will update your file named

$FLINK\AC\TITLES

$FLINK\AC\TITLES.NVA (a backup file) already exists.

To overwrite it, press y followed by Enter (Return).

By pressing n, you may Exit, manually save

your .NVA backup file, and restart this program.

Enter either y or n followed by the Enter (Return) key ==>

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:

This install program will update your file named

$FLINK\CTGEN\CTLIST

$FLINK\CTGEN\CTLIST.NVA (a backup file) already exists.

To overwrite it, press y followed by Enter (Return).

By pressing n, you may Exit, manually save your

.NVA backup file, and restart this program.

Enter either y or n followed by the Enter (Return) key ==>



The messages

Updating listing of driver names. . .

andUpdating CTLIST . . .

are briefly displayed while the backup (.NVA) versions are being created and the $FLINK\AC\TITLES and$FLINK\CTGEN\CTLIST files are updated. If one of the following error messages appear:

!!!! Unable to update $FLINK\AC\TITLES file or

!!!! Unable to update $FLINK\CTGEN\CTLIST file

the lines to be added to these files can be typed in manually using a text editor. Refer to the section “BeforeStarting 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 beencopied the following message will appear:

.....Installation Program Completed.

3.4.3SoftKey Protection Validation

Please refer to the SoftKey Manual and run the program Validate to ensure that your product does notexpire 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.



3.5 Appendix E: (Reserved)




3.6 Appendix F: Driver Status Codes

3.6.1 Application startup errors

The following error codes (alphabetized) may be reported to FactoryLink while the driver tables are beingprocessed at startup.

*****ERROR: Bad edi_dev.ct fileCheck for valid application entries.

*****ERROR: Bad write of Device Definition file ______.dct

Full disk, invalid $FLAPP.

*****ERROR: Could not open Device Definition file ______.dctCheck for valid application entries, invalid $FLAPP.

*****ERROR: LOGICAL PORT ___ is not defined

Check the Logical Port field in the External Device Definition table. Each EDI driver musthave a unique number, between 0 and 999.

*****ERROR: Out of memory

The following error messages (alphabetized) which are preceded by “gehc:“ are followed by a locationindicating 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: Invalid FL_TYPE:The FL_TYPE may not have been specified. Please refer to Appendix H (Data Types andConversions).

gehc: Invalid Logical Station Command:

Please refer to Appendix J (Logical Station Commands) for valid logical stationcommands.

gehc: Invalid PLC Region:Bit addressing regions: G, GA, GB, GC, GD, I, M, Q, S, SA, SB, SC, T;Word addressing regions: AI, AQ, R.

gehc: Invalid PLC TYPE for Analog Tag:Valid types: INT8, UINT8, INT16, UINT16, INT32, FLT.

gehc: Invalid PLC TYPE for Bit Region:

gehc: Invalid PLC TYPE for Digital Tag:Only the BIT PLC data type may be used with digital tags.



gehc: Invalid PLC TYPE for Floating Point Tag:Valid types: INT8, UINT8, INT16, UINT16, INT32, FLT.

gehc: Invalid PLC TYPE for Long Analog Tag:Valid types: INT8, UINT8, INT16, UINT16, INT32, FLT.

gehc: Invalid PLC TYPE for Message Tag:If message tags are used, either the LOHI or HILO data type must be selected for that tag.

gehc: Invalid PLC TYPE for Word Region:The data type specified is not valid for this area of PLC memory.

gehc: Invalid Region for Read:The LS data region is write only.

gehc: Invalid Region for write:Regions S, SA, SB, and SC are for status data and are Read Only regions.

gehc: Invalid Starting Element and length:Either the starting element or length of the PLC data type reference exceeds the maximum

element number for the region. Please check Appendix I (Series 90 Addressing) forexamples of valid addressing.

gehc: Invalid Tag type for bit access:FactoryLink tags that access bits should be of type DIGITAL.

gehc: Invalid Tag type for Logical Station Command

gehc: Message Length limited to 255 bytes:Each message tag must be less than 256 characters in length.

gehc: Message Tags in word regions must have even byte length:Check the Bit or Length field in the Read/Write Information Table.

gehc: Operation must be on byte boundary:In bit addressing regions, all “non-bit” operations must start on a byte boundary (1, 9, 17, 25,...)

gehc: Out of memory allocating internal address structureThe driver was unable to internally allocate all the necessary memory. Malloc returned null.

gehc: Packet Aborted: Maximum __ Analog Tags ExceededThere is a limit of 1024 FactoryLink tags in any one packet. Break up the tags into more thanone table.

gehc: Packet Aborted: Maximum __ Digital Tags ExceededThere is a limit of 1024 FactoryLink tags in any one packet. Break up the tags into more thanone table.

gehc: Packet Aborted: Maximum __ Floating Point Tags Exceeded



There is a limit of 1024 FactoryLink tags in any one packet. Break up the tags into more thanone table.

gehc: Packet Aborted: Maximum __ Long Analog Tags ExceededThere is a limit of 1024 FactoryLink tags in any one packet. Break up the tags into more thanone table.

gehc: Packet Aborted: Maximum __ Message Tags ExceededThere is a limit of 1024 FactoryLink tags in any one packet. Break up the tags into more thanone table.

gehc: Undefined Logical Station:Make sure the Logical Station is specified in the Read/Write Information Table and the Logical Station

Information Table.

3.6.2 Run-time startup errors

The following errors (alphabetized) may be reported when the EDI task is started after all tables have beenprocessed. All the following errors are immediately fatal.

gehccpt(cpt_start) ret: NN from gehc_proc_lportNN indicates the logical port. Check the Logical Port entries in the External Device

Definition and Logical Station Control tables; rebuild DCTS.

gehccpt(lsrun_connect) XXXXXX out of resources attempting to connectToo many active logical stations for platform. Reduce number of logical stations or adjustdisable or inactive timeout fields.

gehccpt(lsrun_connect) Connect XXXXXX SRX error: NNNN

NNNN indicates a hex value to be looked up in Appendix G (HCT SRX Error Codes).

gehccpt(lsrun_connect) Connect XXXXXX Unknown return code: NNNNContact Axisware support and report the values in this error message.

gehccpt(lsrun_connect) port: XXXXXX station: XXXXXX invalid

Check the GEF_CFG.INI file.

gehccpt(lsrun_connecting) XXXXXX Connection FailedCheck the connection to the PLC indicated.

gehccpt(lsrun_connecting) XXXXXX Connection Timeout

Check the connection to the PLC indicated.

gehccpt(lsrun_process_completed_req) HCT_SRX_ERROR: NNNNgehccpt(lsrun_running) HCT_DISCONNECT SRX_ERROR: NNNN from HCT_read_reqgehccpt(lsrun_running) HCT_DISCONNECT SRX_ERROR: NNNN from HCT_write_req


gehccpt(lsrun_running) HCT_MAX_MSG return from HCT_read_req



Maximum requests for platform exceeded. Reduce Max Concurrent Requests field inLogical Station Information table.

gehccpt(lsrun_running) HCT_MAX_MSG return from HCT_write_reqMaximum requests for platform exceeded. Reduce Max Concurrent Requests field inLogical Station Information table.

gehccpt(lsrun_running) HCT_NULL return from HCT_read_reqgehccpt(lsrun_running) HCT_NULL return from HCT_write_reqgehccpt(lsrun_running) HCT_RESOURCE return from HCT_read_reqgehccpt(lsrun_running)HCT_RESOURCE return from HCT_write_reqgehccpt(lsrun_running) HCT_SESS_UNKNOWN return from HCT_read_reqgehccpt(lsrun_running) HCT_SESS_UNKNOWN return from HCT_write_req

Contact Axisware support.

gehccpt(lsrun_running) HCT_SRX_ERROR: NNNN from HCT_read_reqgehccpt(lsrun_running)HCT_SRX_ERROR: NNNN from HCT_write_req


gehccpt(lsrun_running) Unknown return code: NNNN from HCT_read_reqgehccpt(lsrun_running) Unknown return code: NNNN from HCT_write_reqgehccpt(process_completed_request) Unknown return HCT_poll_status: NNNNgehccpt(proc_lscmd) unknown Logical station command NNNN

Contact Axisware support.

gehcrntm(proc_lport) invalid port definition lengthCheck configuration tables; rebuild DCTS. Possibly mismatched versions.

gehcrntm(proc_lport) null malloc station runtime datagehcdsf(solicited request) invalid state: NNNN

Contact Axisware tech support.

3.6.3 SoftKey protection errors

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 followingmessage will be displayed.

Serial #: XXXXXXX Single Processor Run Time LicenseThis is a normal informational message displaying the product name and your SerialNumber.

3.6.4 Run-time errors

The following errors may be reported while the driver is processing application requests. The text representsthe 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 followingerrors are not immediately fatal, recurring errors should be evaluated and eradicated to maintain the integrity ofthe 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 usefulinformation for Axisware technical support personnel. If one of the following error messages appear, please record (write down) the entire message beforecontacting Axisware. (Each message begins with a module name followed by a function name.)

gehcrntm(create_sol_requests) null from mallocgehcrntm(create_sol_tables) null from mallocgehcrntm(get_request_queue) null parametergehcrntm(get_table_queue) null parametergehcrntm(place_request_queue) null parametergehcrntm(place_table_queue) null parametergehcrntm(remove_request_queue) null parametergehcrntm(remove_request_queue) request not foundgehcrntm(remove_table_queue) null parametergehcrntm(remove_table_queue) table not found



3.7 Appendix G: HCT SRX Error Codes

These error codes are returned from the HCT package. Refer back to the section on runtime errors inAppendix F (Driver Status Codes).

3.7.1 Invalid Parameter Errors Error codes in this group indicate that a parameter in a call from the Toolkit to the underlyingcommunications driver was invalid. Value Description of Error Condition(hex)1 SRX Driver did not understand what command was being requested.2 The code identifying the SRX Driver is invalid.3 A flag had an invalid value.4 A type field contained an invalid value.5 The requested feature is not supported by the SRX Driver.

3.7.2 System Errors Error codes in this group indicate that a basic system error of some kind occurred.Value(hex)

Description of Error Condition

7 Some resource other than buffer allocation couldnot be obtained.

8 The maximum number of SRX Driver users arealready active.

9 Attempt to allocate a buffer failed.A SRX Driver timed out waiting for an event to occur.

3.7.3 Communications Stack Errors

Value(hex)


B Error in opening the communications device.C Unable to set status data.D Unable to activate local LSAP address.E Too many LSAPs already registered.F Invalid read address.10 Cannot activate multicast address.11 Error in obtaining Write confirmation.12 Cannot delete multicast address.13 Cannot deactivate local LSAP address.



14 Error in Read Request.15 Received Connect Indication in bad FSM

state.16 Received Connect Confirm in bad FSM state.17 Received Data Indication in bad FSM state.18 Received Disconnect Indication in bad FSM

state.19 Received internal request for data in bad

state.1A Remote application sent disconnect request.1B Remove device sent disconnect request.1C Local connect request failed.1D Local TSAP registration failed.1E Foreign address registration failed.1F Local address registration failed.20 Local Data Request failed.

3.7.4 Connect Errors

Error codes in this group indicate that an error has occurred when attempting to establish a session to theremote PLC. Value(hex)


22 Remote application refused sessionestablishment.

23 Connect Request is not correctly formed.24 Specified remote device is not responding.25 Communications Driver could not form

connect request.26 Specified remote device not found in device

name database.27 The specified protocol is not supported.28 The specified port name is not present in the

*.INI configuration file.

3.7.5Transfer Errors Error codes in this group indicate that an error has occurred when attempting to transfer data between thelocal user application and the remote PLC. Value(hex)


29 An error has occurred in attempting to encode themessage from the Toolkit.

2A Remote device sent a data packet with an improperlength.

2B There is insufficient data to send the request.



2C The data is not valid for this request.2D There is more data than allowed for this request.2E No data currently available for the SRX Driver user.

3.7.6 Invalid State Errors

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. Value(hex)


30 No connection exists.31 Not in sending mode.32 FSM is not in the IDLE state.33 No connect indication pending.34 No local connect request has been issued.35 Not in receiving mode.36 Not in a connected or sending state.37 Not in a connected or receiving state.

3.7.7 PLC CPU Error Codes

Error Code Service Request Error Description05ffH Service request has been aborted.05feH No privilege for attempted operation.05fdH Unable to perform auto configuration.05fcH I/O configuration is invalid.05fbH Cannot clear I/O configuration.05faH Cannot replace I/O module.05f9H Task address out of range.05f8H Invalid task name referenced.05f7H Required to log in to a task for service.05f6H Invalid sweep state to set.05f5H Invalid password.05f4H Invalid input parameter in request. Check to

ensure that the address actually exists in thePLC.

05f3H I/O configuration mismatch.05f2H Invalid program cannot log in.05f1H Request only valid from programmer.05f0H Request only valid in stop mode.05efH Programmer is already attached.05eeH Could not return block sizes.

PLC CPU Error Codes (continued)

Error Code Service Request Error Description



05edH VMEbus error encountered.05ecH Task unable to be created.05ebH Task unable to be deleted.05eaH Not logged in to process service request.05e9H Memory Type selector not valid in context.05e8H No user memory is available to allocate.05e7H Configuration is not valid.05e6H CPU model number does not match.05e5H DOS file area not formatted.05e4H Memory Type for this selector does not exist.05e3H CPU revision number does not match.05e2H IOS could not delete configuration or bad type.05e1H No I/O configuration to read or delete.05e0H Service in process cannot login.05dfH Invalid datagram connection address.05deH Size of datagram connection invalid.05ddH Unable to locate given datagram connection ID.05dcH Unable to find connection address.05dbH Invalid Memory Type selector in datagram.05daH Null pointer to data in Memory Type selector.05d9H Transfer type invalid for this Memory Type selector.05d8H Point length not allowed.05d7H Invalid datagram type specified.05d6H Total datagram connection memory exceeded.05d5H Invalid block name specified in datagram.05d4H Mismatch of configuration checksum.05d3H User Program Module (UPM) read or write exceeded block end.05d2H Invalid write mode parameter.05d1H Packet size or total program size does not match input.05d0H One or more PLC modules configured have unsupported revision.05cfH Specified device is not available in the system (not present).05ceH Specified device has insufficient memory to handle request.05cdH Attempt was made to read a device but no data has been stored on it.05ccH Data stored on device has been corrupted and is no longer reliable.05cbH A comm or write verify error occurred during save or restore.05caH Device is write-protected05c9H Login using non-zero buffer size required for block commands.05c8H Password(s) already enabled and cannot be forced inactive.05c7H Passwords are set to inactive and cannot be enabled or disabled.05c6H Control Program (CP) tasks exist but requester not logged into main CP.05c5H No task-level Rack/Slot configuration to read or delete.05c4H Verify with FA Card or EEPROM failed.05c3H Text length does not match traffic type.05c2H The OEM key is NULL (inactive).05c1H Invalid block state transition.



3.8 Appendix H: Data Types and Conversions

The driver supports the following FactoryLink tag types:

DIGITALANALOGLONG ANALOGFLOATING POINTMESSAGE

The driver also supports the following PLC data types: BIT (single data bit)BIN (single data bit)INT8 (8 bit signed integer)UINT8 (8 bit unsigned integer)INT16 (16 bit signed integer)UINT16 (16 bit unsigned integer)INT32 (32 bit signed integer)UINT32 (32 bit unsigned integer)INT1 (1 byte signed integer)UINT1 (1 byte unsigned integer)INT2 (2 byte signed integer)UINT2 (2 byte unsigned integer)INT4 (4 byte signed integer)UINT4 (4 byte unsigned integer)FLT (32 bit floating point)HILO (character string - “Byte swapped from/to PLC data

stream”)LOHI (character string - same as data from/to PLC data

stream)DEF (type determined by FactoryLink tag type) When DEF is used, the PLC data type is determined and set automatically by the tag type:

FactoryLink TagType

PLC Data Type

DIGITAL BITANALOG INT2 or INT16

LONG ANALOG INT4 or INT32FLOATING POINT FLT

MESSAGE LOHI Valid PLC data types for each of the FactoryLink tag types:

DIGITAL ANALOG LONG ANALOG FLOATINGPOINT

MESSAGE

BIT or BIN INT1 or INT8 INT1 or INT8 INT1 or INT8 LOHIUINT1 or UINT8 UINT1 or UINT8 UINT1 or UINT8 HILOINT2 or INT16 INT2 or INT16 INT2 or INT16

UINT 2 or UINT16 UINT2 or UINT16 UINT2 or UINT16



INT4 or INT32 INT4 or INT32 INT4 or INT32UINT4 or UINT32 UINT4 or UINT32 UINT4 or UINT32

FLT FLT FLT



3.9 Appendix I: Series 90 Addressing

PLC memory regions are divided into two functionally distinct addressingtypes: bit addressing regions, and word addressing regions.

BIT ADDRESSING REGIONS: G, GA, GB, GC, GD, GE, I, M, Q, S, SA,

SB, SC, TWORD ADDRESSING REGIONS AI, AQ, R

Bit addressing regions:

Individual bit writes are only allowed in bit addressing regions. In bitaddressing regions, all “non-bit” operations must start on a byte boundary (1,9, 17, 25, …). When working with bits in bit addressing regions, alwaysleave blank the Bit Or Length fields in the Read/Write Information Tables.

Word addressing regions:

PLC data types INT1, UINT1, INT8 and UINT8 cannot be written to or readfrom word addressing regions. Individual bit writes are not allowed in thisregion. Message tags must have an even byte length.

3.9.1Bit Addressing Regions (Examples)

Global DataThe global data regions are denoted by %G, %GA, %GB, %GC, %GD, and %GE. Thisdata region is accessed by bit addressing rather than word addressing.

Examples:

Region Element DescriptionG 1 %G0001GA 14 %GA0014GE 100 %GE0100



Discrete InputsThe discrete input data region is denoted by %I. This data region is accessed by bitaddressing rather than word addressing.

Examples:

Region Element DescriptionI 1 %I0001I 14 %I0014I 100 %I0100

Discrete InternalsThe discrete internal data region is denoted by %M. This data region is accessed by bitaddressing rather than word addressing.

Examples:

Region Element DescriptionM 1 %M0001M 14 %M0014M 100 %M0100

Discrete OutputsThe discrete output data region is denoted by %Q. This data region is accessed by bitaddressing rather than word addressing.

Examples:

Region Element DescriptionQ 1 %Q0001Q 14 %Q0014Q 100 %Q0100

System Status GroupThe system status group data regions are denoted by %S, %SA, %SB, or %SC. These dataregions are accessed by bit addressing rather than word addressing. The S region is ReadOnly. SA, SB, and SC are read or write.

Examples:

Region Element DescriptionS 1 %S0001SA 14 %SA0014SC 32 %SC0032

Discrete TemporariesThe discrete temporary data region is denoted by %T.

Examples:

Region Element DescriptionT 1 %T0001T 14 %T0014



T 100 %T0100

3.9.2Word Addressing Regions (Examples)

Analog InputsThe analog input data region is denoted by %AI. Examples:

Region Element DescriptionAI 1 %AI0001AI 14 %AI0014AI 50 %AI0050

Analog OutputsThe analog output data region is denoted by %AQ. Examples:

Region Element DescriptionAQ 1 %AQ0001AQ 14 %AQ0014AQ 50 %AQ0050

RegistersThe register data region is denoted by %R. Examples:

Region Element DescriptionR 1 %R00001R 14 %R00014R 150 %R00150

Logical Station Commands (LS)

This is a special region to command driver logical station configuration. See Appendix J:Logical Station Commands.



3.10 Appendix J: Logical Station Commands

3.10.1 SNPX Logical Stations

When the GEHC protocol module is running, each logical station is an object which controls solicitedoperation access to its mapped physical device. The logical station runs in one of six states. The current stateof any logical station can be monitored by the FactoryLink application by specifying an analog tag in theConnect Status Tag Name field of the Logical Station Information Panel. Following is a description ofeach 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/disablecommand, please refer to the logical station command section later in this appendix. In this state all requestsreceived by the logical station are aborted with a status code of 4. The logical station will remain in this stateuntil 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 iswaiting the station reconnect wait period. In this state all requests received by the logical station will beaborted 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 EDItask is terminated. Logical Station Inactive (0): Initial logical station state. In this state the logical station remains idle usingminimal system resources until a request is received. Upon receipt of a request the logical station willattempt 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 physicalstation (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 communicationserror 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 physicalstation. The logical station will remain in this state until disconnected and will then move to either theDisabled or Disconnected state depending on the reason for the disconnection.

3.10.2 Logical Station Commands The Logical Stations Command (LS) data region allows for the FactoryLink application to modify certainelements of a runtime logical station’s configuration. This data region is write only as it commands thelogical 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 LogicalStation field, and the command code in the Element field. Let the remaining fields default by leaving themblank. Following are descriptions of the possible logical station commands. The number preceding thecommand description is the command code (element).



1 Logical Station Enable/Disable: This command will either enable or disable the logical stationdepending on the value of the digital tag written to the logical station. If the value of the digital tagis zero the logical station is disabled, if the value of the digital tag is one the logical station isenabled. 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 themessage tag written to the logical station. This name change will not take effect until the logicalstation is disconnected and reconnected. Use the Logical Station Enable/Disable command to forcedisconnect and reconnect.

3 Included for compatibility with other Axisware GE Fanuc drivers..This command has no effect onSNPX protocol.



3.11 Appendix K: FactoryLink Version Upgrade Procedures

After installing this communications driver, upgrading to a newer version of FactoryLink may appear tocause operational problems. This is due to the modifications to certain text files made by installing thisproduct being overwritten during the install of the new FactoryLink version. However, these files can bereconfigured using a text editor Before installing the FactoryLink upgrade it is important to do a multiplatform save of yourapplication.

After installing the FactoryLink upgrade, the following steps should be done before restoring themultiplatform save file of your application: Where $FLINK indicates the FactoryLink directory (example: FLINK=C:\FLWIN): 1. Edit the file $FLINK\AC\TITLES and add the following line:

snpx.ac EDI Axisware GE SNPX Driver

2. Open the file $FLINK\CTGEN\CTLIST and add the following line:

snpx: snpxshdr snpxsovr snpx_hdr snpx_ovr

The SAMPLE directory of the nstall cd-rom includes compressedmultiplatform save files of a sample application for this driver. The sample

application can be used to test communications, as well as serve as an exampleof how to prepare a FactoryLink application to use the driver. The sampleapplication has examples of block reads, block writes, exception writes and

unsolicited reads from a single PLC. Please refer to the "README.TXT" filein the SAMPLE directory for instructions on how to use this application.



3.12 Appendix L: Samp

The SAMPLE directory of the nstall cd-rom includes compressed multiplatform save files of a sampleapplication for this driver. The sample application can be used to test communications, as well as serve as anexample of how to prepare a FactoryLink application to use the driver. The sample application has examples ofblock 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 worktogether to allow FactoryLink to exchange information from the tag database with the device.

External Device Definition Table

Configuration table that tells the application what type of devices are connected to the computer's ports andassigns them a logical port number.

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).

Logical Station Control Table

Table used to configure each logical port and its associated stations in the Logical Station Information table.The Logical Station Control table specifies which specific port is connected to the external device beingdefined.

Logical Station Information Table

Table which defines the logical station(s) accessible through a specific logical port defined in the LogicalStation Control table. Each logical station is tied to its physical station address and device type.

Proof of License

An 8 1/2 by 11 certificate that must accompany the software indicated by its unique serial number when thatproduct is sold or transferred to another company or entity.

Read/Write Control Table

Table used to configure each logical port and its associated stations in the Logical Station Information table.Each line in this table refers to one Read/Write Information table.

Read/Write Information Table

Configuration table that links FactoryLink tags to specific addresses in the PLC represented by the LogicalStation.

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 thesoftware to function past the grace period.



5 Contact information:

Axisware LLC

[email protected]://www.axisware.com

3213 Peppertree Pl.Plano, TX 75074, USA

T: 1-(214)-764-1876F: 1-(214)-764-1878


http://www.axisware.com/

axisware snpx manual: factorylink driver for ge fanuc snpx serial

Documents