Axisware PCIM Manual: FactoryLink Driver For GE Fanuc PCIM Genius Bus

GE Fanuc PCIM Driver
for FactoryLink
Version 7.2
Axisware GE Fanuc PCIM Driver for FactoryLink 1
Contents
1 Overview......................................................................................................1
1.1 Software License.....................................................................................................1
1.2 Introduction.............................................................................................................1
1.3 Historical Note........................................................................................................1
1.4 PCIM Card Installation...........................................................................................1
1.5 Software Installation...............................................................................................1
2 Factorylink Application Configuration......................................................3
2.1 External Device Definition.....................................................................................3
2.1.1 Logical Port.............................................................................................3
2.1.2 Device Name...........................................................................................3
2.1.3 Function...................................................................................................3
2.1.4 Memory...................................................................................................3
2.1.5 Comment.................................................................................................4
2.2 Axisware GE PCIM Read/Write Control................................................................5
2.2.1 Table Name.............................................................................................5
2.2.2 Unsolicited Read.....................................................................................5
2.2.3 Exception Write......................................................................................5
2.2.4 Block Read Priority.................................................................................6
2.2.5 Block Read Trigger.................................................................................6
2.2.6 Block Read Disable.................................................................................6
2.2.7 Block Read Complete.............................................................................6
2.2.8 Block Read State.....................................................................................6
2.2.9 Block Write Priority................................................................................7
2.2.10 Block Write Trigger..............................................................................7
2.2.11 Block Write Disable..............................................................................7
2.2.12 Block Write Complete..........................................................................7
2.2.13 Block Write State..................................................................................7
2.3 Axisware GE PCIM Read/Write Information Table...............................................8
2.3.1 Tag Name................................................................................................8
2.3.2 Logical Station........................................................................................8
2.3.3 Data Region.............................................................................................8
2.3.4 Memory Offset (Address).......................................................................8
2.3.5 Bit # or Length........................................................................................9
2.3.6 PLC Data Type........................................................................................9
2.3.7 No Current Function...............................................................................9
2.3.8 Program Task Name................................................................................9
2.3.9 Program Block Name..............................................................................9
2.4 Axisware GE PCIM Logical Station Control.......................................................10
2.4.1 Logical Port...........................................................................................10
2.4.2 Timeout (Tenths)...................................................................................10
2.4.3 Card Memory Address (Hex)................................................................10
2.4.4 I/O Port Address (Hex).........................................................................10
2.4.5 Global Reference...................................................................................11
2.4.6 Global Length........................................................................................11
2.4.7 Configure Redundancy..........................................................................11
2.4.8 Redundancy Status Tag.........................................................................11
Axisware LLC support@axisware.com www.axisware.com

10/2004
2.4.9 Message Tag..........................................................................................12

2.5 Axisware GE PCIM Logical Station Information.................................................13
2.5.1 Error/Status Tag Name..........................................................................13
2.5.2 Logical Station (Decimal).....................................................................13
2.5.3 Device Type..........................................................................................13
2.5.4 Station Address.....................................................................................14
2.5.5 Comment...............................................................................................14
3 Appendices................................................................................................15
3.1 Appendix A: Installation of PCIM Card..............................................................15
3.1.1 Original PCIM with DB-9P and 6 pin connector..................................15
3.1.2 Single Slot PCIM with dual 4 pin connectors.......................................17
3.2 Appendix B: Software Installation - OS/2...........................................................20
3.2.1 Before Starting Installation (OS/2 version)..........................................20
3.2.2 Driver Installation Instructions (OS/2).................................................20
3.2.3 Modifying the CONFIG.SYS File (OS/2)............................................22
3.3 Appendix C: (Reserved).......................................................................................23
3.4 Appendix D: Software Installation - Windows 95/NT........................................24
3.4.1 Before Starting Installation (Windows 95/NT version)........................24
3.4.2 Driver Installation Instructions (Windows 95/NT)...............................25
3.4.3 Modifying FLRUN.BAT File (Windows 95/NT).................................27
3.5 Appendix E: (Reserved).......................................................................................28
3.6 Appendix F: Driver Status Codes........................................................................29
3.6.1 Application startup errors.....................................................................29
3.6.2 Run-time startup errors.........................................................................31
3.6.3 SoftKey protection errors......................................................................33
3.6.4 Run-time errors.....................................................................................33
3.6.5 Unsolicited message processing errors.................................................35
3.7 Appendix G: (Reserved)......................................................................................37
3.8 Appendix H: Data Types and Conversions..........................................................38
3.9 Appendix I: Table Names....................................................................................41
3.10 Appendix J: Global Data....................................................................................42
3.11 Appendix K: Datagrams.....................................................................................45
3.12 Appendix L: (Reserved).....................................................................................48
3.13 Appendix M: (Reserved)....................................................................................49
3.14 Appendix N: Unsolicited Reads.........................................................................50
3.15 Appendix O: (Reserved).....................................................................................56
3.16 Appendix P: FactoryLink Version Upgrade Procedures...................................57
3.17 Appendix Q: Sample Application......................................................................58
4 Glossary.....................................................................................................59
5 Contact information:.................................................................................60

10/2004
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 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.
Copyright 1995-1996 NOVA Technologies

Copyright 1997-2000 Bullet Software
Copyright 2000-2004 Axisware LLC
All Rights Reserved

10/2004
1 Overview
1.1 Software License

Axisware LLC grants you a non-exclusive license to use the Software programs and related documentation
for this product on a single processing unit. For each processing unit that executes the Software programs for
this product you must have a unique serial number and Proof of License statement. No one other than a
current Axisware employee or agent is permitted to modify or tamper with in any way the executable
computer files(s) associated with this product. This license applies solely to the software contained in this
product, and does not include any additional software or documentation provided by Axisware or other
parties required for the proper operation of this product.
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 FactoryLink GE Fanuc PCIM communication
driver software.
The driver currently supports the 90-70, Series-6, GCM+ (90-30 module for Genius network), and all the
currently available Genius blocks. Unsolicited messages from the 90-70 and Series-6 are supported. Diagnostic
information may be read from Genius blocks. Also, configuration data can be read from or written to Genius
blocks.
1.3 Historical Note

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

The installation and setup of the PCIM card is briefly described in Appendix A, but you should also refer to
your hardware manuals for complete information.
1.5 Software Installation

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

10/2004
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
OS/2 B
Windows NT 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.

10/2004
2 Factorylink Application Configuration
2.1 External Device Definition

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 PCIM 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.
2.1.1 Logical Port
Number assigned by the user to indicate a particular communication path. This number must be unique
for each EDI driver used in the application.
Valid entries: 0-999 Physical Card & Physical Port
These fields are not used by this driver.
2.1.2 Device Name
The four-character device name for the EDI driver that will use the related Logical Port.
Valid entry: "PCIM"
2.1.3 Function
Type of communication used by the EDI driver for the related Logical Port. This field refers to the
different types of EDI communication modes.
Valid entry: "SYSPRG"
2.1.4 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.
Valid entries: 4-63

10/2004
2.1.5 Comment
(Optional) Description for the current Logical Port. Used only for application documentation.
Valid entry: 14 alphabetic or numeric characters

10/2004
2.2 Axisware GE PCIM 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). It
also 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. Appendix I
contains additional information for the naming conventions that must be followed to configure
Fault/Diagnostic or Configuration tables for Genius blocks.
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 or not the current table will be considered in the processing of an
unsolicited message received from the PLC. Standard addressing is used to correlate the message from
the PLC with the tags configured in the table. Please refer to Appendix N for additional information
and examples.
Valid entries: Descriptions:
Yes Normal write to the real-time database

Force Forced write to the real-time database
No No unsolicited reads are processed
2.2.3 Exception Write
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.
Valid entries: Description:
Yes A change of status of any element in the table generates a write of that
element's value.
No No exception processing.

10/2004
2.2.4 Block Read Priority
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.
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 the
related Read/Write Information Table. This trigger allows the block read operation to be initiated by
some 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 the
Block 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 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.
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 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.

10/2004
2.2.9 Block Write Priority
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.
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 the
related Read/Write Information Table. This trigger allows the block write operation to be initiated by
some 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 the
Block 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 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.
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 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.

