Axisware PCIM Manual: FactoryLink driver for GE Fanuc PCIM Genius Bus

GE Fanuc PCIM Driverfor FactoryLink

Version 7.2

Axisware GE Fanuc PCIM Driver for FactoryLink 1

Contents

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

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

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

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

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

2.3 Axisware GE PCIM Read/Write Information Table...............................................82.3.1 Tag Name................................................................................................82.3.2 Logical Station........................................................................................82.3.3 Data Region.............................................................................................82.3.4 Memory Offset (Address).......................................................................82.3.5 Bit # or Length........................................................................................92.3.6 PLC Data Type........................................................................................92.3.7 No Current Function...............................................................................92.3.8 Program Task Name................................................................................92.3.9 Program Block Name..............................................................................9

2.4 Axisware GE PCIM Logical Station Control.......................................................102.4.1 Logical Port...........................................................................................102.4.2 Timeout (Tenths)...................................................................................102.4.3 Card Memory Address (Hex)................................................................102.4.4 I/O Port Address (Hex).........................................................................102.4.5 Global Reference...................................................................................112.4.6 Global Length........................................................................................112.4.7 Configure Redundancy..........................................................................112.4.8 Redundancy Status Tag.........................................................................11

Axisware LLC [email protected] www.axisware.com10/2004


2.4.9 Message Tag..........................................................................................122.5 Axisware GE PCIM Logical Station Information.................................................13

2.5.1 Error/Status Tag Name..........................................................................132.5.2 Logical Station (Decimal).....................................................................132.5.3 Device Type..........................................................................................132.5.4 Station Address.....................................................................................142.5.5 Comment...............................................................................................14

3 Appendices................................................................................................15

3.1 Appendix A: Installation of PCIM Card..............................................................153.1.1 Original PCIM with DB-9P and 6 pin connector..................................153.1.2 Single Slot PCIM with dual 4 pin connectors.......................................17

3.2 Appendix B: Software Installation - OS/2...........................................................203.2.1 Before Starting Installation (OS/2 version)..........................................203.2.2 Driver Installation Instructions (OS/2).................................................203.2.3 Modifying the CONFIG.SYS File (OS/2)............................................22

3.3 Appendix C: (Reserved).......................................................................................233.4 Appendix D: Software Installation - Windows 95/NT........................................24

3.4.1 Before Starting Installation (Windows 95/NT version)........................243.4.2 Driver Installation Instructions (Windows 95/NT)...............................253.4.3 Modifying FLRUN.BAT File (Windows 95/NT).................................27

3.5 Appendix E: (Reserved).......................................................................................283.6 Appendix F: Driver Status Codes........................................................................29

3.6.1 Application startup errors.....................................................................293.6.2 Run-time startup errors.........................................................................313.6.3 SoftKey protection errors......................................................................333.6.4 Run-time errors.....................................................................................333.6.5 Unsolicited message processing errors.................................................35

3.7 Appendix G: (Reserved)......................................................................................373.8 Appendix H: Data Types and Conversions..........................................................383.9 Appendix I: Table Names....................................................................................413.10 Appendix J: Global Data....................................................................................423.11 Appendix K: Datagrams.....................................................................................453.12 Appendix L: (Reserved).....................................................................................483.13 Appendix M: (Reserved)....................................................................................493.14 Appendix N: Unsolicited Reads.........................................................................503.15 Appendix O: (Reserved).....................................................................................563.16 Appendix P: FactoryLink Version Upgrade Procedures...................................573.17 Appendix Q: Sample Application......................................................................58

4 Glossary.....................................................................................................59

5 Contact information:.................................................................................60



This document contains proprietary information of Axisware LLC (Axisware). This document is based on information available at the time of its publication. While efforts have been madeto be accurate, the information contained herein does not purport to cover all details or variations in hardwareor software, nor to provide for every possible contingency in connection with installation, operation, ormaintenance. Features may be described herein which are not present in all hardware and software systems.Axisware assumes no obligation of notice to holders of this document with respect to changes subsequentlymade. Axisware makes no representation or warranty, expressed, implied, or statutory with respect to, and assumesno responsibility for the accuracy, completeness, sufficiency, or usefulness of the information containedherein. No warranties of merchantability or fitness for purpose shall apply.

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

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



1 Overview

1.1 Software License

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

1.2 Introduction

This manual describes the installation and configuration of the FactoryLink GE Fanuc PCIM communicationdriver software. The driver currently supports the 90-70, Series-6, GCM+ (90-30 module for Genius network), and all thecurrently available Genius blocks. Unsolicited messages from the 90-70 and Series-6 are supported. Diagnosticinformation may be read from Genius blocks. Also, configuration data can be read from or written to Geniusblocks.

1.3 Historical Note

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

1.4 PCIM Card Installation

The installation and setup of the PCIM card is briefly described in Appendix A, but you should also refer toyour 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 FactoryLinkapplication before the install and restore the application after installation. Please refer to FactoryLinkdocumentation for details on multi-platform save and restore.



In the appendix section are appendices describing the software installation for this product on specificplatforms. Please read the appropriate appendix before installing this product.

Platform Appendix

OS/2 B

Windows NT D

When the driver software installation is completed, please refer to the SoftKey Manual for the instructions onrunning the Validate program. Failure to run Validate by the end of the 15-day grace period will result in a non-functioning driver.

After this communications driver has been installed, updating to a newer version of FactoryLink may appear tocause operational problems. Please refer to Appendix P before updating FactoryLink.



2 Factorylink Application Configuration

2.1 External Device Definition

Access this table by selecting External Device Definition from the Configuration Manager main menu. This isone of the five configuration tables that must be configured The other tables are accessed by selecting AxiswareGE 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 withFactoryLink. In this table identifiers are declared which make the external devices recognizable to FactoryLink.

