SBPC-21-EN/IP FifeNet To EtherNet/IP Gateway

Transcription

1 Fife Corporation PO Box 26508, Oklahoma City, OK 73126, U.S.A. Phone: / Fax: / fife@fife.com SBPC-21-EN/IP FifeNet To EtherNet/IP Gateway Customer Instruction Manual EtherNet/IP 2000 Fife Corporation. All rights reserved.

2

3 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL COPYRIGHT All rights reserved. Any reproduction of this Instruction Manual, in any form in whole or in part requires the prior written consent of Fife Corporation. The information given in this Instruction Manual is subject to change without notice. We have compiled this Instruction Manual with the greatest possible care and attention. However, the possibility of error cannot be completely excluded. Fife Corporation accepts no legal liability for incorrect information given and the consequences arising therefrom. MS DOS is a trademark of Microsoft Corporation. All other trademarks are the property of their respective owners.

4

5 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL TABLE OF CONTENTS INTRODUCTION... 1 PRODUCER/CONSUMER MODEL...1 FIFENET...1 SBPC-21-EN/IP SWITCH/JUMPER CONFIGURATION...2 SBPC-21-EN/IP NETWORK STATUS...4 SBPC-21-EN/IP ERROR CODES...5 FEATURES...6 SBPC-21-EN/IP NETWORK CONFIGURATION...6 CONFIGURING IP ADDRESS...7 USING CONFIGURATION SWITCH...7 USING DHCP/BOOTP...7 USING A PREDEFINED CONFIGURATION...7 USING ADDRESS RESOLUTION PROTOCOL (ARP)...8 FILE SYSTEM...9 CONFIGURATION FILE ETHCFG.CFG...9 TELNET SUPPORT...10 ETHERNET/IP...11 IMPLEMENTED OBJECTS...11 ASSEMBLY OBJECT, CLASS 04H...11 I/O DATA INPUT MAPPING OBJECT, CLASS A0H...12 I/O DATA OUTPUT MAPPING OBJECT, CLASS A1H...12 FIFENET THEORY FIFENET TIME SLICES...15 MULTIPLEXED TIME SLICES...15 FIFENET MASTER...16 SBPC-21-EN/IP DATA FLOW...17 CONFIGURATIONS HARDWARE CONFIGURATION SINGLE CDP HARDWARE CONFIGURATION MULTIPLE CDP-01 S...20 SOFTWARE CONFIGURATION...20 COMMUNICATION MAPPING ETHERNET/IP TO FIFENET DATA...21 FIFENET TO ETHERNET/IP DATA...22 CONTROL INFORMATION CDP-01 CONTROL MATRIX...25 EXTERNAL LOCK...25 TRIPLE-DRIVE CDP STATUS DATA BLOCK...29

6 SPECIAL CONTROL OF FIFENET DEVICES...36 CDP-01 KEY CODE DATA PATH...36 CDP-01 KEY CODES...37 SIMULATING DUAL-KEY PRESSES...37 CDP-01 LED PANEL DATA...38 INDEX...40

7 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL 1 INTRODUCTION The Fife SBPC-21-EN/IP (Serial Bus Protocol Converter) provides a gateway between Fife s proprietary FifeNet network and an Ethernet network. The SBPC-21-EN/IP uses the standard RJ-45 connector and conforms to EtherNet/IP Level 2 I/O Server CIP Protocol. As shown in the diagram below, the SBPC-21-EN/IP connects to both FifeNet and Ethernet/IP. Figure 1-1: SBPC-21-EN/IP Network Connection The SBPC-21-EN/IP connects to both FifeNet and Ethernet providing translation between the two networks. FifeNet Customer Ethernet Ethernet Hub Producer/Consumer Model The Producer/Consumer Model allows the exchange of information between a sending device ( producer ) and many receiving devices ( consumer ) without requiring the same date to be sent multiple times to different destinations. The producer sends the data once and each consumer on the network receives the data at the same time. The data can be used (consumed) or ignored by each receiving device independently. FifeNet uses the Producer/Consumer Model. FifeNet FifeNet s deployment of the Producer/Consumer Model allows data sent by a single device to be received simultaneously by multiple devices on the same network. Each receiving device can choose to use (consume) the information or ignore it as needs dictate. FifeNet is based on a fixed time slicing architecture where transmitting devices send data in fixed, predetermined time intervals Figure Sheet A Page 1

8 SBPC-21-EN/IP Switch/Jumper Configuration Since the SBPC-21-EN/IP participates in two networks at the same time, it must have two network addresses (a FifeNet address and an Ethernet IP address). The FifeNet address is set via the FifeNet serial port that is common with many FifeNet peripherals. The Ethernet IP address is programmable by dip switches or via the Ethernet connection. See the dip switch description and IP address configuration setup shown below for more information. If the SBPC-21-EN/IP is installed as the end point in a FifeNet network, all four jumpers described below should be installed. Figure 1-2: SBPC-21-EN/IP Top View These jumpers should be installed if the SBPC-21-EN/IP is at the end of a FifeNet network. They provide network termination. The other two jumpers should always be installed as they select half-duplex FifeNet communication. Terminated Not Terminated The 7-segment LED is used to display errors or exceptions. During normal operation, the display will continuously cycle the outer segments. Ethernet IP address configuration switches. See the following page for description of these switches Figure Sheet A Page 2

9 SBPC-21-EN/IP External Connections/Indicators SBPC-21-EN/IP mounting considerations are simplified as all connections to the SBPC-21-EN/IP are on the same side of the box. Figure 1-3: SBPC-21-EN/IP Side View Connection to FifeNet is accomplished using the standard FifeNet connector. Configuration is also downloaded to the device using this connection. Device and network status LED s. These indicators provide feedback for network troubleshooting. Connection to Ethernet is accomplished using the standard RJ-45 connector. Switch ON ( ) = 1 IP Address SW1 SW2 SW3 SW4 SW5 SW6 SW7 SW8 Switch Value = 0 Switch Value = The first three values of the IP address are fixed at and the dip switch value represents the binary value of the last digit of the IP address. The subnet mask is and the default gateway is Use DHCP/BootP server if present or use the internally stored IP address. If a DHCP/BootP server is not present, the stored IP address will be used. See the section SBPC-21-EN/IP Network Configuration for details about how to store an IP address. OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF OFF ON OFF OFF OFF OFF OFF OFF ON OFF OFF OFF OFF OFF OFF OFF ON ON OFF OFF OFF OFF OFF ON OFF OFF OFF OFF OFF OFF OFF ON OFF ON OFF OFF OFF OFF OFF ON ON OFF ON ON ON ON ON ON OFF OFF ON ON ON ON ON ON OFF ON ON ON ON ON ON ON ON OFF Figure Sheet A Page 3