10/2004
2.3 Axisware GE PCIM Read/Write Information Table

The Read/Write Information Table links FactoryLink tags to specific addresses in the PLC represented by the
Logical Station. Values are either read into the tags from the device or written from the real-time database tags
to the device.
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.
2.3.1 Tag Name
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.
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 that
will define and govern the data transfer to and from the real-time tag.
Valid entries: 0-999
2.3.3 Data Region
Mnemonic defining area of device memory to be accessed, or manner in which device is to be addressed,
e.g., AI, AQ, G, R, ... Sometimes called “Data Table” or “Reference Table”.
Valid entries: Please refer to Appendices J (Global Data) &

K (Datagrams) for further information.
2.3.4 Memory Offset (Address)
Numeric portion of device address. Sometimes referred to as “Element”. May be word, byte, or bit
address depending on the selected device and Data Region.
Valid entries: Please refer to Appendix J (Global Data) &

Appendix K (Datagrams) for further information.

10/2004
2.3.5 Bit # or Length
If a digital tag is used and a byte or word oriented data region has been selected, this field is zero base
and is used to specify the bit offset in the selected byte or 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.
Valid entries: Digital tags 0 - 7 (Byte addressing)

0 - 15 (Word addressing)
Message tags 1 - 127
2.3.6 PLC Data Type
Data type for information being read/written from/to the Logical Station.
Valid entries: Please refer to Appendix H for further information.
2.3.7 No Current Function
This field has been included to maintain compatibility with the GE SNP driver tables. The entry must be
left as the default.
Valid entry: XX
2.3.8 Program Task Name
Used only for the 90-70 Bus Controller and specifies the program task name required for the data
regions "L" and "P".
Valid entries: Alphabetic string of up to 7 characters with no

embedded spaces
2.3.9 Program Block Name
Used only for the 90-70 Bus Controller and specifies the program block name required for data region
"L".
Valid entries: Alphabetic string of up to 7 characters with no

embedded spaces

10/2004
2.4 Axisware GE PCIM 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 communications
path.
This number must also be referenced in the External Device Definition panel.
2.4.2 Timeout (Tenths)
Number of tenths of seconds permitted for the driver to process a request.
Valid entries: Actual value in tenths of seconds.

20 to 30 (or 2 - 3 seconds for most applications).
2.4.3 Card Memory Address (Hex)
Address for memory shared by the PCIM card and the FactoryLink CPU. This number must match the
address configured for the PCIM daughter board.
Valid entries: Hex memory address between A000 and F800

(E000 suggested)
Example: A000, A800, B000, ..., E800, F000, F800
Please refer to Appendix A for further information.
2.4.4 I/O Port Address (Hex)
I/O port address as configured for the PCIM daughter board.
Valid entries: Hex port address as allowed by PCIM card

(3E0 hex suggested)
Please refer to Appendix A for further information.

10/2004
2.4.5 Global Reference
Global Data Reference Address used by some devices on the Genius network. Check documentation for
specific device to determine if and how it is used. This value is not used directly by the PCIM driver;
however, the integer value is written to the card and is available to other devices on the network.
Valid entries: 0 - 32000
2.4.6 Global Length
Number of bytes broadcast as global data and directed outputs and number of bytes received as global
data and directed inputs.
Note: The number of bytes broadcast as global data can drastically affect the speed of the Genius
network.
Valid entries: 0 - 128 bytes
2.4.7 Configure Redundancy
Specifies whether redundant bus controllers exist on the Genius network as devices 30 and 31.
YES Redundant bus controllers have been configured on the

Genius network. All writes directed toward device 31 will
also be sent to device 30. All reads directed toward device 31
will be redirected to device 30 if 31 is no longer on the
network or fails to respond.
NO No special operations are desired.
2.4.8 Redundancy Status Tag
(Optional) Analog tag to which the redundancy status will be written during run-time. The following
codes may be returned by the driver:
0 - Both devices running properly

1 - Device 31 down but 30 is running properly
2 - Device 30 down but 31 is running properly
3 - Both devices are down
Valid entry: FactoryLink analog tag

10/2004
2.4.9 Message Tag
(Optional) Message tag to which a text string will be written in the case of any error encountered in the
processing of an EDI request.
Valid entry: FactoryLink message tag

10/2004
2.5 Axisware GE PCIM 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 logical
station 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 Manager
main 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 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 (PCIM).
2.5.3 Device Type
Type of device on Genius network with which communications are to be established.
"90-30" 90-30 bus controller

"90-70" 90-70 bus controller
"Series5" Series-5 bus controller (Possible future
revision)
"Series6" Series-6 bus controllera
"GCM" 90-30 GCM+
"GDIO_8" Standard 8-circuit I/O block
"GIIO_8" Isolated 8-circuit I/O block
"GDI_16" 16-circuit input block
"GRO_16" 16-circuit relay output block
"GA4I_2O" Analog block with 4 inputs and 2 outputs
"GS4I_2O" Source block with 4 inputs and 2 outputs
"GS6O" Source block with 6 outputs

10/2004
"GRTD_6I" RTD block with 6 inputs

"GTC_6I" Thermocouple block with 6 inputs
"GHSCNT" High speed counter block
"GPWRTRAC" Power monitor block
"PCIM" PCIM card
2.5.4 Station Address
Genius network address of device with which communications are to be established.
Valid entries: 0-31
2.5.5 Comment
(Optional) Description for the current Logical Station. Used only for application documentation.
Valid entry: 31 alphabetic or numeric characters

10/2004
3 Appendices
3.1 Appendix A: Installation of PCIM Card

There are two types of GE Fanuc PCIM card: the original PCIM with DB-9P and 6 pin connector; the Single Slot
PCIM with dual 4 pin connectors. Thedriver supports both cards. This appendix explains how to set up either of
these cards to work with the driver.
3.1.1 Original PCIM with DB-9P and 6 pin connector
The GE Fanuc PCIM card must be installed in the computer in an open, full length slot. However, prior to the
card's installation, the appropriate I/O port address, interrupt, baud rate, serial bus address, shared memory
segment address, watchdog timer setting and any application-specific settings must be properly set by jumpers or
switches. For more information on installing the GE Fanuc PCIM card then is cover in this section refer to GE
Fanuc manual “Genius I/O PCIM User’s Manual” Pub. # GFK-0074A.
3.1.1.1 Jumpers and Switches
I/O Port Address
The I/0 port address is selected by SW1 on the PCIM card. The eight dip switches on SW1 are set in
accordance with what is specified in the PCIM manual (GFK-0074A). An I/O port address setting of 3E0 (hex)
is recommended; the following chart illustrates the proper switch settings for this address.
I/O PORT ADDRESS 3E0
SW1
1 2 3 4 5 6 7
| | | | | | |
C C C 0 0 0 0
where,
C = Closed
O = Open
Interrupt Level
The interrupt level is selected by SW4 on the PCIM card. The current version of the driver does not support
interrupts; therefore, all six switches must be open.

10/2004
Baud Rate
The baud rate is selected by dip switches six (6) and seven (7) on the switch assembly which resides on the
PCIM daughterboard (Please refer to the PCIM manual). Both of these dip switches should remain open unless
the network requires a lower baud rate because of noise. Please note that all nodes on one Genius network must
have the same baud rate
Serial Bus Address

The serial bus address is selected by the first five dip switches on the switch assembly which resides on the
PCIM daughterboard (Please refer to the PCIM manual). This address must be unique from all other nodes on
the Genius network. Valid addresses range from zero (0) to thirty-one (31); however, care should be taken to
avoid conflicts with the hand held monitor and bus controllers which generally reside at address zero (0) and
thirty-one (31), respectively. The following example would configure the PCIM card at serial bus address ten
(10).
SERIAL BUS ADDRESS 10
Daughterboard Switches
1 2 3 4 5 6 7 8
| | | | | | | |
C O C O C X X X
where,
C = Closed
O = Open
X = Not used for address
Shared Memory Segment Address
The shared memory segment address is selected by SW2 and SW3 on the PCIM card. The six dip switches on
each of the two switch assemblies are set in accordance with the PCIM manual. Please note that switch one (1)
of SW3 must be open for the driver to properly function. A shared memory segment address of E0000 (hex) is
recommended; the following chart illustrates the proper switch settings for this address.
SHARED MEMORY SEGMENT ADDRESS E0000

