Axisware Sdkt Manual: Factorylink Driver For Allen-bradley Dh/dh+ Via Sst 5136-sd

S-S Technologies 5136-SD A-B DH/DH+ Driver for FactoryLink

Version 7.2

February 2004

Axisware SDKT Driver for FactoryLink

1

Contents 1 Overview......................................................................................................1 1.1 Software License.....................................................................................................1 1.2 Introduction.............................................................................................................1 1.3 Historical Note........................................................................................................1 1.4 Card Installation......................................................................................................1 1.5 Software Installation...............................................................................................1

2 Factorylink Application Configuration......................................................3 2.1 External Device Definition.....................................................................................3 2.1.1 Logical Port.............................................................................................3 2.1.2 Physical Card & Physical Port................................................................3 2.1.3 Device Name...........................................................................................3 2.1.4 Function...................................................................................................3 2.1.5 Memory...................................................................................................4 2.1.6 Comment.................................................................................................4 2.2 Axisware SDKT Read/Write Control.....................................................................5 2.2.1 Table Name.............................................................................................5 2.2.2 Unsolicited Read.....................................................................................5 2.2.3 Exception Write......................................................................................5 2.2.4 Block Read Priority.................................................................................6 2.2.5 Block Read Trigger.................................................................................6 2.2.6 Block Read Disable.................................................................................6 2.2.7 Block Read Complete.............................................................................6 2.2.8 Block Read State.....................................................................................6 2.2.9 Block Write Priority................................................................................7 2.2.10 Block Write Trigger..............................................................................7 2.2.11 Block Write Disable..............................................................................7 2.2.12 Block Write Complete..........................................................................7 2.2.13 Block Write State..................................................................................7 2.3 Axisware SDKT Read/Write Information Table....................................................8 2.3.1 Tag Name................................................................................................8 2.3.2 Logical Station........................................................................................8 2.3.3 PLC Address...........................................................................................8 2.3.4 Data Type................................................................................................9 2.4 Axisware SDKT Logical Station Control.............................................................10 2.4.1 Logical Port...........................................................................................10 2.4.2 Timeout (Tenths)...................................................................................10 2.4.3 Card Memory Address (Hex)................................................................10 2.4.4 Data Highway Address (Octal).............................................................10 2.4.5 Max Concurrent Packets.......................................................................11 2.4.6 Message Tag..........................................................................................11 2.5 Axisware SDKT Logical Station Information......................................................12 2.5.1 Error/Status Tag Name..........................................................................12 2.5.2 Logical Station (Decimal).....................................................................12 2.5.3 Device Type..........................................................................................12 2.5.4 Local Station Address (Octal)...............................................................12 2.5.5 Local/Remote........................................................................................13 2.5.6 Remote Physical Station (Octal)...........................................................13 Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

2

2.5.7 Link ID Number....................................................................................13 2.5.8 Link Type..............................................................................................13 2.5.9 Comment...............................................................................................14

3 Appendices................................................................................................15 3.1 Appendix A: Installation of Card.........................................................................15 3.1.1 Installation for 5136-SD........................................................................15 3.1.2 I/O Port Addresses................................................................................16 3.1.3 Installation for 5136-SD-MCA.............................................................18 3.1.4 Cable Connections................................................................................18 3.2 Appendix B: Software Installation - OS/2...........................................................19 3.2.1 Before Starting Installation - (OS/2 version)........................................19 3.2.2 Driver Installation Instructions (OS/2).................................................20 3.2.3 Modifying CONFIG.SYS File (OS/2)..................................................21 3.2.4 Modifying FLRUN.CMD File (OS/2)..................................................22 3.2.5 Softkey Protection Validation...............................................................23 3.3 Appendix C: (Reserved).......................................................................................24 3.4 Appendix D: Software Installation - Windows 95/NT........................................25 3.4.1 Before Starting Installation (Windows 95/NT version)........................25 3.4.2 Driver Installation Instructions (Windows 95/NT)...............................25 3.4.3 Modifying FLRUN.BAT File (Windows 95/NT).................................27 3.4.4 Softkey Protection Validation...............................................................28 3.5 Appendix E: (Reserved).......................................................................................29 3.6 Appendix F: Driver Status Codes........................................................................30 3.6.1 Application startup errors.....................................................................30 3.6.2 Run-time startup errors.........................................................................33 3.6.3 SoftKey protection errors......................................................................34 3.6.4 Run-time errors.....................................................................................34 3.6.5 Unsolicited message processing errors.................................................35 3.7 Appendix G: PLC Status Codes...........................................................................37 3.8 Appendix H: Data Types and Conversions..........................................................39 3.9 Appendix I: PLC-2 Addressing............................................................................42 3.10 Appendix J: PLC-3 Logical Addressing............................................................43 3.10.1 I/O Data Tables (PLC-3).....................................................................43 3.10.2 All Other Data Tables (PLC-3)...........................................................44 3.11 Appendix K: PLC-5 Logical Addressing...........................................................48 3.11.1 I/O Data Tables (PLC-5).....................................................................48 3.11.2 All Other Data Tables (PLC-5)...........................................................49 3.12 Appendix L: PLC-5/250 Logical Addressing....................................................56 3.12.1 I/O Data Tables (PLC-5/250)..............................................................56 3.12.2 All Other Data Tables (PLC-5/250)....................................................57 3.13 Appendix M: SLC-5/04 Addressing..................................................................63 3.13.1 I/O Data Tables (SLC-5/04)................................................................63 3.13.2 All Other Data Tables (SLC-5/04)......................................................64 3.14 Appendix N: Unsolicited Reads.........................................................................68 3.14.1 PLC-2 Unsolicited Messages..............................................................68 3.14.2 PLC-3 Unsolicited Messages..............................................................68 3.14.3 PLC-5 Unsolicited Messages..............................................................68 3.14.4 PLC-5/250 Unsolicited Messages.......................................................68 3.14.5 SLC-5/04 Unsolicited Messages.........................................................68 3.15 Appendix O: Conversion of US Data A-B Serial Driver Configuration Tables. . . 70 Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

3

3.16 Appendix P: FactoryLink Upgrade Procedures.................................................71 3.17 Appendix Q: Sample Application......................................................................72 3.18 Appendix R: Environment String Parser...........................................................73

4 Glossary.....................................................................................................74 5 Supplement for SST 5136-SD-PCI Cards................................................76 5.0.1 Installing the SST Card and drivers......................................................76 5.0.2 SST PCI Configuration Control Table..................................................77 5.0.3 Logical Port...........................................................................................77 5.0.4 Card Name............................................................................................77 5.0.5 SST Module ID.....................................................................................78

6 Contact information..................................................................................79

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

1

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

Copyright 1995-1996 NOVA Technologies Copyright 1997-2000 Bullet Software Copyright 2000-2004 Axisware LLC All Rights Reserved

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

Axisware LLC

2

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

1

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

1.2 Introduction This manual describes the installation and configuration of the FactoryLink Data Highway/Data Highway Plus communication driver. The installation of the Sutherland-Schultz 5136-SD or 5136-SD-MCA board, which emulates an Allen-Bradley KT board, is also described. The driver supports the following Allen-Bradley devices: PLC-2, PLC3, PLC-5, PLC-5/250 Pyramid Integrator, and SLC-5/04. Unsolicited messages and remote addressing are also supported. Note:

On PLC-3s, for “bit” writes to work the PLC-3 must be connected to the data highway plus with a 1775-SR5 module.

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

1.4 Card Installation The Sutherland-Schultz 5136-SD(-MCA) board must be installed in the computer in an open slot. Please consult Appendix A for information concerning the installation of the 5136-SD card or the 5136-SD-MCA card. You should also refer to your hardware manuals for complete information.

1.5 Software Installation

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

2

If installing over a previous version of this driver, perform a multi-platform save of the FactoryLink application before the install and restore the application after installation. Please refer to FactoryLink documentation for details on multi-platform save and restore. In the appendix section are appendices describing the software installation for this product on specific platforms. Please read the appropriate appendix before installing this product. Platform OS/2 Windows 95/NT

Appendix B D

When the driver software install program is completed, please see the SoftKey manual for the instructions on running the Validate program. Failure to run Validate by the end of the 15-day grace period will result in a nonfunctioning driver. After this communications driver has been installed, updating to a newer version of FactoryLink may appear to cause operational problems. Please refer to Appendix P before updating FactoryLink. This product uses a SoftKey protection method. Please consult the Bullet Utility manual for a discussion of the procedures to validate the SoftKey for this product.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

3

2 Factorylink Application Configuration 2.1 External Device Definition Access this table by selecting External Device Definition from the Configuration Manager main menu. This is one of the five configuration tables that must be configured The other tables are accessed by selecting Axisware GE PCIM Driver from the Configuration Manager main menu. This table identifies the computer’s ports and I/O cards through which the devices will communicate with FactoryLink. In this table identifiers are declared which make the external devices recognizable to FactoryLink. This panel contains seven fields. Use the Tab key to move among the fields.

2.1.1 Logical Port Number assigned by the user to indicate a particular communication path. This number must be unique for each EDI driver used in the application. Valid entries: 0-999

2.1.2 Physical Card & Physical Port These fields are not used by this driver.

2.1.3 Device Name The four-character device name for the EDI driver that will use the related Logical Port. Valid entry:

SDKT

2.1.4 Function Type of communication used by the EDI driver for the related Logical Port. This field refers to the different types of EDI communication modes. Valid entry:

Axisware LLC

SYSPRG

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

4

2.1.5 Memory The amount of memory in K-bytes used for the block storage size of the read and write information entered by the user. This entry refers only to the memory used by the driver for data storage for the related Logical Port. Valid entries: 4-63

2.1.6 Comment (Optional) Description for the current Logical Port. Used only for application documentation. Valid entry:

Axisware LLC

14 alphabetic or numeric characters

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

5

2.2 Axisware SDKT Read/Write Control This table specifies the tags used to control the reading and writing of the values specified in the Read/Write Information table (the controlling tags are the Read Trigger, Read Disable, Write Trigger, Write Disable). It also defines the tags that will report the status of reads and writes (the status tags are the Read Complete, Read State, Write Complete, Write State). Each line in this table refers to one Read/Write Information Table. After these fields have been configured, select "Next" or Ctrl-N to edit the Read/Write Information Table corresponding to the Control table selected by the cursor.

2.2.1 Table Name User assigned name of the Read/Write Information Table to be defined or modified. Appendix I contains additional information for the naming conventions that must be followed to configure Fault/Diagnostic or Configuration tables for Genius blocks. Valid entry: ASCII string incorporation up to 16 of the following character set: A-Z,a-z,@,$,_, or 0-9

2.2.2 Unsolicited Read Allows the user to select whether or not the current table will be considered in the processing of an unsolicited message received from the PLC. Standard addressing is used to correlate the message from the PLC with the tags configured in the table. Please note that the PLC-5/250 must send PLC-2 Unprotected Writes if it is to be configured for unsolicited messages. Please refer to Appendix N for further details on this topic. Valid entries:

Description:

Yes Force No

Normal write to the real-time database Forced write to the real-time database No unsolicited reads are interpreted

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

Axisware LLC

Valid entries:

Description:

Yes

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

No

No exception processing.

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

6

2.2.4 Block Read Priority Priority influencing the order in which the EDI task handles the queuing of block read requests. If two requests are received simultaneously by EDI, the request with the highest priority (lowest number) is processed first. Valid entries: 1 - 4

(default = 1)

2.2.5 Block Read Trigger Digital tag whose value, when forced to 1 (ON), initiates a block read of the values specified in the related Read/Write Information Table. This trigger allows the block read operation to be initiated by some other task. Valid entry:

FactoryLink digital tag

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

FactoryLink digital tag

2.2.7 Block Read Complete Digital tag whose value is force written to 1 (ON) by the EDI task whenever any block read operation for this table is completed. If this tag is specified then when the EDI task initializes, its value is force written to 1 (ON). Note:

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