10 SBPC-21-EN/IP Network Status The SBPC-21-EN/IP network status is determined by interpretation of the external LED status as described in the table below. Figure 1-4: SBPC-21-EN/IP LED Indicators Off LED State Solid Green Table 1-1 LINK LED Ethernet network not detected. Meaning The SBPC-21-EN/IP is connected to an Ethernet network. LED State Off Solid Green Flashing Green Flashing Red Solid Red Flashing Green / Red MODULE STATUS Meaning No power. The Ethernet module is operating properly. The Ethernet module has not been initialized. A minor recoverable fault has been detected. An internal error has been detected. Self-test in progress. LED State Off Solid Green Flashing Green Flashing Red Solid Red Flashing Green / Red NETWORK STATUS Meaning No power or no IP address has been assigned. At least one Ethernet/IP connection is established. No Ethernet/IP connections are established. One or more of the connections in which this module is the target has timed out. This state is only left if all timed out connections are reestablished or if the module is reset. Duplicate IP address detected. Self-test in progress. N/A LED State ACTIVITY LED Meaning The ACTIVITY LED flashes green when a packet is received or transmitted Figure Sheet A Page 4

11 SBPC-21-EN/IP Error Codes The 7-segment LED digit on the SBPC-21-EN/IP main board is used to indicate errors or other potential problems. See page 2 of this manual for the location of this LED. The error codes are divided into the categories listed below. Since there is only a single-digit display and the error codes are 3 digits in length, the error codes are displayed in three parts. The most significant digit will appear first followed by the second and third digits. The display will go blank for a moment and the cycle repeats unless the SBPC-21-EN/IP has been configured to attempt to restart after an error. If this is the case, the error will only cycle once. All state machine errors 5XX are considered nonfatal and only cycle once. Here are the error codes and their meanings. Table 1-2 SBPC PROCESSOR ERRORS F01 Processor attempted to execute and undefined instruction. F02 Software interrupt vector occurred. F03 Attempt to fetch instruction from invalid memory. F04 Attempt to read data from invalid memory. F05 Reserved exception vector. F06 FLASH memory checksum fault. F07 Pool memory allocation error. F08 Byte memory allocation error. F09 Unable to create thread. F0A Unable to create event. F0B Unable to create semaphore. F0C Unable to create mutex. F0D Unable to create queue. F0E Unable to write to queue. F0F Console I/O error. COMMUNICATION MODULE ERRORS E01 The configuration matrix is corrupted. E02 No HMS Anybus module detected. E03 Anybus module failed to initialize (no interrupt received). E04 Anybus module failed to initialize (interrupt stuck). E05 Anybus module failed to initialize (mailbox not ready). E06 Anybus mailbox timeout. E07 Anybus mailbox response indicated error. E08 Anybus mailbox response timeout. E09 Anybus dual-port RAM fault. E0A Anybus output area release timeout. E0B Anybus initialization timeout. STATE MACHINE ERRORS 501 State machine file is corrupted. 502 State machine is disabled. 503 State machine started in shutdown mode. 504 Bad state machine instruction encountered. 505 State machine instruction fetch from address is out of range. 506 State machine stack error (too many nested calls). 507 State machine stack error (too many returns). 508 State machine attempted divide by zero. 509 State machine tried to access more than four timers. 50A State machine variable address is out of range. Errors that begin with F are unrecoverable faults. The SBPC cannot participate in FifeNet or Ethernet operations. In the default configuration, the SBPC will attempt to restart. Errors that begin with E are associated with the Ethernet interface. In the default configuration, the SBPC will attempt to restart. With the exception of error E01, FifeNet is functional; however, the default configuration will attempt to restart which will interrupt FifeNet. Errors that begin with 5 are related to the state machine capability of the SBPC. These errors are cycled only once and do not cause the SBPC to restart Figure Sheet A Page 5

12 Features The SBPC-21-EN/IP supports the following features: Ethernet/IP protocol. DHCP/BootP bootstrap address resolution. File system with approximately 1.4 MB of space available. TELNET server featuring a command line interface similar to MS DOS. FTP server provides easy file management using standard FTP clients. ICMP echo request (ping). SBPC-21-EN/IP Network Configuration Before you can use the module on your network, you must configure the IP (Internet Protocol) address, the subnet mask, and optionally, the gateway address. IP Address The IP address is used to identify each node on the TCP/IP network. Therefore, each node on the network must have a unique IP address. IP addresses are written as four decimal integers (0-255) separated by periods, where each integer represents the binary value of one byte in the IP address. This is called dotted-decimal notation. Example: Address is written as Subnet Mask The IP address is divided into three parts: net ID, subnet ID, and host ID. To separate the net ID and the subnet ID from the host ID, a subnet mask is used. The subnet mask is a 32-bit binary pattern, where a set bit allocates a bit for network/subnet ID, and a cleared bit allocates a bit for the host ID. Like the IP address, the subnet mask is commonly written in dotted-decimal notation. Example: To make the IP address belong to subnet , the subnet mask shall be set to Subnet Mask: ( ) Note: To be able to establish communication between two devices, both devices must belong to the same subnet. If not, the communication must be done through a gateway. It is, therefore, recommended to configure the module to the same subnet as your PC. Special Case IP Addresses Devices on an Ethernet network are not allowed to be configured to the following IP addresses; therefore, do not configure the SBPC-21-EN/IP to use any of them. IP ADDRESS 0.X.X.X DESCRIPTION IP address where the first byte is zero 127.X.X.X IP address where the first byte is 127. X.X.X.0 IP address where the last byte is zero. X.X.X.255 IP address where the last byte is Figure Sheet A Page 6

13 Configuring IP Address The SBPC-21-EN/IP offers several ways to configure the IP address: Configuration Switch DHCP/BootP Using a predefined IP address stored in the FLASH. ARP Using Configuration Switch The configuration switch provides an easy way to configure the module for intranet use. The switch represents the binary value of the last byte in the IP address. If the switch is set to a value between the module will use the settings described below. IP ADDRESS DESCRIPTION IP Address n 1 Subnet Mask Gateway Address (No gateway set.) 1 n represents the binary value of the configuration switches. 2 The subnet mask and gateway are fixed to these values when using the configuration switch to set the IP address Example: The switches are set to (20 decimal) The IP address of the module will be set to Switch ON ( ) = 1 Note: These settings can only be used on an intranet. This is because the IP address that is being set belongs to the private address set, see RFC Using DHCP/BootP If the configuration switches are set to 0, the SBPC-21-EN/IP will read the configuration stored in FLASH. If DHCP/BootP is enabled and a DHCP or BootP server is found, the IP address, subnet mask, and gateway are automatically configured by the DHCP/BootP server. DHCP/Bootp must be enabled by modification of the file ethcfg.cfg in the internal file system. See the file system section for information about this file and how to change it All switches in the position shown (0) use DHCP/BootP or internal configuration. Switch ON ( ) = 1 Using a Predefined Configuration If the configuration switches are set to 0, the SBPC-21-EN/IP will read the configuration stored in internal FLASH. If DHCP/BootP is disabled or a DHCP/BootP client cannot be found, the SBPC-21-EN/IP will try to use the configuration stored in the FLASH. If no configuration is found, the SBPC-21-EN/IP will indicate an error on the Network Status LED. In this state, the SBPC-21-EN/IP will only run the ARP protocol Figure Sheet A Page 7