10/2004
SW2
1 2 3 4 5 6
| | | | | |
C C C O O O
SW3
1 2 3 4 5 6
| | | | | |
O X X X X X
where,
C = Closed
O = Open
X = Not used
Watchdog Timer
The watchdog timer MUST be disabled by placing jumper JP2 in the 1-2 position (Please refer to the PCIM
manual). If JP2 is left in the 2-3 position, the driver will not complete any requests.
Application-Specific Settings
Two (2) selections on the board remain which should be configured in accordance with the needs defined by the
specific application. JP1 is used to connect or disconnect the terminating resistor; please see discussion in the
PCIM manual. Dip switch number eight (8) on the PCIM daughterboard is used to enable or disable outputs
from the PCIM card. If outputs are enabled, all devices capable of receiving directed global data will receive
their outputs from the PCIM card. If outputs are disabled, only those devices to which writes have been
configured in FactoryLink will receive their outputs from the PCIM card. Both of these settings can be selected
to meet the needs of the specific application.
Cable Connections
The required communication cable is discussed in the PCIM manual. The same twisted shielded pair used for
other Genius network devices should be used with the PCIM card. The six (6) pin connectors on the back of the
PCIM card should be wired as follows: pin 1 is Serial 1, pin 2 is Serial 2, pin 3 is Shield In, and pin 4 is Shield
Out. Pin 5 and pin 6 are not used.
3.1.2 Single Slot PCIM with dual 4 pin connectors
The GE Fanuc PCIM card must be installed in the computer in an open, full length slot. However, before
installing the card the appropriate I/O port address for configuring the board must be set in the DIP switch on the

10/2004
PCIM board. The GE Fanuc PCIM card must be configured with the configuration software “DPCIMCFG.EXE”
provided be GE Fanuc. For more information on installing the GE Fanuc PCIM card please refer to the GE
Fanuc manual “Single-Slot PC Interface Module (PCIM)” Pub. # GFK-0881.
Note: It is important to note that “DPCIMCFG.EXE” is a DOS program. It will run in a DOS window in
Windows and also in a DOS window in OS/2 but it will not correctly run in a DOS window under
Windows NT. To configure the card on Windows NT the computer MUST be booted in DOS..
Note: The FactoryLink GE Fanuc PCIM Communication Driver WILL support two PCIM daughter boards on
the same PCIM card. Simply treat the daughter boards as two separate cards.
3.1.2.1 Switches
The default setting for the Board Address DIP switches is 222hex. If there are multiple PCIMs or if the address
conflicts with addresses used by other modules, it must be changed to an address in the range 102hex to 3FEhex.
Switches 1 and 2 set the high hex digit, 3, 4, 5, and 6 set the middle digit, and switches 7 and 8 set the low hex
digit.
Switch Positions for 222hex (default):
Switch: 1 2 3 4 5 6 7 8
| | | | | | | |
U D D D U D D D
where,
U = Up
D = Down
3.1.2.2 Configuration Software
I/O Port Address
Use the up and down arrow keys to move to the field labeled I/O base and enter in the desired I/O Port address in
HEX.
Note: This I/O Port to be entered in the “Axisware GE PCIM Logical Station Control” I/O Port Address field
NOT the I/O Port set with dip switches on the card..
Interrupt Level
Use the up and down arrow keys to move to the field labeled Interrupt. The current version of the driver does not
support interrupts; therefore, the Interrupt field must read “Disabled”. Use the left and right arrow keys to toggle
the field to disabled.

10/2004
Baud Rate
Use the arrow keys to move to the field labeled Baud. Use the left and right arrow keys to select the desired
network Baud Rate. The baud rate should remain “153.6K Std” unless the network requires a lower baud rate
because of noise. Please note that all nodes on one Genius network must have the same baud rate.
Serial Bus Address

Use the up and down arrow keys to move to the field labeled Device and type in the desired Serial Bus Address.
This address must be unique from all other nodes on the Genius network. Valid addresses range from zero (0) to
thirty-one (31); however, care should be taken to avoid conflicts with the hand held monitor and bus controllers
which generally reside at address zero (0) and thirty-one (31), respectively.
Shared Memory Segment Address

Use the up and down arrow keys to move to the field labeled Memory base and enter the desired Shared
Memory Address.
Watchdog Timer
The watchdog timer MUST be disabled. Use the up and down arrow keys to move to the field labeled
Watchdog then use the left and right arrows to toggle to the selection disabled.
3.1.2.3 Cable Connections
The required communication cable is discussed in the PCIM manual. The same twisted shielded pair used for
other Genius network devices should be used with the PCIM card. The four pin connectors on the back of the
PCIM card should be wired as follows: pin 1 is Serial 1, pin 2 is Serial 2, pin 3 is Shield In, and pin 4 is Shield
Out.

10/2004
3.2 Appendix B: Software Installation - OS/2
3.2.1 Before Starting Installation (OS/2 version)
Updating From A Previous Version:
If the driver software is an update from an older version of the driver, 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 NOVA Technologies 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:\FLOS2.
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 value by using the SET
command (example: set flink=d:\flos2).
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 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.)
pcim.ac EDI NOVA GE PCIM Driver
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 files used by the Run-time FactoryLink. The following line will be added to the
CTLIST file.
pcim: pcimshdr pcimsovr pcim_hdr pcim_ovr
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.
3.2.2 Driver Installation Instructions (OS/2)
It is important that you have followed the hardware installation procedures described in Appendix A
before proceeding with the driver installation instructions.

10/2004
The driver software is loaded by inserting the driver diskette in drive A or B. At the OS/2 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 the OS/2 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 “NOVA Technologies” 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 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 following
message 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:

10/2004

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

By pressing n, you may Exit, manually save your

.NVA backup file, and restart this program.
The messages
Updating listing of driver names. . .
and
Updating 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. Please refer to the section
Before Starting Installation (OS/2 version) 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 on the screen:
.....NOVA Installation Program Completed.
3.2.3 Modifying the CONFIG.SYS File (OS/2)
The device driver NOVAMEM.SYS must be loaded into memory when your system boots in order for the
FactoryLink PCIM driver to function properly. After the INSTALL program is run, the CONFIG.SYS file must
be modified manually, using a text editor, such as OS/2’s System Editor.
The following line (or one similar) must be added to the OS/2 CONFIG.SYS file. The directory specified for
the device driver is created when the software is installed from the installation diskette. Assuming that
$FLINK is set to c:\flos2, the line should be:
DEVICE=C:\FLOS2\EDI\PCIM\NOVAMEM.SYS
It is very important that only one reference to this device driver be made in the CONFIG.SYS file.
This driver will support four cards. They may be PCIM cards, or other cards that use the NOVAMEM.SYS
driver.

10/2004
Note: The changes you make to your CONFIG.SYS file will not take effect until you reboot your system.

10/2004
3.3 Appendix C: (Reserved)
This appendix is reserved for future use.

10/2004
3.4 Appendix D: Software Installation - Windows 95/NT
3.4.1 Before Starting Installation (Windows 95/NT version)
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:\FLNT.
If $FLINK has not been defined when the install is started, you will be requested to exit and assign a
parameter to $FLINK, and then restart the install program. $FLINK can be assigned a value by using the
SET command from a DOS prompt (example: set flink=d:\flnt).
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. 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.
pcim.ac EDI Axisware GE PCIM Driver
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 files used by the Run-time 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.
It is important that you have followed the hardware installation procedures described in Appendix A
before proceeding with the driver installation instructions.

10/2004
3.4.2 Driver Installation Instructions (Windows 95/NT)
The driver software is loaded by inserting the driver diskette in drive A or B. After making the drive
containing the diskette the current working drive, type INSTALL at a DOS prompt and press Enter. The
installation may also be started by using File… Run…from Windows NT’s Program Manager or File
Manager, or by using Start… Run..
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 the DOS 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\flnt or set FLINK=t:\sect2\factory. Make sure that the only space in this command
is between “set” and “FLINK”.
After the “NOVA Technologies” 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 the Enter (Return) key to
continue.
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 following
message is displayed:

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