FactoryLink digital tag

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

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

Axisware LLC

FactoryLink digital tag

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

7

2.2.9 Block Write Priority Priority influencing the order in which the EDI task handles the queuing of block write and exception write requests. If two requests are received simultaneously by EDI, the request with the highest priority (lowest number) is processed first. Valid entries: 1-4

(default = 1)

2.2.10 Block Write Trigger Digital tag whose value, when forced to 1 (ON), initiates a block write of the values specified in the related Read/Write Information Table. This trigger allows the block write operation to be initiated by some other task. Valid entry:

FactoryLink digital tag

2.2.11 Block Write Disable Digital tag used to determine whether or not a block write table will be processed. If the tag value is 0, the table is permitted to function normally; however, if the value is 1, the table will not respond to the Block Write Trigger defined above. Valid entry:

FactoryLink digital tag

2.2.12 Block Write Complete Digital tag whose value is force written to 1 (ON) by the EDI task whenever any block write operation for this table is completed. If this tag is specified then, when the EDI task initializes, its value is force written to 1 (ON). Note:

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

FactoryLink digital tag

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

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink Note:

8

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

FactoryLink digital tag

2.3 Axisware SDKT Read/Write Information Table The Read/Write Information Table links FactoryLink tags to specific addresses in the PLC represented by the Logical Station. Values are either read into the tags from the device or written from the real-time database tags to the device. These tables are sometimes referred to as overlay panels, or ovr panels. Each table has one entry (line) for it in the Read/Write Control Table. Note:

Please verify that the table name displayed at the bottom of the panel correctly shows the table to be modified.

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

2.3.1 Tag Name Name of the FactoryLink tag to be updated as a result of the read operation or the tag from which information is taken to be written to the device. Valid entry:

FactoryLink tag (DIGITAL, ANALOG, LONGANA, FLOAT, MESSAGE)

2.3.2 Logical Station Number from the Logical Station Table identifying the particular combination of physical attributes that will define and govern the data transfer to and from the real-time tag. Valid entries: 0-999

2.3.3 PLC Address PLC address with which the real-time database element will be associated. Valid entries: Please refer to: Appendix I (PLC-2), Appendix J (PLC-3), Appendix K (PLC-5), Appendix L (PLC-5/250), and Appendix M (SLC-5/04) Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

9

2.3.4 Data Type Data type for information being read/written from/to the PLC. Valid entries: Please refer to Appendix H

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

10

2.4 Axisware SDKT Logical Station Control This table is used to configure each logical port and its associated stations in the Logical Station Information table. It specifies which specific port is connected to the external device being defined. After completing these fields, select "Next" or Ctrl-N to edit the Logical Station Information Table corresponding to the table selected by the cursor.

2.4.1 Logical Port Number specified in the External Device Definition Table which represents a particular communications path. This number must also be referenced in the External Device Definition panel. Valid entries: 0-999

2.4.2 Timeout (Tenths) Number of seconds in tenths permitted by the driver to process a request. A value of at least 20 to 30 is recommended. 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 S-S Technologies card and the FactoryLink CPU. This number must match the parameter specified in the CONFIG.SYS file, the memory parameter for the SDLOAD or MCINST loader software, and the setting for the card. Valid entries: Hex memory address as allowed by S-S card. Please refer to Appendix A.

2.4.4 Data Highway Address (Octal) This entry is in OCTAL and represents the card's unique data highway address (the data highway address for the FactoryLink station). A data highway error will occur if any other node on the highway shares this address. Valid entries: 0 - 77 Data Highway Plus (DH+) 0 - 377 Data Highway (DH)

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

11

2.4.5 Max Concurrent Packets Maximum number of packets that are allowed to be placed on the Data Highway at one time. This is used to keep the FactoryLink station from overloading PLCs on the Data Highway with more messages then they can buffer at one time. This field’s default value is 20 and should be left at this value for the best performance unless the PLCs on the Data Highway are responding with an Error 1, “station cannot buffer command.” Valid entries: Numeric value between 1 and 20. Default is 20

2.4.6 Message Tag Real-time database message element to which a text string will be written in the case of any error encountered in the processing of an EDI request. Valid entry: Any valid FactoryLink message tag

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

12

2.5 Axisware SDKT Logical Station Information This table defines the logical station(s) accessible through a specific logical port defined in the Logical Station Control Table. Each logical station is tied to its physical station address and device type. This logical station information structure allows communications to multiple devices on a network using one logical port. Note:

Please verify that the table name displayed at the bottom of the panel is showing the table to be modified.

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

2.5.1 Error/Status Tag Name (Optional) Analog tag to which all error codes for this logical station are to be written. Valid entries: FactoryLink analog tag

2.5.2 Logical Station (Decimal) Number entered by user to represent a particular combination of a logical port (card) and physical device (PLC). This number is referenced in the Read/Write Information Table to correlate specific addresses and tags with a physical device (PLC). Please note that this number must be unique for each four-letter device ID (SDKT). Valid entries: 0-999

2.5.3 Device Type Type of device on data highway with which communications are to be established. If remote addressing is used, the device type represents the actual device on the remote link. Valid entries: “PLC2” “PLC3” “PLC5” “PLC250” “SLC504” Note:

On PLC-3s, for “bit” writes to work the PLC-3 must be connected to the data highway plus with a 1775-SR5 module.

2.5.4 Local Station Address (Octal)

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

13

Data highway address of device on local DH/DH+ network with which communications are to be established. If a remote device is to be accessed, this is the address of the device used as a bridge between the DH+ networks (the PI or KA module). Valid entries: 0 - 77 Data Highway Plus (DH+) 0 - 377 Data Highway (DH)

2.5.5 Local/Remote Defines the related logical station as existing on the local DH/DH+ or on a remote DH/DH+. If LOCAL is specified, the remaining fields in this entry are not required. Valid entries: LOCAL REMOTE

Description: Physical station exists on local DH/DH+ Physical station exists on remote DH/DH+

2.5.6 Remote Physical Station (Octal) This field is a required entry only for remote stations. The DH/DH+ address of the device to be accessed on the remote DH/DH+ network. Valid entries: 0 - 77

2.5.7 Link ID Number This field is a required entry only for remote DH/DH+ stations. It is used for a PI link type. Each DH/DH+ network in a Pyramid Integrator system must be given a unique link ID number. These numbers are assigned in the 5/250 configuration. This field represents the link ID number of the DH/DH+ network where the target PLC resides. Valid entries: 0 - 32767

2.5.8 Link Type This field is a required entry only for remote DH/DH+ stations. It indicates the type of device to be used as the bridge between the DH/DH+ networks containing the remote physical station and the FactoryLink station.

Axisware LLC

Valid entries: PI

Description: A Pyramid Integrator is to be used as the link. Data will be transferred between ports 2 and 3 on the RM.

KA

Two KA modules will be used as the bridge. The KA modules on each DH+ network will be connected with a DH drop.

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

14

2.5.9 Comment (Optional) Description for the current Logical Station. Used only for application documentation. Valid entry:

Axisware LLC

31 alphabetic or numeric characters

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

15

3 Appendices 3.1 Appendix A: Installation of Card 3.1.1 Installation for 5136-SD The 5136-SD is used for the standard ISA computer bus. The following chart shows the valid RAM memory addresses for the ISA version of the 5136-SD card. The card's RAM memory is selected via software. There are no switches on the card to be set for the RAM memory location. MEMORY 0xA000 0xD000 0xA800 0xD800 0xB000 0xE000 0xB800 0xE800 0xC000 0xF000 0xC800 0xF800 Prior to installation, the appropriate I/O port address must be set using the switches on the board. The tables on the following two pages show the possible settings. An I/O port address of 250 (hex) is recommended. It should be noted when installing the card that no interrupts are used by the driver or by the card.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

16

3.1.2 I/O Port Addresses Table 1: This table and the one following show possible settings for the I/O port address.

Axisware LLC

ADDRESS

SW1

SW2

SW3

SW4

SW5

SW6

0x200

ON

ON

ON

ON

ON

ON

0x208

ON

ON

ON

ON

ON

OFF

0x210

ON

ON

ON

ON

OFF

ON

0x218

ON

ON

ON

ON

OFF

OFF

0x220

ON

ON

ON

OFF

ON

ON

0x228

ON

ON

ON

OFF

ON

OFF

0x230

ON

ON

ON

OFF

OFF

ON

0x238

ON

ON

ON

OFF

OFF

OFF

0x240

ON

ON

OFF

ON

ON

ON

0x248

ON

ON

OFF

ON

ON

OFF

0x250

ON

ON

OFF

ON

OFF

ON

0x258

ON

ON

OFF

ON

OFF

OFF

0x260

ON

ON

OFF

OFF

ON

ON

0x268

ON

ON

OFF

OFF

ON

OFF

0x270

ON

ON

OFF

OFF

OFF

ON

0x278

ON

ON

OFF

OFF

OFF

OFF

0x280

ON

OFF

ON

ON

ON

ON

0x288

ON

OFF

ON

ON

ON

OFF

0x290

ON

OFF

ON

ON

OFF

ON

0x298

ON

OFF

ON

ON

OFF

OFF

0x2A0

ON

OFF

ON

OFF

ON

ON

0x2A8

ON

OFF

ON

OFF

ON

OFF

0x2B0

ON

OFF

ON

OFF

OFF

ON

0x2B8

ON

OFF

ON

OFF

OFF

OFF

0x2C0

ON

OFF

OFF

ON

ON

ON

0x2C8

ON

OFF

OFF

ON

ON

OFF

0x2D0

ON

OFF

OFF

ON

OFF

ON

0x2D8

ON

OFF

OFF

ON

OFF

OFF

0x2E0

ON

OFF

OFF

OFF

ON

ON

0X2E8

ON

OFF

OFF

OFF

ON

OFF

0x2F0

ON

OFF

OFF

OFF

OFF

ON

0x2F8

ON

OFF

OFF

OFF

OFF

OFF

Default

COM2

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

17

Table 2:

Axisware LLC

ADDRESS

SW1

SW2

SW3

SW4

SW5

SW6

0x600

OFF

ON

ON

ON

ON

ON

0x608

OFF

ON

ON

ON

ON

OFF

0x610

OFF

ON

ON

ON

OFF

ON

0x618

OFF

ON

ON

ON

OFF

OFF

0x620

OFF

ON

ON

OFF

ON

ON

0x628

OFF

ON

ON

OFF

ON

OFF

0x630

OFF

ON

ON

OFF

OFF

ON

0x638

OFF

ON

ON

OFF

OFF

OFF

0x640

OFF

ON

OFF

ON

ON

ON

0x648

OFF

ON

OFF

ON

ON

OFF

0x650

OFF

ON

OFF

ON

OFF

ON

0x658

OFF

ON

OFF

ON

OFF

OFF

0x660

OFF

ON

OFF

OFF

ON

ON

0x668

OFF

ON

OFF

OFF

ON

OFF

0x670

OFF

ON

OFF

OFF

OFF

ON

0x678

OFF

ON

OFF

OFF

OFF

OFF

0x680

OFF

OFF

ON

ON

ON

ON

0x688

OFF

OFF

ON

ON

ON

OFF

0x690

OFF

OFF

ON

ON

OFF

ON

0x698

OFF

OFF

ON

ON

OFF

OFF

0x6A0

OFF

OFF

ON

OFF

ON

ON

0x6A8

OFF

OFF

ON

OFF

ON

OFF

0x6B0

OFF

OFF

ON

OFF

OFF

ON

0x6B8

OFF

OFF

ON

OFF

OFF

OFF

0x6C0

OFF

OFF

OFF

ON

ON

ON

0x6C8

OFF

OFF

OFF

ON

ON

OFF

0x6D0

OFF

OFF

OFF