14 Using Address Resolution Protocol (ARP) The IP address can be changed during runtime using the ARP command from a PC. The new IP address will also be stored in internal FLASH. Below is an example on how to change the IP address from an MS DOS window: arp -s <IP address> 1 <MAC address> 2 ping <IP address> 1 arp -d <IP address> 1 1 The IP Address to assign to the SBPC-21-EN/IP. 2 The 6-digit MAC address from the label on the SBPC-21-EN/IP. The arp -s command will store the IP and MAC addresses in the PC s ARP table. When the ping command is executed, the PC sends this information to the SBPC-21-EN/IP using the MAC address. The module detects that it was addressed with the correct MAC address and adopts the IP address sent by the PC. The new IP address will also be stored in internal FLASH. (The arp -d command is optional, but it removes the static route from the PC ARP table) This method can be used to reconfigure modules that already have been configured. The MAC address is printed on a label on the bottom side of the SBPC-21-EN/IP. Note: As the arp command automatically configures the subnet mask to , the first three bytes of the IP address must be the same as for the PC executing the command. Figure 1-4: Example Connection Using ARP to Change SBPC-21-EN/IP IP Address SBPC-21-EN/IP MAC ID: 00-aa c6-09 Desired IP Address FifeNet provides power for SBPC-21-EN/IP. Ethernet crossover cable allows direct connection to SBPC-21-EN/IP. PC s IP address is In the above example, the following commands would set the SBPC-21-EN/IP IP address to : arp s aa c6-09 ping arp d Figure Sheet A Page 8

15 File System The file system is a fixed-size storage area with a hierarchical directory structure. Files can be grouped in directories for readability. The file system features two security levels. Depending on security level, different users can have access to different files and directories. The file system is accessible via FTP and TELNET. Case Sensitivity The file system is case sensitive. File Name / Path Name Length File names can be a maximum of 48 characters long. Path names can be 256 characters in length, including the file name. File Size The file size is not restricted. Naturally, a file cannot be larger than the available space (see below). Free Space There is approximately 1.4 MB available for user files. Configuration File ethcfg.cfg This file contains the network configuration and is read during initialization. It is an ASCII text file that may be edited with any text editor. If DHCP/BootP configuration is needed, edit this file to enable it. Once changed, the SBPC-21-EN/IP needs to be restarted for changes to take effect. The format of the file is shown below. EXAMPLE : ethcfg.cfg file: [IP Address] [Subnet Mask] [Gateway Address] [SMTP Address] [DHCP/BootP] OFF [Speed] Auto [Duplex] Auto IP address. Subnet mask. Gateway address. N/A ON = Enabled. OFF= Disabled. Auto - Default. Auto negotiation will be used Forces the module to operate only at 100 mbit Forces the module to operate only at 10 mbit. Auto - Default. Auto negotiation will be used. Full - Forces the module to operate only at full duplex. Half - Forces the module to operate only at half duplex. Using a standard FTP client, this file can be transferred from the SBPC-21-EN/IP to a PC, edited, and sent back Figure Sheet A Page 9

16 TELNET Support Through a TELNET client, the user can access the SBPC-21-EN/IP file system using a command line interface similar to MS DOS. The following commands are supported by this utility. Command version help exit Table 1-3 GENERAL COMMANDS Description This command will display version information, serial number, and MAC ID of the module. Displays a help menu. Terminates the current TELNET session. Command arp Iface socket route DIAGNOSTIC COMMANDS Description Display ARP stats and table. Display net interface stats. Display socket list. Display IP route table. Command dir md rd cd format del ren move copy type mkfile append FILE SYSTEM OPERATION Description dir [path] Lists the contents of a directory. If no path is given, the contents of the current directory are listed. md [[path][directory name]] Creates a directory. If no path is given, the directory is created in the current directory. rd [[path][directory name]] Removes a directory. The directory can only be removed if it is empty. cd [path] Changes current directory. format Formats the file system. This is a privileged command and can only be called in administration mode. del [[path][filename]] Deletes a file. ren [[path][old name]] [[path][new name]] Rename a file or directory. move [[source path][source file]] [[destination path]] This command moves a file or directory from the source location to a specified destination. copy [[source path][source file]] [[destination path][destination file]] This command creates a copy of the source file at a specified location. type [[path][filename]] Types the contents of a file. mkfile [[path][filename]] Creates an empty file. append [[path][filename]] [ The line to append ] Appends a line to a file. For commands where file names, directory names, or paths shall be given as an argument, the names can be written directly or within quotes. For names including spaces, the file names must be surrounded by quotes. It is also possible to use relative pathnames using., \, and Figure Sheet A Page 10

17 Ethernet/IP EtherNet/IP is based on the control and information protocol (CIP) which is also the framework for DeviceNet and ControlNet to carry and exchange data between nodes. Implemented Objects EtherNet/IP requires some mandatory objects; these are implemented as well as some vendor specific objects. The mandatory objects are the ones in the specification from ODVA. The following vendor specific objects are implemented: I/O data input mapping object, Class A0h I/O data output mapping object, Class A1h Diagnostic object, Class AAh Assembly Object, Class 04h Description The assembly object binds all mapped I/O data. This data is used for I/O connections. Default I/O instances used are 64h and 96h. Class Attributes ID NAME SERVICE DESCRIPTION SEMANTICS 01 Revision Get_Attribute_All Object Revision The revision attribute containing the revision of the object. DEFAULT, MIN, MAX DATA TYPE 1,1,1 UINT Input Area, Instance 64h Output Area, Instance 96h ID NAME SERVICE DESCRIPTION 03 Data Get_Attribute_Single The data is produced from I/O data input object, attribute 1. By default this data is configured as I/O input data. ID NAME SERVICE DESCRIPTION 03 Data Get_Attribute_Single Set_Attribute_Single The data is produced from I/O data output object, attribute 1. By default this data is configured as I/O output data. DATA TYPE Array of USINT DATA TYPE Array of USINT Figure Sheet A Page 11