By pressing n, you may Exit, manually save

your .NVA backup file, and restart this program..
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:

%FLINK%\CTGEN\CTLIST

10/2004
%FLINK%\CTGEN\CTLIST.NVA (a backup file) already exists.

By pressing n, you may Exit, manually save your

.NVA backup file, and restart this program.
The messages
Updating listing of driver names. . .

and
Updating 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 Before
Starting Installation (Windows NT version) for the specific lines and where they are to be added.
When all of the necessary files have been copied the following message will appear on the screen:
.....NOVA Installation Program Completed.
Restart your computer to ensure that all changes have been properly made.

10/2004
3.4.3 Modifying FLRUN.BAT File (Windows 95/NT)
During the installation process, the NOVAMEM.SYS device driver is registered with the Windows NT system
registry. However, an additional step is required to actually start the NOVAMEM.SYS device driver.
The NOVAMEM device driver must be loaded for the communications driver to function. This can be
accomplished by either of two methods. The first is by adding the following command to the FLRUN.BAT
(located in $FLINK\BIN\). The line should be added just beneath the 'setlocal' command line.
net start novamem
A better method is to open the Control Panel folder located on the Windows NT Program Manager, then start
the Devices program using the icon located in that folder. Scroll down the list of services until NOVAMEM is
located, then change its startup type to SYSTEM.

10/2004
3.5 Appendix E: (Reserved)

10/2004
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 GE PCIM Driver tables are
being processed at startup.
Bitwise data anomaly

Duplicate binary address encountered.
Configuration/Fault information may not be accessed for bus controllers / GCM / PCIM
The selected device does not support datagrams that read or write configuration/ fault
information. If this information is needed for a bus controller, it may be read from the bus
controller by the host PLC and then read into FactoryLink from the PLC.
Configuration/Fault information may only be returned with types DGBIT, DGBYT, and DGWRD
If configuration data is to be read from or written to a Genius block, one of these Data Regions
must be used. All other data regions are considered invalid.
Data anomaly
Indicates that addresses and data types specify overlapping elements.
Datagram write not valid for selected Genius block

Write operations via datagrams are not valid to the selected Genius block; however, some
blocks permit global data writes.
Data offset invalid for PCIM card memory

When memory accesses are defined in the Read/Write Information Tables, the maximum byte
offset is 128.
Data offset must be non-zero for selected data table

Only GIBYT, GOBYT, DGBYT, DCBYT, WDBYT are zero based. All other data tables
(regions) are one based, and, therefore, must have addresses which are greater than 0.
Data table invalid for Genius block

DGBIT, DGBYT, and DGWRD are the only datagrams supported for Genius blocks.
However, global data may also be read from blocks.
Data table "L" for 90-70 requires both task and block names
The specified data table (region) is not valid unless the program task name and program block
name are both given.
Data table "P" for 90-70 requires task name

The specified data table (region) is not valid unless the program task name is given.
DIGITAL tags may not be used with numerical types

DIGITAL tags may only be used to read or write discretes.

10/2004
Digital write not allowed for word address

The protocol for the 90-70 does not permit digital writes to be directed toward word addresses.
(R, AI, AQ, L, P)
Digital write not valid for Genius block datagram

Datagrams to Genius blocks do not support digital writes.
Invalid bit number specified

A bit number greater than 15 may not be specified. Specifying the proper byte or word will
allow access to all bits without exceeding this limit.
Invalid data offset specified for High Speed Counter

The addressing for the High Speed Counter is different than any other device. Please refer to
Appendix K for the details concerning addresses for this device.
Invalid data table specified for X

Please refer to Appendix J (Global Data)& Appendix K (Datagrams) for a list and discussion
of valid addresses for each device. X represents the specific device selected.
Invalid data type encountered

Please refer to Appendix H for list of valid data types.
Invalid data type selected for device

The number of bytes required for the data type specified is greater than the maximum number
of bytes returned by the selected device.
Invalid data type selected for High Speed Counter

Only four bytes of data may be requested from a High Speed Counter. Any data type requiring
more than four bytes is invalid.
Invalid device type specified

The data file is corrupted and contains a device not recognized by the driver. Delete the
indicated record and type in the record again, selecting a valid device type.
Logical station X not found

The logical station X was specified in the current Read/Write Information Table, but this
logical station number was never defined in the Logical Station Information Table.
MESSAGE tags may not be used with numerical types

Only the ASC data type may be used with MESSAGE tags.
Negative data offset not permitted

No data region supports a data offset of less than zero. Enter a valid positive address for the
offset.
No tag given
The indicated line of the Read/Write Information Table currently being processed does not
contain a valid FactoryLink tag name.
No tags, read/write packet not made

10/2004
The current Read/Write Information Table contained entries that caused a portion of the table
to generate an error and consequently no DCT information was output.
Only DIGITAL tags may be used with BIN

Binary data may only be accessed with DIGITAL tags.
Only GIXXX and GOXXX used with digital blocks, GCM, or PCIM card
Please refer to Appendix J (Global Data) & Appendix K (Datagrams) for the details of
addressing each device.
Only MESSAGE tags may be used with ASC

ASCII strings may only be read into MESSAGE tags.
Ordering anomaly
Indicates that the Read/Write Information Table currently being processed contains addresses
such that the driver is unable to properly arrange all the entries.
Out of Memory
The driver was unable to internally allocate all the necessary memory. Allocate more memory
in the External Device Definition Table.
Positive string length for MESSAGE tags required

If a message tag is used, the Bit # or Length field in the Read/Write Information Table
represents the length (in bytes) of the message used in the transaction. This number must be
between 1 and 128.
Specified configuration/fault offset or data length is too large

There are a limited number of configuration and fault bytes available for each Genius block.
The requested offset and data type defines a transaction which is beyond the end of the data
that can possibly be returned.
Unsolicited not permitted for configuration/fault tables

Configuration tables and fault tables may not be processed as unsolicited messages. Only
standard tables for 90-70 and Series-6 PLCs will be processed and evaluated to resolve
incoming unsolicited messages.
Writes are not permitted for fault table

The operator has configured writes in a fault table. Diagnostic information may not be written
to a Genius device.
Write not allowed to specified data table

Status tables in the 90-70 are configured to be read only. Any writes defined to these regions
are considered invalid.
3.6.2 Run-time startup errors
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.

10/2004
Cannot get pointer from card driver (error : X) [OS/2 only]

System call failed to return card pointer. Check that the driver NOVAMEM.SYS is specified in
the CONFIG.SYS file as indicated in Appendix B.
Cannot open device (error: X) [OS/2 only]

Unable to open the OS/2 device driver NOVAMEM.SYS. Check that this file is specified in the
CONFIG.SYS file as indicated in Appendix B.
Invalid global length

The global length entered on the Logical Station Control Table must be between 0 and 128. If
this error occurs, the driver corrects the value to 128 and continues.
Invalid redundancy status tag

The redundancy status tag entered on the Logical Station Control Table must be an analog tag.
If this error occurs, the driver functions as if no tag was configured.
No heartbeat detected after setup complete

Check the PCIM card jumpers, dip switches, and that it is properly inserted. Verify that the
watchdog timer has not been enabled. Ensure that no shared memory conflicts (including ROM
shadowing) exist.
PCIM card failed to initialize in allowed time

shadowing) exist.
PCIM communications error

shadowing) exist.
PCIM configuration error returned

shadowing) exist.
PCIM configuration never accepted

shadowing) exist.
PCIM OK signal never received from card

shadowing) exist.
Specified I/O port address X is invalid

The I/O port address must be on a four byte boundary. The address must fall between 200 hex
and 6FF hex.
Timeout waiting for card reset

10/2004
The PCIM card did not respond as expected. Check all card jumpers, dip switches, and verify
that the PCIM card is properly inserted. Verify that the watchdog timer has not been enabled.
Ensure that no shared memory conflicts (including ROM shadowing) exist.
Unable to allocate needed memory

Increase memory allocated to PCIM task.
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 following
message will be displayed.
Serial #: XXXXXXX Single Processor Run Time License

