Beruflich Dokumente
Kultur Dokumente
for FactoryLink
Contents
1 Overview......................................................................................................1
1.1 Software License.....................................................................................................1
1.2 Introduction.............................................................................................................1
1.3 Historical Note........................................................................................................1
1.4 SY/LINK Card Installation.....................................................................................1
1.5 Software Installation...............................................................................................1
3 Appendices................................................................................................15
3.1 Appendix A: Installation of SY/LINK Card........................................................15
3.1.1 Sy/Link Segment Memory Addresses:..................................................15
3.1.2 Cable Connections................................................................................15
3.1.3 Network Configuration and Addressing...............................................15
3.2 Appendix B: Software Installation - OS/2...........................................................18
3.2.1 Before Starting Installation (OS/2 version)..........................................18
3.2.2 Driver Installation Instructions (OS/2).................................................19
3.2.3 Modifying the CONFIG.SYS File (OS/2)............................................20
3.2.4Softkey Protection Validation................................................................21
3.3 Appendix C: (Reserved).......................................................................................22
3.4 Appendix D: Software Installation - Windows 95/NT........................................23
3.4.1 Before Starting Installation - (Windows 95/NT version).....................23
3.4.2 Driver Installation Instructions (Windows 95/NT)...............................23
3.4.3 Softkey Protection Validation...............................................................25
3.5 Appendix E: (Reserved).......................................................................................26
3.6 Appendix F: Driver Status Codes........................................................................27
3.6.1 Application startup errors.....................................................................27
3.6.2 Run-time startup errors.........................................................................29
3.6.3 SoftKey protection messages................................................................29
3.6.4 Run-time errors.....................................................................................30
3.6.5 Unsolicited message processing errors.................................................30
3.7 Appendix G: Tables for Network and Alarm Errors...........................................33
3.7.1Network Error Table..............................................................................33
3.7.2Alarm Error Table..................................................................................35
3.8 Appendix H: Data Types and Conversions..........................................................36
3.9 Appendix I: SY/LINK Addressing.......................................................................39
3.9.1Data Tables............................................................................................39
3.9.2 Device Types.........................................................................................40
3.10 Appendix J: Unsolicited Reads..........................................................................41
3.10.1Unsolicited Alarms..............................................................................42
3.10.2Unsolicited Data...................................................................................43
3.11 Appendix K: FactoryLink Version Upgrade Procedures...................................44
3.12 Appendix L: Sample Application......................................................................45
4 Glossary of Terms.....................................................................................46
5 Contact information..................................................................................48
This document is based on information available at the time of its publication. While efforts have been made
to be accurate, the information contained herein does not purport to cover all details or variations in hardware
or software, nor to provide for every possible contingency in connection with installation, operation, or
maintenance. Features may be described herein which are not present in all hardware and software systems.
Axisware assumes no obligation of notice to holders of this document with respect to changes subsequently
made.
Axisware makes no representation or warranty, expressed, implied, or statutory with respect to, and assumes
no responsibility for the accuracy, completeness, sufficiency, or usefulness of the information contained
herein. No warranties of merchantability or fitness for purpose shall apply.
All trademarks are the property of their respectve owners. All trademarks acknowledged.
1 Overview
This product uses a SoftKey protection method. Please consult the SoftKey manual for a discussion of the
procedures to validate the SoftKey for this product.
1.2 Introduction
This manual describes the installation and configuration of the Square D SY/LINK communication driver for
FactoryLink . The installation of the SY/LINK card is also briefly described.
The driver currently supports all standard SY/NET devices. Unsolicited messages, faults, alerts, and warnings
are supported from all SY/MAX PLCs. Register status and force information may also be read from SY/MAX
PLCs.
In this document are appendices describing the software installation for this product on specific platforms. Please
read the appropriate appendix before installing this product.
Platform Appendix
OS/2 B
Windows 95/NT D
When the driver software installation is completed, please refer to the SoftKey Manual for the instructions on
running the Validate program. Failure to run Validate by the end of the 15-day grace period will result in a non-
functioning driver.
After this communications driver has been installed, updating to a newer version of FactoryLink may appear to
cause operational problems. Please refer to Appendix K before updating FactoryLink.
Access this table by selecting External Device Definition from the Configuration Manager main menu. This is
one of the five configuration tables that must be configured The other tables are accessed by selecting Axisware
SY/LINK 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 or five fields depending on FactoryLink version. Here we describe only the
applicable fields, you shuld ignore any fields not described here. Use the Tab key to move among the fields.
Number assigned by the user to indicate a particular communication path. This number must be unique
for each EDI driver used in the application.
The four-character device name for the EDI driver that will use the related Logical Port.
2.1.3 Function
Type of communication used by the EDI driver for the related Logical Port. This field refers to the
different types of EDI communication modes.
2.1.4 Memory
The amount of memory in K-bytes used for the block storage size of the read and write information
entered by the user. This entry refers only to the memory used by the driver for data storage for the
related Logical Port.
2.1.5 Comment
(Optional) Description for the current Logical Port. Used only for application documentation.
After these fields have been configured, select "Next" or Ctrl-N to edit the Read/Write Information Table
corresponding to the Control table selected by the cursor.
Allows you to select whether or not the current table will be considered in the processing of an
unsolicited message received from the PLC. Standard addressing is used to correlate the message from
the PLC with the tags configured in the table. Please refer to Appendix N for additional information
and examples.
Option determining whether or not a specific tag in the related Read/Write Information Table is written
to the selected logical station whenever the real-time database value for that tag changes.
Yes A change of status of any element in the table generates a write of that
element's value.
No No exception processing.
Priority influencing the order in which the EDI task handles the queuing of block read requests. If two
requests are received simultaneously by EDI, the request with the highest priority (lowest number) is
processed first.
Digital tag whose value, when forced to 1 (ON), initiates a block read of the values specified in the
related Read/Write Information Table. This trigger allows the block read operation to be initiated by
some other task.
Digital tag used to determine whether or not a block read table will be processed. If the tag value is 0,
the table is permitted to function normally; however, if the value is 1, the table will not respond to the
Block Read Trigger defined above.
Digital tag whose value is force written to 1 (ON) by the EDI task whenever any block read operation for
this table is completed. If this tag is specified then when the EDI task initializes, its value is force
written to 1 (ON).
Note: Block Read Complete tags are valid only if a different table is used for each logical port.
Digital tag whose value is 0 (OFF) when a block read of the tags specified in this table is in progress and
1 (ON) otherwise. If this tag is specified then when the EDI task initializes, its value is force written to 1
(ON).
Note: Block Read State tags are valid only if a different table is used for each logical port.
Priority influencing the order in which the EDI task handles the queuing of block write and exception
write requests. If two requests are received simultaneously by EDI, the request with the highest priority
(lowest number) is processed first.
Dgital tag whose value, when forced to 1 (ON), initiates a block write of the values specified in the
related Read/Write Information Table. This trigger allows the block write operation to be initiated by
some other task.
Dgital tag used to determine whether or not a block write table will be processed. If the tag value is 0,
the table is permitted to function normally; however, if the value is 1, the table will not respond to the
Block Write Trigger defined above.
Dgital tag whose value is force written to 1 (ON) by the EDI task whenever any block write operation
for this table is completed. If this tag is specified then, when the EDI task initializes, its value is force
written to 1 (ON).
Note: Block Write Complete tags are valid only if a different table is used for each logical port.
Dgital tag whose value is 0 (OFF) when a block write of the tags specified in this table is in progress and
1 (ON) otherwise. If this tag is specified then, when the EDI task initializes, its value is force written to
1 (ON).
Note: Block Write State tags are valid only if a different table is used for each logical port.
These tables are sometimes referred to as overlay panels, or ovr panels. Each table has one entry (line) for it
in the Read/Write Control Table.
Note: Please verify that the table name displayed at the bottom of the panel correctly shows the table to be
modified.
After these fields have been completed, select "Next" or Ctrl-N to edit the Logical Station Control Table.
Name of the FactoryLink tag to be updated as a result of the read operation or the tag from which
information is taken to be written to the device.
Number from the Logical Station Table identifying the particular combination of physical attributes that
will define and govern the data transfer to and from the real-time tag.
Mnemonic defining the area of device memory to be accessed, or the manner in which the device is to be
addresse
Numeric portion of device address. Specifies word offset or address of data to be accessed.
If a digital tag is used, this field is one based and is used to specify the bit offset in the selected word. If a
message tag is used, the field specifies the number of bytes that are to be transferred between the
message tag and the Logical Station. Please see Appendix I for additional information concerning the
use of bit numbers to access the status bits for a PLC register.
Data type for information being read/written from/to the Logical Station.
Priority of read or write operation. If an operation is given priority status, the operation will preempt
other normal priority operations on the network.. Care should be taken when using priority messages,
because the overall performance of the network can be adversely affected if too many priority messages
are used.
After completing these fields, select "Next" or Ctrl-N to edit the Logical Station Information Table
corresponding to the table selected by the cursor.
Number specified in the External Device Definition Table which represents a particular communications
path.
This number must also be referenced in the External Device Definition panel.
Address for memory shared by the SY/LINK card and the FactoryLink CPU. This number must match
the address selected by the dip switches on the card.
Valid entries: Hex memory address as selected by key file (D0000 recommended)
CA000, CB000, CC000, CD000, CE000, CF000, D0000,
D1000, D2000, D3000
Network address for the FactoryLink computer. Must be unique on the network.
Three possible choices for the maximum network size are available, 30, 31, and 100. The default is 30.
All devices on the network must be configured for the same size (number of drops). If less than 30
devices will be used, a significant speed increase can be attained by configuring for only 30 devices.
However, some configurations will require that the maximum size of 100 be used.
The baudrate determines the speed with which data will be transmitted over the network. All devices on
the network must be configured for the same baudrate. Before selecting a baudrate, please note the
guidelines and restrictions indicated in section 4.0 Network Configuration and Connections in the
SY/LINK manual by Square D Company.
This field is used to select the operating mode for the RS-422 port on the SY/LINK card.
The baudrate determines the speed data will be transmitted over the RS-422 line. The device connected
to the 422 line must be configured for the same baudrate.
Valid entry: 110, 300, 600, 1200, 2400, 4800, 9600 and 19200
The parity selects how the parity bit is used on the RS-422 port. The device connected to the 422 line
must be configured for the same parity.
This field is used to select the number of data bits used on the RS-422 port. The device connected to the
422 line must be configured for the same number of data bits.
Valid entry: NO
Valid entry: 1
Unsolicited messages received from other PLCs are written directly into register memory on the
SY/LINK card. The driver does not have the capability of determining which device sent the data or how
many words of data were sent. This field allows the user to specify the number of words the driver is to
assume are received with each unsolicited message.
(Optional) Message tag to which a text string will be written if an error is encountered in the processing
of an EDI request.
Note: Please verify that the table name displayed at the bottom of the panel is showing the table to be
modified.
After these fields have been completed, "Exit" or F3 will allow you to return to the Configuration Manager
main menu.
(Optional) Analog tag to which all error codes for this logical station are to be written.
Number entered by user to represent a particular combination of a logical port and physical device. This
number is referenced in the Read/Write Information Table to correlate specific addresses and tags with a
physical device. Please note that this number must be unique for each device name (SYLK).
Type of device on the SY/NET network with which communications are to be established.
The number of drop addresses from the seven following fields to be considered as valid. The specified
number of valid addresses will be copied to the routing portion of the SY/LINK card for each transaction
involving the selected Logical Station. Please see page 38 of the SY/LINK manual and Appendix I of
this manual for additional information concerning routing.
These seven fields specify the actual route values that will be used to access a device on the network.
Only the number of fields specified above will be actually used. Please see page 38 of the SY/LINK
manual for additional information regarding routing.
2.5.6 Comment
(Optional) Description for the current Logical Station. Used only for application documentation.
3 Appendices
The SY/LINK card must be installed in the computer in an open, full length slot. However, Prior to installing the
SY/LINK card, the appropriate memory segment address must be properly set by the dip switches.
The memory segment address is selected by the dip switches on the SY/LINK card. The four dip switches are set
in accordance with pages 14 and 15 of the SY/LINK manual. The following chart illustrates the proper switch
settings for all valid addresses. A segment memory address of D0000 (hex) is recommended.
The following scenarios show different configurations for connecting the SY/LINK card to PLCs. Note that
the first actual routing level is automatically handled by the driver so only the remaining levels are entered in
the Logical Station Information Table. All addresses used are for example purposes only.
Going out through 422 port and going straight to the PLC:
Going out through 422 port and through the NIM to the PLC:
SY/LINK Card
Network Address = 5
Going out through 422 port and through two NIMs to a PLC:
SY/LINK Card
Network Address = 5
SY/LINK Card
Network Address = 05
If the driver software is an update from an older version of the Axisware driver, the following procedures must
be followed for the software to be properly installed. First, the operator must exit from both the Run Manager
and the Configuration Manager. Second, a multiplatform save file should be created. Third, the driver should be
installed as described below. Fourth, restore the multiplatform save file created in step 2. Fifth, update the
Configuration Manager tables for the 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.)
If you have a backup file named $FLINK\AC\TITLES.NVA (possibly created by a previous install), the
program will warn you during the install that it is about to be overwritten and will ask you if you want to exit,
and manually save the .NVA file.
The second file to be modified is $FLINK\CTGEN\CTLIST. This file is used by the CTGEN utility in the
creation of the binary CT (configuration table) files used at run-time by FactoryLink. The following line will
be added to the CTLIST file.
If you have a backup file named $FLINK\CTGEN\CTLIST.NVA (possibly created by a previous install), the
program will ask you during the install if you wish to exit, and manually save a copy of this .NVA file before
it is overwritten
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 install program checks for a backup file named $FLINK\AC\TITLES.NVA. If found, the following
message is displayed:
The install program will then go through the same procedure before updating the file
$FLINK\CTGEN\CTLIST. The install program checks for a backup file named
$FLINK\CTGEN\CTLIST.NVA. If found, this message appears:
The messages
will be displayed while the backup (.NVA) versions are being created and the $FLINK\AC\TITLES and
$FLINK\CTGEN\CTLIST files are updated.
the lines to be added to these files can be typed in manually using a text editor. Refer to the section “Before
Starting” (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:
.....NOVA Installation Program Completed.
This portion of the manual should only be consulted after the general installation has been completed. The device
driver NOVAMEM.SYS must be loaded into memory when your system boots for the FactoryLink SY/LINK
driver to function properly. After the Axisware installation diskette'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".
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 NOVAMEM.SYS is automatically created when the software is installed from the
Axisware installation diskette. Assuming that $FLINK is set to c:\flos2, the line to be added to the CONFIG.SYS
would be:
DEVICE=C:\FLOS2\EDI\SYLK\NOVAMEM.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.
Please refer to the SoftKey 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.
If the driver software is an update from an older version of the Axisware driver, the following procedures must
be followed for the software to be properly installed. First, the operator must exit from both the Run Manager
and the Configuration Manager. Second, a multiplatform save file should be created. Third, the driver should be
installed as described below. Fourth, restore the multiplatform save file created in step 2. Fifth, update the
Configuration Manager tables for the 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:\FLNT.
If $FLINK has not been defined when the install is started, you will be requested to exit and assign a value
to $FLINK, and then restart the install program. $FLINK can be assigned a parameter by using the SET
command (example: set flink=d:\flnt). Be sure to include the drive letter.
During the installation, two ASCII text files will be modified by the installation program. The original copies
of both files will be copied to a file with the same filename but a .NVA extension. The first file to be modified
is $FLINK\AC\TITLES (where $FLINK is the FactoryLink directory). This file is used by the Configuration
Manager to determine which tasks to list and also the order in which they are to be listed. The following line
will be added to the TITLES file. (The line may be different, depending on your FactoryLink version.)
If you have a backup file named $FLINK\AC\TITLES.NVA (possibly created by a previous install), the
program will warn you during the install that it is about to be overwritten and will ask you if you want to exit,
and manually save the .NVA file.
The second file to be modified is $FLINK\CTGEN\CTLIST. This file is used by the CTGEN utility in the
creation of the binary CT (configuration table) files used at run-time by FactoryLink. The following line will
be added to the CTLIST file.
If you have a backup file named $FLINK\CTGEN\CTLIST.NVA (possibly created by a previous install), the
program will ask you during the install if you wish to exit, and manually save a copy of this .NVA file before
it is overwritten.
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. After making the drive
containing the diskette the current working drive, type INSTALL and then press Enter. (Do not use File…
Run…from Windows NT's Program Manager or File Manager.)
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
required by your platform to specify the location of the FactoryLink program files (example: set
FLINK=f:\flnt), 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 the 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 install program checks for a backup file named $FLINK\AC\TITLES.NVA. If found, the following
message is displayed:
The install program will then go through the same procedure before updating the file
$FLINK\CTGEN\CTLIST. The install program checks for a backup file named
$FLINK\CTGEN\CTLIST.NVA. If found, this message appears:
The messages
will be displayed while the backup (.NVA) versions are being created and the $FLINK\AC\TITLES and
$FLINK\CTGEN\CTLIST files are updated.
the lines to be added to these files can be typed in manually using a text editor. Refer to the section “Before
Starting” (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:
Be sure to restart your computer to ensure that the proper changes have been made.
Please refer to the SoftKey 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.
The following error codes (alphabetized) may be reported to FactoryLink while the SY/LINK Driver tables are
being processed at startup. These messages will appear within the Run-Time Manager window during the startup
of the application. Messages that scroll off the screen may be redirected to an output file by opening an OS/2 or
DOS window and, at the prompt, typing edistart -r -v > edi.out followed by the Enter (Return) key. When the
process has completed, edit the file edi.out to view the error codes generated by FactoryLink
Data anomaly
Indicates that addresses and data types specify overlapping elements.
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.
No tag given
The indicated line of the Read/Write Information Table currently being processed does not
contain a valid FactoryLink tag name.
Ordering anomaly
Indicates that the Read/Write Information Table currently being processed contains addresses
such that the driver is unable to properly arrange all the entries.
Out of Memory
The driver was unable to internally allocate all the necessary memory. Allocate more memory
in the External Device Definition Table.
The maximum word address for all alarm data tables is 16. Consult Appendix J for a more complete
discussion of alarms (Faults, Alerts, and Warnings)
The following errors may be reported when the EDI task is started after all tables have been processed. All the
following errors are immediately fatal. Check separately enclosed manual for all errors reported
concerning the security key.
The following errors may be reported when the EDI task is started after all tables have been processed. All the
following errors are immediately fatal. Check separately enclosed manual for all errors reported concerning
the security key.
Messages relating to SoftKey protection may appear after the driver has been initialized by the EDI task.
Please refer to the SoftKey manual if they appear. If SoftKey does not detect a problem the following
message will be displayed.
The following errors may be reported while the driver is processing the EDI requests. The text represents the
error message returned to the message tag defined in the Logical Station Control Table. The number in
parentheses is returned to the analog tag defined in the Logical Station Information Table. While the following
errors are not immediately fatal, recurring errors should be evaluated and eradicated to maintain the integrity of
the network.
The following errors may be reported while the driver is attempting to process unsolicited message requests. The
text represents the error message returned to the message tag defined in the Logical Station Control Table. While
the following errors are not immediately fatal, recurring errors should be evaluated and eradicated to maintain the
integrity of the network
Unsolicited messages must be read from the card after they are received. After having
received a message, the request to the card for the message was refused. Increase the timeout
permitted in the Logical Station Control Table. Contact Axisware if the error persists.
User programs should be designed to check for error codes in these locations and to either alert the operator or
perform other appropriate actions.
Code Description
001 Illegal protocol opcode
002 Illegal intermediate code
003 Illegal address attempted
004 Illegal rack address attempted
005 Instruction attempted which is not allowed
006 Item being searched for cannot be found
007 Attempt to alter data in a protected register
008 Attempt to alter data in protected memory
009 Attempt to alter data in a read-only register
010 Attempt to exceed memory limitations
011 Communications overflow
012 Illegal CPU rack addressing
013 Communications error
014 The operation attempted is not allowed in run
015 Communication overflow
016 Register count too large for the processor
017 Remote device inactive
018 The rung number used is not allowed
019 Illegal read parameter
020 Illegal channel number
021 Trying to change a forced bit
022 Forcing function is inhibited
023 Attempt to alter data in a forced register
024 Attempt to force a non-forcible register
025 CPU error, check register 8175
026 Rack addressing and user memory overlap
027 Memory error - clear all operation required
028 Illegal baud rate selected
029 Attempt to send message with illegal route
030 Attempt to alter protected memory - inhibit coil
031 End of file encountered
032 Operation not allowed in protected memory
033 Data error
034 UVPROM memory error
035 Write protected
036 Replace not allowed - use delete and insert
037 Attempt to skip or read a file past last file
038 Data view protected - cannot read
039 Alarm already set
Code Description
001 Invalid opcode
002 Invalid fault count
003 Invalid alert count
004 Invalid warning count
005 Invalid fault acknowledgment register
006 Invalid alert acknowledgment register
007 Invalid warning acknowledgment register
DIGITAL
ANALOG
LONG ANALOG
FLOATING POINT
MESSAGE
DIGITAL
BIN
DIGITAL tags may only be converted to and from the BIN data type. If the requested binary PLC data
type is on, the DIGITAL tag will be set to one. If the binary element is off, the DIGITAL tag will be set
to zero.
ANALOG
INT2
The ANALOG tag is a 16 bit signed integer; therefore, no conversion is needed.
INT4
The lowest 16 bits of the INT4 data type correspond directly with the 16 bits comprising the ANALOG
tag.
BCD4
After being read from the PLC, the BCD4 value is converted into a 16 bit integer. The value is then
directly transferred without conversion into the ANALOG tag.
BCD8
After being read from the PLC, the BCD8 value is converted into a 32 bit integer. The value is then
handled as the INT4 data type above.
FLT4
The whole number portion of the floating point number is transferred to the ANALOG tag. This
conversion is accurate only if the whole number value is between -32767 and +32767. When converting
back to a FLT4, a fractional portion of zero is assumed.
FLT8
The whole number portion of the floating point number is transferred to the ANALOG tag. This
conversion is accurate only if the whole number value is between -32767 and +32767. When converting
back to a FLT8, a 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
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.
BCD8
After being read from the PLC, the BCD8 value is converted into a 32 bit integer. The value is then
handled as the INT4 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
-4.3e09 and +4.3e09. When converting back to a FLT4, a fractional portion of zero is assumed.
FLT8
The whole number portion of the floating point number is transferred to the LONG ANALOG tag. This
conversion is accurate only if the whole number value is between
-4.3e09 and +4.3e09. When converting back to a FLT8, a 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.
BCD8
After being read from the PLC, the BCD8 value is converted into a 32 bit integer. The value is then
handled as the INT4 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
The data is transferred directly; no conversion is necessary.
MESSAGE
ASC
All data is read directly into the message tag from the specified device address. No conversion of any
kind is employed.
3.9.1Data Tables
REGISTER
The register data table is the primary area of device memory that is accessed by the driver. SY/MAX
devices consist of a maximum of 32767 words of addressable memory. Not all devices use all this
memory; therefore, it is the responsibility of the operator to ensure that the memory map entered in the
Configuration Manager is valid. The register memory is divided into 4 equal areas: general purpose
registers (1 - 8192), status registers (8193 - 16384), force enable registers (16385 - 24576), and force
status registers (24577 - 32767). Write and unsolicited read operations are only to be directed toward the
general purpose registers; all other areas are read only.
Example:
Data Table: Offset: Bit Description:
REGISTER 100 0 General purpose register 100
REGISTER 101 0 General purpose register 101
REGISTER 8193 0 Status for register 1
REGISTER 24577 0 Force status for register 1
REGISTER 102 4 General purpose register 102 bit 4
In addition to the above word operations, the status bits for a register may also be addressed as follows:
Example:
Data Table: Offset: Bit: Description:
REGISTER 100 17 Bit 1 of status for register 100
REGISTER 101 32 Bit 16 of status for register 101
STATUS
The status data table contains status information for each of the general purpose registers. This data table
only supports read operations. Write and unsolicited read operations are not allowed. The range of
addressable offsets is 1 - 8192.
Example:
Data Table: Offset: Description:
STATUS 100 Status for general purpose register 100
STATUS 101 Status for general purpose register 101
STATUS 424 Status for general purpose register 424
STATUS 1000 Status for general purpose register 1000
FRC_ENBL
The force enable table contains forcing information for each of the general purpose registers. If a bit in
the force enable table is on (a one), that bit is either forced on or off depending on the value of that bit in
the force status table. These registers are read only. Write and unsolicited read operations are not
allowed. The range of addressable offsets is 1 - 8192. The highest addressable bit is 16.
Example:
Data Table: Offset: Bit: Description:
FRC_ENBL 100 10 Force enable bit 10 of register 100
FRC_ENBL 101 12 Force enable bit 12 of register 101
FRC_STAT
The force status table contains forcing information for each of the general purpose registers. If a bit in
the force status table is on (a one), that bit is forced on if the corresponding bit in the force enable table
is also on. If a bit in the force status table is off (a zero), that bit is forced off if the corresponding bit in
the force enable table is on. These registers are read only. Write and unsolicited read operations are not
allowed. The range of addressable offsets is 1 - 8192. The highest addressable bit is 16.
Example:
Data Table: Offset: Bit: Description:
FRC_STAT 100 10 Force status bit 10 of register 100
FRC_STAT 101 12 Force status bit 12 of register 101
SCP-XXX
This is a general mnemonic for all the PLCs supported by the driver. This device type should be used for
all block reads from and all writes to network devices that are PLCs or functionally equivalent to a PLC.
The only difference between the PLC types as far as the driver is concerned is the number of words that
can be transferred for priority operations. These limitations are listed on page 59 and page 66 of the
SY/LINK manual. If a device is used that is addressed in a fashion similar to a PLC, a device type of
SCP-4XX or SCP-6XX could be used for a general form of interface. The first level of routing used
when addressing these device types is the address assigned to FactoryLink on the Logical Station
Control Table. The remaining routing levels are copied from the Logical Station Information Table;
therefore, at least one level of routing must be specified in the Logical Station Information Table.
SY/LINK
This device type is used to directly address the SY/LINK card. The card has 512 registers that can be
accessed by read or write operations just as any other PLC registers. However, any writes to these
registers (even FactoryLink) will be flagged by the SY/LINK card as an unsolicited message. If
unsolicited messages, other than alarms, are to be processed by the driver, a Logical Station must be
configured with a device type of SY/LINK. Each message received will then be evaluated based on the
records that are defined in unsolicited tables with that Logical Station. No routing levels should be
specified in the Logical Station Information Table for this device type.
GENERIC
This device type assumes a maximum priority operation size of 128 words (the maximum). The primary
difference for this device type is the way routing is handled. All routing levels are copied directly from
the Logical Station Information Table. No routing information is taken from the Logical Station Control
Table as it is for the PLC types. This allows for special routing if required by the application.
Unsolicited messages can be configured to allow a PLC to send data to the FactoryLink real-time database
without the PLC being polled by the EDI driver. This can be useful for logging PLC data that is not generated at
predefined intervals such as alarm reporting or data that changes infrequently. Two different types of unsolicited
messages can be received by FactoryLink: alarms and register data.. Several simple steps are required to
configure the system to receive either type of unsolicited message.
The first step is to set the column titled Unsolicited Read in the NOVA SY/LINK Read/Write Control Table to
either "Forced" or "Yes". This will allow that specific table to be included in the driver's search for tags with
which to associate the incoming data. The table for which unsolicited reads have been enabled may now be
edited to associate FactoryLink real-time database elements to addresses in the PLC. The same addressing rules
should be followed for unsolicited read tables as for the standard read or write tables.
Note: The number of tags that are configured as unsolicited read tags directly affects the time that is required
to process incoming requests; therefore, if speed is critical, only include the unsolicited read tags that
are essential to the application.
3.10.1Unsolicited Alarms
The following section briefly describe the steps necessary to configure FactoryLink to receive alarms transmitted
by a SCP-400.
The NOVA SY/LINK Read/Write Information Table must be completed with a data table of either FAULT,
ALERT, or WARNING. The data offset must be set to a number between 1 and 16. A data offset of 1 will return
the alarm code, while larger numbers will index further into the returned data.
Example:
Data Table Data Offset Description
ALERT 1 Alarm code from any alert from related Logical Station
WARNING 3 Third word from any warning from related Logical Station
One of the two following lines of logic must also be added to the PLC. The write command permits more
flexibility, while the alarm command is more straight forward.
WRITE COMMAND
ROUTE ROUTE STAT LOCAL REMOTE
COUNT
TWRTE2 15 10 S0300 S0100 S8201 5
STANDARD ALARM
ROUTE ROUTE STAT REMOTE CODE
TALRM2 15 10 S0300 S8201 00162
Both commands will write out of CPU port 2 to a NIM with a network address of 15. The final destination
would be a FactoryLink terminal defined as device number 10.
As a result of the first command, five words of data will be written from CPU registers starting at S0100 to the
Alert registers (S8201+) on the SY/LINK card.
As a result of the second command, an alarm code of 162 will be written from the CPU to the Alert register
(S8201) on the SY/LINK card.
3.10.2Unsolicited Data
The following section briefly describes the steps necessary to configure FactoryLink to receive data transmitted
by a SCP-400.
The NOVA SY/LINK Read/Write Information Table must be completed with a data table of REGISTER and a
data offset between 1 and 512. All other data tables are invalid for unsolicited read operations. The device type
for the associated Logical Station, configured within the NOVA SY/LINK Logical Station Information Table,
must have a device type of SY/LINK. A write from another PLC will flag the SY/LINK card that a write has
occurred and also the first register involved in the write, but information concerning the device sending the data
and the number of words transmitted is not available; therefore, the user must also configure the Logical Station
Control Table so the Unsolicited Msg Length field indicates the number of words that the driver is to assume
will be received with each unsolicited message.
Example:
Data Table: Data Offset: Description:
REGISTER 1 Register 1 of the SY/LINK memory
REGISTER 15 Register 15 of the SY/LINK memory
WRITE COMMAND
ROUTE ROUTE STAT LOCAL REMOTE
COUNT
TWRTE2 15 10 S0300 S0100 S0001 15
The command will write out of CPU port 2 to a NIM with a network address of 15. The final destination would
be a FactoryLink terminal defined as device number 10.
As a result of the command, fifteen words of data will be written from CPU registers starting at S0100 to the
SY/LINK registers starting at S0001. The FactoryLink tag associated with the first line of the example will be
set equal to S0100 of the PLC. If the Unsolicited Msg Length parameter is greater than 15, the tag associated
with the second line of the example will be set equal to S0114 of the PLC. However, if the Unsolicited Msg
Length is less than 15, the first tag will still receive a value; but the second tag will be left unchanged.
After installing this communications driver, upgrading to a newer version of FactoryLink may appear to
cause operational problems. This is due to the modifications to certain text files made by installing this
product being overwritten during the install of the new FactoryLink version. However, these files can be
reconfigured using a text editor.
After installing the FactoryLink upgrade, the following steps should be done before restoring the
multiplatform save file of your application:
3. Please refer to the appropriate appendix for your platform for further information on modifications needed
in the CONFIG.SYS or SYSTEM.INI files.
The SAMPLE directory of the install 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 the application.
The SAMPLE directory of the install 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 the application.
4 Glossary of Terms
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 database with the device.
logical port
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
Number entered by the user to represent a particular combination of a logical port and a physical device
(PLC). Correlates specific addresses and tags with a physical device (PLC).
Proof of License
An 8 1/2 by 11 certificate that must accompany the software indicated by its unique serial number when that
product is sold or transferred to another company or entity.
SoftKey
Axisware' software protection system where no hardware key (dongle) is required.
Validate
The program run after the software is installed that checks for improper use of the product and enables the
software to function past the grace period.
5 Contact information
Axisware LLC
support@axisware.com
http://www.axisware.com
T: 1-(214)-764-1876
F: 1-(214)-764-1878