18 I/O Data Input Mapping Object, Class A0h Description The assembly object binds all mapped I/O data. This data is used for I/O connections. Default I/O instances used are 64h and 96h. Class Attributes ID NAME SERVICE DESCRIPTION SEMANTICS 01 Revision Get_Attribute_All Object Revision The revision attribute containing the revision of the object. DEFAULT, MIN, MAX DATA TYPE 1,1,1 UINT Input Area, Instance 01h ID NAME SERVICE DESCRIPTION SEMANTICS DEFAULT, MIN, MAX 01 Data Get_Attribute_Single Data that is read. Input Data. N/A DATA TYPE Array of USINT I/O Data Output Mapping Object, Class A1h Description The assembly object binds all mapped I/O data. This data is used for I/O connections. Default I/O instances used are 64h and 96h. Class Attributes ID NAME SERVICE DESCRIPTION 01 Revision Get_Attribute_All Object Revision SEMANTICS The revision attribute containing the revision of the object. DEFAULT, MIN, MAX DATA TYPE 1,1,1 UINT Input Area, Instance 01h ID NAME 01 Data SERVICE DESCRIPTION SEMANTICS Get_Attribute_Single Set_Attribute_Single Data that is read or written. Output Data. DEFAULT, MIN, MAX N/A DATA TYPE Array of USINT Figure Sheet A Page 12

19 Diagnostic Object, Class AAh Description This vendor-specific object provides diagnostic information from the SBPC-21-EN/IP. Class Attributes ID NAME SERVICE DESCRIPTION SEMANTICS DEFAULT, MIN, MAX 01 Revision Get_Attribute_All Object Revision Contains the revision of the object. 1,1,1 UINT Instance Attributes, Instance 01h ID NAME SERVICE DESCRIPTION DEFAULT, MIN, MAX DATA TYPE DATA TYPE 01h Module Serial Number Get_Attribute_Single Serial number. N/A UDINT 02h Vendor ID Get_Attribute_Single Manufacturer ID. N/A UINT 03h Fieldbus Type Get_Attribute_Single Fieldbus type. N/A UINT 04h Module Software Version Get_Attribute_Single Module software version N/A UINT 05h Interrupt Count Get_Attribute_Single Counter incremented on each handshake interrupt. 06h Watchdog Counter In Get_Attribute_Single (Not implemented.) N/A UINT 07h Watchdog Counter Out Get_Attribute_Single Counter incremented every 1 ms. N/A UINT 08h (Reserved) Get_Attribute_Single N/A UINT 09h LED Status Get_Attribute_Single LED indicator status (1 byte/led). N/A STRUCT of { USINT, USINT, USINT, USINT, USINT, USINT } 0Ah Module Type Get_Attribute_Single Module type. N/A UINT 0Bh Module Status Get_Attribute_Single Bit information( freeze, clear, etc.). N/A WORD 0Ch New Data Field Get_Attribute_Single Array of new data flags for 8 bytes area. N/A LWORD 0Dh Interrupt Cause Get_Attribute_Single Interrupt cause register. N/A UINT 0Eh Interrupt notification Get_Attribute_Single Interrupt notification register. N/A UINT 0Fh IN Cycle I/O Length Get_Attribute_Single Size of I/O IN data (bytes). N/A UINT 10h IN DPRAM length Get_Attribute_Single Number of valid IN bytes in DPRAM. N/A UINT 11h IN Total Length Get_Attribute_Single Total number of IN bytes. N/A UINT 12h OUT Cyclic I/O Length Get_Attribute_Single Size of I/O OUT data (bytes). N/A UINT 13h OUT DPRAM Length Get_Attribute_Single Number of valid OUT bytes in DPRAM. N/A UINT 14h OUT Total Length Get_Attribute_Single Total number of OUT bytes supported. N/A UINT 15h Reserved N/A Reserved for future 16-bit compatibility. N/A UINT 16h Application Indication Get_Attribute_Single Application indication register. N/A UINT 17h AnyBus Indication Get_Attribute_Single AnyBus indication register. N/A UINT 18h Module MAC ID Get_Attribute_Single The module MAC ID. N/A Array of USINT (6 bytes) 19h IP Address Get_Attribute_Single The IP address. N/A UDINT 1Ah Subnet Mask Get_Attribute_Single The subnet mask. N/A UDINT 1Bh Gateway Address Get_Attribute_Single The gateway address. N/A UDINT 1Ch SMTP Server Get_Attribute_Single SMTP server address. N/A USINT 1Dh DHCP Configured Get_Attribute_Single 0 = No DHCP. 1 = DHCP available. 1Eh Bootloader Version Get_Attribute_Single Bootloader SW version. N/A UINT 1Fh 20h Application Interface Version Fieldbus Software Version N/A N/A UINT USINT Get_Attribute_Single Application interface SW version. N/A UINT Get_Attribute_Single Fieldbus SW version. N/A UINT Figure Sheet A Page 13

20 Figure Sheet A Page 14

21 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL 2 FIFENET THEORY FifeNet Time Slices Data on FifeNet is divided into time intervals called time slices. The FifeNet protocol runs in fixed repeating cycles. Each time slice can transmit a single 16-bit value. All time slice values are updated every cycle. Multiplexed Time Slices FifeNet devices can send a single 16-bit value in one or more time slices. This is acceptable for values that require high performance such as guiding. The penalty for this performance is the usage of one time slice per value sent. With limited time slices available, network bandwidth can be consumed quickly. If some variables are not needed at a high rate, FifeNet offers a way to multiplex a single time slice to carry multiple data words. There are two multiplex options available in the CDP-01 permitting a single time slice to carry 16 words or 64 words. Multiplexing works by inserting the specified data words in a sequential repeating cycle. The receiving SBPC-21-EN/IP synchronizes with the multiplexed data to extract it. This method trades data update speed for higher data quantities (up to 64 words per time slice). Any combination of real-time or multiplexed data can exist on FifeNet. Figure 2-1: Multiplexed Data Time Slices D1 ACTIVITY D1 is real-time. This data is updated every cycle. T0 T1 T2 T3 D1 D5 D1 D5 D1 D5 D1 D5 MULTIPLEXING D5 is multiplexed or switched to a different variable every cycle. After the last variable is sent, the process repeats continuously. D5 ACTIVITY Tn TS Contents T0 - Edge Right Sensor T1 - Line Edge Sensor T2 - CDP Key Pressed T3 - Status Register Common T4 - Drive 1 Mode T5 - Drive 1 Sensor Mode T6 - Drive 1 Encoder T7 - Drive 1 Status Reg 0 T8 - Drive 2 Mode T9 - Drive 2 Sensor Mode T10 - Drive 2 Encoder T11 - Drive 2 Status Reg 0 T12 - Drive 3 Mode T13 - Drive 3 Sensor Mode T14 - Drive 3 Encoder T15 - Drive 3 Status Reg Figure Sheet A Page 15

22 In the example diagram (Figure 2-1), there is real-time data on D1 and 16 multiplexed data words on D5. D1 contains the Edge Left Sensor value from a CDP-01. D5 is used to send 16 different values from the CDP-01. For the real-time value, the CDP-01 sends the Edge Left Sensor value in D1 every cycle. For the multiplexed time slice, the CDP-01 sends the Edge Right Sensor value in D5 during time T0. During time T1, D5 contains the Line Edge Sensor value. As you can see in the example on the previous page, 17 values are being sent over FifeNet, but only two time slices of network bandwidth are used. The 16 values in time slice 5 are updated at a slower rate than the value in time slice 1. The application dictates which method should be implemented. FifeNet Master The FifeNet protocol uses the time slice architecture described previously for configurable network traffic. Without some synchronization, however, neither the SBPC-21-EN/IP, nor the CDP-01, would know where the time slice boundaries were located. This would create problems when they are trying to send and receive data. This is one of the primary functions of the FifeNet Master, in this case, that would be the SBPC-21-EN/IP Figure Sheet A Page 16