This is a normal informational message displaying the product name and your Serial
Number.
3.6.4 Run-time errors
The following errors may be reported while the driver is processing the EDI 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.
(10) Device X failed to respond

The indicated Genius device did not respond to a datagram. Check cabling and the device
address. Also check that no restrictions concerning global data are being violated.
(11) Buffer manipulation error

Internal communication error between DSF and CPT module. Please contact Axisware if the
error persists.
(12) Datagram may not be sent to host PCIM

The configured transaction defined a datagram to the host PCIM card.
(13) Station 31 down - Control to redundant CPU!

Station 30 down - No backup CPU!
Redundancy failure - No CPU response!
A redundancy error was detected by the driver. The Redundancy Status Tag should be used to
determine the exact status of redundancy.
(14) Device X not found on network

The indicated Genius device was not found on the network. Check cabling and the device
address. Also check that no restrictions concerning global data are being violated. Error may
also be seen on the Windows platform if memory is not properly excluded in SYSTEM.INI or
CONFIG.SYS.

10/2004
(15) Syntax error occurred on read from/write to device X

The transaction defined to the specified device could not be completed because of a syntax
error. If the error persists, contact Axisware.
(16) Process error occurred on read from/write to device X

The transaction defined to the specified device could not be completed because of a process
error. Verify that the transaction is valid. This error occurs if an invalid area of memory is
being accessed or a device does not accept a datagram.
(17) Unknown error Y occurred on read from/write to device X

The transaction defined generated an unknown error. Verify that the transaction is valid.
Contact Axiswares if the error persists.
(18) Lockout table malfunction

The PCIM card is not responding as expected. Check that card is configured properly. If error
persists, contact Axisware
(19) Zero length buffer error

A request has been made to the CPT module with a zero byte transaction length. This error
should not occur, please contact Axisware.
(20) Timeout waiting for clear to transfer

Transmit buffer on PCIM card was not free to receive new message before timeout occurred.
Check that all messages are valid, that the card is properly configured, and that the timeout
value specified in the Logical Station Control Table is greater than the total driver cycle time.
(21) Timeout initializing PowerTRAC data

PowerTRAC failed to give data ready signal within allowed time. Check block configuration
and timeout values.
(22) Overcurrent data not available for device X

Overcurrent data can only be read from a PowerTRAC block when an overcurrent error has
occurred. The status word returned from the PowerTRAC block contains this information.
(40) XXXX pcimdsf dsf_read()/dsf_write() error returned from dsf_t_q_mail()

Internal queue handling error encountered. Contact Axisware.
(41) Calculated memory address out of range

The maximum memory offset for global data must be less than the Global Length configured in
the Logical Station Control Table.
(42) Bytes requested less than one

Internal processing error. Contact Axisware if the error persists.
(43) Module communication timeout

Communication failure between modules. Increase the timeout specified in the Logical Station
Control Table. If the error persists, contact Axisware.
(44) Datagram write to block not supported

10/2004
The operator attempted to write data to a Genius block. This operation is not supported by the
Genius protocol.
(45) DSF attempt to write fault information

Diagnostic or fault information may only be read. Any attempt to write such information will
generate an error.
3.6.5 Unsolicited message processing errors
The following errors may be reported while the driver is attempting to process unsolicited message requests.
The text represents the error message returned to the message tag defined in the Logical Station Control Table.
While the following errors are not immediately fatal, recurring errors should be evaluated and eradicated to
maintain the integrity of the network.
Unsolicited queue full; messages may have been lost

Only 16 unsolicited messages may be queued to the PCIM card at one time. This error
indicates that the driver cannot process the messages as quickly as they are received.
No unsolicited reads have been defined

An unsolicited message has been received over the Genius network; however, no unsolicited
messages were defined in the Configuration Manager. If unsolicited messages are to be used,
at least one line on the Read/Write Control Table must specify unsolicited message support.
Unable to establish unsolicited index

Internal software error, contact Axisware.
Unable to evaluate unsolicited message

An unsolicited message was received over the Genius network with an unexpected format.
Please check Appendix N for details concerning the processing of unsolicited messages.
X undefined unsolicited message - Y

An unsolicited message directed toward device X, address Y was received. This address has
not been configured as an unsolicited message in the Configuration Manager.
EDI DSF pointer error

Software error; contact Axisware.
Linked list error

Software error; contact Axisware.
Unable to allocate memory for all unsolicited messages

Allocate more memory to EDI task. Please note that the current driver limits the number of
unsolicited messages configured to about 6500 due to the segment size. If this limit is reached,
please contact Axisware.
Maximum number of unsolicited reads exceeded

A maximum number of 32,000 unsolicited reads may be configured. However, the practical
limitation due to memory is about 6500. If this limit is reached, please contact Axisware.

10/2004
Unsolicited message received, but length invalid

The length specified in the unsolicited message is greater than 136. Check that the message
from the 90-70 or Series-6 is valid. Please refer to Appendix N for more information.
Partial byte detected within returned data

Due to the 90-70 binary addressing used in the returned message, a configured tag received
only a portion of the necessary data required from the PLC.
Invalid tag type for unsolicited message

Internal software error. Contact Axisware.

10/2004
3.7 Appendix G: (Reserved)

10/2004
3.8 Appendix H: Data Types and Conversions
The driver supports the following FactoryLink tag types:
DIGITAL
ANALOG
LONG ANALOG
FLOATING POINT
MESSAGE
The driver also supports the following PLC data types:
BIN (single data bit)

BYTE (8 bit unsigned integer)
INT2 (16 bit signed integer)
INT4 (32 bit signed integer)
BCD4 (16 bit, 4 digit BCD)
BCD8 (32 bit, 8 digit BCD)
FLT4 (32 bit floating point - single precision)
FLT8 (64 bit floating point - double precision)
ASC (ASCII strings)
Valid PLC data types for each of the FactoryLink tag types:
DIGITAL ANALOG LONG ANALOG FLOATING POINT MESSAGE

BIN BYTE BYTE BYTE ASC
INT2 INT2 INT2
INT4 INT4 INT4
BCD4 BCD4 BCD4
BCD8 BCD8 BCD8
FLT4 FLT4 FLT4
FLT8 FLT8 FLT8
The following descriptions are from the viewpoint of “read”. A similar transfer occurs on writes.
DIGITAL
BIN
DIGITAL tags may only be converted to and from the BIN data type. If the requested binary PLC data
type is on, the DIGITAL tag will be set to one. If the binary element is off, the DIGITAL tag will be set
to zero.
ANALOG
BYTE
The 8 bits of this data type are transferred to the lowest 8 bits of the ANALOG tag.

10/2004
INT2
The ANALOG tag is a 16 bit signed integer; therefore, no conversion is needed.
INT4
The lowest 16 bits of the INT4 data type correspond directly with the 16 bits comprising the ANALOG
tag.
BCD4
After being read from the PLC, the BCD4 value is converted to a 16 bit integer. The value is then
directly transferred without conversion into the ANALOG tag.
BCD8
handled as the INT4 data type above.
FLT4
The whole number portion of the floating point number is transferred to the ANALOG tag. This
conversion is accurate only if the whole number value is between -32768 and +32767. When converting
back to a FLT4, a fractional portion of zero is assumed.
FLT8
The whole number portion of the floating point number is transferred to the ANALOG tag. This
conversion is accurate only if the whole number value is between -32768 and +32767. When converting
back to a FLT8, a fractional portion of zero is assumed.
LONG ANALOG
BYTE
The 8 bits of this data type are transferred to the lowest 8 bits of the LONG ANALOG tag.
INT2
The LONG ANALOG is a 32 bit signed integer; therefore, the 16 bits of the INT2 data type correspond
to the lowest 16 bits of the LONG ANALOG tag.
INT4
No conversion necessary; all 32 bits transfer directly.
BCD4
BCD8
FLT4
The whole number portion of the floating point number is transferred to the LONG ANALOG tag. This
conversion is accurate only if the whole number value is between -2,147,483,648 and +2,147,483,647.
When converting back to a FLT4, a fractional portion of zero is assumed.