This panel contains seven fields. Use the Tab key to move among the fields.

2.1.1 Logical Port

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

Valid entries: 0-999 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 thedifferent 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 informationentered by the user. This entry refers only to the memory used by the driver for data storage for therelated Logical Port.

Valid entries: 4-63



2.1.5 Comment

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

Valid entry: 14 alphabetic or numeric characters



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/WriteInformation table (the controlling tags are the Read Trigger, Read Disable, Write Trigger, Write Disable). Italso defines the tags that will report the status of reads and writes (the status tags are the Read Complete,Read State, Write Complete, Write State). Each line in this table refers to one Read/Write InformationTable.

After these fields have been configured, select "Next" or Ctrl-N to edit the Read/Write Information Tablecorresponding 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 Icontains additional information for the naming conventions that must be followed to configureFault/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 anunsolicited message received from the PLC. Standard addressing is used to correlate the message fromthe PLC with the tags configured in the table. Please refer to Appendix N for additional informationand examples.

Valid entries: Descriptions:

Yes Normal write to the real-time databaseForce Forced write to the real-time databaseNo 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 writtento the selected logical station whenever the real-time database value for that tag changes.

Valid entries: Description:

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

No No exception processing.



2.2.4 Block Read Priority

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

Valid entries: 1 - 4 (default = 1)

2.2.5 Block Read Trigger

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

Valid entry: FactoryLink digital tag

2.2.6 Block Read Disable

Digital tag used to determine whether or not a block read table will be processed. If the tag value is 0,the table is permitted to function normally; however, if the value is 1, the table will not respond to theBlock Read Trigger defined above.


2.2.7 Block Read Complete

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

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


2.2.8 Block Read State

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

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




2.2.9 Block Write Priority

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

Valid entries: 1-4 (default = 1)

2.2.10 Block Write Trigger

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


2.2.11 Block Write Disable

Dgital tag used to determine whether or not a block write table will be processed. If the tag value is 0,the table is permitted to function normally; however, if the value is 1, the table will not respond to theBlock Write Trigger defined above.


2.2.12 Block Write Complete

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

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


2.2.13 Block Write State

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

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




2.3 Axisware GE PCIM Read/Write Information Table

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

These tables are sometimes referred to as overlay panels, or ovr panels. Each table has one entry (line) for itin the Read/Write Control Table.

Note: Please verify that the table name displayed at the bottom of the panel correctly shows the table to bemodified.

After these fields have been completed, select "Next" or Ctrl-N to edit the Logical Station Control Table.

2.3.1 Tag Name

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

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

2.3.2 Logical Station

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

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 bitaddress depending on the selected device and Data Region.

Valid entries: Please refer to Appendix J (Global Data) &Appendix K (Datagrams) for further information.



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 baseand is used to specify the bit offset in the selected byte or word. If a message tag is used, the fieldspecifies 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 beleft 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 dataregions "L" and "P".

Valid entries: Alphabetic string of up to 7 characters with noembedded 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 noembedded spaces



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 Informationtable. 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 Tablecorresponding to the table selected by the cursor.

2.4.1 Logical Port

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

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


2.4.2 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 theaddress configured for the PCIM daughter board.

Valid entries: Hex memory address between A000 and F800(E000 suggested)Example: A000, A800, B000, ..., E800, F000, F800Please 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.



2.4.5 Global Reference

Global Data Reference Address used by some devices on the Genius network. Check documentation forspecific 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 globaldata and directed inputs.

Note: The number of bytes broadcast as global data can drastically affect the speed of the Geniusnetwork.

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 theGenius network. All writes directed toward device 31 willalso be sent to device 30. All reads directed toward device 31will be redirected to device 30 if 31 is no longer on thenetwork 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 followingcodes may be returned by the driver:

0 - Both devices running properly1 - Device 31 down but 30 is running properly2 - Device 30 down but 31 is running properly3 - Both devices are down

Valid entry: FactoryLink analog tag



2.4.9 Message Tag

(Optional) Message tag to which a text string will be written in the case of any error encountered in theprocessing of an EDI request.

Valid entry: FactoryLink message tag



2.5 Axisware GE PCIM Logical Station Information

This table defines the logical station(s) accessible through a specific logical port defined in the LogicalStation Control Table. Each logical station is tied to its physical station address and device type. This logicalstation information structure allows communications to multiple devices on a network using one logical port. Note: Please verify that the table name displayed at the bottom of the panel is showing the table to be

modified.

After these fields have been completed, "Exit" or F3 will allow you to return to the Configuration Managermain menu.

2.5.1 Error/Status Tag Name

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

Valid entries: FactoryLink analog tag

2.5.2 Logical Station (Decimal)

Number entered by user to represent a particular combination of a logical port (PCIM card) and physicaldevice (PLC). This number is referenced in the Read/Write Information Table to correlate specificaddresses and tags with a physical device (PLC). This number must be unique for each four-letterdevice ID (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"GDIO_16" Standard 16-circuit I/O block"GDIO_32" Standard 32-circuit I/O 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



"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



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 SlotPCIM with dual 4 pin connectors. Thedriver supports both cards. This appendix explains how to set up either ofthese 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 thecard's installation, the appropriate I/O port address, interrupt, baud rate, serial bus address, shared memorysegment address, watchdog timer setting and any application-specific settings must be properly set by jumpers orswitches. For more information on installing the GE Fanuc PCIM card then is cover in this section refer to GEFanuc 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 inaccordance 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 LevelThe interrupt level is selected by SW4 on the PCIM card. The current version of the driver does not supportinterrupts; therefore, all six switches must be open.



Baud RateThe baud rate is selected by dip switches six (6) and seven (7) on the switch assembly which resides on thePCIM daughterboard (Please refer to the PCIM manual). Both of these dip switches should remain open unlessthe network requires a lower baud rate because of noise. Please note that all nodes on one Genius network musthave the same baud rate

Serial Bus AddressThe serial bus address is selected by the first five dip switches on the switch assembly which resides on thePCIM daughterboard (Please refer to the PCIM manual). This address must be unique from all other nodes onthe Genius network. Valid addresses range from zero (0) to thirty-one (31); however, care should be taken toavoid conflicts with the hand held monitor and bus controllers which generally reside at address zero (0) andthirty-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 = ClosedO = OpenX = 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 oneach 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) isrecommended; the following chart illustrates the proper switch settings for this address.