ON

OFF

ON

0x6D8

OFF

OFF

OFF

ON

OFF

OFF

0x6E0

OFF

OFF

OFF

OFF

ON

ON

0X6E8

OFF

OFF

OFF

OFF

ON

OFF

0x6F0

OFF

OFF

OFF

OFF

OFF

ON

0x6F8

OFF

OFF

OFF

OFF

OFF

OFF

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

18

3.1.3 Installation for 5136-SD-MCA The 5136-SD-MCA is used for the Micro Channel computer bus. Currently, only IBM manufactures and markets personal computers that utilize the Micro Channel bus. The 5136-SD-MCA is not currently supported by the Windows NT version of this driver. Installing any card in a Micro Channel computer involves updating the computer's configuration. This is done using a reference disk supplied with the computer. The .ADF file for installing the 5136-SD-MCA is included on the distribution disk. Before you install the card, copy the file C:\$FLINK\EDI\SDKTOS2(SDKTWIN) \@6167.ADF to the reference diskette for the computer. Note:

Once the card is installed, the computer cannot boot until you have changed the configuration. If additional information is required for adding the S-S card to a Micro Channel computer, please consult the manual shipped with the card or the computer.

The port address and the memory address must both be configured with the program supplied with the computer. The possible port addresses will be displayed by the configuration program. There are four possible 32K windows that may be selected for the 5136-SD-MCA card; these are listed in the following table: MEMORY 0xC000 0xD000 0xC800 0xD800 The card must be configured with a 32K window; a 16K window is not adequate for the driver. The memory address that is selected should be recorded so that this same memory address may be entered in the NOVA SD/KT Logical Station Control Table.

3.1.4 Cable Connections The following diagram shows the cable pin connections for connecting the Sutherland-Schultz board to the Allen-Bradley Data Highway/Data Highway Plus. Note that internal to the card the first set of three pins is connected to the second set of three pins (1 to 4, 2 to 5, and 3 to 6). Any connections to pins 1, 2, or 3 could be made to 4, 5, or 6, respectively.

PIN# 1 2 3 4 5 6

Axisware LLC

DESCRIPTION Clear wire Shield wire Blue wire Clear wire Shield wire Blue wire

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

19

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, the following procedures must be followed for the software to be properly installed. First, the operator must exit from both the Run Manager and the Configuration Manager. Second, a multiplatform save file should be created. Third, the driver should be installed as described below. Fourth, restore the multiplatform save file created in step 2. Fifth, update the Configuration Manager tables for the Axisware driver (Logical Station Information). The install command file relies upon the environment variable $FLINK to complete the installation process. ($FLINK is used to refer to the environment variable “FLINK”, which points to the FactoryLink directory.) Before starting the install program you may want to manually set $FLINK if you want to have the files copied to a directory other than the default of C:\FLOS2. If $FLINK has not been defined when the install is started, you will be requested to exit and assign a value to $FLINK, and then restart the install program. $FLINK can be assigned a parameter by using the SET command (example: set flink=d:\flos2). Be sure to include the drive letter. During the installation, two ASCII text files will be modified by the installation program. The original copies of both files will be copied to a file with the same filename but a .NVA extension. The first file to be modified is $FLINK\AC\TITLES (where $FLINK is the FactoryLink directory). This file is used by the Configuration Manager to determine which tasks to list and also the order in which they are to be listed. The following line will be added to the TITLES file. (The line may be different, depending on your FactoryLink version.) sdkt.ac EDI Axisware SD/KT Driver If you have a backup file named $FLINK\AC\TITLES.NVA (possibly created by a previous install), the program will warn you during the install that it is about to be overwritten and will ask you if you want to exit, and manually save the .NVA file. The second file to be modified is $FLINK\CTGEN\CTLIST. This file is used by the CTGEN utility in the creation of the binary CT (configuration table) files used at run-time by FactoryLink. The following line will be added to the CTLIST file. sdkt: sdktshdr sdktsovr sdkt_hdr sdkt_ovr If you have a backup file named $FLINK\CTGEN\CTLIST.NVA (possibly created by a previous install), the program will ask you during the install if you wish to exit, and manually save a copy of this .NVA file before it is overwritten.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

20

3.2.2 Driver Installation Instructions (OS/2) It is important that you have followed the hardware installation procedures described in Appendix A before proceeding with the driver installation instructions. The driver software is loaded by inserting the driver diskette in drive A or B. At the OS/2 command prompt, make the drive containing the diskette the current working drive, type INSTALL and then press Enter. Note:

A source other than drive A or B can be used; e.g., from a directory on a hard drive, or across a network.

If a message is displayed stating that the INSTALL program is having difficulty finding the directory containing the FactoryLink program files, press a key to exit and use the set command to reset the $FLINK environment variable. The problem may be resolved by clearly stating the drive letter. At the OS/2 command prompt type set FLINK= followed by the drive letter (a-z), a colon (:), a backslash (\) and the directory name (s) giving the path to the FactoryLink program files. Examples: set FLINK=d:\work1\flos2 or set FLINK=t:\sect2\factory. Make sure that the only space in this command is between “set” and “FLINK”. After the “Axisware” screen appears the FactoryLink Path and FactoryLink Release Version are displayed. Press y and then the Enter (Return) key if the information is correct. The driver Serial Number and Release Type are then displayed. Press y and then the Enter (Return) key to continue. The following message will appear Copying configuration files to hard disk . . . followed by a message relevant to obtaining authorization for the product, if required. The install program checks for a backup file named $FLINK\AC\TITLES.NVA. If found, the following message is displayed: This install program will update your file named $FLINK\AC\TITLES $FLINK\AC\TITLES.NVA (a backup file) already exists. To overwrite it, press y followed by Enter (Return). By pressing n, you may Exit, manually save your .NVA backup file, and restart this program. Enter either y or n followed by the Enter (Return) key ==>

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

21

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\TITLES and $FLINK\CTGEN\CTLIST files are updated. If one of the following error messages appear: !!!! Unable to update %FLINK%\AC\TITLES file or

!!!! Unable to update %FLINK%\CTGEN\CTLIST file the lines to be added to these files can be typed in manually using a text editor. Refer to the section “Before Starting” (above) for the specific lines and where they are to be added. Please notice any additional messages displayed on the screen. When all of the necessary files have been copied the following message will appear: .....Installation Program Completed.

3.2.3 Modifying CONFIG.SYS File (OS/2) The S-S Technologies 5136-SD device driver DL.SYS must be loaded into memory when your system boots for the FactoryLink A-B DH/DH+ driver to function properly. After the installation cdrom's INSTALL program is run, the CONFIG.SYS file must be modified manually, using a text editor, such as OS/2’s System Editor “e”. Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

22

The following line (or one similar to it) must be added to the OS/2 CONFIG.SYS file. A directory that will contain the device driver DL.SYS is automatically created when the software is installed from the installation medium. Assuming that $FLINK is set to c:\flos2, the line to be added to the CONFIG.SYS would be: DEVICE=C:\FLOS2\EDI\SDKTOS2\DL.SYS It is very important that only ONE reference to this device driver be made in the CONFIG.SYS file. Note:

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

3.2.4 Modifying FLRUN.CMD File (OS/2) Depending upon the card type and whether the Data Highway (DH) or the Data Highway Plus (DH+) is to be used, one of the following lines should be entered from the OS/2 command line or added to the file FLRUN.CMD located in the $FLINK\BIN directory. (Example: C:\FLOS2\BIN\FLRUN.CMD). The line should be added at the beginning of the file immediately after the two lines: "@echo off" and "setlocal". A line similar to one of the following two examples should be entered from the OS/2 command line or added to the file FLRUN.CMD located in the $FLINK\BIN directory. The line should be added at the beginning of the file immediately after the two lines: "@echo off" and "setlocal". This example configures a 5136-SD card to an I/O port address of 250 (hex) and a memory address of D800 (hex). The “p” and “m” should be lowercase. @echo off setlocal rem For ISA card $FLINK\edi\sdktos2\sdload $FLINK\edi\sdktos2\[progname] p=250 m=D800 · · · rem where, [progname] is SDDHP for DH+ and SDDH for DH

This example shows how to configure a 5136-SD-MCA for slot 2. @echo off setlocal rem For MCA card $FLINK\edi\sdktos2\mcinst $FLINK\edi\sdktos2\[progname] 2 · · · rem where, [progname] is MCDHP for DH+ and MCDH for DH

Valid memory addresses for the ISA card are listed in Appendix A. The card and driver will utilize 32k starting at the address specified. The user must ensure that no other device or program (including caches or ROM shadowing) is attempting to utilize this same block of memory.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

23

3.2.5 Softkey Protection Validation Please refer to the Utility Manual and run the program Validate to ensure that your product does not expire at the end of the 15-day grace period. Specific steps are included in the SoftKey Manual. Warning: The installation of this product is not complete until the Validate program is run.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

24

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

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

25

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 $FLINK has not been defined when the install is started, you will be requested to exit and assign a value to $FLINK, and then restart the install program. $FLINK can be assigned a parameter by using the SET command (example: set flink=d:\flnt). During the installation, two ASCII text files will be modified by the installation program. The original copies of both files will be copied to a file with the same filename but a .NVA extension. The first file to be modified is $FLINK\AC\TITLES. This file is used by the Configuration Manager to determine which tasks to list and also the order in which they are to be listed. The following line will be added to the TITLES file. sdkt.ac EDI NOVA SD/KT Driver If you have a backup file named $FLINK\AC\TITLES.NVA (possibly created by a previous install), the program will warn you during the install that it is about to be overwritten and will ask you if you want to exit, and manually save the .NVA file. The second file to be modified is $FLINK\CTGEN\CTLIST. This file is used by the CTGEN utility in the creation of the binary files used by the Run-time FactoryLink. The following line will be added to the CTLIST file. sdkt: sdktshdr sdktsovr sdkt_hdr sdkt_ovr If you have a backup file named $FLINK\CTGEN\CTLIST.NVA (possibly created by a previous install), the program will ask you during the install if you wish to exit, and manually save a copy of this .NVA file before it is overwritten. It is important that you have followed the hardware installation procedures described in Appendix A before 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. From Start…Run (or File… Run), type INSTALL and then press Enter. Note:

A source other than drive A or B can be used; e.g., from a directory on a hard drive, or across a network.

If the $FLINK environment entry is not defined, you will be asked if you want to accept a default setting for it. Press y to accept this default setting. If n is pressed, the program exits, and you may use the command

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

26

required by your platform to specify the location of the FactoryLink program files (example: set FLINK=f:\flwin), and then restart. If a message is displayed stating that the INSTALL program is having difficulty finding the directory containing the FactoryLink program files, press a key to exit and use the set command to reset the $FLINK environment variable. The problem may be resolved by clearly stating the drive letter. At a DOS command prompt type set FLINK= followed by the drive letter (a-z), a colon (:), a backslash (\) and the directory name (s) giving the path to the FactoryLink program files. Examples: set FLINK=d:\work1\flnt or set FLINK=t:\sect2\factory. Make sure that the only space in this command is between “set” and “FLINK”. After the “Axisware” screen appears the FactoryLink Path and FactoryLink Release Version are displayed. Press y and then the Enter (Return) key if the information is correct. The driver Serial Number and Release Type are then displayed. Press y and then the Enter (Return) key to continue. The following message will appear Copying configuration files to hard disk . . . followed by a message relevant to obtaining authorization for the product, if required. The install program checks for a backup file named $FLINK\AC\TITLES.NVA. If found, the following message is displayed: This install program will update your file named %FLINK%\AC\TITLES %FLINK%\AC\TITLES.NVA (a backup file) already exists. To overwrite it, press y. By pressing n, you may Exit, manually save your .NVA backup file, and restart this program. Enter either y or n followed by the Enter (Return) key ==> The install program will then go through the same procedure before updating the file $FLINK\CTGEN\CTLIST. The install program checks for a backup file named $FLINK\CTGEN\CTLIST.NVA. If found, this message appears: This install program will update your file named %FLINK%\CTGEN\CTLIST %FLINK%\CTGEN\CTLIST.NVA (a backup file) already exists.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