10/2004
FLT8
The whole number portion of the floating point number is transferred to the LONG ANALOG tag. This
conversion is accurate only if the whole number value is between -2,147,483,648 and +2,147,483,647.
When converting back to a FLT8, a fractional portion of zero is assumed.
FLOATING POINT
BYTE
The BYTE value is converted into a standard IEEE 64 bit floating point value and then transferred
directly to the FLOATING POINT tag. The fractional portion of the number is assumed to be zero.
INT2
The INT2 value is converted into a standard IEEE 64 bit floating point value and then transferred
INT4
The INT4 value is converted into a standard IEEE 64 bit floating point value and then transferred
BCD4
BCD8
FLT4
The FLT4 value is converted from a standard IEEE 32 floating point number into a standard IEEE 64 bit
floating point number. This value is then transferred directly to the FLOATING POINT tag.
FLT8
The data is transferred directly; no conversion is necessary.
MESSAGE
ASC
All data is read directly into the message tag from the specified device address. No conversion of any
kind is employed.

10/2004
3.9 Appendix I: Table Names
The GE PCIM driver incorporates a system of reserved table names which is not generally part of an EDI driver;
however, in so doing, this driver maintains all aspects of EDI compatibility. Reserved table names may be used
for additional functionality or completely abandoned for a standard configuration. The only data region
mnemonics that may be used for special function configuration tables are DGBIT, DGBYT, and DGWRD.
Please refer to Appendix K for more information concerning data regions. The first four (4) characters of the
table name define the intended purpose of the table. If neither of these table name prefixes are used, the table is
assumed to be a standard read or write table. The following two four-character sequences are reserved:
_FLT If the first four (4) characters of the table name are "_FLT", the table is considered by the driver
to define a fault or diagnostic table. The letters used must be all uppercase and preceded by an
underscore. Fault tables are only valid when configured for block reads from Genius blocks.
All other attempted operations for fault tables will generate errors from the driver. The specific
fault information that can be accessed by a fault table is described in the manuals for each
Genius device. The GE manual Genius I/O System and Communications I (GEK 90486D-1)
contains the most complete listing of this information for all Genius devices in chapter 5.
_CFG If the first four (4) characters of the table name are "_CFG", the table is considered by the driver
to define a configuration table. The letters used must be all uppercase and preceded by an
underscore. Configuration tables are only valid when configured for any type of writes to or
block reads from Genius blocks. All other attempted operations for configuration tables will
generate errors from the driver. The specific configuration information that can be accessed by
a configuration table is described in the manuals for each Genius device. The GE manual
Genius I/O System and Communications I (GEK 90486D-1) contains the most complete listing
of this information for all Genius devices in chapter 4.

10/2004
3.10 Appendix J: Global Data
INTRODUCTION
Two types of data transfers are available to the GE PCIM driver. These two methods are Global Data and
Datagrams. It is the responsibility of the operator to intelligently select between these two methods. Both
methods have positive and negative features; however, the specific application and function will dictate the wise
choice. This appendix describes the use of Global Data; Appendix K is dedicated to the use of Datagrams.
These two appendices are not intended to be an exhaustive or complete discussion of these topics; therefore, if
additional information is desired, please consult the appropriate GE technical manual. A brief description of
Global Data and its implementation for each supported Genius device follows.
DESCRIPTION
The following description of Global data is included in the Genius I/O System and Communication manual
(GEK 90498D-1) page 7-2.
"Global Data is data which is automatically and repeatedly broadcast by a bus controller. All other bus
controllers on the same bus are capable of receiving the data, although some bus controllers can choose
not to. The ability to send Global Data is set up when each bus controller is configured. Once the
system is in operation, the only further action required of an application program is to place new data to
be sent into the selected memory area as often as needed, and to read incoming Global Data which has
been received."
The whole of chapter seven (7) is dedicated to the subject of Global Data in the GE manual referenced above;
therefore, additional information may be obtained from this source. Of special importance and interest may be
the discussion on pages 7-12 and 7-13.
The standard FactoryLink configuration tables previously discussed are used to control and access Global Data
for the PCIM card. This method of data transfer can be very fast; however, if excessive amounts of Global Data
are transferred, the speed of the entire Genius network may be adversely affected.
IMPLEMENTATION
The only data region mnemonics that may be used are GIBIT, GOBIT, GIBYT, GOBYT, GIWRD, and
GOWRD. The second character used in the mnemonic indicates whether the transaction is to be directed toward
the Input or Output tables on the PCIM card. The last three characters of the mnemonic indicate the method in
which the memory offset will be interpreted:
BIT indicates that a one-based bitwise addressing will be used.

BYT indicates that zero-based byte (8 bits) addressing will be used. Zero-based addressing was used for
this selection so that the numeric portion of the address would exactly correspond to the memory maps
given in the GE reference manuals.
WRD indicates that one-based word addressing is to be used.

10/2004
Please note that the data type determines how the data at a given address will be interpreted; therefore, any
addressing scheme may be used with any valid combination of tag types and data types.
Examples:
GIBIT 10 Bit 10 of the Global Data input table
GOBIT 10 Bit 10 of the Global Data output table
GIBIT 33 Bit 33 (bit 1 of word 3) of input table
GIBYT 4 fifth byte of input table (same as above)
GIWRD 3 third word of input table (same as above)
Discrete Blocks (GDIO_8, GIIO_8, ..., GDIO_32)
Each circuit of the block that has been configured as an input may be read directly from the input table
(GIXXX). If circuit 14 of a 16 or 32 circuit block was configured as an input, it could be read as any of the
following addresses:
Table Element Bit