SHARED MEMORY SEGMENT ADDRESS E0000



SW2

1 2 3 4 5 6 | | | | | | C C C O O O

SW31 2 3 4 5 6 | | | | | | O X X X X X

where,C = ClosedO = OpenX = Not used

Watchdog TimerThe watchdog timer MUST be disabled by placing jumper JP2 in the 1-2 position (Please refer to the PCIMmanual). If JP2 is left in the 2-3 position, the driver will not complete any requests.

Application-Specific SettingsTwo (2) selections on the board remain which should be configured in accordance with the needs defined by thespecific application. JP1 is used to connect or disconnect the terminating resistor; please see discussion in thePCIM manual. Dip switch number eight (8) on the PCIM daughterboard is used to enable or disable outputsfrom the PCIM card. If outputs are enabled, all devices capable of receiving directed global data will receivetheir outputs from the PCIM card. If outputs are disabled, only those devices to which writes have beenconfigured in FactoryLink will receive their outputs from the PCIM card. Both of these settings can be selectedto 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 forother Genius network devices should be used with the PCIM card. The six (6) pin connectors on the back of thePCIM 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 ShieldOut. 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, beforeinstalling the card the appropriate I/O port address for configuring the board must be set in the DIP switch on the



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 GEFanuc 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 inWindows and also in a DOS window in OS/2 but it will not correctly run in a DOS window underWindows 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 onthe 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 addressconflicts 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 hexdigit.

Switch Positions for 222hex (default):

Switch: 1 2 3 4 5 6 7 8 | | | | | | | | U D D D U D D D

where,U = UpD = 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 inHEX.

Note: This I/O Port to be entered in the “Axisware GE PCIM Logical Station Control” I/O Port Address fieldNOT the I/O Port set with dip switches on the card..

Interrupt LevelUse the up and down arrow keys to move to the field labeled Interrupt. The current version of the driver does notsupport interrupts; therefore, the Interrupt field must read “Disabled”. Use the left and right arrow keys to togglethe field to disabled.



Baud RateUse the arrow keys to move to the field labeled Baud. Use the left and right arrow keys to select the desirednetwork Baud Rate. The baud rate should remain “153.6K Std” unless the network requires a lower baud ratebecause of noise. Please note that all nodes on one Genius network must have the same baud rate.

Serial Bus AddressUse 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) tothirty-one (31); however, care should be taken to avoid conflicts with the hand held monitor and bus controllerswhich generally reside at address zero (0) and thirty-one (31), respectively.

Shared Memory Segment AddressUse the up and down arrow keys to move to the field labeled Memory base and enter the desired SharedMemory Address.

Watchdog TimerThe watchdog timer MUST be disabled. Use the up and down arrow keys to move to the field labeledWatchdog 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 forother Genius network devices should be used with the PCIM card. The four pin connectors on the back of thePCIM 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 ShieldOut.



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 followedfor the software to be properly installed. First, the operator must exit from both the Run Manager and theConfiguration Manager. Second, a multiplatform save file should be created. Third, the driver should beinstalled as described below. Fourth, restore the multiplatform save file created in step 2. Fifth, update theConfiguration 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 filescopied 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 valueto $FLINK , and then restart the install program.$FLINK can be assigned a value by using theSETcommand (example: set flink=d:\flos2).

During the installation, two ASCII text files will be modified by the installation program. The originalcopies of both files will be copied to a file with the same filename but a.NVAextension. The first file to bemodified is$FLINK \AC\TITLESThis file is used by the Configuration Manager to determine which tasks tolist and also the order in which they are to be listed. The following line willbe added to theTITLESfile.(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), theprogram will warn you during the install that it is about to be overwritten and will ask you if you want to exit,and manually save the .NVA file.

The second file to be modified is$FLINK \CTGEN\CTLIST. This file is used by the CTGEN utility in thecreation of the binary files used by the Run-time FactoryLink. The following line will be added to theCTLIST 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), theprogram will ask you during the install if you wish to exit, and manually savea copy of this .NVA file beforeit is overwritten.

3.2.2 Driver Installation Instructions (OS/2)

It is important that you have followed the hardware installation procedures described in Appendix Abefore proceeding with the driver installation instructions.



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 anetwork. If a message is displayed stating that the INSTALL program is having difficulty finding the directorycontaining the FactoryLink program files, press a key to exit and use theset command to reset the FLINKenvironment variable. The problem may be resolved by clearly stating the drive letter. At the OS/2 commandprompt type set FLINK= followed by the drive letter (a-z), a colon (:), a backslash (\) and the directory name(s) giving the path to the FactoryLink program files. Examples: set FLINK=d:\work1\flos2 or set FLINK=t:\sect2\factory. Make sure that the onlyspace in this commandis between “set” and “FLINK”. After the “NOVA Technologies” screen appears the FactoryLink Path and FactoryLink Release Version aredisplayed. Press y and then the Enter (Return) key if the information is correct. The driver Serial Number and Release Type are then displayed. Pressy and then theEnter (Return) key tocontinue. The following message will appear