27

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\TITLES and $FLINK\CTGEN\CTLIST files are updated. If one of the following error messages appear: !!!! Unable to update %FLINK%\AC\TITLES file or !!!! Unable to update %FLINK%\CTGEN\CTLIST file the lines to be added to these files can be typed in manually using a text editor. Refer to the section “Before Starting” (above) for the specific lines and where they are to be added. Please notice any additional messages displayed on the screen. When all of the necessary files have been copied the following message will appear: .....Installation Program Completed.

3.4.3 Modifying FLRUN.BAT File (Windows 95/NT) During the installation process, the NOVAMEM.SYS device driver is registered with the Windows NT system registry. The following line MUST be added to the FLRUN.BAT file (located in $FLINK\BIN\). The line should be added just beneath the 'setlocal' command line. If ECS, it should go just after the :flrun_started label. The 250 (I/O port address) and D800 (RAM memory address) entries should be replaced with your correct values. %FLINK%\EDI\SDKTW32\SDINST %FLINK%\EDI\SDKTW32\SDDHP 250 D800 Additional information on the above command, and other available command line options are contained in the S-S Technologies user's manual shipped with the 5136-SD card.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

28

The computer should now be rebooted to correctly register the driver. Proper installation of the NOVAMEM.SYS driver can be verified by using the utility program NODELIST.EXE which was installed into the $FLINK\EDI\SDKT directory. This program can typically be run as follows: 1. 2. 3.

After performing the install procedure reboot the computer Open an MS-DOS command prompt window under Windows NT. If the NOVAMEM device driver was not configured under the Control Panel/Devices program, then enter and run the following: NET START NOVAMEM

4. 5.

The response should say that the service was started successfully. Change to the C:\FLNT\EDI\SDKT\ sub-directory (or where the FactoryLink system is installed on your computer). Enter and run the following: SDINST SDDHP 250 D800 32k chk

6.

where the 250 is your port number as selected by the dip switches on the card, and the D800 is the free RAM memory location for the card to use. The loader program should load the card and perform diagnostics. Ensure that all tests pass. Enter and run the following: NODELIST D800 77 where 77 is the DH+ node number for this card. It must not conflict with any other node on the data highway. The program should display the active nodes present on the DH+, including itself.

3.4.4 Softkey Protection Validation Please refer to the Utility Manual and run the program Validate to ensure that your product does not expire at the end of the 15-day grace period. Specific steps are included in the SoftKey Manual. ASCII file not valid for PLC-5/250, X

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

29

3.5 Appendix E: (Reserved) This appendix is reserved for future use.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

30

3.6 Appendix F: Driver Status Codes

3.6.1 Application startup errors The following error codes (alphabetized) may be reported to FactoryLink while the GE PCIM Driver tables are being processed at startup. ASCII file not valid for PLC-5/250, X An ASCII file (A) was specified for a PLC-5/250. This file type is only valid for a PLC-5. Check Appendix L for a list of all file types supported for PLC-5/250s. X represents the address as entered in the configuration table. ASCII length error, X A length of 0 was specified in the PLC-5(/250) ASCII address when a MESSAGE tag was used. X represents the address as entered in the configuration table. Attempted digital write not valid for file and device, X Digital writes to floating point files are not permitted for the PLC-5/250. Check Appendix L for examples of valid PLC-5/250 addresses. X represents the address as entered in the configuration table. Attempted member write not valid for file and device, X Member writes to floating point files are not permitted for the PLC-5/250. Check Appendix L for examples of valid PLC-5/250 addresses. X represents the address as entered in the configuration table. BCD file not valid for PLC-5/250, X A binary coded decimal file (BCD) was specified for a PLC-5/250. This file type is only valid for a PLC-5. Check Appendix L for a list of all file types supported for PLC-5/250s. X represents the address as entered in the configuration table. BTD file not valid for PLC-5, X A block transfer data file (BTD) was specified for a PLC-5. This file type is only valid for a PLC-5/250. Check Appendix K for a list of all file types supported for PLC-5s. X represents the address as entered in the configuration table. BT file not valid for PLC-5/250, X A block transfer file (BT) was specified for a PLC-5/250. This file type is only valid for a PLC-5. Check Appendix L for a list of all file types supported for PLC-5/250s. X represents the address as entered in the configuration table. Configured tag does not support bit number, X Only Digital tags are permitted to specify a bit number in the address. X represents the address as entered in the configuration table.

CT line #X, no tag given

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

31

Line X of the Read/Write Information Table currently being processed does not contain a valid FactoryLink tag name. DIGITAL tags may not be used with numerical types DIGITAL tags may only be used to read or write discretes. I, O, and IS word addresses must be in octal, X All word addresses for PLC-5(/250) file types I, O, and IS must be entered in octal. X represents the address as entered in the configuration table. Illegal member or sub-element, X A member (PLC-5/250) or a sub-element (PLC-5) was larger than permissible for the selected file type. Please consult the appendix dedicated to the specific device for details concerning member/sub-element range. X represents the address as entered in the configuration table. Illegal mnemonic, X An alphabetic character or sequence of characters was detected and it does not represent a valid PLC-5(/250) mnemonic. Please consult the appendix dedicated to the specific device for details concerning member/sub-element range. X represents the address as entered in the configuration table. Inconsistent addressing encountered Condition may occur when both mnemonics and numbers are used to address subelements or bit numbers. When entering addresses, be consistent in whether or not mnemonics are used. Input bit address must be in octal, X All bit numbers specified for a PLC-5(/250) input address (file type I) must be entered in octal. X represents the address as entered in the configuration table. Internal storage file not valid for PLC-5, X An internal storage file (IS) was specified for a PLC-5. This file type is only valid for a PLC5/250. Check Appendix K for a list of all file types supported for PLC-5s. X represents the address as entered in the configuration table. Invalid address delimiters found, X An illegal delimiter was detected when the specified address was being evaluated. Check the appropriate appendix for your PLC model for examples of correct addresses. X represents the address as entered in the configuration table. Invalid bit number specified, X A letter rather than a number was detected after the "/" in a PLC-5(/250) address for which the file type does not support bit mnemonics. Check the related appendix for examples using bit numbers for the given PLC. X represents the address as entered in the configuration table. Invalid data type encountered Please consult Appendix H for list of valid data types. Invalid file type, X The first characters of the ASCII address do not define a supported PLC-5(/250) file type. Check the related appendix for a list of all file types supported for the given PLC. X represents the address as entered in the configuration table. IS bit address must be in octal, X Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

32

All bit numbers specified for a PLC-5/250 internal storage address (file type IS) must be entered in octal. X represents the address as entered in the configuration table. Logical station X not found The logical station X was specified in the current Read/Write Information Table, but this logical station number was never defined in the Logical Station Information Table. MESSAGE tags may not be used with numerical types Only BIN and ASC data types may be used with MESSAGE tags. MG file not valid for PLC-5/250 (use MSG), X A message file (MG) was specified for a PLC-5/250. This file type is only valid for a PLC-5. Message files are indicated for the PLC-5/250 with "MSG". Check Appendix L for a list of all file types supported for PLC-5/250s. X represents the address as entered in the configuration table. MSG file not valid for PLC-5 (use MG), X A message file (MSG) was specified for a PLC-5. This file type is only valid for a PLC-5/250. Message files are indicated for the PLC-5 with "MG". Check Appendix K for a list of all file types supported for PLC-5s. X represents the address as entered in the configuration table. No address delimiters found, X All PLC-5(/250) addresses must include at least one valid delimiter following the file type. Check the related appendix for examples using the appropriate delimiters for the given PLC. X represents the address as entered in the configuration table. No default file number available for selected file, X Not all PLC-5 file types have default file numbers. Check Appendix K for the details concerning the specified file type. X represents the address as entered in the configuration table. No length delimiter, X All message strings require the length to be specified. This length defines the number of words to read into the provided message tag. X represents the address as entered in the configuration table. No tags, packet not made The current Read/Write Information Table contained entries that caused a portion of the table to generate an error and consequently no DCT information was produced. Only MESSAGE tags may be used with ASC ASCII strings may only be read into MESSAGE tags. Ordering anomaly, inefficient grouping Indicates that the Read/Write Information Table currently being processed contains addresses such that the driver is unable to properly arrange all the entries. This generally occurs with the abnormal use of subelements or when bit numbers greater than the word length are used. Out of Memory The driver was unable to internally allocate all the necessary memory. Allocate more memory in the External Device Definition Table. Out of RAM Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

33

EDI was unable to parse the entire read/write table due to its size. The solution is to break the table into multiple smaller tables. There will not be any performance degradation due to breaking up the table, since the table is already being broken up into several data packets. Output bit address must be in octal, X All bit numbers specified for a PLC-5(/250) output address (file type O) must be entered in octal. X represents the address as entered in the configuration table. PLC-2 bit number must be in octal, X All bit numbers specified in PLC-2 addresses must be entered in octal. X represents the address as entered in the configuration table. PLC-2 word address must be in octal, X All word addresses for PLC-2 must be entered in octal. X represents the address as entered in the configuration table. PLC-5/250 addresses not valid for unsolicited reads Only PLC-2 and PLC-5 addresses may be used when configuring unsolicited reads. If an unsolicited message is to be received from a PLC-5/250, the PLC must send a PLC-2 Unprotected Write. The driver must then have a Logical Station defined as a PLC-2 with a Data Highway address equal to the PLC-5/250. The PLC-2 addresses defined with this Logical Station will then be considered in the driver's search to resolve the incoming message. Please see Appendix N for details. Status file not valid for PLC-5/250, X A status file (S) was specified for a PLC-5/250. This file type is only valid for a PLC-5. Check Appendix L for a list of all file types supported for PLC-5/250s. X represents the address as entered in the configuration table.

3.6.2 Run-time startup errors The following errors (alphabetized) may be reported when the EDI task is started after all tables have been processed. 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 file DL.SYS is specified in the CONFIG.SYS file as indicated in Appendix B of this manual. Cannot open device (error: X) [OS/2 Only] Unable to open the OS/2 device driver DL.SYS. Check that this file is specified in the CONFIG.SYS file as indicated in Appendix B of this manual. Invalid Data Highway Plus station address Check the data highway address for FactoryLink specified in the NOVA SD/KT Logical Station Control Table. Invalid Data Highway station address Check the data highway address for FactoryLink specified in the NOVA SD/KT Logical Station Control Table. No card or DH/DH+ module running at X Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

34

The 5136-SD card was not found at memory address X as specified in the NOVA SD/KT Logical Station Control Table. Check that the command line parameter specifying the memory address for the SDLOAD or MCINST loader program and the CONFIG.SYS device driver matches the address selected in the Configuration Manager (should be something like D000 or D800). Also check that the card is properly seated, that the device driver in the CONFIG.SYS loaded without any errors, and that the loader program executed without any errors. Timeout waiting for card reset Expected response not returned from card. Check that the command line parameter specifying the memory address for the SDLOAD or MCINST loader program and the CONFIG.SYS device driver matches the address selected in the Configuration Manager (should be something like D000 or D800). Also check that the card is properly seated, that the device driver in the CONFIG.SYS loaded without any errors, and that the loader program executed without any errors.

3.6.3 SoftKey protection errors Messages relating to SoftKey protection may appear after the driver has been initialized by the EDI task. Please refer to the SoftKey manual if they appear. If SoftKey does not detect a problem the following message will be displayed. Serial #: XXXXXXX Single Processor Run Time License This is a normal informational message displaying the product name and your Serial Number.

