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.
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
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.
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.
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
Ethernet IP address configuration
switches. See the following page
for description of these switches.
The 7-segment LED is
used to display errors or
exceptions. During normal
operation, the display will
continuously “cycle” the
outer segments.
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
Switch Value = 0
Switch Value = 1 – 254
The first three values of the
IP address are fixed at
192.168.0 and the dip switch
value represents the binary
value of the last digit of the IP
address. The subnet mask is
255.255.255.0 and the
default gateway is 0.0.0.0.
IP Address SW1 SW2 SW3 SW4 SW5 SW6 SW7 SW8
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.
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
Table 1-1
LINK LED
LED State Meaning
Off Ethernet network not detected.
Solid Green The SBPC-21-EN/IP is connected to an Ethernet network.
MODULE STATUS
LED State Meaning
Off No power.
Solid Green The Ethernet module is operating properly.
Flashing Green The Ethernet module has not been initialized.
Flashing Red A minor recoverable fault has been detected.
Solid Red An internal error has been detected.
Flashing Green / Red Self-test in progress.
NETWORK STATUS
LED State Meaning
Off No power or no IP address has been assigned.
Solid Green At least one Ethernet/IP connection is established.
Flashing Green No Ethernet/IP connections are established.
Flashing Red
Solid Red Duplicate IP address detected.
Flashing Green / Red Self-test in progress.
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.
ACTIVITY LED
LED State Meaning
N/A The ACTIVITY LED flashes green when a packet is received or transmitted.
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.
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 10000000 00001010 00000010 00011110 is written as 128.10.2.30
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 128.10.2.30 belong to subnet 128.10.2, the subnet mask shall
be set to 255.255.255.0.
Subnet Mask: 11111111 11111111 1111111 00000000 (255.255.255.0)
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 DESCRIPTION
0.X.X.X
127.X.X.X
X.X.X.0
X.X.X.255
IP address where the first byte is zero
IP address where the first byte is 127.
IP address where the last byte is zero.
IP address where the last byte is 255.
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
1-254 the module will use the settings described below.
IP ADDRESS DESCRIPTION
IP Address 192.168.0.n1
Subnet Mask2 255.255.255.0
Gateway Address2 0.0.0.0 (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.
00010100
Example:
The switches are set to 00010100 (20 decimal)
The IP address of the module will be set to 192.168.0.20
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 1918.
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.
00000000
ll switches in the position shown (0) use DHCP/BootP or internal
uration.
confi
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.
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>
ping <IP address>
arp -d <IP address>
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.
1
<MAC address>2
1
1
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 255.255.255.0, 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-00-62-c6-09
Desired IP Address
84.83.83.5
FifeNet provides power for SBPC-21-EN/IP.
Ethernet crossover cable allows
direct connection to SBPC-21-EN/IP.
PC’s IP address is 84.83.83.2
In the above example, the following commands would set the SBPC-21-EN/IP IP address to
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]
IP address.
10.10.12.212
[Subnet Mask]
Subnet mask.
255.255.255.0
[Gateway Address]
Gateway address.
0.0.0.0
[SMTP Address]
N/A
0.0.0.0
[DHCP/BootP]
OFF
ON = Enabled.
OFF= Disabled.
[Speed]
Auto
Auto - Default. Auto negotiation will be used.
100 - Forces the module to operate only at 100 mbit.
10 - Forces the module to operate only at 10 mbit.
[Duplex]
Auto
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.
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.
Table 1-3
GENERAL COMMANDS
Command Description
version
help Displays a help menu.
exit Terminates the current TELNET session.
This command will display version information, serial number, and MAC ID of the
module.
DIAGNOSTIC COMMANDS
Command Description
arp Display ARP stats and table.
Iface Display net interface stats.
socket Display socket list.
route Display IP route table.
FILE SYSTEM OPERATION
Command Description
dir
md
rd
cd
format
del
ren
move
copy
type
mkfile
append
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 “..”
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
01 Revision Get_Attribute_All Object Revision
NAME
SERVICE
DESCRIPTION
SEMANTICS
The revision attribute containing
the revision of the object.
DEFAULT,
MIN, MAX
1,1,1 UINT
DATA
TYPE
Input Area, Instance 64h
ID NAME
03 Data Get_Attribute_Single
Output Area, Instance 96h
ID NAME
03 Data
SERVICE
SERVICE
Get_Attribute_Single
Set_Attribute_Single
DESCRIPTION
The data is produced from I/O data
input object, attribute 1. By default this
data is configured as I/O input data.
DESCRIPTION
The data is produced from I/O data
output object, attribute 1. By default this
data is configured as I/O output data.
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.
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.
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
D2
D3
•
•
•
•
•
•
•
•
The time slice
buffers hold
the raw time
slice data.
M
A
T
R
I
X
M
A
T
R
I
X
EtherNet/IP Data
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 64 16-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.
The SBPC-21-EN/IP connection diagram is shown below. As you can see, this allows a single CDP01 at FifeNet address 1 and an SBPC-21-EN/IP at address 10. The SBPC-21-EN/IP default Ethernet
IP address is 192.168.0.1, 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
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 SBPC21-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
ddress 1
FifeNet
ddress 1
FifeNet Master
ddress 10
Ethernet
IP Address
192.168.0.1
FifeNet
FifeNet Master
ddress 10
Ethernet
IP Address
192.168.0.2
FifeNet
SBPC-21-EN/IP to
CDP-01 Cable:
Fife P/N 67075-001
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:
Table 3-1
CONFIGURATION
SBPC-21-EN/IP Default Matrix for use with Single-Drive CDP-01 100410-02X 100246-02X
SBPC-21-EN/IP Default Matrix for use with Dual-Drive CDP-01 100411-02X 100247-02X
SBPC-21-EN/IP Default Matrix for use with Triple-Drive CDP-01 100412-02X 100248-02X
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
Word1 Data Type2 Variable Description
0 (0x00) WORD
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
3
All data words are 16-bit.
1
Data Types:
2
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.
Commands to the CDP-01.
CDP-01 Matrix
100246-02X Single
100247-02X Dual
100248-02X Triple
Device 1
Command
Network commands sent to the CDP-01. Simulated key presses, etc.
19 (0x13) INT Drive 1 Encoder Value Drive 1 encoder value.
All data words are 16-bit
1
Data Types:
2
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,295.
25 (0x19) INT Drive 2 Encoder Value Drive 2 encoder value.
All data words are 16-bit
1
Data Types:
2
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,295.
31 (0x20) INT Drive 3 Encoder Value Drive 3 encoder value.
All data words are 16-bit
1
Data Types:
2
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,295.
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
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 CDP01 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.
Figure 6-1: Key Code Data Path
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.
The CDP-01 keypad is shown below, along with the key codes for each key. The key codes can be
used to send a command to the CDP-01 to simulate a key pressed on the CDP-01 keypad.
Commands are sent via a 16 bit command word, Register 0 in Table 4-1. Commands are issued by
placing an 8-bit “command” byte in the lower half of the command word and an 8-bit “action” byte in
the upper half of the command word. The “Key Pressed’ command is byte 0x13. The “Manual” key
code is 0x88. To simulate that the “Manual” key is pressed, send the command word 0x8813 to the
CDP-01. As long as the command is issued, the CDP-01 acts as though the key is being held down.
Even the actual keys on the CDP-01 keypad will be ignored until the command is cleared by writing
zero 0x0000 to the command word. This provides the ability to lock out the CDP-01 keypad. If local
keypad operation was needed concurrently with network control, the command should be maintained
until the correct feedback is obtained. Feedback is obtained by monitoring the CDP-01 status data
block parameters of Section 5. For instance, Register 0x40D could be monitored to verify that the key
pressed command was received and Register 0x405 could be monitored to see what the CDP-01
response was to the key pressed command.
Figure 6-2: CDP-01 Key Codes
Automatic 0xAA
Servo-Center 0x99
Manual 0x88
F1 0xCC
F2 0xDD
F3 0xEE
ASC 0xFF
Sensor 0xBB
Setup 0x66
Jog Minus 0x44
Drive Select 0x77
Jog Plus 0x55
KEY
HEX
CODE
Simulating Dual-Key Presses
It is also possible to simulate dual-key presses. Single-key presses contain a value like 0x44 for “jog
minus” or 0x55 for “jog plus.” To simulate two keys pressed simultaneously, combine the two key
codes like this: “job minus” combined with “jog plus” is 0x54. Any two keys can be combined as long
as the key code with the higher value is placed in the upper nibble. This allows simulation of setup
functions. Key combinations of three keys or more cannot be simulated by network commands.
To make remote control complete, we must have a way to duplicate the CDP-01 panel LED’s. The
CDP-01 keypad contains integrated LED’s to indicate operating modes, sensors selected, and many
other parameters. The CDP-01 can be configured to send its panel LED data over FifeNet so that
remote devices can duplicate the CDP-01 panel state. We have to look a little deeper to understand
how to use this capability.
Since there are 31 LED’s on the CDP-01 panel, the information has to use the multiplexed mode to
send all the LED states. The CDP-01 sends the panel data in two parts: Input Registers 0x0403 and
0x0404 as shown in Section 5, Status Data Block. The first word (Input Register 0x0403) contains the
state of 15 panel LED’s, while the second word (Input Register 0x0404) contains the remaining 16 LED
states. The logic is negative so a bit that is zero indicates that this LED is on.
By using the panel data, the setup procedures in the CDP-01 reference manual can be monitored to
ensure proper sequence of steps.