Copying configuration files to hard disk . . . followed by a message relevant to obtaining authorization for the product, if required.

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

This install program will update your file named$FLINK\AC\TITLES

$FLINK\AC\TITLES.NVA (a backup file) already exists.To overwrite it, press y followed by Enter (Return). By pressing n, you may Exit, manually saveyour .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 messageappears:



This install program will update your file named $FLINK\CTGEN\CTLIST

$FLINK\CTGEN\CTLIST.NVA (a backup file) already exists.To overwrite it, press y followed by Enter (Return). By pressing n, you may Exit, manually save your.NVA backup file, and restart this program. Enter either y or n followed by the Enter (Return) key ==>

The messages

Updating listing of driver names. . . and

Updating CTLIST . . . are briefly displayed while the backup (.NVA) versions are being created and the$FLINK\AC\TITLESand$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 sectionBefore 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 thenecessary files have beencopied 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 theFactoryLink PCIM driver to function properly. After the INSTALL program is run, the CONFIG.SYS file mustbe 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 forthe 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.SYSdriver.



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



3.3 Appendix C: (Reserved)

This appendix is reserved for future use.



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 filescopied 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 aparameter to$FLINK , and then restart the install program.$FLINK can be assigned a value by using theSET 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 originalcopies of both files will be copied to a file with the same filename but a.NVAextension. The first file to bemodified is$FLINK \AC\TITLES. This file is used by the Configuration Manager to determine which tasks tolist 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), theprogram will warn you during the install that it is about to be overwritten and will ask you if you want to exit,and manually save the .NVA file. The second file to be modified is$FLINK \CTGEN\CTLIST. This file is used by the CTGEN utility in thecreation of the binary files used by the Run-time FactoryLink. The following line will be added to theCTLIST 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), theprogram will ask you during the install if you wish to exit, and manually savea copy of this .NVA file beforeit is overwritten. It is important that you have followed the hardware installation procedures described in Appendix Abefore proceeding with the driver installation instructions.



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 drivecontaining the diskette the current working drive, typeINSTALL at a DOS prompt and press Enter. Theinstallation may also be started by using File…Run…from Windows NT’s Program Manager or FileManager, 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 anetwork.

If a message is displayed stating that the INSTALL program is having difficulty finding the directorycontaining the FactoryLink program files, press a key to exit and use theset command to reset the FLINKenvironment variable. The problem may be resolved by clearly stating the drive letter. At the DOS commandprompt type set FLINK= followed by the drive letter (a-z), a colon (:), a backslash (\) and the directory name(s) giving the path to the FactoryLink program files. Examples:

set FLINK=d:\work1\flnt or set FLINK=t:\sect2\factory. Make sure that the onlyspace in this commandis between “set” and “FLINK”.

After the “NOVA Technologies” screen appears the FactoryLink Path and FactoryLink Release Version aredisplayed. 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 tocontinue.

The following message will appear

Copying configuration files to hard disk . . .

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

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

This install program will update your file named%FLINK%\AC\TITLES

%FLINK%\AC\TITLES.NVA (a backup file) already exists.To overwrite it, press y followed by Enter (Return). By pressing n, you may Exit, manually saveyour .NVA backup file, and restart this program.. Enter either y or n followed by the Enter (Return) key ==>

The install program will then go through the same procedure before updating the file$FLINK\CTGEN\CTLIST. The install program checks for a backup file named$FLINK\CTGEN\CTLIST.NVA. If found, this message appears:

This install program will update your file named %FLINK%\CTGEN\CTLIST



%FLINK%\CTGEN\CTLIST.NVA (a backup file) already exists.To overwrite it, press y followed by Enter (Return). By pressing n, you may Exit, manually save your.NVA backup file, and restart this program. Enter either y or n followed by the Enter (Return) key ==>

The messages

Updating listing of driver names. . . and

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

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