3.6.4 Run-time errors The following errors may be reported while the driver is processing application requests. The text represents the error message returned to the message tag defined in the Logical Station Control Table. The number in parentheses is returned to the analog tag defined in the Logical Station Information Table. While the following errors are not immediately fatal, recurring errors should be evaluated and eradicated to maintain the integrity of the network. Status codes and extended status codes are listed in Appendix G. (-)

Timeout, retry attempted Data Highway communication error No analog value is returned for this error. This should serve as a warning that the network integrity is suspect. Check for cabling problems or noise.

(-)

XXXX sdktcpt iomgr() unknown state Buffer manipulation error No analog value is returned for these errors. An internal processing error has occurred during driver execution. Please contact NOVA Technologies with the problem.

(-1)

Module communication timeout Communications between the DSF module and the CPT module were disrupted. If this error occurs regularly, contact NOVA Technologies with the problem.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

35

(-2)

Buffer manipulation error Communication error with PLC These errors should not occur during normal processing. However, if one of these errors occurs, please contact NOVA Technologies.

(-3)

Logical station X failed to respond SD/KT card timeout malfunction Timeout waiting for PLC response The indicated logical station did not reply to the driver's write message or read request. Check cabling and PLC station number.

(-4)

XXXX sdktdsf dsf_read/write() error returned from bld_q_rd/wr() EDI communication problem, report error to NOVA Technologies.

(4)

Data Highway network down! Check all data highway cabling and connectors. This error is generated by a status code of 4.

(*)

Status code X, extended status Y The indicated status and extended status codes were returned by the selected PLC. Check X and Y against the error table provided in Appendix G.

(**)

Status code X The indicated status code was returned by the PLC. No extended status code was returned. Action as above.

* All errors returned with an extended status code are placed in the analog error tag as the extended status code plus 1000. ** All errors returned with only a status value are placed directly in the analog error tag.

3.6.5 Unsolicited message processing errors The following errors may be reported while the driver is attempting to process unsolicited message requests. The text represents the error message returned to the message tag defined in the Logical Station Control Table. While the following errors are not immediately fatal, recurring errors should be evaluated and eradicated to maintain the integrity of the network. EDI DSF pointer error Software error; contact NOVA Technologies with error message. Invalid PLC type for EDI processing Check that the MSG instruction in the PLC is PLC-2 Unprotected Write or PLC-5 Typed Write. Linked list error Software error; contact Axisware with error message. Maximum number of unsolicited reads exceeded Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

36

A maximum number of 32000 unsolicited reads may be configured. If this limit is reached, please contact Axisware. No unsolicited reads have been defined An unsolicited message has been received over the data highway; however, no unsolicited messages were defined in the Configuration Manager. If unsolicited messages are to be used, at least one line on the Read/Write Control Table must specify unsolicited message support. PLC-2/PLC-5 address format error Check that the MSG instruction in the PLC is PLC-2 Unprotected Write or PLC-5 Typed Write. Subelement unexpected Check that the MSG instruction in the PLC is PLC-2 Unprotected Write or PLC-5 Typed Write. Unable to allocate memory for all unsolicited messages Allocate more memory to EDI task. Unable to establish unsolicited index Internal software error, contact Axisware. Unable to evaluate unsolicited message An unsolicited message was received over the data highway that has an unexpected format. Check that the MSG instruction in the PLC is PLC-2 Unprotected Write or PLC-5 Typed Write. Undefined unsolicited message received - X An unsolicited message directed toward PLC address X was received. This address has not been configured as an unsolicited message in the Configuration Manager. Unsolicited message buffer exceeded EDI limits the maximum number of unsolicited messages that can be queued before being processed by the driver. This error indicates that FactoryLink is receiving messages over the network more quickly than the driver can process them. Reduce the number of messages directed toward FactoryLink or reduce the number of tags that are configured as unsolicited reads. Unsolicited message too long The message instruction from the PLC required more than one packet to transmit. Data may be lost in transfer. Split MSG instruction into two smaller instructions. Unsolicited odd byte address encountered The PLC-2 Unprotected Write will only generate messages with even byte counts; therefore, if this error occurs, the operator must verify that the PLC is properly configured to send messages to FactoryLink.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

37

3.7 Appendix G: PLC Status Codes The following status and extended status codes may be returned during the driver's operation: STS

EXT STS

DESCRIPTION

0 1 2 3 4 5 6 7 8 16 32 48 64 80 96 112 128 144 160 176 192 208 224

-

success, no error station cannot buffer command destination node (PLC) not found on DH+ duplicate token holder detected local port is disconnected application layer timed out waiting for a response duplicate node detected station off-line hardware fault illegal command or format host has a problem and will not communicate remote node host is missing, disconnected, or shut down host could not complete function due to hardware problem addressing problem or memory protect rungs function disallowed due to command protection selection processor is in program mode compatibility mode file is missing or communication zone problem remote node cannot buffer command not used remote node problem due to download cannot execute command due to active IPBs not used not used

240 240 240 240 240 240 240 240 240

0 1 2 3 4 5 6 7 8

240 240 240 240 240 240 240 240 240 240

9 10 11 12 13 14 15 16 17 18

not used a field has an illegal value less levels specified in address than minimum for any address more levels specified in address than system supports symbol not found symbol is of improper format address does not point to something usable file is of wrong size cannot complete request, situation has changed since the start of the command data or file is too large transaction size plus word size is too large access denied, improper privilege condition cannot be generated, resource is not available (upload active) condition already exists, resource is already available command cannot be executed histogram overflow no access illegal data type invalid parameter or invalid data

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink 240 240 240 240 240 240 240 240 240

19 20 21 22 23 24 25 26 27

Axisware LLC

38

address reference exists to deleted data table command execution failure for unknown reason data conversion error scanner not able to communicate with 1771 rack adapter adapter cannot communicate with module 1771 module response was not valid duplicated label file is open; another node owns it another node is the program owner

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

39

3.8 Appendix H: Data Types and Conversions The driver supports the following FactoryLink tag types: DIGITAL ANALOG LONG ANALOG FLOATING POINT MESSAGE The driver also supports the following PLC data types: BIN INT2 INT4 BCD4 FLT4 FLT8 P3FLT ASC

(single data bit) (16 bit signed integer) (32 bit signed integer) (16 bit, 4 digit BCD) (32 bit floating point - single precision) (64 bit floating point - double precision) (32 bit PLC-3 floating point - single precision) (ASCII strings)

Note P3FLT is valid only with A-B PLC-3s. The floating point format used by PLC-3s is different from the format used in other types of A-B PLCs. The native floating point format for other types of A-B PLCs is specified by using FLT4. Note:

FLT8 is not a native A-B PLC data type. It is present in this driver for compatibility with USData's FactoryLink Allen-Bradley Asynchronous Driver. This data type is designed to be used to pass FactoryLink Floating Point Tags between FactoryLink stations using the PLC as an intermediary device.

Valid PLC data types for each of the FactoryLink tag types: DIGITAL ANALOG LONG ANALOG FLOATING POINT BIN BIN BIN BIN INT2 INT2 INT2 INT4 INT4 INT4 BCD4 BCD4 BCD4 FLT4 FLT4 FLT4 FLT8 FLT8 FLT8 P3FLT P3FLT P3FLT

MESSAGE BIN ASC

The following descriptions are from the viewpoint of “read”. A similar transfer occurs on writes. DIGITAL BIN DIGITAL tags may only be converted to and from the BIN data type. If the requested binary PLC data type is on, the DIGITAL tag will be set to one. If the binary element is off, the DIGITAL tag will be set to zero.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

40

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

FLT8

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

41

The whole number portion of the floating point number is transferred to the LONG ANALOG tag. This conversion is accurate only if the whole number value is between -2,147,483,648 and +2,147,483,647. When converting back to a FLT8, the fractional portion of zero is assumed. P3FLT The whole number portion of the floating point number is transferred to the LONG ANALOG tag. This conversion is accurate only if the whole number value is between -2,147,483,648 and +2,147,483,647. When converting back to a P3FLT, the fractional portion of zero is assumed. FLOATING POINT INT2 The INT2 value is converted into a standard IEEE 64 bit floating point value and then transferred directly into the FLOATING POINT tag. The fractional portion of the number is assumed to be zero. INT4 The INT4 value is converted into a standard IEEE 64 bit floating point value and then transferred directly into the FLOATING POINT tag. The fractional portion of the number is assumed to be zero. BCD4 After being read from the PLC, the BCD4 value is converted into a 16 bit integer. The value is then handled as the INT2 data type above. FLT4 The FLT4 value is converted from a standard IEEE 32 floating point number into a standard IEEE 64 bit floating point number. This value is then transferred directly into the FLOATING POINT tag. FLT8 or BIN The data is transferred directly; no conversion is necessary. P3FLT The PLC-3 floating point value is converted to a IEEE 32 floating point number, and then converted into a standard IEEE 64 bit floating point number. This value is then transferred directly into the FLOATING POINT tag. MESSAGE BIN All data is read directly into the message tag from the specified word address. No conversion of any kind is employed. ASC When reading ASCII strings from the PLC, a byte inversion must be done for the string to be properly displayed in FactoryLink. The ASC data type automatically does the needed conversion.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

42

3.9 Appendix I: PLC-2 Addressing The addressing scheme for the PLC-2 follows exactly the standards established by the A-B programming software. The standard format is as follows: word number[/bit] [,length] where word number

=

Word number in OCTAL. Must be included.

bit

=

Bit number specified in OCTAL. If omitted the bit number is assumed to be zero (0).

length

=

Number of words for string specified in DECIMAL. Must be used with Message tags only.

Examples: Address: 10/17 2/0 2 16,22

Axisware LLC

Description: Word 10 (octal), bit 17 (octal) Word 2, bit 0 As above Word 16 (octal), 22 (decimal) words requested

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

43

3.10 Appendix J: PLC-3 Logical Addressing

3.10.1 I/O Data Tables (PLC-3) The addressing scheme for inputs and outputs is different from that used for other PLC-3 file types. The difference is that the element number is specified in octal. The addressing used by the Driver is detailed below. The standard format is as follows: filetype[filenumber]:[elementnumber][/bit] where filetype

=

Either I for input or O for output

filenumber

=

File number in DECIMAL (optional) If the file number is omitted, a zero (0) is assumed. Valid range for file number is 0 - 999

elementnumber=

Element number in OCTAL (optional) If the element number is omitted, a zero (0) is assumed. The valid range for word number is 0 - 7777.

bit

Bit number in OCTAL (optional) specified after slash (slash must be included if bit number is specified) If the bit number is omitted, a zero (0) is assumed.

=

Note: The filenumber and elementnumber may be separated by either a colon(:) or a semicolon(;). I - Inputs The input image file uses no mnemonics. Examples: Address: I:7/1 I20:30/7 I/17 I:32/0

Description: File 0, element 7, bit 1 File 20, element 30 (octal), bit 7 File 0, element 0, bit 17 (octal) File 0, element 32 (octal), bit 0

O - Outputs The output image file uses no mnemonics. Examples: Address: O:7/1 O20:30/7 O/17

Axisware LLC

Description: File 0, element 7, bit 1 File 20, element 30 (octal), bit 7 File 0, element 0, bit 17 (octal)

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink O:32/0

44

File 0, element 32 (octal), bit 0

3.10.2 All Other Data Tables (PLC-3) The addressing scheme for the remaining tables is similar to inputs and outputs. The addressing used by the Driver is detailed below. The standard format is as follows: filetype[filenumber]:[element][.subelement] [/bit] [,length] where filetype

=

One of the following (required) A, B, C, D, F, H, N, S, or T.

filenumber

=

File number in DECIMAL (optional) If the file number is omitted, a zero (0) is assumed. Valid range for file number is 0 - 999, except for C and T files where 0 is the only valid file number. = Element number in DECIMAL (optional) If element is not specified, a zero (0) is assumed. Valid range for element is 0 - 9999.