23 SBPC-21-EN/IP Data Flow In order to effectively connect two dissimilar networks, some means must be provided to collect the data from each network and exchange it in a controlled manner so that no partial or incomplete data is sent on either network. This is accomplished by using a block of memory in the SBPC-21-EN/IP to reassemble FifeNet time slice data and then when it is complete, transfer it to the EtherNet/IP buffers for transmission on EtherNet/IP. Keep in mind that the gateway has to be bidirectional so this process works the same way for data traveling from EtherNet/IP to FifeNet. The diagram below shows the process. Figure 2-2: SBPC-21-EN/IP Data Flow Block Diagram FifeNet D1 M M EtherNet/IP Data D2 D3 A A T R I T R I The time slice buffers hold the raw time slice data. X X This matrix is used to connect any time slice to any memory buffer location. The memory array is used to assemble and hold data passing through the gateway. This matrix is used to connect EtherNet scheduled data to any memory buffer location. EtherNet data is placed here for transmission. Consumed data is read from here and sent to FifeNet. As you can see in Figure 2-2, each time slice has enough memory to store bit data words. This is the maximum amount of data that appears on a FifeNet multiplexed time slice. These data words are referenced by their order of reception in the multiplexed sequence with DW0 being first and DW63 being last. When the time slice is used in the real-time mode, only the first location DW0 in the memory array is used. Multiplexed modes 4, 8, and 16 each use 4, 8, and 16 words of memory, respectively Figure Sheet A Page 17

24 Figure Sheet A Page 18

25 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL 3 CONFIGURATIONS Hardware Configuration Single CDP-01 The SBPC-21-EN/IP connection diagram is shown below. As you can see, this allows a single CDP- 01 at FifeNet address 1 and an SBPC-21-EN/IP at address 10. The SBPC-21-EN/IP default Ethernet IP address is , but it can be changed using any of the methods described previously. Figure 3-1: SBPC-21-EN/IP Network Connection with Single CDP-01 FifeNet Address 1 FifeNet Master Address 10 Ethernet IP Address FifeNet Customer Ethernet Ethernet Hub Figure Sheet A Page 19

26 Hardware Configuration Multiple CDP-01 s In the network below, the default SBPC-21-EN/IP configuration is used multiple times to provide control to multiple CDP-01 s. Each SBPC-21-EN/IP is connected to a single CDP-01 creating a separate FifeNet network for each CDP-01. Each SBPC-21-EN/IP appears as both a FifeNet node and an Ethernet node. Notice the SBPC-02-EN/IP Ethernet address must be different for each SBPC- 21-EN/IP. The Ethernet address is set by dip switches inside the enclosure or by configuration during a TELNET session. Figure 3-2: SBPC-21-EN/IP Network Connection with Multiple CDP-01 s FifeNet Address 1 FifeNet Address 1 FifeNet Master Address 10 Ethernet IP Address FifeNet FifeNet Master Address 10 Ethernet IP Address FifeNet SBPC-21-EN/IP to CDP-01 Cable: Fife P/N Customer Ethernet Ethernet Hub Software Configuration Configurations have been created to match the single CDP-01 network shown in Figure 3-1. Since the CDP-01 can have one, two, or three drives, a configuration has been created to match the parameters present in each drive configuration. The three configurations are: CONFIGURATION Table 3-1 SBPC-21-EN/IP MATRIX CDP-01 MATRIX SBPC-21-EN/IP Default Matrix for use with Single-Drive CDP X X SBPC-21-EN/IP Default Matrix for use with Dual-Drive CDP X X SBPC-21-EN/IP Default Matrix for use with Triple-Drive CDP X X Figure Sheet A Page 20

27 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL 4 COMMUNICATION MAPPING EtherNet/IP to FifeNet Data In each of the three configurations (single- dual- or triple-drive CDP-01), the EtherNet/IP to FifeNet data is the same. The table below shows the configuration mapping for data traveling from EtherNet/IP to FifeNet. The control matrix data on data word 1 is present so that if it is mapped to the parallel input for the CDP-01, a great deal of control can be exercised without a special state machine in the CDP-01. If this control is insufficient, the data capabilities on Data Words 2 through 6 are provided for custom application using state machine interpretation. Table 4-1 ETHERNET / IP TO FIFENET DATA SINGLE-, DUAL-, OR TRIPLE-DRIVE CDP-01 CDP-01 Matrix X Single X Dual X Triple SBPC-21-EN/IP Matrix X Single X Dual X Triple Word 1 Data Type 2 Variable Description 0 (0x00) WORD Device 1 Command 3 Network commands sent to the CDP-01. Simulated key presses, etc. 1 (0x01) WORD Control Matrix Used to control the CDP-01 in accordance with the control matrix. 2 (0x02) WORD [0] Reserved These values are reserved for state machine communication. 3 (0x03) WORD [1] Reserved 4 (0x04) WORD [2] Reserved 5 (0x05) INT [3] Reserved 6 (0x06) INT [4] Reserved 1 All data words are 16-bit. 2 Data Types: INT 16-bit signed value in the range of 32,768 to +32,767. WORD 16-bit unsigned value in the range of 0 to 65, Commands to the CDP Figure Sheet A Page 21

28 FifeNet to EtherNet/IP Data The following single-, dual-, and triple-drive tables show the default configuration mapping for data traveling from FifeNet to EtherNet/IP. Single-Drive CDP-01 Word 1 CDP-01 Matrix X Single Data Type 2 Table 4-2 FIFENET TO ETHERNET / IP DATA SINGLE-DRIVE CDP-01 Variable 0 (0x00) WORD Reserved Reserved. 1 (0x01) 2 (0x02) 3 (0x03) 4 (0x04) DWORD Reserved Reserved. DWORD Panel Data 0 Panel Data 1 CDP-01 LED panel data. SBPC-21-EN/IP Matrix X Single Description 5 (0x05) WORD Device 1 Response 3 CDP-01 Fife network responses. 6 (0x06) INT Edge Left Sensor Value Sensor signal. 7 (0x07) INT Edge Right Sensor Value Sensor signal. 8 (0x08) INT Line Center Sensor Value Sensor signal. 9 (0x09) INT Line Edge Sensor Value Sensor signal. 10 (0x0A) WORD SM Command Feedback Reserved for state machine control. 11 (0x0B) WORD SM Status Feedback Reserved for state machine control. 12 (0x0C) WORD Common Status Register CDP-01 status. 13 (0x0D) WORD Key Pressed Current key pressed on CDP-01 Panel. 14 (0x0E) WORD Drive 1 Operation Mode Drive 1 status. 15 (0x0F) WORD Drive 1 Sensor Mode Drive 1 status. 16 (0x10) WORD Drive 1 Fault Register Drive 1 fault status. 17 (0x11) WORD Drive 1 Encoder Register Drive 1 encoder status. 18 (0x12) WORD Drive 1 Alarm Register Drive 1 alarm status. 19 (0x13) INT Drive 1 Encoder Value Drive 1 encoder value. 1 All data words are 16-bit 2 Data Types: INT 16-bit signed value in the range of 32,768 to +32,767. WORD 16-bit unsigned value in the range of 0 to 65,535. DWORD 32-bit unsigned value in the range of 0 to 4,29,4967, This is the device response from CDP Figure Sheet A Page 22