!!!! Unable to update %FLINK%\CTGEN\CTLIST file the lines to be added to these files can be typed in manually using a text editor.Refer to the section BeforeStarting Installation (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.



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 systemregistry. 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 beaccomplished 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 startthe Devices program using the icon located in that folder. Scroll down the list of services until NOVAMEM islocated, then change its startup type to SYSTEM.



3.5 Appendix E: (Reserved)




3.6 Appendix F: Driver Status Codes

3.6.1 Application startup errors

The following error codes (alphabetized) may be reported to FactoryLink while the GE PCIM Driver tables arebeing processed at startup.

Bitwise data anomalyDuplicate binary address encountered.

Configuration/Fault information may not be accessed for bus controllers / GCM / PCIMThe selected device does not support datagrams that read or write configuration/ faultinformation. If this information is needed for a bus controller, it may be read from the buscontroller by the host PLC and then read into FactoryLink from the PLC.

Configuration/Fault information may only be returned with types DGBIT, DGBYT, and DGWRDIf configuration data is to be read from or written to a Genius block, one of these Data Regionsmust be used. All other data regions are considered invalid.

Data anomalyIndicates that addresses and data types specify overlapping elements.

Datagram write not valid for selected Genius blockWrite operations via datagrams are not valid to the selected Genius block; however, someblocks permit global data writes.

Data offset invalid for PCIM card memoryWhen memory accesses are defined in the Read/Write Information Tables, the maximum byteoffset is 128.

Data offset must be non-zero for selected data tableOnly 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 blockDGBIT, 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 namesThe specified data table (region) is not valid unless the program task name and program blockname 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 typesDIGITAL tags may only be used to read or write discretes.



Digital write not allowed for word addressThe 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 datagramDatagrams to Genius blocks do not support digital writes.

Invalid bit number specifiedA bit number greater than 15 may not be specified. Specifying the proper byte or word willallow access to all bits without exceeding this limit.

Invalid data offset specified for High Speed CounterThe addressing for the High Speed Counter is different than any other device. Please refer toAppendix K for the details concerning addresses for this device.

Invalid data table specified for XPlease refer to Appendix J (Global Data)& Appendix K (Datagrams) for a list and discussionof valid addresses for each device. X represents the specific device selected.

Invalid data type encounteredPlease refer to Appendix H for list of valid data types.

Invalid data type selected for deviceThe number of bytes required for the data type specified is greater than the maximum numberof bytes returned by the selected device.

Invalid data type selected for High Speed CounterOnly four bytes of data may be requested from a High Speed Counter. Any data type requiringmore than four bytes is invalid.

Invalid device type specifiedThe data file is corrupted and contains a device not recognized by the driver. Delete theindicated record and type in the record again, selecting a valid device type.

Logical station X not foundThe logical station X was specified in the current Read/Write Information Table, but thislogical station number was never defined in the Logical Station Information Table.

MESSAGE tags may not be used with numerical typesOnly the ASC data type may be used with MESSAGE tags.

Negative data offset not permittedNo data region supports a data offset of less than zero. Enter a valid positive address for theoffset.

No tag givenThe indicated line of the Read/Write Information Table currently being processed does notcontain a valid FactoryLink tag name.

No tags, read/write packet not made



The current Read/Write Information Table contained entries that caused a portion of the tableto generate an error and consequently no DCT information was output.

Only DIGITAL tags may be used with BINBinary data may only be accessed with DIGITAL tags.

Only GIXXX and GOXXX used with digital blocks, GCM, or PCIM cardPlease refer to Appendix J (Global Data) & Appendix K (Datagrams) for the details ofaddressing each device.

Only MESSAGE tags may be used with ASCASCII strings may only be read into MESSAGE tags.

Ordering anomalyIndicates that the Read/Write Information Table currently being processed contains addressessuch that the driver is unable to properly arrange all the entries.

Out of MemoryThe driver was unable to internally allocate all the necessary memory. Allocate more memoryin the External Device Definition Table.

Positive string length for MESSAGE tags requiredIf a message tag is used, the Bit # or Length field in the Read/Write Information Tablerepresents the length (in bytes) of the message used in the transaction. This number must bebetween 1 and 128.

Specified configuration/fault offset or data length is too largeThere 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 datathat can possibly be returned.

Unsolicited not permitted for configuration/fault tablesConfiguration tables and fault tables may not be processed as unsolicited messages. Onlystandard tables for 90-70 and Series-6 PLCs will be processed and evaluated to resolveincoming unsolicited messages.

Writes are not permitted for fault tableThe operator has configured writes in a fault table. Diagnostic information may not be writtento a Genius device.

Write not allowed to specified data tableStatus tables in the 90-70 are configured to be read only. Any writes defined to these regionsare 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 beenprocessed. All the following errors are immediately fatal.



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 inthe 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 lengthThe global length entered on the Logical Station Control Table must be between 0 and 128. Ifthis error occurs, the driver corrects the value to 128 and continues.

Invalid redundancy status tagThe 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 completeCheck the PCIM card jumpers, dip switches, and that it is properly inserted. Verify that thewatchdog timer has not been enabled. Ensure that no shared memory conflicts (including ROMshadowing) exist.

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

PCIM communications errorCheck the PCIM card jumpers, dip switches, and that it is properly inserted. Verify that thewatchdog timer has not been enabled. Ensure that no shared memory conflicts (including ROMshadowing) exist.

PCIM configuration error returnedCheck the PCIM card jumpers, dip switches, and that it is properly inserted. Verify that thewatchdog timer has not been enabled. Ensure that no shared memory conflicts (including ROMshadowing) exist.

PCIM configuration never acceptedCheck the PCIM card jumpers, dip switches, and that it is properly inserted. Verify that thewatchdog timer has not been enabled. Ensure that no shared memory conflicts (including ROMshadowing) exist.

PCIM OK signal never received from card

Check the PCIM card jumpers, dip switches, and that it is properly inserted. Verify that thewatchdog timer has not been enabled. Ensure that no shared memory conflicts (including ROMshadowing) exist.

Specified I/O port address X is invalidThe I/O port address must be on a four byte boundary. The address must fall between 200 hexand 6FF hex.

Timeout waiting for card reset



The PCIM card did not respond as expected. Check all card jumpers, dip switches, and verifythat 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 memoryIncrease 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 followingmessage will be displayed.

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

3.6.4 Run-time errors

The following errors may be reported while the driver is processing the EDI requests. The text represents theerror message returned to the message tag defined in the Logical Station Control Table. The number inparentheses is returned to the analog tag defined in the Logical Station Information Table. While the followingerrors are not immediately fatal, recurring errors should be evaluated and eradicated to maintain the integrity ofthe network.

(10) Device X failed to respondThe indicated Genius device did not respond to a datagram. Check cabling and the deviceaddress. Also check that no restrictions concerning global data are being violated.

(11) Buffer manipulation errorInternal communication error between DSF and CPT module. Please contact Axisware if theerror persists.

(12) Datagram may not be sent to host PCIMThe 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 todetermine the exact status of redundancy.

(14) Device X not found on networkThe indicated Genius device was not found on the network. Check cabling and the deviceaddress. Also check that no restrictions concerning global data are being violated. Error mayalso be seen on the Windows platform if memory is not properly excluded in SYSTEM.INI orCONFIG.SYS.



(15) Syntax error occurred on read from/write to device XThe transaction defined to the specified device could not be completed because of a syntaxerror. If the error persists, contact Axisware.

(16) Process error occurred on read from/write to device XThe transaction defined to the specified device could not be completed because of a processerror. Verify that the transaction is valid. This error occurs if an invalid area of memory isbeing accessed or a device does not accept a datagram.

(17) Unknown error Y occurred on read from/write to device XThe transaction defined generated an unknown error. Verify that the transaction is valid.Contact Axiswares if the error persists.

(18) Lockout table malfunctionThe PCIM card is not responding as expected. Check that card is configured properly. If errorpersists, contact Axisware

(19) Zero length buffer errorA request has been made to the CPT module with a zero byte transaction length. This errorshould not occur, please contact Axisware.

(20) Timeout waiting for clear to transferTransmit 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 timeoutvalue specified in the Logical Station Control Table is greater than the total driver cycle time.

(21) Timeout initializing PowerTRAC dataPowerTRAC failed to give data ready signal within allowed time. Check block configurationand timeout values.

(22) Overcurrent data not available for device XOvercurrent data can only be read from a PowerTRAC block when an overcurrent error hasoccurred. 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 rangeThe maximum memory offset for global data must be less than the Global Length configured inthe Logical Station Control Table.

(42) Bytes requested less than oneInternal processing error. Contact Axisware if the error persists.

(43) Module communication timeoutCommunication failure between modules. Increase the timeout specified in the Logical StationControl Table. If the error persists, contact Axisware.

(44) Datagram write to block not supported



The operator attempted to write data to a Genius block. This operation is not supported by theGenius protocol.

(45) DSF attempt to write fault informationDiagnostic or fault information may only be read. Any attempt to write such information willgenerate 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 tomaintain the integrity of the network.

Unsolicited queue full; messages may have been lostOnly 16 unsolicited messages may be queued to the PCIM card at one time. This errorindicates that the driver cannot process the messages as quickly as they are received.

No unsolicited reads have been definedAn unsolicited message has been received over the Genius network; however, no unsolicitedmessages 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 indexInternal software error, contact Axisware.

Unable to evaluate unsolicited messageAn 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 - YAn unsolicited message directed toward device X, address Y was received. This address hasnot been configured as an unsolicited message in the Configuration Manager.

EDI DSF pointer errorSoftware error; contact Axisware.

Linked list errorSoftware error; contact Axisware.

Unable to allocate memory for all unsolicited messagesAllocate more memory to EDI task. Please note that the current driver limits the number ofunsolicited messages configured to about 6500 due to the segment size. If this limit is reached,please contact Axisware.

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



Unsolicited message received, but length invalidThe length specified in the unsolicited message is greater than 136. Check that the messagefrom the 90-70 or Series-6 is valid. Please refer to Appendix N for more information.

Partial byte detected within returned dataDue to the 90-70 binary addressing used in the returned message, a configured tag receivedonly a portion of the necessary data required from the PLC.

Invalid tag type for unsolicited messageInternal software error. Contact Axisware.



3.7 Appendix G: (Reserved)




3.8 Appendix H: Data Types and Conversions

The driver supports the following FactoryLink tag types:

DIGITALANALOGLONG ANALOGFLOATING POINTMESSAGE

The driver also supports the following PLC data types:

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 MESSAGEBIN BYTE BYTE BYTE ASC

INT2 INT2 INT2INT4 INT4 INT4BCD4 BCD4 BCD4BCD8 BCD8 BCD8FLT4 FLT4 FLT4FLT8 FLT8 FLT8

The following descriptions are from the viewpoint of “read”. A similar transfer occurs on writes.

DIGITAL

BINDIGITAL tags may only be converted to and from the BIN data type. If the requested binary PLC datatype is on, the DIGITAL tag will be set to one. If the binary element is off, the DIGITAL tag will be setto zero.

ANALOG

BYTEThe 8 bits of this data type are transferred to the lowest 8 bits of the ANALOG tag.



INT2The ANALOG tag is a 16 bit signed integer; therefore, no conversion is needed.

INT4The lowest 16 bits of the INT4 data type correspond directly with the 16 bits comprising the ANALOGtag.

BCD4After being read from the PLC, the BCD4 value is converted to a 16 bit integer. The value is thendirectly transferred without conversion into the ANALOG tag.

BCD8After being read from the PLC, the BCD8 value is converted to a 32 bit integer. The value is thenhandled as the INT4 data type above.

FLT4The whole number portion of the floating point number is transferred to the ANALOG tag. Thisconversion is accurate only if the whole number value is between -32768 and +32767. When convertingback to a FLT4, a fractional portion of zero is assumed.

FLT8The whole number portion of the floating point number is transferred to the ANALOG tag. Thisconversion is accurate only if the whole number value is between -32768 and +32767. When convertingback to a FLT8, a fractional portion of zero is assumed.

LONG ANALOG

BYTEThe 8 bits of this data type are transferred to the lowest 8 bits of the LONG ANALOG tag.

INT2The LONG ANALOG is a 32 bit signed integer; therefore, the 16 bits of the INT2 data type correspondto the lowest 16 bits of the LONG ANALOG tag.

INT4No conversion necessary; all 32 bits transfer directly.



FLT4The whole number portion of the floating point number is transferred to the LONG ANALOG tag. Thisconversion 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.



FLT8The whole number portion of the floating point number is transferred to the LONG ANALOG tag. Thisconversion 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

BYTEThe BYTE value is converted into a standard IEEE 64 bit floating point value and then transferreddirectly to the FLOATING POINT tag. The fractional portion of the number is assumed to be zero.

INT2The INT2 value is converted into a standard IEEE 64 bit floating point value and then transferreddirectly to the FLOATING POINT tag. The fractional portion of the number is assumed to be zero.

INT4The INT4 value is converted into a standard IEEE 64 bit floating point value and then transferreddirectly to the FLOATING POINT tag. The fractional portion of the number is assumed to be zero.



FLT4The FLT4 value is converted from a standard IEEE 32 floating point number into a standard IEEE 64 bitfloating point number. This value is then transferred directly to the FLOATING POINT tag.

FLT8The data is transferred directly; no conversion is necessary.

MESSAGE

ASCAll data is read directly into the message tag from the specified device address. No conversion of anykind is employed.



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 usedfor additional functionality or completely abandoned for a standard configuration. The only data regionmnemonics 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 thetable name define the intended purpose of the table. If neither of these table name prefixes are used, the table isassumed 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 driverto define a fault or diagnostic table. The letters used must be all uppercase and preceded by anunderscore. 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 specificfault information that can be accessed by a fault table is described in the manuals for eachGenius 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 driverto define a configuration table. The letters used must be all uppercase and preceded by anunderscore. Configuration tables are only valid when configured for any type of writes to orblock reads from Genius blocks. All other attempted operations for configuration tables willgenerate errors from the driver. The specific configuration information that can be accessed bya configuration table is described in the manuals for each Genius device. The GE manualGenius I/O System and Communications I (GEK 90486D-1) contains the most complete listingof this information for all Genius devices in chapter 4.



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 andDatagrams. It is the responsibility of the operator to intelligently select between these two methods. Bothmethods have positive and negative features; however, the specific application and function will dictate the wisechoice. 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, ifadditional information is desired, please consult the appropriate GE technical manual. A brief description ofGlobal 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 buscontrollers on the same bus are capable of receiving the data, although some bus controllers can choosenot to. The ability to send Global Data is set up when each bus controller is configured. Once thesystem is in operation, the only further action required of an application program is to place new data tobe sent into the selected memory area as often as needed, and to read incoming Global Data which hasbeen 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 bethe discussion on pages 7-12 and 7-13.

The standard FactoryLink configuration tables previously discussed are used to control and access Global Datafor the PCIM card. This method of data transfer can be very fast; however, if excessive amounts of Global Dataare 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, andGOWRD. The second character used in the mnemonic indicates whether the transaction is to be directed towardthe Input or Output tables on the PCIM card. The last three characters of the mnemonic indicate the method inwhich 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 forthis selection so that the numeric portion of the address would exactly correspond to the memory mapsgiven in the GE reference manuals.WRD indicates that one-based word addressing is to be used.



Please note that the data type determines how the data at a given address will be interpreted; therefore, anyaddressing scheme may be used with any valid combination of tag types and data types.

Examples:GIBIT 10 Bit 10 of the Global Data input tableGOBIT 10 Bit 10 of the Global Data output tableGIBIT 33 Bit 33 (bit 1 of word 3) of input tableGIBYT 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 thefollowing 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 outputtable. Care must be taken that more than one device is not attempting to control the outputs for one block. Ifcircuit 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 analoginput 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. Ifanalog output 1 is to be written, the following addresses could be used:

GOBIT 1,GOBYT 0,GOWRD 1.



Specialty Blocks (GHSCNT, GPWRTRAC)

A wide range of parameters are sent from these devices each bus scan. The inputs, both discrete and analog, areaccessed from the input table as the other devices described above. The outputs are written to the output table asdescribed above. The specific values and parameters that may be accessed are described in the manuals for eachdevice. Great care should be taken in writing to PowerTRAC outputs, because they may actually interfere withthe 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 ratherthan 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 examplesassume 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 bebroadcast from the PCIM card rather than being written directly to the Genius device. Data is broadcast from thePCIM card by selecting a logical station defined as a device type "PCIM" and a station address corresponding tothat of the card as selected by the dip switches on the PCIM daughterboard. This data will be broadcast to alldevices on the network capable of receiving such data and will be placed in PLC memory as configured. All datato be broadcast should be written to the output table for the PCIM card.



3.11 Appendix K: Datagrams

INTRODUCTION

Two types of data transfers are available to the GE PCIM driver. These two methods are Global Data andDatagrams. It is the responsibility of the operator to intelligently select between these two methods. Bothmethods have positive and negative features; however, the specific application and function will dictate the wisechoice. 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, ifadditional information is desired, please consult the appropriate GE technical manual. A brief description ofDatagrams 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 todirectly access all data types in the 90-70 or Series-6, obtain fault information, directly access configurationinformation, 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 untilit is solicited. However, the speed of the network overall is not affected significantly because messages are notsent 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 forconfiguration 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 andconfiguration information. The following entry, assuming the table name was prefixed with "_CFG", would reador write configuration information for circuit five (5):

DGBIT 57DGBYT 8DGWRD 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 informationmay also be returned. The same three data region mnemonics are used. The GE documentation for each devicecontains 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 inaddition to that which is returned via global data may be obtained through datagrams. A complete listing may be



obtained from GE documentation; however, examples of such data would be fundamental VARs, harmonicVARs, fundamental power factor or line frequency.

In addition to these standard datagram features, waveform data and overcurrent data may be returned from theblock. In general, this information should only be read with a dedicated FactoryLink read table. Waveform datashould not be read more frequently than once every 0.5 seconds. Overcurrent data can only be read after anovercurrent condition, and not more frequently than once every 0.5 seconds. Waveform data is accessed usingthe following data region mnemonics: WDBIT, WDBYT, or WDWRD. Beyond these additional mnemonics, allprevious guidelines apply to accessing this data.

Example:WDBYT 1024 first byte of channel C currentWDBYT 514 third byte of channel C voltageWDWRD 129 first word of channel B voltageWDWRD 896 last word of table

Overcurrent data is accessed using the following data region mnemonics: OCBIT, OCBYT, or OCWRD. Thesevalues 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 areaccessed. 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 allthree valid mnemonics are treated identically when the tables are processed. The protocol requires the operatorto specify a timer number and a data type code. The valid type codes are listed in the manual for the High SpeedCounter. Since this addressing is not easily implemented with the current addressing schemes, the followingrules 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 1DGBYT 4006 Read counter timer base (code 6) for timer 4DGBYT 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-70No 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 bitaddresses. Digital writes may not be directed to word addresses, but digital reads may be used. All addresses areentered exactly as they are used in the PLC. The following examples list possible FactoryLink addresses.

Examples:AQ 16 %AQ0016,



G 1 %G0001,M 256 %M0256.T 15 %T0015,

Series-6No 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:

OIRAUXOAUXIO1+ 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 dataregions and channelized I/O are accessed as they are mapped to the registers by the Series-6. The followingexamples list possible FactoryLink addresses. Please note that a WINDOW command in the PLC is necessaryfor 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.



3.12 Appendix L: (Reserved)




3.13 Appendix M: (Reserved)




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 isnot 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 ControlTable to either "Forced" or "Yes". This will allow that specific table to be included in the driver's search for tagswith which to associate the incoming data. The table for which unsolicited reads have been enabled may now beedited to associate FactoryLink real-time database elements to addresses in the PLC. The same addressing rulesshould be followed for unsolicited read tables as for the standard read or write tables. Note: The number of tagsthat 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 unsolicitedmessages.

TAG LOGICAL DATA DATANAME STATION TABLE OFFSETtagR1000 10 R 1000tagR1001 10 R 1001tagR1019 10 R 1019tagR1025 10 R 1025

The second step is to configure the PLC to send the messages to the FactoryLink PCIM card. This isaccomplished via the 90-70 COMREQ command. The following rung of logic is an example to illustrate thisprocedure:



| << 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 datatransmission. If it is left energized for multiple, successive PLC scans, the Genius LAN will not be able totransmit the communication commands as quickly as they are being generated. After the message has beenreceived 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 thePLC 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 commandblock information defines the communication request and supplies all necessary addresses and parameters. ACOMREQ #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 (Rung1...%R0001) to transmit 20 registers starting at location %R1000 to a PCIM card at a Genius node address of 31:



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



SERIES-6 PLC

If Logical Station 11 is a Series-6 bus controller, the following would be an example to receive unsolicitedmessages.

TAG LOGICAL DATA DATANAME STATION TABLE OFFSETtagR6000 11 R 6000tagR6001 11 R 6001tagR6005 11 R 6005tagR6025 11 R 6025

The second step is to configure the PLC to send the messages to the FactoryLink PCIM card. This isaccomplished via the Series-6 DPREQ command. The rungs of logic on the following page represent anexample to illustrate this procedure:



|| << 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 accessSeries-6 memory. The remaining rungs control and execute the DPREQ command which sends data to FactoryLink. R00500 andthe 6 successive registers define the command block. A full description of the command block is given in the GESeries Six Bus Controller manual (GFK-0171B). R00503 should contain the Genius address for FactoryLink asdefined in the Logical Station Control Table. R00505 represents the number of bytes that will be sent toFactoryLink; 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 forthis 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 toabsolute address 576F hex or 22383 decimal. This would represent a register address of 6000 decimal (22383 -16383 = 6000).



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



3.15 Appendix O: (Reserved)




3.16 Appendix P: FactoryLink Version Upgrade Procedures

BEFORE installing the FactoryLink upgrade you MUST make a multiplatform save of yourapplication.

After installing the driver, upgrading to a newer version of FactoryLink may appear to cause operationalproblems. This is due to the modifications to certain text files made by installing this product beingoverwritten during the install of the new FactoryLink version. However, these files can be reconfiguredusing a text editor

AFTER installing the FactoryLink upgrade and BEFORE restoring the multiplatform save file of yourapplication, 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:

pcim: pcimshdr pcimsovr pcim_hdr pcim_ovr

3 Perform a multiplatform restore and conversion of your application.



3.17 Appendix Q: Sample Application

The SAMPLE directory of the nstall cd-rom includes compressed multiplatform save files of a sampleapplication for this driver. The sample application can be used to test communications, as well as serve as anexample of how to prepare a FactoryLink application to use the driver. The sample application has examples ofblock reads, block writes, exception writes and unsolicited reads from a single PLC. Please refer to the"README.TXT" file in the SAMPLE directory for instructions on how to use this application.



4 Glossary

Configuration TablesWhere you establish the communication path and specify elements in the database. These tables worktogether to allow FactoryLink to exchange information from the tag database with the device.

Data RegionArea of device (e.g., PLC) memory to be accessed. Also called "Data Table" or "Reference Table".

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

Logical PortNumber specified in the External Device Definition table which represents a particular communication path.

Logical StationNumber 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 TableTable used to configure each logical port and its associated stations in the Logical Station Information table.The Logical Station Control table specifies which specific port is connected to the external device beingdefined.

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

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

Read/Write Control TableTable 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 TableConfiguration table that links FactoryLink tags to specific addresses in the PLC represented by the LogicalStation.

SoftKeyAxisware software protection system where no hardware key (dongle) is required.

ValidateThe program run after the software is installed that checks for improper use of the product and enables thesoftware to function past the grace period.



5 Contact information:

Axisware LLC

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

3213 Peppertree Pl.Plano, TX 75074, USA

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


http://www.axisware.com/

Axisware PCIM Manual: FactoryLink driver for GE Fanuc PCIM Genius Bus

Documents

Transcript of Axisware PCIM Manual: FactoryLink driver for GE Fanuc PCIM Genius Bus