GIBIT 14, (bit #13 -- one-based)
GIBYT 1 (bit # 5 -- zero-based; i.e, the 6th bit of the
second byte)
GIWRD 1 (bit # 13 -- one-based)
Each circuit of the block that has been configured as an output may be assigned directly by writing to the output
table. Care must be taken that more than one device is not attempting to control the outputs for one block. If
circuit 31 of a 32 circuit block was configured as an output, it could be written as any of the following addresses:
GOBIT 31,
GOBYT 3 (bit # 6),
GOWRD 2 (bit # 14).
Analog Blocks (GA4I_2O, GS4I_2O, ..., GTC_6I)
The four (4) or six (6) analog input circuits will be located in consecutive words in the input table. If analog
input four is to be read, the following addresses could be used:
GIBIT 49,
GIBYT 6,
GIWRD 4.
The two (2) output circuits that exist on some blocks may be controlled by writing directly to the output table. If
analog output 1 is to be written, the following addresses could be used:
GOBIT 1,
GOBYT 0,
GOWRD 1.

10/2004
Specialty Blocks (GHSCNT, GPWRTRAC)
A wide range of parameters are sent from these devices each bus scan. The inputs, both discrete and analog, are
accessed from the input table as the other devices described above. The outputs are written to the output table as
described above. The specific values and parameters that may be accessed are described in the manuals for each
device. Great care should be taken in writing to PowerTRAC outputs, because they may actually interfere with
the return of working and overcurrent data.
PLC Data (90-70, Series-6, GCM)
Global Data broadcast from these devices is read from the input table with the above described mnemonics rather
than the natural addressing for that PLC type. This function is not automatic as it is for the Genius blocks;
therefore, each PLC device must be properly configured to broadcast Global Data. The following read examples
assume that the GCM+ has been configured to broadcast from %R0001 and the 90-70 to broadcast from %
G1001:
GCM+
%R0002 GIWRD 2,
%R0019 GIBYT 36,
90-70
%G0010 GIBIN 10,
%G0065 GIBIN 65,
GIBYT 8,
GIWRD 5.
Writing Global Data to these devices is handled a little differently than the other Genius devices discussed so far.
These three devices are configured to receive data broadcast by other devices; therefore, the data must be
broadcast from the PCIM card rather than being written directly to the Genius device. Data is broadcast from the
PCIM card by selecting a logical station defined as a device type "PCIM" and a station address corresponding to
that of the card as selected by the dip switches on the PCIM daughterboard. This data will be broadcast to all
devices on the network capable of receiving such data and will be placed in PLC memory as configured. All data
to be broadcast should be written to the output table for the PCIM card.

10/2004
3.11 Appendix K: Datagrams
INTRODUCTION
Two types of data transfers are available to the GE PCIM driver. These two methods are Global Data and
Datagrams. It is the responsibility of the operator to intelligently select between these two methods. Both
methods have positive and negative features; however, the specific application and function will dictate the wise
choice. This appendix describes the use of Datagrams; Appendix J is dedicated to the use of Global Data.
These two appendices are not intended to be an exhaustive or complete discussion of these topics; therefore, if
additional information is desired, please consult the appropriate GE technical manual. A brief description of
Datagrams and their implementation for each supported Genius device follows.
DESCRIPTION
A Datagram is a message sent over the Genius network to obtain or write information. Datagrams are used to
directly access all data types in the 90-70 or Series-6, obtain fault information, directly access configuration
information, and read input or output information from some Genius blocks.
Datagrams are generally slower than Global Data transfers because the required information is not available until
it is solicited. However, the speed of the network overall is not affected significantly because messages are not
sent continually as with Global Data.
IMPLEMENTATION
Discrete Blocks (GDIO_8, GIIO_8, ..., GDIO_32)

Discrete blocks do not support datagrams that access input or output states; however, datagrams must be used for
configuration and diagnostic information. The available data region mnemonics for these functions are DGBIT,
DGBYT, and DGWRD. The manuals supplied with each device gives the memory map for fault and
configuration information. The following entry, assuming the table name was prefixed with "_CFG", would read
or write configuration information for circuit five (5):
DGBIT 57
DGBYT 8
DGWRD 5 (First byte)
The same method would be used to read fault information.
Analog Blocks (GA4I_2O, GS4I_2O, ..., GTC_6I)

These blocks are handled in a fashion very similar to the discrete blocks; however, some real-time information
may also be returned. The same three data region mnemonics are used. The GE documentation for each device
contains memory maps describing all the information that can be accessed.
PowerTRAC Blocks (GPWRTRAC)

The PowerTRAC blocks handle datagrams essentially like the analog blocks mentioned above. Information in
addition to that which is returned via global data may be obtained through datagrams. A complete listing may be

10/2004
obtained from GE documentation; however, examples of such data would be fundamental VARs, harmonic
VARs, fundamental power factor or line frequency.
In addition to these standard datagram features, waveform data and overcurrent data may be returned from the
block. In general, this information should only be read with a dedicated FactoryLink read table. Waveform data
should not be read more frequently than once every 0.5 seconds. Overcurrent data can only be read after an
overcurrent condition, and not more frequently than once every 0.5 seconds. Waveform data is accessed using
the following data region mnemonics: WDBIT, WDBYT, or WDWRD. Beyond these additional mnemonics, all
previous guidelines apply to accessing this data.
Example:
WDBYT 1024 first byte of channel C current
WDBYT 514 third byte of channel C voltage
WDWRD 129 first word of channel B voltage
WDWRD 896 last word of table
Overcurrent data is accessed using the following data region mnemonics: OCBIT, OCBYT, or OCWRD. These
values are accessed exactly as the waveform data region.
IMPORTANT: The operator must always read the last word from either of these two tables when they are
accessed. This would be addressed as OCBYT 1790, WDBYT 1790, OCWRD 896, or WDWRD 896.
High Speed Counter (GHSCNT)

Configuration and diagnostic information is handled the same way it is with the other blocks. However, the real-
time information is read in a very different fashion. The data region mnemonic must be a datagram type, but all
three valid mnemonics are treated identically when the tables are processed. The protocol requires the operator
to specify a timer number and a data type code. The valid type codes are listed in the manual for the High Speed
Counter. Since this addressing is not easily implemented with the current addressing schemes, the following
rules are used:
1) The number in the fourth decimal digit represents the timer number,
2) The number in the first, second, and third digits represents the timer data type code.
Example:
DGBYT 1001 Read accumulator value (code 1) for timer 1
DGBYT 4006 Read counter timer base (code 6) for timer 4
DGBYT 3031 Read counter preload #1 (code 31) for timer 3
Genius Communications Module - Plus (GMC)

No datagrams may be written to the GCM+. All data to be transferred must be done via Global Data.
90-70
No configuration or diagnostic information for a bus controller may be accessed from FactoryLink; however,
Datagrams are used to access all the memory types in the 90-70. Valid data region mnemonics are as follows:
AI, AQ, G, I, M, Q, R, S, SA, SB, SC, and T. AI, AQ, and R are all word addresses; the remaining types are bit
addresses. Digital writes may not be directed to word addresses, but digital reads may be used. All addresses are
entered exactly as they are used in the PLC. The following examples list possible FactoryLink addresses.
Examples:
AQ 16 %AQ0016,

10/2004
G 1 %G0001,
M 256 %M0256.
T 15 %T0015,
Series-6
No configuration or diagnostic information for a bus controller may be accessed from FactoryLink; however,
Datagrams are used to access all the memory types in the Series-6. Valid data region mnemonics are as follows:
O
I
R
AUXO
AUXI
O1+ through OF+
I1+ through IF+
O0- through OF-
I0- through IF-
O and I are byte addresses, and the remaining data regions are accessed with word addresses. The auxiliary data
regions and channelized I/O are accessed as they are mapped to the registers by the Series-6. The following
examples list possible FactoryLink addresses. Please note that a WINDOW command in the PLC is necessary
for the PCIM card to access the PLC memory.
Examples:
R 1 R00001,
O 15 O0015,
I 16 I0016,
AUXI 256 AI0256,
IC+ 39 IC+0039,
O8- 560 O8-0560.

10/2004
3.12 Appendix L: (Reserved)

10/2004
3.13 Appendix M: (Reserved)

10/2004
3.14 Appendix N: Unsolicited Reads
Unsolicited messages can be configured to allow a PLC (90-70 or Series 6) to send data to the FactoryLink real-
time database without the PLC being polled by the EDI driver. This can be useful for logging PLC data that is
not generated at predefined intervals such as error reporting, diagnostics or data that changes infrequently.
Several simple steps are required to configure the system to receive unsolicited messages.
The first step is to set the column titled Unsolicited Read in the Axisware GE PCIM Read/Write Control
Table to either "Forced" or "Yes". This will allow that specific table to be included in the driver's search for tags
with which to associate the incoming data. The table for which unsolicited reads have been enabled may now be
edited to associate FactoryLink real-time database elements to addresses in the PLC. The same addressing rules
should be followed for unsolicited read tables as for the standard read or write tables. Note: The number of tags
that are configured as unsolicited read tags directly affects the time that is required to process incoming requests;
therefore, if speed is critical, only include the unsolicited read tags that are essential to the application.
The following two sections briefly describe the steps necessary to configure FactoryLink and a 90-70 or a Series-
6 to communicate via unsolicited messages.
90-70 PLC
If Logical Station 10 is a 90-70 bus controller, the following would be an example to receive unsolicited
messages.
TAG LOGICAL DATA DATA

NAME STATION TABLE OFFSET
tagR1000 10 R 1000
tagR1001 10 R 1001
tagR1019 10 R 1019
tagR1025 10 R 1025
The second step is to configure the PLC to send the messages to the FactoryLink PCIM card. This is
accomplished via the 90-70 COMREQ command. The following rung of logic is an example to illustrate this
procedure:

10/2004
| << RUNG 1 STEP #0001 >>

|
|%M0001 +-----+
+--] [-----------+COMM_|
| | REQ |
| | |
| %R0001 -+IN FT+-
| | |
| CONST -+SYSID|
| 0004 | |
| | |
| CONST -+TASK |
| 00000001 +-----+
|
Program: TEST
C:\LM90\TEST
TABLE OF CONTENTS
In the above example, contact %M0001 must only be energized for one PLC scan to initialize the data
transmission. If it is left energized for multiple, successive PLC scans, the Genius LAN will not be able to
transmit the communication commands as quickly as they are being generated. After the message has been
received by FactoryLink, the %M0001 may again be energized for one scan to re-transmit the message.
The SYSID of 4 specified in the COMREQ command indicates the location of the bus controller card in the
PLC rack. The TASK number of 1 must be left unchanged.
The register %R0001 is the starting address for the command block which defines the message. The command
block information defines the communication request and supplies all necessary addresses and parameters. A
COMREQ #14 or Write Device Command, as defined in the Series 90-70 PLC Genius Bus Controller manual
(GFK-0398C), should be used.
The following example illustrates the command block that could be used with the above line of PLC logic (Rung
1...%R0001) to transmit 20 registers starting at location %R1000 to a PCIM card at a Genius node address of 31:

10/2004
%R0001 33 Command Length

%R0002 0 No Wait
%R0003 8 Status information stored at %R0100

%R0004 99
%R0005 0 Idle timeout value

%R0006 0 Maximum communications time
%R0007 12 Command number
%R0008 31 Device number (Address of PCIM card)
%R0009 8 Address to which data will be sent (%R1000)

%R0010 999
%R0011 - 0 Program name and Block name

%R0018
%R0019 20 20 words are to be written
%R0020 - 20 actual data words as sent to PCIM

%R0039
If the three examples in this appendix are combined and the contact %M0001 is energized as described above,
tags tagR1000, tagR1001, tagR1019 would receive the values stored in %R0020, %R0021, and %R0038,
respectively. However, no value would be placed into tag tagR1025 since only 20 values are transmitted (%
R1000 - %R1019).

10/2004
SERIES-6 PLC
If Logical Station 11 is a Series-6 bus controller, the following would be an example to receive unsolicited
messages.
TAG LOGICAL DATA DATA

NAME STATION TABLE OFFSET
tagR6000 11 R 6000
tagR6001 11 R 6001
tagR6005 11 R 6005
tagR6025 11 R 6025
The second step is to configure the PLC to send the messages to the FactoryLink PCIM card. This is
accomplished via the Series-6 DPREQ command. The rungs of logic on the following page represent an
example to illustrate this procedure:

10/2004
|
| << RUNG 1 >>
|
| R01000
+[ BLOCK MOVE ]-( )
| +00001 +00001 +00001 +00001 +00001 +00001 +00001
|
| << RUNG 2 >>
|
| R01000 R01000 O0002
+[WINDOW ADDRESS COMM BLOCK]--------------( )
|
|
| << RUNG 3 >>
|
| O0101 O0100
+--] [---------------------------(OS)
|
|
| << RUNG 4 >>
|
| O0100 R00500
+--] [---[ BLOCK MOVE ]-( )
| +01009 +00012 +00000 +00010 +00510 +00020 +08224
|
| << RUNG 5 >>
|
| O0100 R00510
+--] [---[ BLOCK MOVE ]-( )
| +28416 +00087 +07296 +00001 +00002 +00003 +00004
|
| << RUNG 6 >>
|
| O0100 R00517
+--] [---[ BLOCK MOVE ]-( )
| +00005 +00006 +00007 +00008 +00009 +00010 +00011
|
| << RUNG 7 >>
|
| O0100 R0500
+--] [---[DPREQ]- ( )
|
|
In the above example, contact O0100 is only energized for one PLC scan which initializes the data transmission.
After the message has been received by FactoryLink, I0100 may be toggled to re-transmit the message.
Rungs 1 and 2 set up and execute the WINDOW command which is necessary for the PCIM card to access
Series-6 memory.
The remaining rungs control and execute the DPREQ command which sends data to FactoryLink. R00500 and
the 6 successive registers define the command block. A full description of the command block is given in the GE
Series Six Bus Controller manual (GFK-0171B). R00503 should contain the Genius address for FactoryLink as
defined in the Logical Station Control Table. R00505 represents the number of bytes that will be sent to
FactoryLink; 20 bytes would be transferred in this example.
R00510 and all the successive registers represent the data that is actually sent to FactoryLink. The format for
this data is described in the Series-6 manual referenced above. Please note that absolute addressing is used;
absolute addressing is also described in the Series-6 manual. The above example would send a message to
absolute address 576F hex or 22383 decimal. This would represent a register address of 6000 decimal (22383 -
16383 = 6000).

10/2004
If this example is followed exactly, tags tagR6000, tagR6001, tagR6005 would receive the values of 1, 2, and 5,
respectively. However, no value would be placed in tag tagR6025 since only 10 registers (20 bytes) were
transmitted.

10/2004
3.15 Appendix O: (Reserved)

10/2004
3.16 Appendix P: FactoryLink Version Upgrade Procedures
BEFORE installing the FactoryLink upgrade you MUST make a multiplatform save of your
application.
After installing the 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 and BEFORE restoring the multiplatform save file of your
application, do the following:
Where $FLINK indicates the FactoryLink directory (example: FLINK=C:\FLWIN):
1. Edit the file $FLINK\AC\TITLES and add the following line:
pcim.ac EDI Axisware GE PCIM Driver
2. Open the file $FLINK\CTGEN\CTLIST and add the following line:
3 Perform a multiplatform restore and conversion of your application.

10/2004
3.17 Appendix Q: Sample 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.

10/2004
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.
Data Region
Area of device (e.g., PLC) memory to be accessed. Also called "Data Table" or "Reference Table".
External Device Definition Table

Configuration table that tells the application what type of devices are connected to the computer's ports and
assigns 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 being
defined.
Logical Station Information Table

Table which 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.
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.
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 Logical
Station.
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.

10/2004
5 Contact information:
Axisware LLC
support@axisware.com
http://www.axisware.com
3213 Peppertree Pl.

Plano, TX 75074, USA
T: 1-(214)-764-1876
F: 1-(214)-764-1878

10/2004

Axisware PCIM Manual: FactoryLink Driver For GE Fanuc PCIM Genius Bus

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Axisware PCIM Manual: FactoryLink Driver For GE Fanuc PCIM Genius Bus

Загружено:

Авторское право:

Доступные форматы

GE Fanuc PCIM Driver

Axisware LLC support@axisware.com www.axisware.com

2.4.9 Message Tag..........................................................................................12

Axisware LLC support@axisware.com www.axisware.com

This document contains proprietary information of Axisware LLC (Axisware).

Copyright 1995-1996 NOVA Technologies

Axisware LLC support@axisware.com www.axisware.com

1.1 Software License

1.3 Historical Note

1.4 PCIM Card Installation

1.5 Software Installation

Axisware LLC support@axisware.com www.axisware.com

Axisware LLC support@axisware.com www.axisware.com

2 Factorylink Application Configuration

2.1 External Device Definition

2.1.1 Logical Port

Valid entries: 0-999 Physical Card & Physical Port

These fields are not used by this driver.

2.1.2 Device Name

Valid entry: "PCIM"

Valid entry: "SYSPRG"

Valid entries: 4-63

Axisware LLC support@axisware.com www.axisware.com

Valid entry: 14 alphabetic or numeric characters

Axisware LLC support@axisware.com www.axisware.com

2.2 Axisware GE PCIM Read/Write Control

2.2.1 Table Name

Valid entry: ASCII string incorporation up to 16 of the following character set:

2.2.2 Unsolicited Read

Valid entries: Descriptions:

Yes Normal write to the real-time database

2.2.3 Exception Write

Valid entries: Description:

Axisware LLC support@axisware.com www.axisware.com

2.2.4 Block Read Priority

Valid entries: 1 - 4 (default = 1)

2.2.5 Block Read Trigger

Valid entry: FactoryLink digital tag

2.2.6 Block Read Disable

Valid entry: FactoryLink digital tag

2.2.7 Block Read Complete

Valid entry: FactoryLink digital tag

2.2.8 Block Read State

Valid entry: FactoryLink digital tag

Axisware LLC support@axisware.com www.axisware.com

2.2.9 Block Write Priority

Valid entries: 1-4 (default = 1)

2.2.10 Block Write Trigger

Valid entry: FactoryLink digital tag

2.2.11 Block Write Disable

Valid entry: FactoryLink digital tag

2.2.12 Block Write Complete

Valid entry: FactoryLink digital tag

2.2.13 Block Write State

Valid entry: FactoryLink digital tag

Axisware LLC support@axisware.com www.axisware.com

2.3 Axisware GE PCIM Read/Write Information Table

2.3.1 Tag Name

Valid entry: FactoryLink tag

2.3.2 Logical Station

Valid entries: 0-999

2.3.3 Data Region

Valid entries: Please refer to Appendices J (Global Data) &