element

(Of the following you may use one or none:) subelement

=

Subelement number specified in DECIMAL or mnemonic (optional). Subelements are only valid for the file types where they are specifically mentioned below.

bit

=

Bit number in OCTAL (optional) specified after slash (slash must be included if bit number is specified). If the bit number is omitted, a zero (0) is assumed. Some file types, as described below, permit the use of bit mnemonics.

length

=

Number of words to be read into message tag. This is always preceded by a comma.

Note: The filenumber and element may be separated by either a colon(:) or a semicolon(;). A - ASCII The ASCII file uses no subelements or mnemonics. Please note that no default file number exists for an ASCII file. Examples: Address: A10:10 Axisware LLC

Description: File 10, word 10, bit 0 [email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink A10:10,20 A20:30/14

45

File 10, word 10, length 20 (40 bytes) File 20, word 30, bit 14 (octal)

B - Binary The binary file uses no subelements or mnemonics. Examples: Address: B/17 B0/17 B13:1/2

Description: File 0, word 0, bit 17 (octal) As above File 13, word 1, bit 2

C - Counter The counter file permits both subelement mnemonics and bit mnemonics. Bits: Number: 17 16 15 14 13

Mnemonic: CU CD DN OV UF

Description: Count up enable Count down enable Counter done Counter overflow Counter underflow

Subelements: Number: 1 2

Mnemonic: PRE ACC

Description: Preset Value Accumulated Value

Examples: Address: C:1.PRE C2.ACC C:5.DN C:6/13

Description: Counter 1, preset value Counter 2, accumulated value Counter 5, done bit Counter 6, overflow bit

D- Decimal The decimal file uses no subelements or mnemonics. This section is comprised of 16 bit BCD words. Please note that no default file number exists for a decimal file. Examples: Address: D0:10 D8:11

Description: File 0, element 10 File 8, element 11

F - Floating Point The floating point file uses no subelements or mnemonics. Examples:

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink Address: F:10 F8:10

46

Description: File 0, element 10 As above

H - High-Order Integer (Long) The High-Order integer or long file uses no subelements or mnemonics. Elements are 32 bit signed integers Examples: Address: H:10 H7:10 H20:30/14

Description: File 0, element 10, bit 0 File 7, element 10, bit 0 File 20, element 30, bit 14 (octal)

N - Integer The integer file uses no subelements or mnemonics. Examples: Address: N:10 N7:10 N20:30/14

Description: File 0, word 10, bit 0 File 7, word 10, bit 0 File 20, word 30, bit 14 (octal)

S - Status The status file uses no subelements or mnemonics. Examples: Address: S:10 S2:10

Description: File 0, word 10, bit 0 File 2, word 10, bit 0

T - Timer The timer file permits both subelement mnemonics and bit mnemonics. Bits:

Axisware LLC

Number: 17 16 15

Mnemonic: TE TT TD

Description: Timer enabled Timer timing Timer done

Subelements: Number: 1 2

Mnemonic: PRE ACC

Description: Preset Value Accumulated Value

Examples: Address: T:1.PRE T0:2.ACC

Description: Timer 1, preset value Timer 2, accumulated value

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink T5.TD T6/17

Axisware LLC

47

Timer 5, timer done bit Timer 6, enabled bit

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

48

3.11 Appendix K: PLC-5 Logical Addressing

3.11.1 I/O Data Tables (PLC-5) The addressing scheme for inputs and outputs is different from that used for other PLC-5 data types. The addressing used by the Driver is detailed below. The standard format is as follows: filetype:[wordnumber][/bit] where filetype

=

Either I for input or O for output

wordnumber

=

Word number in OCTAL (optional) If the word number is omitted, a zero (0) is assumed. The valid range for word number is 0 - 37.

bit

=

Bit number in OCTAL (optional) specified after slash (slash must be included if bit number is specified) If the bit number is omitted, a zero (0) is assumed.

Note: The filetype and wordnumber may be separated by either a colon(:) or a semicolon(;). I - Inputs The input image file uses no mnemonics. Examples: Address: I:7/1 I:30/7 I/17 I:32/0

Description: Element 7, bit 1 Element 30 (octal), bit 7 Element 0, bit 17 (octal) Element 32 (octal), bit 0

O - Outputs The output image file uses no mnemonics. Examples: Address: O:7/1 O:30/7 O/17 O:32/0

Axisware LLC

Description: Element 7, bit 1 Element 30 (octal), bit 7 Element 0, bit 17 (octal) Element 32 (octal), bit 0

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

49

3.11.2 All Other Data Tables (PLC-5) The addressing scheme for the remaining tables is similar to inputs and outputs; however, there are enough differences to cover them separately. The addressing used by the Driver is detailed below. The standard format is as follows: filetype[filenumber]:[element][.subelement] [/bit] [,length] where filetype

=

One of the following (required) A, B, BT, C, D, F, MG, N, PD, R, S, ST, or T

filenumber

=

File number in DECIMAL (optional) If the file number is omitted, the default for that file type is assumed (i.e. T: = T4:). = Element number in DECIMAL (optional) Valid ranges are as configured in PLC. If element is not specified, a zero (0) is assumed.

element

(Of the following you may use one or none:) subelement

=

Subelement number specified in DECIMAL or mnemonic (optional). Subelements are only valid for the file types where they are specifically mentioned below.

bit

=

Bit number in DECIMAL (optional) specified after slash (slash must be included if bit number is specified). If the bit number is omitted, a zero (0) is assumed. Some file types, as described below, permit the use of bit mnemonics.

length

=

Number of words to be read into message tag. This is always preceded by a comma.

Note: The filenumber and element may be separated by either a colon(:) or a semicolon(;).

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

50

A - ASCII The ASCII file uses no subelements or mnemonics. Please note that no default file number exists for an ASCII file. Examples: Address: A10:10 A10:10,20 A20:30/14

Description: File 10, word 10, bit 0 File 10, word 10, length 20 (40 bytes) File 20, word 30, bit 14

B - Binary The binary file uses no subelements or mnemonics. Examples: Address: B/17 B3/17 B13:1/2

Description: File 3, word 1, bit 1 As above File 13, word 1, bit 2

BT - Block Transfer The block transfer file permits both subelement mnemonics and bit mnemonics. Please note that no default file number exists for this file type and that this file type is only valid for “new” generation PLC-5s (5/30, 5/40, 5/60, 5/80). Bits: Number: 15 14 13 12 11 10 9 8 7

Mnemonic: EN ST DN ER CO EW NR TO RW

Description: Enabled Start Done Error Continue Enable wait No response Time out Read/Write

Subelements: Number: 1

Mnemonic: RLEN

Description: Receive length. Requested word count. Done length. Transmitted word count. File-type number. Element. Word number. Rack/Group/Slot.

2

DLEN

3 4 5

FILE ELEM RGS

Examples: Address: Description: BT12:1.RLEN File 6, control 1, receive length value BT20:2.FILE File 20, control 2, File type value

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink BT15:5/ST

51

File 6, control 5, start bit

C - Counter The counter file permits both subelement mnemonics and bit mnemonics. Bits: Number: 15 14 13 12 11

Mnemonic: CU CD DN OV UN

Description: Count up Count down Done Overflow Underflow

Subelements: Number: 1 2

Mnemonic: PRE ACC

Description: Preset Value Accumulated Value

Examples: Description: Address: C:1.PRE File 5, counter 1, preset value C20:2.ACC File 20, counter 2, accumulated value C5:5.DN File 5, counter 5, done bit C5:6/12 File 5, counter 6, overflow bit D- Decimal The decimal file uses no subelements or mnemonics. This section is comprised of 16 bit BCD words. Please note that no default file number exists for a decimal file. Examples: Address: D0:10 D8:11

Description: File 0, element 10 File 8, element 11

F - Floating Point The floating point file uses no subelements or mnemonics. Examples: Address: F:10 F8:10

Description: File 8, element 10, bit 0 As above

MG - Message The message file permits both subelement mnemonics and bit mnemonics. Please note that no default file number exists for this file type and that this file type is only valid for “new” generation PLC-5s (5/30, 5/40, 5/60, 5/80). Bits:

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

52

Number: 9 8 7 6 5 4 3 2

Mnemonic: NR TO EN ST DN ER CO EW

Description: No response Time out Enable Start transmission Done Error Continuous Enable waiting

Subelements: Number: 1 2 3

Mnemonic: ERR RLEN DLEN

Description: Error code Request length. Done length

Examples: Address: MG11:1.ERR MG21:2.3 MG15:5/CO

Description: File 11, message 1, error code File 21, message 2, done length File 15, message 5, continuous bit

N - Integer The integer file uses no subelements or mnemonics. Examples: Address: N:10 N7:10 N20:30/14

Description: File 7, word 10, bit 0 As above File 20, word 30, bit 14

PD - PID Loop The PID file permits both subelement mnemonics and bit mnemonics. Please note that no default file number exists for this file type and that this file type is only valid for “new” generation PLC-5s (5/30, 5/40, 5/60, 5/80). Bits: Number: 28 27 26 25 24 19 18 17 16 15 9 8

Axisware LLC

Mnemonic: INI SPOR OLL OLH EWD DVNA DVPA PVLA PVHA EN CT CL

Description: PID initialized Set point out of range Output alarm, Low limit Output alarm, High limit Error within dead band Deviation High Alarm Deviation Low Alarm Process Variable Low Alarm PV High Alarm Enable Cascaded Type Cascaded Loop

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink 7 6 4 2 1 0

53

PVT DO SWM CA MO PE

Process Variable Tracking Derivative Of Software A/M Mode Control Action Station Mode (auto/manual) PID Equation Type

Subelements: Number: 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 34 36 38 40 42 44 46 48

Mnemonic: SP KP KI KD BIAS MAXS MINS DB SO MAXO MINO UPD PV ERR OUT PVH PVL DVP DVN PVDB DVDB MAXI MINI TIE

Description: Setpoint Proportional gain Initial gain Derivative gain Output bias % Maximum scaled value Minimum scaled value Dead band Set output % Maximum Output limit Minimum Output limit Update time Process Variable Error: Scaled Output PV alarm High PV alarm Low Deviation Alarm + Deviation Alarm PV alarm dead band Deviation alarm dead band Maximum Input Minimum Input Tieback %

Examples: Address: PD11:1.SP PD16:2.DB PD15:5/PE PD70:1/OLL

Description: File 11, PID 1, setpoint File 16, PID 2, dead band File 15, PID 5, equation bit File 70, PID 1, lower output alarm

R - Control The control file permits both subelement mnemonics and bit mnemonics. Bits: Number: 15 14 13 12 11

Axisware LLC

Mnemonic: EN EU DN EM ER

Description: Enabled Enable unload Done Empty Error

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink 10 9 8 Subelements: Number: 1 2

Examples: Address: R:1.LEN R20:2.POS R6:5.UL R6:6/14

54

UL IN FD

Unload Inhibit Comparison Found

Mnemonic: LEN POS

Description: Length Position

Description: File 6, control 1, length value File 20, control 2, position value File 6, control 5, unload bit File 6, control 6, enable unload bit

S - Status The status file uses no subelements or mnemonics. Examples: Address: S:10 S2:10

Description: File 2, word 10, bit 0 As above

ST - String The string file permits subelement mnemonics. Please note that no default file number exists for this file type and that this file type is only valid for “new” generation PLC-5s (5/30, 5/40, 5/60, 5/80). Subelements: Number: 0 1 Examples: Address: ST22:1.LEN ST22:2.1,5

Mnemonic: LEN DATA

Description: Length. Specifies an even number of bytes. Actual string data

Description: File 22, string 1, length value File 22, string 2, string data, length 5

T - Timer The timer file permits both subelement mnemonics and bit mnemonics. Bits: Number: 15 14

Axisware LLC

Mnemonic: EN TT

Description: Enabled Timing

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink 13 Subelements: Number: 1 2

55

DN

Done

Mnemonic: PRE ACC

Description: Preset Value Accumulated Value

Examples: Address: Description: T:1.PRE File 4, timer 1, preset value T20:2.ACC File 20, timer 2, accumulated value T4:5.DN File 4, timer 5, timer done bit T4:6/15 File 4, timer 6, enabled bit

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

56

3.12 Appendix L: PLC-5/250 Logical Addressing

3.12.1 I/O Data Tables (PLC-5/250) The addressing scheme for inputs, outputs, and internal storage is different from that used for other PLC-5/250 data tables. The addressing used by the Driver is detailed below. The standard format is as follows: [RS]filetype:[wordnumber][/bit] where RS

=

Always 1. Please Note: the remote scanner number must always be set to a 1 to access I, O, or IS data on any remote scanner.

filetype

=

Either I for input, O for output, or IS for internal storage

wordnumber

=

Word number in OCTAL (optional). If the word number is omitted, a zero (0) is assumed. The valid range for word number is 0 - 377 (0 - 777 for IS).

bit

=

Bit number in OCTAL (optional) specified after slash (slash must be included if bit number is specified). If the bit number is omitted, a zero (0) is assumed.

Note: The filetype and wordnumber may be separated by either a colon(:) or a semicolon(;). I - Inputs The input image file uses no mnemonics. Please note the octal word addresses that are valid for each remote scanner module. Address Ranges: RS Module: 1 2 3 4 Examples: Address: 1I:7/1 1I:110/7 1I/17 1I:320/0 Axisware LLC

Addresses (octal): 0 - 77 100 - 177 200 - 277 300 - 377 Description: RS 1, element 7, bit 1 RS 2, element 110 (octal), bit 7 RS 1, element 0, bit 17 (octal) RS 4, element 320 (octal), bit 0 [email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

57

O - Outputs The output image file uses no mnemonics. Please note the octal word addresses that are valid for each remote scanner module. Address Ranges: RS Module: 1 2 3 4

Addresses (octal): 0 - 77 100 - 177 200 - 277 300 - 377

Examples: Address: 1O:7/1 1O:110/7 1O/17 1O:320/0

Description: RS 1, element 7, bit 1 RS 2, element 110 (octal), bit 7 RS 1, element 0, bit 17 (octal) RS 4, element 320 (octal), bit 0

IS - Internal Storage The internal storage file uses no mnemonics. Please note the octal word addresses that are valid for each remote scanner module. Address Ranges: RS Module: 1 2 3 4

Addresses (octal): 0 - 177 200 - 377 400 - 577 600 - 777

Examples: Address: 1IS:7/1 1IS:110/7 1IS/17 1IS:620/0

Description: RS 1, element 7, bit 1 RS 1, element 110 (octal), bit 7 RS 1, element 0, bit 17 (octal) RS 4, element 620 (octal), bit 0

3.12.2 All Other Data Tables (PLC-5/250) The addressing scheme for the remaining tables is similar to inputs and outputs; however, there are enough differences to cover them separately. The addressing used by the Driver is detailed below. The standard format is as follows: [module]filetype[filenumber]:[element][.subelement] [/bit] [,length] Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

58

where module

=

Processor module where data is to be accessed. Please refer to each data type for valid module numbers. (RM = 0, RS and LP = 1 - 4.) If not specified, it defaults to 0.

filetype

=

One of the following (required) B, BTD, C, F, L, MSG, N, PD, R, ST, or T.

filenumber

=

File number in DECIMAL (optional) If the file number is omitted, a default of zero is assumed. = Element number in DECIMAL (optional) Valid ranges are as configured in PLC. If element is not specified, a zero (0) is assumed.

element

(Of the following you may use one or none:) subelement

=

Subelement number specified in DECIMAL or mnemonic (optional). Subelements are only valid for the file types where they are specifically mentioned below.

bit

=

Bit number in DECIMAL (optional) specified after slash (slash must be included if bit number is specified). If the bit number is omitted, a zero (0) is assumed. Some file types as described below permit the use of bit mnemonics.

length

=

Number of words to be read into message tag. This is always preceded by a comma.

Note: The filenumber and element may be separated by either a colon(:) or a semicolon(;).

B - Binary The binary file uses no subelements or mnemonics. Valid module numbers are 0 - 4. Examples: Address: 0B/17 1B3/17 4B13:1/2

Description: RM (resource manager), file 0, word 1, bit 1 LP 1 (logic processor), file 3, word 1, bit 1 LP 4, file 13, word 1, bit 2

BTD - Block Transfer Data The block transfer data file uses no subelements or mnemonics. Valid module numbers are 1 4. These module numbers represent remote scanner modules. Examples: Address: 1BTD1:1 1BTD8;2

Axisware LLC

Description: RS 1, file 1, element 1 RS 1, file 8, element 2

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink 4BTD2:5/2

59

RS 4, file 2, element 5, bit 2

C - Counter The counter file permits both member mnemonics and bit mnemonics. Valid module numbers are 0 - 4. Bits: Number: 15 14 13 12 11

Mnemonic: CU CD DN OV UN

Description: Count up Count down Done Overflow Underflow

Subelements: Number: 1 2

Mnemonic: PRE ACC

Description: Preset Value Accumulated Value

Examples: Address: 1C:1.PRE 0C20:2.ACC C5:5/DN

Description: LP 1, file 0, counter 1, preset value RM, file 20, counter 2, accumulated value RM (default), file 5, counter 5, done bit

F - Floating Point The floating point file permits no subelements or mnemonics. Examples: Address: 4F:10 0F8:10 1F9:22/2

Description: LP 4, file 0, element 10, bit 0 RM, file 8, element 10, bit 0 LP 1, file 9, element 22, bit 2

L - Long Integer The long integer file (32 bit integers) uses no subelements or mnemonics. Valid module numbers are 0 - 4. Examples: Address: Description: 0L:10 RM, file 0, word 10, bit 0 L7:12/1 RM, file 7, word 12, bit 1 4L20:30/14 LP 4, file 20, word 30, bit 14 MSG - Message The message file permits both subelement mnemonics and bit mnemonics. The only valid module number is 0.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

60

Bits: Number: 7 6 5 4 3 2 1 0

Mnemonic: EN ST AD AE CO EW DN ER

Description: Enable Start transmission Async done Async error Continuous Enabled waiting Done Error

Subelements: Number: 1 2 3

Mnemonic: ERR RLEN DLEN

Description: Error code Requested length. Done length

Examples: Address: 0MSG11:1.ERR MSG16:7/EN

Description: RM, file 11, message 1, error code RM, file 16, message 7, enable bit

N - Integer The integer file uses no subelements or mnemonics. Valid module numbers are 0 - 4. Examples: Address: Description: 0N:10 RM, file 0, word 10, bit 0 N7:12/1 RM, file 7, word 12, bit 1 4N20:30/14 LP 4, file 20, word 30, bit 14 PD - PID Loop The PID file permits subelement mnemonics and bit mnemonics. Please refer to the PLC-5 PID file for a list of all valid mnemonics. The valid module numbers are 0 - 4. Examples: Address: 0PD11:1.SP 1PD16:2.DB 3PD15:5/PE 3PD70:1/EN

Description: RM, file 11, PID 1, setpoint LP 1, file 16, PID 2, dead band LP 3, file 15, PID 5, equation bit LP 3, file 70, PID 1, enable

R - Control The control file permits both subelement mnemonics and bit mnemonics. Valid module numbers are 0 - 4. Bits: Number: 15

Axisware LLC

Mnemonic: EN

Description: Enabled

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink 14 13 12 11 10 9 8

61

EU DN EM ER UL IN FD

Enable unload Done Empty Error Unload Inhibit Comparison Found

Subelements: Number: 1 2

Mnemonic: LEN POS

Description: Length Position

Examples: Address: 0R:1.LEN 1R20:2.POS 1R6:5/UL 2R6:6/14

Description: RM, file 0, control 1, length value LP 1, file 20, control 2, position value LP 1, file 6, control 5, unload bit LP 2, file 6, control 6, error bit

ST - String The string file permits subelement mnemonics. The valid module numbers are 0 - 4. Subelements: Number: 0 1

Mnemonic: LEN DATA

Examples: Address: 0ST22:1.LEN 1ST22:2.DATA,5

Description: Length. Specifies an even number of bytes. Actual string data

Description: RM, file 22, string 1, length value LP 1, file 22, string 2, string data, length 5

T - Timer The timer file permits both subelement mnemonics and bit mnemonics. Valid module numbers are 0 - 4. Please note that the preset and accumulator are both 32 bit values; therefore, they must be read with data type INT4. Bits:

Axisware LLC

Number: 31 30 29

Mnemonic: EN TT DN

Description: Enabled Timing Done

Subelements: Number: 2 4

Mnemonic: PRE ACC

Description: Preset value Accumulated value

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

Examples: Address: 0T:1.PRE 1T20:2.ACC 2T4;5/DN 4T4:6/31

Axisware LLC

62

Description: RM, file 0, timer 1, preset value LP 1, file 20, timer 2, accumulated value LP 2, file 4, timer 5, done bit LP 4, file 4, timer 6, enabled bit

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

63

3.13 Appendix M: SLC-5/04 Addressing 3.13.1 I/O Data Tables (SLC-5/04) The addressing used by the Driver is detailed below. The standard format is as follows: filetype:I/Oslotnumber[.wordnumber][/bit] where filetype

Note:

=

Either I for input or O for output

I/Oslotnumber =

I/O Slot Number in DECIMAL (0-30)

wordnumber

=

Word number in DECIMAL (optional) If the word number is omitted, a zero (0) is assumed. The valid range for the word number is 0 - 1. Only required for bits above bit number 15 with 24 and 32 bit I/O Devices. To access bits above 15 specify wordnumber of 1, and subtract 16 from the desired bit number

bit

=

Bit number in DECIMAL (optional) specified after slash (slash must be included if bit number is specified). The valid range is: 0 - 7 (8 bit I/O) 0 - 15 (16, 24, 32 bit I/0) If the bit number is omitted, a zero (0) is assumed.

The filetype and I/Oslotnumber may be separated by either a colon(:) or a semicolon(;).

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

64

3.13.2 All Other Data Tables (SLC-5/04) The addressing used by the Driver is detailed below. The standard format is as follows: filetype[filenumber]:[element][.subelement] [/bit] [,length] where filetype

=

One of the following (required) A, B, C, F, N, R, or T.

filenumber

=

File number in DECIMAL (optional) If the file number is omitted, the default for that file type is assumed (i.e. T: = T4:). = Element number in DECIMAL (optional) Valid ranges are as configured in PLC. If element is not specified, a zero (0) is assumed.

element

(Of the following you may use one or none:)

Note:

subelement

=

Subelement number specified in DECIMAL or mnemonic (optional). Subelements are only valid for the file types where they are specifically mentioned below.

bit

=

Bit number in DECIMAL (optional) specified after slash (slash must be included if bit number is specified). Valid bit numbers are 0 - 15. Some file types, as described below, permit the use of bit mnemonics. If the bit number is omitted, a zero (0) is assumed.

length

=

Number of words to be read into message tag. This is always preceded by a comma.

The filenumber and element may be separated by either a colon(:) or a semicolon(;).

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

65

A - ASCII The ASCII file uses no subelements or mnemonics. Please note that no default file number exists for an ASCII file. Examples: Address: A10:10 A10:10,20 A20:30/14

Description: File 10, word 10, bit 0 File 10, word 10, length 20 (40 bytes) File 20, word 30, bit 14

B - Bit (Binary) Each binary element consists of one word. You can address a binary element in its entirety or you can address any particular data bit of an element individually. Examples: Address: B/17 B3/17 B13:1/2

Description: File 3, word 1, bit 1 As above File 13, word 1, bit 2

C - Counters Each counters structure consists of three words. The counters file permits both subelement mnemonics and bit mnemonics. Bits: Number: 15 14 13 12 11

Mnemonic: CU CD DN OV UN

Description: Count up Count down Done Overflow Underflow

Subelements: Number: 1 2

Mnemonic: PRE ACC

Description: Preset Value Accumulated Value

Examples: Description: Address: C:1.PRE File 5, counter 1, preset value C20:2.ACC File 20, counter 2, accumulated value C5:5/DN File 5, counter 5, done bit C5:6/12 File 5, counter 6, overflow bit

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

66

F - Floating Point Each floating point element consists of two words. The floating point file uses no subelements or no mnemonics. Examples: Address: F:10 F8:10

Description: File 8, element 10, bit 0 As above

N - Integer The integer file uses no subelements or mnemonics. Examples: Address: N:10 N7:10 N20:30/14

Description: File 7, word 10, bit 0 As above File 20, word 30, bit 14

R - Control Each control block consists of three words. The control file permits both subelement mnemonics and bit mnemonics. Bits: Number: 15 14 13 12 11 10 9 8

Mnemonic: EN EU DN EM ER UL IN FD

Description: Enabled Unloading Enabled Done Empty Error Unload Inhibit Comparisons Found

Subelements: Number: 1 2

Mnemonic: LEN POS

Description: Length Position

Examples: Address: R:1.LEN R20:2.POS R6:5/UL R6:6/14

Axisware LLC

Description: File 6, control 1, length value File 20, control 2, position value File 6, control 5, unload bit File 6, control 6, enable unload bit

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

67

T - Timers The timers file accommodates up to 256 timer structures. Each timer structure consists of three words. You can address a timer structure in its entirety or you can address any particular member of a structure individually. Bits: Number: 15 14 13

Mnemonic: EN TT DN

Description: Enabled Timer Timing Done

Subelements: Number: 1 2

Mnemonic: PRE ACC

Description: Preset Value Accumulated Value

Examples: Description: Address: T:1.PRE File 4, timer 1, preset value T20:2.ACC File 20, timer 2, accumulated value T4:5/DN File 4, timer 5, done bit T4:6/15 File 4, timer 6, enabled bit

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

68

3.14 Appendix N: Unsolicited Reads

3.14.1 PLC-2 Unsolicited Messages The PLC-2 should be programmed to send a PLC-2 Unprotected Write message directed toward FactoryLink. The destination node should be the Data Highway address selected for the FactoryLink computer in the Logical Station Control Table. The Logical Station used in the Read/Write Information Table which has been configured for unsolicited messages should be defined as a PLC-2 in the Logical Station Information Table.

3.14.2 PLC-3 Unsolicited Messages The PLC-3 may be programmed to send either PLC-2 Unprotected Write or PLC-3 Word Range Write messages directed toward FactoryLink. The destination node should be the Data Highway address selected for the FactoryLink computer in the Logical Station Control Table. The Logical Station used in the Read/Write Information Table which has been configured for unsolicited messages should be defined as a PLC-2 if PLC-2 Unprotected Writes are used, or a PLC-3 if PLC-3 Word Range Writes are used. A single Physical Station may have multiple Logical Stations defined in one application.

3.14.3 PLC-5 Unsolicited Messages The PLC-5 may be programmed to send either PLC-2 Unprotected Write or PLC-5 Typed Write messages directed toward FactoryLink. The destination node should be the Data Highway address selected for the FactoryLink computer in the Logical Station Control Table. The Logical Station used in the Read/Write Information Table which has been configured for unsolicited messages should be defined as a PLC-2 if PLC-2 Unprotected Writes are used, or a PLC-5 if PLC-5 Typed Writes are used. A single Physical Station may have multiple Logical Stations defined in one application.

3.14.4 PLC-5/250 Unsolicited Messages The PLC-5/250 should be programmed to send a PLC-2 Unprotected Write message directed toward FactoryLink. The destination node should be the Data Highway address selected for the FactoryLink computer in the Logical Station Control Table. The Logical Station used in the Read/Write Information Table which has been configured for unsolicited messages should be defined as a PLC-2 in the Logical Station Information Table. All other communication functions for the PLC-5/250 require that the Logical Station be defined as a PLC5/250; therefore, as can be seen, at least two Logical Stations for each PLC-5/250 must be defined if unsolicited message support is desired.

3.14.5 SLC-5/04 Unsolicited Messages

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

69

The SLC-5/04 should be programmed to send a PLC-5 Typed Write message directed toward FactoryLink. The destination node should be the Data Highway address selected for the FactoryLink computer in the Logical Station Control Table. The Logical Station used in the Read/Write Information Table which has been configured for unsolicited messages should be defined as a PLC-5 in the Logical Station Information Table.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

70

3.15 Appendix O: Conversion of US Data A-B Serial Driver Configuration Tables Several steps are required to convert the FactoryLink A-B serial driver configuration tables to the Axisware A-B DH+ tables. There are four different configuration tables associated with the A-B serial port EDI driver. The Read/Write Control and Read/Write Information tables use a database format identical to the corresponding tables for the AB Serial Port EDI driver. This means that several options are available to transfer information from one set of tables to the other. The four relating files may be copied from the command line in the following manner (for AB Serial to A-B DH+). copy ab___ovr.cdb sdkt_ovr.cdb copy ab___ovr.cdx sdkt_ovr.cdx copy ab___hdr.cdb sdkt_hdr.cdb copy ab___hdr.cdx sdkt_hdr.cdx The remaining A-B files (ab__sovr.* and ab__shdr.*) should be deleted. The External Device Interface table should be modified to match the description in this manual. The method works and is very simple; however, the Configuration Manager can potentially lose track of what tags are used in what tables by what tasks. Therefore, a multiplatform save and restore must be performed before the application can be used. The Station Information and Station Control tables may not be transferred but must be entered normally according to the manual.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

71

3.16 Appendix P: FactoryLink Upgrade Procedures

BEFORE installing the FactoryLink upgrade you MUST make a multiplatform save of your application. Do these steps before restoring the multiplatform save file of your application: Where $FLINK indicates the FactoryLink directory (example: FLINK=C:\FLOS2): 1. Edit the file $FLINK\AC\TITLES and add the following line: sdkt.ac EDI Axisware SD/KT Driver 2. Open the file $FLINK\CTGEN\CTLIST and add the following line: sdkt: sdktshdr sdktsovr sdkt_hdr sdkt_ovr 3. Open the file $FLINK\BIN\FLRUN.CMD and add the following line at the beginning of the file, immediately after the two lines: "@echo off" and "setlocal". (The example below configures a 5136-SD ISA card to an I/O port address of 250 (hex) and a memory address of D800). $FLINK\edi\sdktos2\sdload $FLINK\edi\sdktos2\[progname] p=250 m=D800 Please refer to Appendix B for further information on the entries that need to be made to the FLRUN.CMD file. Appendix Q: Sample Application

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

72

3.17 Appendix Q: Sample Application

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

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

73

3.18 Appendix R: Environment String Parser

The Environment string parser is designed to allow multiple computers running the same FactoryLink application to use different settings in the Logical Station Control Table. This will allow, for example, two FactoryLink stations to run the same FactoryLink application on a Data Highway with different Data Highway addresses. The parser works by reading the environment string NVLSCnnn (where nnn is the logical port number) and assigning the values in the string to the corresponding values in the Logical Station Control Table. NOTE : The logical station number must fill all three available digits by padding with 0; e.g., NVLSC002 for logical port 2. If the environment string is not found then the values that were entered in the Logical Station Control table are used. The format for the string is as follows. NVLSCnnn=TIMEOUT;CARD MEMORY ADDRESS;DATA HIGHWAY ADDRESS; Where TIMEOUT is the Number of seconds in tenths permitted by the driver to process a request, CARD MEMORY ADDRESS is Address (in HEX) for memory shared by S-S Technologies card and the FactoryLink CPU and DATA HIGHWAY ADDRESS is the card's unique data highway address (the OCTAL data highway address for the FactoryLink station) Any of the values may be set to the value in the Logical Station Control Table by simple entering no value for that position in the environment string. For example : set NVLSC001=30;;10; Where the logical port is 1, the timeout is set to 30 (3 seconds), the card memory address is read from the Logical Station Control table and the Data Highway address for the card is 10 (OCTAL).

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

74

4 Glossary Configuration Tables Where you establish the communication path and specify elements in the database. These tables work together to allow FactoryLink to exchange information from the tag database with the device. Data Region Area of device (e.g., PLC) memory to be accessed. Also called "Data Table" or "Reference Table". External Device Definition Table Configuration table that tells the application what type of devices are connected to the computer's ports and assigns them a logical port number. Logical Port Number specified in the External Device Definition table which represents a particular communication path. Logical Station Number entered by the user to represent a particular combination of a logical port and a physical device (PLC). Correlates specific addresses and tags with a physical device (PLC). Logical Station Control Table Table used to configure each logical port and its associated stations in the Logical Station Information table. The Logical Station Control table specifies which specific port is connected to the external device being defined. Logical Station Information Table Table which defines the logical station(s) accessible through a specific logical port defined in the Logical Station Control table. Each logical station is tied to its physical station address and device type. Proof of License An 8 1/2 by 11 certificate that must accompany the software indicated by its unique serial number when that product is sold or transferred to another company or entity. Read/Write Control Table Table used to configure each logical port and its associated stations in the Logical Station Information table. Each line in this table refers to one Read/Write Information table. Read/Write Information Table Configuration table that links FactoryLink tags to specific addresses in the PLC represented by the Logical Station.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

75

SoftKey Axisware software protection system where no hardware key (dongle) is required. Validate The program run after the software is installed that checks for improper use of the product and enables the software to function past the grace period.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

76

5 Supplement for SST 5136-SD-PCI Cards The SDKT product has been modified to support SST 5136-SD-PCI cards. If you are not using the SST 5136SD-PCI card please ignore this supplement. These cards are supported using SST’s low-level drivers. In order to interface with the SST drivers an additional FactoryLink configuration table has been added for the information required.

5.0.1 Installing the SST Card and drivers Please refer to SST documentation and support for information on installing and setting up the SST 5136-SDPCI card and drivers. We suggest that you verify functionality using supplied SST programs before proceeding with the SD-KT product configuration. Once the card and drivers are installed start the SST program: SD Card Manager. Verify the card is configured similar to the screen sample below:

Make note of the SST SD Card Name in the top left corner of the dialog and the Module field: PCI_SDKT and Data Highway Plus in this example.

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

77

5.0.2 SST PCI Configuration Control Table The SST PCI Configuration Control Table is a new FactoryLink configuration table added to support the SST 5136-SD-PCI card. If you are not using the SST 5136-SD-PCI-card leave this table blank. Create one entry in this table for each SST 5136-SD-PCI card being used in the application.

5.0.3 Logical Port This number must match the Logical Port number in the rest of the SDKT FactoryLink application for the specific card referenced in this row. Valid entries: 0 - 999

5.0.4 Card Name Name of the SST 5136-SD-PCI card referenced this row. This text field must match exactly the SD Card Name field in the top left corner of the SST SD Card Manager dialog. Valid entries: Text field

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

78

5.0.5 SST Module ID This entry must correspond to the “Module” section of the SST SD Card Manager dialog. This product supports SST Data Highway Plus modules with baud rate of 56KB, 115 KB, or 230 KB. Valid entries: DHP_56 DHP_115 DHP_230

Axisware LLC

[email protected]

www.axisware.com

Axisware SDKT Driver for FactoryLink

79

6 Contact information Axisware LLC [email protected] http://www.axisware.com 3213 Peppertree Pl. Plano, TX 75074, USA T: 1-(214)-764-1876 F: 1-(214)-764-1878

Axisware LLC

[email protected]

www.axisware.com