29 FifeNet to EtherNet/IP Data (cont d) Dual-Drive CDP-01 Word 1 CDP-01 Matrix X Dual Data Type 2 Table 4-3 FIFENET TO ETHERNET / IP DATA DUAL-DRIVE CDP-01 Variable 0 (0x00) WORD Reserved Reserved. 1 (0x01) 2 (0x02) 3 (0x03) 4 (0x04) DWORD Reserved Reserved. DWORD Panel Data 0 Panel Data 1 CDP-01 LED panel data. SBPC-21-EN/IP Matrix X Dual Description 5 (0x05) WORD Device 1 Response 3 CDP-01 Fife network responses. 6 (0x06) INT Edge Left Sensor Value Sensor signal. 7 (0x07) INT Edge Right Sensor Value Sensor signal. 8 (0x08) INT Line Center Sensor Value Sensor signal. 9 (0x09) INT Line Edge Sensor Value Sensor signal. 10 (0x0A) WORD SM Command Feedback Reserved for state machine control. 11 (0x0B) WORD SM Status Feedback Reserved for state machine control. 12 (0x0C) WORD Common Status Register CDP-01 status. 13 (0x0D) WORD Key Pressed Current key pressed on CDP-01 Panel. 14 (0x0E) WORD Drive 1 Operation Mode Drive 1 status. 15 (0x0F) WORD Drive 1 Sensor Mode Drive 1 status. 16 (0x10) WORD Drive 1 Fault Register Drive 1 fault status. 17 (0x11) WORD Drive 1 Encoder Register Drive 1 encoder status. 18 (0x12) WORD Drive 1 Alarm Register Drive 1 alarm status. 19 (0x13) INT Drive 1 Encoder Value Drive 1 encoder value. 20 (0x14) WORD Drive 2 Operation Mode Drive 2 status. 21 (0x15) WORD Drive 2 Sensor Mode Drive 2 status. 22 (0x16) WORD Drive 2 Fault Register Drive 2 fault status. 23 (0x17) WORD Drive 2 Encoder Register Drive 2 encoder status. 24 (0x18) WORD Drive 2 Alarm Register Drive 2 alarm status. 25 (0x19) INT Drive 2 Encoder Value Drive 2 encoder value. 1 All data words are 16-bit 2 Data Types: INT 16-bit signed value in the range of 32,768 to +32,767. WORD 16-bit unsigned value in the range of 0 to 65,535. DWORD 32-bit unsigned value in the range of 0 to 4,29,4967, This is the device response from CDP Figure Sheet A Page 23

30 FifeNet to EtherNet/IP Data (cont d) Triple-Drive CDP-01 Word 1 CDP-01 Matrix X Triple Data Type 2 Table 4-4 FIFENET TO ETHERNET / IP DATA TRIPLE-DRIVE CDP-01 Variable 0 (0x00) WORD Reserved Reserved. 1 (0x01) 2 (0x02) 3 (0x03) 4 (0x04) DWORD Reserved Reserved. DWORD Panel Data 0 Panel Data 1 CDP-01 LED panel data. 5 (0x05) WORD Device 1 Response 3 CDP-01 Fife network responses. 6 (0x06) INT Edge Left Sensor Value Sensor signal. 7 (0x07) INT Edge Right Sensor Value Sensor signal. 8 (0x08) INT Line Center Sensor Value Sensor signal. SBPC-21-EN/IP Matrix X Triple Description 9 (0x09) INT Line Edge Sensor Value Sensor signal. 10 (0x0A) WORD SM Command Feedback Reserved for state machine control. 11 (0x0B) WORD SM Status Feedback Reserved for state machine control. 12 (0x0C) WORD Common Status Register CDP-01 status. 13 (0x0D) WORD Key Pressed Current key pressed on CDP-01 Panel. 14 (0x0E) WORD Drive 1 Operation Mode Drive 1 status. 15 (0x0F) WORD Drive 1 Sensor Mode Drive 1 status. 16 (0x10) WORD Drive 1 Fault Register Drive 1 fault status. 17 (0x11) WORD Drive 1 Encoder Register Drive 1 encoder status. 18 (0x12) WORD Drive 1 Alarm Register Drive 1 alarm status. 19 (0x13) INT Drive 1 Encoder Value Drive 1 encoder value. 20 (0x14) WORD Drive 2 Operation Mode Drive 2 status. 21 (0x15) WORD Drive 2 Sensor Mode Drive 2 status. 22 (0x16) WORD Drive 2 Fault Register Drive 2 fault status. 23 (0x17) WORD Drive 2 Encoder Register Drive 2 encoder status. 24 (0x18) WORD Drive 2 Alarm Register Drive 2 alarm status. 25 (0x19) INT Drive 2 Encoder Value Drive 2 encoder value. 26 (0x1A) WORD Drive 3 Operation Mode Drive 3 status. 27 (0x1B) WORD Drive 3 Sensor Mode Drive 3 status. 28 (0x1C) WORD Drive 3 Fault Register Drive 3 fault status. 29 (0x1D) WORD Drive 3 Encoder Register Drive 3 encoder status. 30 (0x1E) WORD Drive 3 Alarm Register Drive 3 alarm status. 31 (0x20) INT Drive 3 Encoder Value Drive 3 encoder value. 1 All data words are 16-bit 2 Data Types: INT 16-bit signed value in the range of 32,768 to +32,767. WORD 16-bit unsigned value in the range of 0 to 65,535. DWORD 32-bit unsigned value in the range of 0 to 4,29,4967, This is the device response from CDP Figure Sheet A Page 24

31 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL 5 CONTROL INFORMATION CDP-01 Control Matrix The CDP-01 parallel input matrix normally applied to the X7 port on the CDP-01. If the default matrix using the SBPC-21-EN/IP, the CDP-01 parallel input matrix is connected to a time slice. This connection allows serial commands to be used to control the CDP-01 instead of the hardware parallel input. The commands described in the control matrix tables on the following pages apply to the commands issued from Ethernet to FifeNet over the network via Data Word 1 in Table 4-1. External Lock There is one command, however, that the CDP-01 firmware will not accept over a serial connection for safety reasons. This command is External Lock. Even though the CDP-01 matrix has the parallel inputs mapped to a FifeNet time slice, the External Lock command is still activated by the matrix shown below when this condition appears on the X7 port of the CDP-01. For multidrive CDP-01 s, the command is applied to all drive present. CDP-01 Parallel Input Matrix for Use with SBPC-21-EN/IP Table 5-1 INPUTS Command Via X7 Parallel Port External Lock (All drives applicable.) Single-Drive CDP-01 CDP-01 Matrix: X CDP-01 State Machine: SBPC-21-EN/IP Matrix: X CDP-01 Control Matrix Table 5-2 COMMAND VIA NETWORK HEX DRIVE 1, AUTOMATIC 04 DRIVE 1, MANUAL 08 DRIVE 1, SERVO-CENTER 0C DRIVE 1, JOG LEFT 10 DRIVE 1, JOG RIGHT 20 DRIVE 1, AUTO SETUP 30 DRIVE 1, RGPC SHIFT LEFT 18 DRIVE 1, RGPC SHIFT RIGHT 28 DRIVE 1, RGPC RESET 38 DRIVE 1, SENSOR EDGE LEFT 14 DRIVE 1, SENSOR EDGE RIGHT 24 DRIVE 1, SENSOR EDGE CENTER 34 DRIVE 1, SENSOR LINE CENTER 1C DRIVE 1, SENSOR LINE EDGE 2C DRIVE 1, SENSOR LINE E&C 3C Figure Sheet A Page 25

32 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL Figure Sheet A Page 26

33 Dual-Drive CDP-01 CDP-01 Matrix: X CDP-01 State Machine: SBPC-21-EN/IP Matrix: X CDP-01 Control Matrix Table 5-3 COMMAND VIA NETWORK HEX DRIVE 1, AUTOMATIC 04 DRIVE 1, MANUAL 08 DRIVE 1, SERVO-CENTER 0C DRIVE 1, JOG LEFT 10 DRIVE 1, JOG RIGHT 20 DRIVE 1, AUTO SETUP 30 DRIVE 1, RGPC SHIFT LEFT 18 DRIVE 1, RGPC SHIFT RIGHT 28 DRIVE 1, RGPC RESET 38 DRIVE 1, SENSOR EDGE LEFT 14 DRIVE 1, SENSOR EDGE RIGHT 24 DRIVE 1, SENSOR EDGE CENTER 34 DRIVE 1, SENSOR LINE CENTER 1C DRIVE 1, SENSOR LINE EDGE 2C DRIVE 1, SENSOR LINE E&C 3C DRIVE 2, AUTOMATIC 05 DRIVE 2, MANUAL 09 DRIVE 2, SERVO-CENTER 0D DRIVE 2, JOG LEFT 11 DRIVE 2, JOG RIGHT 21 DRIVE 2, AUTO SETUP 31 DRIVE 2, RGPC SHIFT LEFT 19 DRIVE 2, RGPC SHIFT RIGHT 29 DRIVE 2, RGPC RESET 39 DRIVE 2, SENSOR EDGE LEFT 15 DRIVE 2, SENSOR EDGE RIGHT 25 DRIVE 2, SENSOR EDGE CENTER 35 DRIVE 2, SENSOR LINE CENTER 1D DRIVE 2, SENSOR LINE EDGE 2D DRIVE 2, SENSOR LINE E&C 3D Figure Sheet A Page 27

34 Triple-Drive CDP-01 CDP-01 Matrix: X CDP-01 State Machine: SBPC-21-EN/IP Matrix: X CDP-01 Control Matrix Table 5-4 COMMAND VIA NETWORK HEX DRIVE 1, AUTOMATIC 04 DRIVE 1, MANUAL 08 DRIVE 1, SERVO-CENTER 0C DRIVE 1, JOG LEFT 10 DRIVE 1, JOG RIGHT 20 DRIVE 1, AUTO SETUP 30 DRIVE 1, RGPC SHIFT LEFT 18 DRIVE 1, RGPC SHIFT RIGHT 28 DRIVE 1, RGPC RESET 38 DRIVE 1, SENSOR EDGE LEFT 14 DRIVE 1, SENSOR EDGE RIGHT 24 DRIVE 1, SENSOR EDGE CENTER 34 DRIVE 1, SENSOR LINE CENTER 1C DRIVE 1, SENSOR LINE EDGE 2C DRIVE 1, SENSOR LINE E&C 3C DRIVE 2, AUTOMATIC 05 DRIVE 2, MANUAL 09 DRIVE 2, SERVO-CENTER 0D DRIVE 2, JOG LEFT 11 DRIVE 2, JOG RIGHT 21 DRIVE 2, AUTO SETUP 31 DRIVE 2, RGPC SHIFT LEFT 19 DRIVE 2, RGPC SHIFT RIGHT 29 DRIVE 2, RGPC RESET 39 DRIVE 2, SENSOR EDGE LEFT 15 DRIVE 2, SENSOR EDGE RIGHT 25 DRIVE 2, SENSOR EDGE CENTER 35 DRIVE 2, SENSOR LINE CENTER 1D DRIVE 2, SENSOR LINE EDGE 2D DRIVE 2, SENSOR LINE E&C 3D DRIVE 3, AUTOMATIC 06 DRIVE 3, MANUAL 0A DRIVE 3, SERVO-CENTER 0E DRIVE 3, JOG LEFT 12 DRIVE 3, JOG RIGHT 22 DRIVE 3, AUTO SETUP 32 DRIVE 3, RGPC SHIFT LEFT 1A DRIVE 3, RGPC SHIFT RIGHT 2A DRIVE 3, RGPC RESET 3A DRIVE 3, SENSOR EDGE LEFT 16 DRIVE 3, SENSOR EDGE RIGHT 26 DRIVE 3, SENSOR EDGE CENTER 36 DRIVE 3, SENSOR LINE CENTER 1E DRIVE 3, SENSOR LINE EDGE 2E DRIVE 3, SENSOR LINE E&C 3E Figure Sheet A Page 28

35 Status Data Block For reference, the CDP-01 Status Data Blocks are listed in the tables on the following pages. NOTE: In the Data Word Bit # fields on the following tables: _ 0 = Low, 1 = High, Blank = Ignore DW4, DW5: CDP-01 LED Panel Data PANEL DATA WORD 0: DW4 PANEL DATA WORD 1: DW5 Bit CDP-01 LED Bit CDP-01 LED 0 LED 12 (Line Edge Sensor Mode 0 1 LED 11 (Line Center Sensor Mode) 1 2 LED 10 (Edge Right Sensor Mode) 2 3 LED 9 (Edge Left Sensor Mode) 3 4 LED 17 (Polarity) 4 5 LED 16 (Gain) 5 6 LED 15 (Guide Point) 6 7 LED 14 (Auto Setup) LED 3 (Manual Key) 9 9 LED 2 (Servo-Center Key) LED 1 (Auto Key) 11 Not Used 11 LED 8 (Sensor Key) 12 Drive 3 LED 12 LED 4 (f1 Key) 13 Drive 2 LED 13 LED 5 (F2 Key) 14 Drive 1 LED 14 LED 6 (F3 Key) 15 LED 13 (Setup Key) 15 LED 7 (ASC Key) DW6: Device 1 Response DEVICE 1 RESPONSE: DW6 Data Word Bit No Description Automatic Servo-Center Manual Jog Plus Jog Minus Edge Left Edge Right Center Line Center Line Edge Line Edge & Center 0 0 Drive Drive Drive Figure Sheet A Page 29

36 Status Data Block (cont d) DW7: EDGE LEFT Sensor Value DW8: EDGE RIGHT Sensor Value DW9: LINE CENTER Sensor Value DW10: LINE EDGE Sensor Value NOTE: These data words contain the normalized values of the connected sensors. Data Type: signed 16-bit number. Range: -32,768 to +32,767 DW12: Common Status Register COMMON STATUS REGISTER: DW12 Data Word Bit No Description 0 0 Drive 1 Panel Active 0 1 Drive 2 Panel Active 1 0 Drive 3 Panel Active 1 1 External A/D Converter Installed 1 1 Drive 3 Installed 1 1 Drive 2 Installed 1 Status of Parallel Output A 1 Status of Parallel Output B 1 Status of Parallel Input 0 1 Status of Parallel Input 1 1 Status of Parallel Input 2 1 Status of Parallel Input 3 1 Status of Parallel Input 4 1 Status of Parallel Input 5 Bit = 1 indicates transistor on (output active). Bit = 0 indicates transistor off (output inactive) Figure Sheet A Page 30

37 Status Data Block (cont d) DW13: Key Pressed To ensure proper recognition, a key must be depressed for a minimum of 500 ms. KEY PRESSED: DW13 Data Word Bit No. Key Hex Value ASC 0 0x7FF F3 0 0xBFFF F2 0 0xDFFF F1 0 0xEFFF Sensor 0 0xF7FF Automatic 0 0xFBFF Servo-Center 0 0xFDFF Manual 0 0xFEFF Drive Select 0 0xFF7F Setup 0 0xFFBF Jog Plus 0 0xFFDF Jog Minus 0 0xFFEF RGPC Right 0 0xFFF7 RGPC Left 0 0xFFFB Remote Calibration 0 0xFFFD Error x0FFF Timeout xF0FF No Key Pressed xFF0F Saving xFFF0 Undefined Key x Figure Sheet A Page 31

38 Status Data Block (cont d) DW14, DW20, DW26: Drive-Specific Operating Mode DW14 Drive 1 DW20 Drive 2 DW26 Drive 3 OPERATING MODE: DW14, DW20, DW26 Data Word Bit No Description Automatic Servo-Center Manual Jog Left Jog Right Setup (Auto or Man is Also Set) DW15, DW21, DW27: Drive-Specific Sensor Selection and Temperature Fault DW15 Drive 1 DW21 Drive 2 DW27 Drive 3 SENSOR SELECTION: DW15, DW21, DW27 Data Word Bit No Description Edge Left (X2) Edge Right (X1) Edge Center (X1 and X2) Line Center (X3) Line Edge (X3) Line Edge and Center (X3 with VTB-20) 1 Fault - Overtemperature Figure Sheet A Page 32

39 Status Data Block (cont d) DW16, DW22, DW28: Drive-Specific Fault Register DW16 Drive 1 DW22 Drive 2 DW28 Drive 3 FAULT REGISTER (SR0): DW16, DW22, DW28 Data Word Bit No Description 1 Fault Motor Drive Power Supply 1 Fault Motor Overcurrent 1 Fault +12V Power Supply 1 Fault -12V Power Supply 1 Fault Analog Ground 1 Fault A/D Converter Initialization 1 Fault Overtemperature DW17, DW23, DW29: Drive-Specific Encoder Register DW17 Drive 1 DW23 Drive 2 DW29 Drive 3 ENCODER REGISTER (SR2): DW17, DW23, DW29 Data Word Bit No Description 1 Encoder Counterclockwise Stroke Limit 1 Encoder Clockwise Stroke Limit 1 Counterclockwise Web Measurement Limit 1 Clockwise Web Measurement Limit 1 Counterclockwise Limit Switch 1 Clockwise Limit Switch Figure Sheet A Page 33

40 Status Data Block (cont d) DW18, DW24, DW30: Drive-Specific Alarm Register DW18 Drive 1 DW24 Drive 2 DW30 Drive 3 ALARM REGISTER (SR3): DW18, DW24, DW30 Data Word Bit No Description 1 Encoder Stroke Alarm 1 Web Measurement Alarm 1 Loss of Null 1 ASC (Automatic Sensor Control) Active 1 Fault Serial Power 1 Drive Centered 1 Drive in Shutdown 1 Counterclockwise Maximum Motor Speed 1 Clockwise Maximum Motor Speed 1 Motor Blocked; Motor Current 1 SSC (Sensor Signal Comparator) Active 1 Counterclockwise Maximum Motor Current 1 Clockwise Maximum Motor Current 1 Valid Motor Installed DW19: Drive 1 Encoder Value. DW25: Drive 2 Encoder Value. DW31: Drive 3 Encoder Value. NOTE: These data words contain the normalized values of the connected encoders. Data Type: Signed 16 bit-number. Range: -32,768 to +32, Figure Sheet A Page 34

41 Figure Sheet A Page 35

42 SBPC-21-EN/IP CUSTOMER INSTRUCTION MANUAL 6 SPECIAL CONTROL OF FIFENET DEVICES Note: This section is intended to be used for special commands not available in the Control Matrix via keypad emulation or for setup purposes. CDP-01 Key Code Data Path When a key is pressed on a FifeNet CDP-01, the key code goes through many steps before any action is taken. The keys are scanned and the key is detected, but the key is not acted upon yet. Instead, the key is buffered until the FifeNet Master polls the CDP-01 with a command that asks, What keys are pressed on your panel? The CDP-01 responds with the key code representing which key (or keys) are currently pressed. Normally, the FifeNet Master then issues a command back to the CDP-01 with the key code and a command that tells the CDP-01 which keys are pressed. Now that the CDP- 01 has received the command from the FifeNet Master telling it that a key has been pressed, it will act on that key. (This is why a FifeNet CDP-01 keypad does not work when the network is down.) This sequence is shown below. FifeNet Master Figure 6-1: Key Code Data Path 1) What keys are pressed? 2) My AUTO key is pressed. 3) Your AUTO key is pressed. By skipping steps 1 and 2 in the sequence above and injecting key codes/commands into the command stream for the CDP-01, the SBPC-21-EN/IP can simulate keys being pressed on its local panel. This provides the ability to make a fully functional remote control over the network Figure Sheet A Page 36