controlnet user manual - lvmcc-pubs.rockwellautomation.com
TRANSCRIPT
User
Manual
ControlNet�
Communication
Interface
(Cat. No.1770-KFC15,1770-KFCD15)
Allen�Bradley
Important User Information
The illustrations, charts, sample programs and layout examplesshown in this guide are intended solely for purposes of example.Since there are many variables and requirements associated with anyparticular installation, Allen-Bradley does not assume responsibilityor liability (to include intellectual property liability) for actual usebased upon the examples shown in this publication.
Allen-Bradley publication SGI-1.1, Safety Guidelines for theApplication, Installation, and Maintenance of Solid-State Control(available from your local Allen-Bradley office), describes someimportant differences between solid-state equipment andelectromechanical devices that should be taken into considerationwhen applying products such as those described in this publication.
Reproduction of the contents of this copyrighted publication, inwhole or in part, without written permission of Allen-BradleyCompany, Inc., is prohibited.
Throughout this manual we use notes to make you aware of safetyconsiderations:
!ATTENTION: Identifies information about practicesor circumstances that can lead to personal injury ordeath, property damage or economic loss.
Attention statements help you to:
• identify a hazard
• avoid the hazard
• recognize the consequences
Important: Identifies information that is critical for successfulapplication and understanding of the product.
ControlNet is a trademark of ControlNet International; PLC is a registered trademark of Allen-Bradley Company, Inc.
Important User Information 1. . . . . . . . . . . . . . . . . . .
Preface P-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose of the Manual P-1. . . . . . . . . . . . . . . . . . . . . . . . . .
Related Publications P-2. . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Products P-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Glossary of Terms and Abbreviations P-3. . . . . . . . . . . . . . .
ControlNet System Overview 1-1. . . . . . . . . . . . . . . . . .
Overview of ControlNet 1-1. . . . . . . . . . . . . . . . . . . . . . . . .
Physical Characteristics 1-1. . . . . . . . . . . . . . . . . . . . . . . . .
Communication Protocol 1-2. . . . . . . . . . . . . . . . . . . . . . . .
Understanding the ControlNet Architecture 1-3. . . . . . . . . . .
Planning the Host Cable System 1-3. . . . . . . . . . . . . . . . . . .
Planning for a Parallel Port 1-4. . . . . . . . . . . . . . . . . . . . .
Planning for an RS�232C Serial Port 1-5. . . . . . . . . . . . . .
Introducing the KFC15/KFCD15 Module 2-1. . . . . . . . . .
Overview of the KFC15/KFCD15 Module 2-1. . . . . . . . . . . . .
Compatibility 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents
Table of ContentsI–2
Installing the KFC15/KFCD15 Module 3-1. . . . . . . . . . .
Electrostatic Damage 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the Installation Procedure 3-2. . . . . . . . . . . . . .
Connecting to a Host through the RS�232C Port 3-3. . . . . . . .
RS�232C Baud Rates 3-3. . . . . . . . . . . . . . . . . . . . . . . .
Cables 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connector 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS�232C Activity Indicator 3-3. . . . . . . . . . . . . . . . . . . . .
Connecting to a Host through the Parallel Port 3-4. . . . . . . . .
Cables 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connector 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parallel Port Activity Indicator 3-4. . . . . . . . . . . . . . . . . . .
Connecting a Device to the Network Access Port 3-5. . . . . . .
Cables 3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to the AC Power Supply (KFC15) 3-5. . . . . . . . .
Connecting to the DC Power Supply (KFCD15) 3-6. . . . . . . .
Connecting to the ControlNet Cable System 3-7. . . . . . . . . .
Attaching the KFC15/KFCD15 Module to a Wall or Mounting Bracket 3-9. . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the KFC15/KFCD15 Module 4-1. . . . . . . . .
Overview of Configuration Procedures 4-1. . . . . . . . . . . . . .
Displays 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pushbuttons 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the KFC15/KFCD15 Module Using Pushbuttons 4-4
Viewing Basic Parameter Settings 4-4. . . . . . . . . . . . . . . .
Configuring the Basic Parameters 4-5. . . . . . . . . . . . . . . .
Configuring the Advanced Parameters 4-8. . . . . . . . . . . .
Saving Configuration Changes 4-10. . . . . . . . . . . . . . . . . .
Exit without Saving 4-12. . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Factory Defaults 4-13. . . . . . . . . . . . . . . . . . . . . . .
Verifying the Communication Parameters 4-13. . . . . . . . . . . .
Table of Contents I–3
Communicating with the KFC15/KFCD15 Module 5-1. . .
DF1 Communication 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . .
Serial Communication 5-2. . . . . . . . . . . . . . . . . . . . . . . . . .
Parallel Communication 5-4. . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting the KFC15/KFCD15 Module 6-1. . . . . .
Interpreting the Status LEDs 6-1. . . . . . . . . . . . . . . . . . . . . .
Interpreting the Seven�Segment LED Displays 6-4. . . . . . . . .
Product Specifications A-1. . . . . . . . . . . . . . . . . . . . . .
RS�232C Interface A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parallel Port Interface A-1. . . . . . . . . . . . . . . . . . . . . . . . . .
ControlNet Interface A-2. . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Access Port (NAP) Interface A-2. . . . . . . . . . . . . . .
Electrical A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environmental A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agency Safety Certification A-3. . . . . . . . . . . . . . . . . . . . . .
Agency Emissions Certification A-4. . . . . . . . . . . . . . . . . . . .
European Union Directive Compliance A-4. . . . . . . . . . . . . .
Installation Requirements A-4. . . . . . . . . . . . . . . . . . . . . .
Cabling and Pinouts B-1. . . . . . . . . . . . . . . . . . . . . . . .
Cabling and Pinouts for RS�232C Connection B-1. . . . . . . . .
Cabling and Pinouts for Parallel Port Connection B-5. . . . . . .
DF1 Diagnostic Command Support C-1. . . . . . . . . . . . .
Diagnostic Loop C-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic Read Counters C-2. . . . . . . . . . . . . . . . . . . . . . .
Diagnostic Status C-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic Counter Reset C-5. . . . . . . . . . . . . . . . . . . . . . .
Table of ContentsI–4
Writing a Parallel Communication Driver D-1. . . . . . . . .
DF1 Parallel Communication D-1. . . . . . . . . . . . . . . . . . . . .
Data Transmission D-4. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Transfer in Byte Mode D-5. . . . . . . . . . . . . . . . . . . .
Data Transfer in Nibble Mode D-6. . . . . . . . . . . . . . . . . . .
Preface
Publication 1770�6.5.20 - June 1997
Preface
The 1770-KFC15/KFCD15 Communication Interface provides acommunication link between a ControlNet� cable system anddevices with a serial or parallel port that do not connect directly tothe cable system, such as programming terminals, portablecomputers, and other serial/parallel devices.
The 1770-KFC15/KFCD15 Communication Interface refers to thefollowing modules: 1770-KFC15, or 1770-KFCD15. The physicalfeatures that distinguish the KFCD15 from the KFC15 are:
• DC power connector (1771-KFCD15)
• Reset switch (1771-KFCD15)
• Single, 0.5-amp, slow-blow, 250-volt fuse (1771-KFCD15)
• Single, 0.25-amp, slow-blow, 250-volt fuse (1770-KFC15)
Purpose of the Manual
Throughout this manual we refer to both Communication Interfacesas the KFC15/KFCD15 module. Where information applies only to aparticular module this will be stated. Use the manual to:
• install and configure the KFC15/KFCD15 module
• understand how the KFC15/KFCD15 module communicates onthe network (procedures and protocols)
• troubleshoot for problems
PrefaceP–2
Publication 1770�6.5.20 - June 1997
Related Publications
The following publications contain information related to the1770-KFC15/KFCD15 Communication Interface:
Publication Reference Number
Allen�Bradley ControlNet Cable System Planning andInstallation Manual
1786�6.2.1
Allen�Bradley ControlNet Cable System Component List AG�2.2
Allen�Bradley Industrial Automation Wiring and GroundingGuidelines
1770�4.1
Allen�Bradley PLC�5 Family Programmable ControllersHardware Installation Manual
1785�6.6.1
Allen�Bradley PLC�5 Programming Software Manual 6200�6.4.7
Related Products
The KFC15/KFCD15 modules creates an interface between theControlNet cable system and devices with a serial or parallel port. Ithas been verified to work with the following products:
• Allen-Bradley ControlNet taps (1786-TPR, 1786-TPS,1786-TPYR and 1786-TPYS)
• Allen-Bradley high voltage AC and DC type repeaters(1786-RPT and 1786-RPTD)
• Allen-Bradley PLC-5�s (1785-L20C15, L40C15, L60C15,L80C15)
• Allen-Bradley computer interface cards (1784-KTC15 and1784-KTCX15)
• Allen-Bradley 1794 Flex I/O Adapters (1794-ACN15,1794-ACNR15)
Preface P–3
Publication 1770�6.5.20 - June 1997
• Allen-Bradley 1771 I/O Adapters (1771-ACN15, ACNR15)
• Rockwell Software’s RSLogix5�, RSView32�, and RSLinx�
• Network Access cable (1786-CP)
Other ControlNet devices and software that comply with theControlNet Network specifications can also be used with theKFC15/KFCD15 module.
Glossary of Terms and Abbreviations
This manual uses the following terms as defined below.
ControlNet—the communication architecture that allows theexchange of messages between devices that follow the ControlNetspecifications. It is a realtime, control-layer network that provideshigh-speed transport for both time-critical I/O and messaging data.A ControlNet cable system can be either single or redundant media.
DF1—Allen-Bradley’s RS-232 proprietary protocol
DH+� (Data Highway Plus�) network—existing Allen-Bradleypeer-to-peer network for messaging and program upload/download
full duplex—simultaneous send/receive between devices,point-to-point
half duplex—data transmission in one direction at a time, usuallypoint-to-multipoint
NAP (network access port)—input/output (RJ-45 style) connectorfor a programming terminal to gain full access to the network
network—a collection of connected nodes (end devices). Theconnection paths between any pair of nodes can include repeaters,routers, bridges and gateways.
PrefaceP–4
Publication 1770�6.5.20 - June 1997
network address—the network address of a node on the ControlNetcable system. This address must be in the range of 1 to 99 (decimal)and be unique to that subnet. A subnet can contain a maximum of99 nodes.
node—any physical device connecting to the ControlNet cablesystem that requires a network address in order to function on thenetwork.
NUT (network update time)—the rate at which access to thenetwork is granted
parallel port—input/output port for a device that transmits multipledata and control bits over wires connected in parallel
PCCC (Programmable Controller CommunicationsCommands)—an Allen-Bradley communication protocol used onthe Data Highway Plus network
repeater—a two-port active physical layer component thatreconstructs all traffic it hears on one network segment side andretransmits it to another network segment side. Repeaters allow forextensions in network distance, conversion to alternate media(coaxial cable, fiber, etc.) and altering the topology of the network.
RIO (Remote Input/Output)—an Allen-Bradley remoteinput/output link that supports remote, time-critical, I/O and controlcommunication between a master PLC controller and its remote I/Oand adapter mode slave processors
RS-232C port—a serial port that complies with accepted industrystandards for serial communications connections
segment—trunkline sections connected via taps with terminators ateach end, and with no repeaters
Preface P–5
Publication 1770�6.5.20 - June 1997
serial port—input/output connector for a device that transmits dataand control bits sequentially over a single transmission line. (SeeRS-232C port.)
subnet—network segments connected by repeaters to make up oneControlNet network
tap—the connection device between any device and the trunkline.A tap is required for each node and for both sides of each repeater.
terminator —a special circuit that prevents signal reflections fromoccurring at the end of a cable
trunkline —the bus or central part of a cable system
trunkline section—a length of trunkline cable between any two taps
Chapter 1
Publication 1770�6.5.20 - June 1997
ControlNet System Overview
This chapter briefly describes the network architecture. For detailedinformation, refer to the ControlNet Cable System Planning andInstallation Manual (1786-6.2.1).
Overview of ControlNet
ControlNet combines the capabilities of Data Highway Plus andRemote I/O in a single local area network (LAN). It providestime-critical communication capabilities for realtime control, andmessaging services for peer-to-peer communication.
Several devices can be connected to the ControlNet cable systemincluding personal computers, programmable logic controllers,modems, variable speed drivers, operator interfaces, and otherdevices with direct ControlNet cable system connections. To connectdirectly, devices must be able to handle ControlNet communicationprotocol. The PLC-5/40C15 is such a device. Some equipment,however, requires an intermediate device to act as an interfacebetween it and the network. The KFC15/KFCD15 module acts asthis interface. Refer to Chapter 2 for more information on theKFC15/KFCD15 module.
Physical Characteristics
The physical base for ControlNet is coaxial cable with redundantmedia connections as an option. The allowable length of a cablesegment in the network depends on the number of nodes in thesegment. A single subnet can accommodate several segments byusing repeaters.
1–2 ControlNet System Overview
Publication 1770�6.5.20 - June 1997
Communication Protocol
The most important function of the ControlNet network is totransport time-critical control information. Other information is alsotransported but is not allowed to interfere with time-criticalmessages. This is done through a communication protocol thatdetermines access to the ControlNet network using a time-sliceaccess algorithm. Access to the network occurs at auser-configurable period called the network update time (NUT).The NUT is divided into three parts:
Scheduled—every node is guaranteed one opportunity to transmit
Unscheduled—remaining time is divided among all nodes on around-robin basis. This rotation of access repeats until the timeallotted to the unscheduled portion is used up. The amount of timeavailable for the unscheduled portion is determined by the trafficload of the scheduled portion.
Maintenance—the moderator node (the one with the lowest address)transmits information to keep the other nodes synchronized in time
ControlNet System Overview 1–3
Publication 1770�6.5.20 - June 1997
The part of the interval in which any given data will be sent dependson its priority, of which there are two levels:
Scheduled Data—time-critical information that must be sent at afixed and repetitive rate is sent exclusively in the scheduled portionof the NUT.
Unscheduled Data—information that does not have strict timeconstraints. It is sent only if no data is waiting to be sent at a higherpriority.
The KFC15/KFCD15 module supports non-time-critical messagingand programming data, and sends only unscheduled data.
Understanding the ControlNet Architecture
The ControlNet cable system provides the flexibility to design acommunication network for your application. To take advantage ofthis flexibility, you should spend enough time planning how to installyour cable system before assembling any of the hardware. Consultthe ControlNet Cable System Planning and Installation Manual(1786-6.2.1) for a full description of the cable system and detailedinstallation instructions.
Planning the Host Cable System
A serial or parallel host (computer, controller, or other device) canconnect to the KFC15/KFCD15 module through either the parallel orRS-232C serial port. Both ports on the KFC15/KFCD15 modulecannot be active at the same time so you must decide which port isthe most appropriate for your application. This decision determinesthe cabling and hardware requirements for your system.
1–4 ControlNet System Overview
Publication 1770�6.5.20 - June 1997
Communication between either a parallel or serial host and theKFC15/KFCD15 module is carried out using Allen-Bradley’sproprietary DF1 protocol. DF1 is a full- or half-duplex protocol thatcarries messages intact over a link. The protocol delimits messages,detects and signals errors, retries after errors, and controls messageflow. In a typical network, as discussed in this manual, the host is themaster station and the KFC15/KFCD15 module is the slave. For acomplete description of the DF1 protocol, refer to the DataHighway/Data Highway Plus/DH-485 Protocol and Command SetReference (1770-6.5.16).
Planning for a Parallel Port
The parallel port interface consists of eight, bidirectional data linesand nine handshaking lines. Consider the following requirementswhen planning for a parallel port connection,
• Data transfers occur in half-duplex mode between the parallelhost and the KFC15/KFCD15 module.
• Data transfer mode is configured using pushbuttons on theKFC15/KFCD15 module and can be bytes or nibbles (four bits).
ControlNet System Overview 1–5
Publication 1770�6.5.20 - June 1997
• When connection is via the parallel port you can have only oneKFC15/KFCD15 module per host.
• The maximum recommended cable length between theKFC15/KFCD15 module and the parallel host is 3 m (10 ft).
• The cable between the KFC15/KFCD15 module and the parallelhost must be shielded.
For detailed cabling and pinout information see Appendix B,Cabling and Pinouts. For a discussion of data transfer modes andother communication issues, see Chapter 5, Communicating with theKFC15/KFCD15 Module and Appendix D, Writing a ParallelCommunication Driver.
Planning for an RS-232C Serial Port
Serial port communication can take place in either full- orhalf-duplex mode. If a single KFC15/KFCD15 module per serialhost is used, either half-duplex or full-duplex communication cantake place.
1–6 ControlNet System Overview
Publication 1770�6.5.20 - June 1997
If more than one KFC15/KFCD15 is connected to a host, onlyhalf-duplex communication can occur and modems must be usedbetween the KFC15/KFCD15 module and the host. Determine howmany KFC15/KFCD15 modules you will need before planning thelayout of the host system because cable length and baud rate areaffected as well. See Appendix B for details.
Chapter 2
Publication 1770�6.5.20 - June 1997
Introducing theKFC15/KFCD15 Module
Overview of the KFC15/KFCD15 Module
The KFC15/KFCD15 module enables you to connect devices thatcannot communicate directly to the ControlNet. Such devices willuse either an RS-232C serial port or an enhanced parallel port toconnect to the KFC15/KFCD15 module. Device types requiringconnection to the ControlNet cable system are varied, includingmulti-vendor automation equipment, personal computers,mini-computers, and modems.
The 1770-KFCD15, as shown below, is functionally equivalent to the1770-KFC15, except it is powered on by a 24 V dc power supplyinstead of a 115 V ac supply.
2–2 Introducing the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
The KFC15/KFCD15 module connects to the ControlNet from one(Channel A) or both of its two BNC connectors via a standard,one-meter, ControlNet coaxial tap. For redundant media, bothconnectors are used.
Introducing the KFC15/KFCD15 Module 2–3
Publication 1770�6.5.20 - June 1997
The KFC15/KFCD15 module has three ports for device connections:
RS-232C serial port—provides half- or full-duplex communicationwith a serial node such as a host computer, an intelligent controlleror a modem
parallel port—provides half-duplex communication with a parallelhost such as a computer
network access port—lets you connect a programming terminal orother device to the KFC15/KFCD15 module for full network accesswithout disrupting the cable wiring
The serial and parallel ports use DF1 protocol while the remainingnetwork access port handles ControlNet packets directly.
Status, Host, and ControlNet LEDs on the top of the KFC15/KFCD15indicate current operating conditions of the unit and communicationactivities taking place through the ports.
2–4 Introducing the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Use the pushbuttons and seven-segment LEDs in the configurationpanel on the bottom of the unit to set and verify the ControlNetaddress for the KFC15/KFCD15 module and all serial RS-232C orparallel communication parameters.
Compatibility
The KFC15/KFCD15 is compatible with the following interfaces:
• RS-232C serial ports
• IBM PC-compatible parallel ports
• IBM Type 1 PS/2-compatible parallel ports
• ControlNet devices that comply with the ControlNet specification
• programming terminal products that comply with ControlNetspecifications for the Network Access Port
Chapter 3
Publication 1770�6.5.20 - June 1997
Installing the KFC15/KFCD15Module
Use this chapter to install the KFC15/KFCD15 module. This chapterdescribes:
• an overview of the general installation procedure
• how to connect the KFC15/KFCD15 module to a host through theRS-232C serial port
• how to connect the KFC15/KFCD15 module to a host through theparallel port
• how to connect the KFC15/KFCD15 module to a host through theisolated network access port (NAP)
• how to connect the KFC15/KFCD15 module to the ControlNetcable system
• how to attach the KFC15/KFCD15 module to a wall or mountingbracket
Pinout and wiring details are provided in Appendix B, Cabling andPinouts. Read this if you need to construct cables. If a tap is notavailable on the ControlNet cable system for the KFC15/KFCD15module, refer to the ControlNet Cable System Planning andInstallation Manual (1786-6.2.1) to determine if your cable systemcan accommodate another node and to plan where to mount the tap,then follow the mounting instructions at the end of this chapter.
3–2 Installing the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Electrostatic Damage
!ATTENTION: Electrostatic discharge can damagesemiconductor devices inside the KFC15/KFCD15module. To guard against electrostatic damage wear anapproved wrist strap grounding device, or touch agrounded object to rid yourself of electrostatic chargebefore handling the products.
Overview of the Installation Procedure
1. Make sure that the ControlNet cable system can accommodateadditional nodes (one per KFC15/KFCD15 module beinginstalled).
2. Determine the placement of the KFC15/KFCD15 module (desk,wall or mounting bracket).
3. Connect the KFC15/KFCD15 module to the host through eitherthe parallel or serial port, or through the network access port.
4. Connect the KFC15/KFCD15 to a power supply as detailed laterin this chapter.
5. Configure the communications parameters on theKFC15/KFCD15 as detailed in Chapter 4, Configuring theKFC15/KFCD15 Module.
6. Connect the KFC15/KFCD15 to the network using taps.
Note: Placement of the KFC15/KFCD15 module willdetermine if mounting comes before or after connecting thecables.
�
Installing the KFC15/KFCD15 Module 3–3
Publication 1770�6.5.20 - June 1997
Connecting to a Host through the RS�232C Port
A single, full- or half-duplex, RS-232C serial port using the DF1protocol provides communications with either a host computer orintelligent controller. For an explanation of full- and half-duplex seeChapter 5, Communicating with the KFC15/KFCD15 Module.
RS-232C Baud Rates
The KFC15/KFCD15 module supports the following baud rates:300, 600, 1200, 2400, 4800, 9600, 19200 and 38400.
Cables
Cabling for the RS-232C connector will vary depending on yourapplication. You can use either a 3-wire cable or a cable withhandshaking lines. For wiring diagrams see Appendix B, Cablingand Pinouts. The maximum recommended cable lengths are:
• for baud rates ≤ 19200 15 m (50 ft)
• for baud rates = 38400 7.5 m (25 ft)
Connector
The RS-232C interface connector at the KFC15/KFCD15 moduleend is a DB-25 male connector (DTE) with EIA (ElectronicsIndustries Association) standard pinout as outlined in Appendix B,Cabling and Pinouts.
RS-232C Activity Indicator
The HOST LED will flicker when the KFC15/KFCD15 module isreceiving or transmitting data over the RS-232C interface. The LEDwill be off when no data activity is occurring over the RS-232Cinterface.
3–4 Installing the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Connecting to a Host through the Parallel Port
The parallel port interface is compatible with the parallel ports ofIBM PCs, and also with bidirectional parallel ports of PS/2computers. Two data transfer modes are available to providecompatibility. Both types of parallel ports can send data from thecomputer in bytes and receive information in nibbles. You canconfigure the KFC15/KFCD15 module to send data back in bytes,instead of nibbles, for computers with bidirectional parallel ports.Specify the mode of parallel port operation using the push buttons onthe configuration panel. Configuration is discussed in Chapter 5,Communicating with the KFC15/KFCD15 Module. In either case,the appropriate software driver is required on the host computer.
Cables
The maximum cable length recommended is 3 m (10 ft). The cableshould be shielded.
Connector
The parallel port interface connector is a DB-25 female connectorwith a standard Centronics pinout. See Appendix B, Cabling andPinouts for cabling and pinout details.
Parallel Port Activity Indicator
The HOST LED will flicker when the KFC15/KFCD15 module isreceiving or transmitting data over the parallel interface. The LEDwill be off when no data activity is occurring over either theRS-232C or the parallel port interface.
Installing the KFC15/KFCD15 Module 3–5
Publication 1770�6.5.20 - June 1997
Connecting a Device to the Network Access Port
Use the isolated network access port to connect a transitory device,such as a programming device, to the KFC15/KFCD15 module.
Cables
You must use the Allen-Bradley Network Access Cable (Cat. No.1786-CP).
Connecting to the AC Power Supply (KFC15)
The KFC15 module contains an internal transformer that allows youto switch between 115V ac or 230V ac at 60 HZ or 50 Hzrespectively.
!ATTENTION: The KFC15 module does not have anON/OFF switch so power is applied to the module assoon as you plug it in. For this reason you must selectthe voltage before plugging in the KFC15 module toprevent damaging the unit.
3–6 Installing the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
To select the input voltage:
1. Locate the red voltage selector switch on the side of the KFC15module beside the fuses.
2. Slide the switch to the left for 115V ac or to the right for 230V ac.The selected voltage is visible in the indented part of the switch.
3. Plug in the KFC15 module.
Connecting to the DC Power Supply (KFCD15)
The KFCD15 module operates on 18 to 40 volts dc power, providingan RS-232C interface to ControlNet, while maintaining all thefunctionality of the 1770-KFC15.
!ATTENTION: This equipment is to be powered by aClass 2 power supply only (such as 1784-DNPS), andis to be installed by qualified service personnel only.
Connect the KFCD15 module to a power supply, as shown. Thisstarts the initialization routine.
Installing the KFC15/KFCD15 Module 3–7
Publication 1770�6.5.20 - June 1997
!ATTENTION: The KFCD15 module does not havean ON/OFF switch so power is applied to the moduleas soon as you plug it in.
To reinitialize the module at any time after it has been running, pressthe reset switch on the side of the unit.
Connecting to the ControlNet Cable System
To connect the KFC15/KFCD15 to the ControlNet cable system usean approved ControlNet tap. Refer to the ControlNet Cable SystemPlanning and Installation Manual (1786-6.2.1) for completeinstructions on connecting the tap to the cable system.
3–8 Installing the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
!ATTENTION: If the KFC15/KFCD15 module isconnected to a cable system that does not supportredundant media, the tap dropline should be connectedto the BNC connector labeled channel A. The channelB connector should be unused. If the cable system isredundant, the KFC15/KFCD15 module should beconnected such that all devices on the network use thesame cable for the same channel. The channel Aconnector on all products should be connected to thesame cable. The same applies for the channel Bconnectors.
To connect the KFC15/KFCD15 module to the tap do the following:
1. If the KFC15/KFCD15 module is not the last device in thesegment:
• Connect the tap to the coaxial trunkline.• Connect the dropline BNC to the channel A BNC of the
KFC15/KFCD15 module.
2. If the KFC15/KFCD15 module is the last device in the segment,install a terminator at the end of the cable segment, then followthe instructions in step 1.
3. If using redundant media, repeat either step 1 or step 2 forchannel B of the KFC15/KFCD15 module.
Installing the KFC15/KFCD15 Module 3–9
Publication 1770�6.5.20 - June 1997
Attaching the KFC15/KFCD15 Module to a Wall or Mounting
Bracket
You can set the KFC15/KFCD15 module on any flat surface, such asa desk or shelf, or attach it to a mounting bracket or directly to a wallfor vertical placement. Use the two #10-32 threaded inserts on theunit if you are mounting it vertically.
To attach the KFC15/KFCD15 module to a wall:
1. Mark the position of the screw inserts on the surface to which it isto be attached.
2. Drill holes through the surface, as shown in the drawing above.
3. Insert screws from the back of the surface, through the holes andinto the screw inserts, then tighten.
Note: The configuration pushbuttons and displays will not beaccessible or visible if the KFC15/KFCD15 module is wall orbracket mounted.
�
Chapter 4
Publication 1770�6.5.20 - June 1997
Configuring theKFC15/KFCD15 Module
Use this chapter to configure the KFC15/KFCD15 communicationparameters via the pushbuttons and seven-segment displays in theconfiguration panel on the bottom of the module.
Overview of Configuration Procedures
The KFC15/KFCD15 module has two modes of operation, run modeand configuration mode. During normal operation theKFC15/KFCD15 module functions in run mode. To change thecommunication parameters the unit must be in configuration mode.Any changes made to the communication parameters take effect assoon as they are saved and the unit returns to run mode. While inconfiguration mode the KFC15/KFCD15 module continues tocommunicate according to its current settings. This allows you toview the current settings without interrupting the operation of theunit.
Important: Verify all parameter settings before connecting theKFC15/KFCD15 module to the network. Incorrectsettings may cause unreliable and unpredictableoperation of the network.
Parameter settings are saved in non-volatile memory so that you donot lose them even if power to the KFC15/KFCD15 module isinterrupted. When the KFC15/KFCD15 module is in run mode, theseven-segment display is off to conserve power.
4–2 Configuring the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Important: If the KFC15/KFCD15 module displays symbols otherthan those shown in this chapter, it is malfunctioning.Contact your A-B representative to arrange to return theunit for servicing.
Displays
The following drawing shows the displays on the configuration panelon the bottom of the KFC15/KFCD15 module. The left display (onedigit) shows the number of the parameter being configured. The tworight displays (two digits) show the current setting for that parameter.Communication parameters are configured in two menus, a mainmenu for basic parameters, and a sub-menu for more advancedparameters for the RS-232C serial port.
11024
VIEW DATA EXIT
SAVE
Parameter NumberCurrent Setting
Configuring the KFC15/KFCD15 Module 4–3
Publication 1770�6.5.20 - June 1997
Pushbuttons
The operation of the three pushbuttons labelled VIEW, DATA, and EXIT
in the configuration panel are described in the following table.
Pressing this button orbutton combination:
Performs this task:
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
VIEW ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In run mode, places the KFC15/KFCD15 module inconfiguration mode.This is the only button that has a function in run mode.
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In configuration mode, cycles through the possiblecommunication parameters (displayed on the left digit).
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If you hold the button down for more than 1 second, theparameter number advances automatically.
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁDATA ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In configuration mode, cycles through the possiblecommunication settings for the parameter shown on the left.The data is displayed on the right two digits. If you hold thebutton down for more than 1 second, the settings advanceand accelerate automatically.When the left display shows A, press DATA to enter thesub�menu.
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
EXIT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In configuration mode at the main menu, returns theKFC15/KFCD15 module to run mode without saving anychanges. From the sub�menu, returns to the main menu.ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
VIEW + EXIT
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In configuration mode, saves all configuration changes, andreturns the KFC15/KFCD15 module to run mode from eithermenu. The KFC15/KFCD15 module will begin operating withthe new configuration as soon as it returns to run mode.
VIEW + DATA In configuration mode, resets all communication parametersto their factory defaults. The changes do not take effect untilthe configuration is saved, and the KFC15/KFCD15 modulereturns to run modei.e. until VIEW and EXIT are pressedsimultaneously. If only EXIT is pressed the unit returns torun mode without making the factory default changes.
4–4 Configuring the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Configuring the KFC15/KFCD15 Module Using Pushbuttons
Before configuring the KFC15/KFCD15 module, you shoulddetermine the parameter settings the network requires. If they differfrom the factory defaults shown in the parameter tables on thefollowing pages, use the directions below to change them.
For normal operation, you must configure the basic communicationparameters. For special communication needs you can configure theadvanced communication parameters, which provide more flexibilityin the operation of the KFC15/KFCD15 module.
While you are changing the parameters in configuration mode, theKFC15/KFCD15 module continues to operate using its currentsettings. The changed parameter settings do not take effect until theyare saved and the KFC15/KFCD15 module returns to run mode.
Viewing Basic Parameter Settings
To view the current parameter settings:
1. Press the VIEW button to enter configuration mode. The firstparameter number is displayed on the left display, with its currentsetting in the right two displays.
2. Press VIEW to display the next parameter and its current setting, orhold it down to cycle through the communication parameters.When the last parameter is reached, the configuration numberwraps back to the start.
3. Press EXIT to return the KFC15/KFCD15 to run mode withoutchanging parameters.
Configuring the KFC15/KFCD15 Module 4–5
Publication 1770�6.5.20 - June 1997
Configuring the Basic Parameters
The basic parameters are numbered zero to eight. The letters A and Falso come up on the seven-segment LEDs as you cycle through themas described above. The letter A lets you into the sub-menu thatcontains the advanced communication parameters. The settingsdisplayed beside letter F are the series and revision number of theKFC15/KFCD15 module.
To configure the basic parameters:
1. Press the VIEW button to enter configuration mode.
2. Press VIEW as often as necessary or hold it down until the desiredparameter is reached.
3. Once the desired parameter is displayed, press the DATA button tocycle through the available settings. Only valid selections for thegiven parameter option are displayed.
4. When you have reached the desired data setting, you can pressVIEW to display the next parameter.
5. When all relevant parameters have been set, press VIEW and EXIT
together to save the parameter settings and return the module torun mode.
4–6 Configuring the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
The basic communication parameters and their valid settings aredescribed in the table below.
ParameterNumber
Parameter Description FactoryDefault
ControlNet
NetworkAddress
Auto Addressing (AA) or 01-99 AA
Port
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁDF1 port ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
Serial (00), Parallel (01) ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
00
RS�232C
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
Baud Rate ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
300 (03), 600 (06), 1200 (12), 2400(24), 4800 (48), 9600 (96), 19200 (19),38400 (38) bits/sec
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
96
Parity None (00), Even (01), Odd (02) 00
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
Full/HalfDuplex
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
Full duplex (00), Half duplex (01) forserial port only
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
00
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Parallel
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
Parallel PortTransfer
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
Nibble data transfers to host (01), Bytedata transfers to host (02)
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
01
Configuring the KFC15/KFCD15 Module 4–7
Publication 1770�6.5.20 - June 1997
ParameterNumber
FactoryDefault
DescriptionParameter
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DF1
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
Error DetectionÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
BCC Block Check Code (00), orCRC16 Cyclic Redundancy Check (01)
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
00
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
DF1 StationAddress
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
The station address of this node on theDF1 link. Valid addresses are 00�77 Octalinclusive.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
00
DiagnosticCommandExecution
Determines whether PCCC diagnosticcommands are executed directly by theKFC15/KFCD15 (01) or passed throughto the host computer (00).
01
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Other
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
Sub�Menu ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
Lets user into the sub�menu. ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
N/A
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
Series/Revision
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
Displays the module series andrevision.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
N/A
4–8 Configuring the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Configuring the Advanced Parameters
The advanced communication parameters, numbers zero to five, arein the sub-menu. Sub-menu parameters are followed by a decimal inthe display. View them the same way basic parameters are viewed,when you enter the sub-menu.
VIEW DATA EXIT
SAVE
Advanced Parameter NumberCurrent Setting
Sub-Menu Indicator
1. To enter the sub-menu, press VIEW until parameter A appears inthe left display and dashes in the right display, then press DATA.
The number on the left changes from A to 0, and its decimal pointlights up, remaining lit as long as you are in the sub-menu.
2. Press VIEW to display the sub-menu parameters, as described forthe basic parameters, until you reach one you want to configure.
3. Press DATA to display and cycle through the settings for theadvanced parameter until you get to the one you want.
4. Repeat the process until you have completed setting theparameters.
5. Press VIEW and EXIT while in the sub-menu to save the changesand return the module to run mode.
Configuring the KFC15/KFCD15 Module 4–9
Publication 1770�6.5.20 - June 1997
Note: You can press EXIT to return to the main menu from thesub-menu, if necessary. This does not end the configurationsession. You can go back to the sub-menu as described in step 1. The changes you have made to advanced parametersare not lost as long as you go through the save and exitprocedure, described later in this chapter, when you return themodule to run mode.
ParameterNumber
Parameter Description FactoryDefault
Number ofRetries
Number of allowable retries per attempton the RS�232C link: 00 � 10
02
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
DuplicateMessageDetection
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
Disabled (00), Enabled (01). If enabled,the KFC15/KFCD15 will acknowledgeand discard duplicate messagesreceived on the DF1 link.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
01
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
DF1 ACKTime�out
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
The time to wait for an ACK from thehost computer. The time is from 0.1 to 5seconds in 0.1 second increments(01�50). To calculate the time�out,multiply the number in the display by0.1 second.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
10
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ModemHandshaking
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
Disabled (00), Enabled (01)
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
00
�
4–10 Configuring the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
ParameterNumber
FactoryDefault
DescriptionParameter
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
CTS toTransmit Delay
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
The delay between the CTS signal andthe start of transmission (half duplexonly). The delay is from 0 to
0.99 seconds, in 10 ms.(0.01 second) increments (00�99). To calculate the delay, multiply thenumber in the display by 0.01 seconds.This parameter takes effect only whenthe KFC15/KFCD15 is in half�duplexmode and handshaking is enabled.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
No delay (00)
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁEnd ofMessage toRTS Off
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
The delay between the end of amessage and the KFC15/KFCD15setting RTS inactive. The delay is from0 to 0.99 seconds in 10 ms
(0.01 second) increments. To calculate the delay, multiply thenumber in the display by 0.01 seconds.This parameter takes effect only whenthe KFC15/KFCD15 is in half�duplexmode and handshaking is enabled.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
No delay (00)
Saving Configuration Changes
To save all parameters in both the main menu and the sub-menu innon-volatile memory:
• Press the VIEW and EXIT buttons simultaneously.
The KFC15/KFCD15 module returns to run mode. This ends theconfiguration session.
Configuring the KFC15/KFCD15 Module 4–11
Publication 1770�6.5.20 - June 1997
If the save is successful, the display will show three dashes for aperiod of two seconds. When the KFC15/KFCD15 module returns torun mode, the new configuration takes effect immediately, and thedisplays turn off.
VIEW DATA EXIT
SAVE
11022
If the save is not successful, the KFC15/KFCD15 module ismalfunctioning. The left display will show hardware fault number 6and the STATUS LED will show solid red. If this happens, contactyour A-B representative.
VIEW DATA EXIT
SAVE
11023
4–12 Configuring the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Exit without Saving
To exit without saving while in the main menu:
• Press EXIT.
The KFC15/KFCD15 module returns to run mode fromconfiguration mode without saving any changes. This ends theconfiguration session and the previous settings will remain ineffect.
To return to the main menu from the sub-menu:
• Press EXIT.
You can move between the two menus as much as you need toduring any given configuration session.
If you exit from the main menu without saving, as described above,any changes made in the sub-menu are not saved. If you save andexit from the main menu, changes made in the sub-menu are savedas well.
Important: If the KFC15/KFCD15 module is left inactive (i.e., withno buttons pressed) in configuration mode for 3minutes, it returns to run mode. Any changes madesince going into configuration mode will not be saved.Also, if power to the unit is interrupted while inconfiguration mode, any changes made will not besaved.
Configuring the KFC15/KFCD15 Module 4–13
Publication 1770�6.5.20 - June 1997
Setting Factory Defaults
To reset all parameters in both menus to their factory defaults:
• Press the VIEW and DATA buttons simultaneously when inconfiguration mode.
When this button combination is pressed, the KFC15/KFCD15displays the first parameter and its factory default.
To save the factory default parameters:
• Press the VIEW and EXIT buttons simultaneously.
If only the EXIT button is pressed, the unit returns to run modewithout changing the parameters to their factory defaults.
Verifying the Communication Parameters
Before connecting the KFC15/KFCD15 to the network, cyclethrough the parameter settings and verify that they are correct.Incorrect settings may cause unreliable and unpredictable operationof the network.
Chapter 5
Publication 1770�6.5.20 - June 1997
Communicating with theKFC15/KFCD15 Module
Read this chapter if you are configuring a half-duplex network or ifyou plan to write a communication driver for the KFC15/KFCD15module.
DF1 Communication
The KFC15/KFCD15 module supports both full-duplex andhalf-duplex DF1 protocol between it and a host device. This protocolcan be used over either the serial or parallel interface to send PCCCor ControlNet messages across the ControlNet cable system to othernodes. For more information on PCCC messages refer to theAllen-Bradley Data Highway/Data Highway Plus/Data Highway485 Protocol and Command Set Reference Manual (1770-6.5.16).
The host device must send messages in a form that the end node it iscommunicating with understands. The KFC15/KFCD15 module doesnot translate between two types of messages. If the end node onlyrecognizes one type, the host device’s communication driver mustsend the same form.
5–2 Communicating with the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Serial Communication
Serial communication with the KFC15/KFCD15 module can beeither full or half duplex DF1. The duplex used depends on theoverall application’s requirements.
Full-duplex serial protocol:
• is a direct link that allows simultaneous two-way transmission
• often requires a system programmer to use interrupts andmulti-tasking techniques
• is intended for high-performance applications where maximumdata throughput is necessary
• gives faster data throughput than half duplex, but is more difficultto expand or to use when communicating with more than oneKFC15/KFCD15 module
11031
ProgrammableController or
Host Computer
KFC15/KFCD15
End Devices
RS-232C Link
TT
E-D
T
E-D
T
E-D
ControlNet
Half-duplex serial protocol:
• is a protocol for one host processor and one or more field devices.(You must use modems if there is more than oneKFC15/KFCD15 module.)
Communicating with the KFC15/KFCD15 Module 5–3
Publication 1770�6.5.20 - June 1997
• allows only one host processor or field device to transmit at anyone time
• provides a less effective usage of resources than full duplex, butis easier to implement
Half-duplex protocol can be used on a point-to-point link, but morecommonly it operates on a link with all nodes interfaced throughhalf-duplex modems. There can be from 0 to 63 decimal nodessimultaneously connected to a single link.
With half duplex protocol, you can use a:
two-circuit system—the master sends and slaves receive on onecircuit, slaves send and master receives on the other
one-circuit system—master and slaves send and receive on the samecircuit
11030
PLC Computeror
Other Hosts
Modem
ModemModem Modem
RS-232C Link
Multidrop Network
Nodes
RS-232C Link
ControlNet
RS-232C Link
T T T T
N N N
Nodes
ControlNet
T T T T
N N N
KFC15/KFCD15
Nodes
ControlNet
T T T T
N N N
KFC15/KFCD15KFC15/KFCD15
5–4 Communicating with the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Parallel Communication
Parallel communication with the KFC15/KFCD15 module can behalf-duplex DF1 only. Full duplex is not supported.
Half-duplex parallel protocol:
• uses the same protocol as with half-duplex RS-232C (serial)
• must be point-to-point (cannot be multidrop)
11032
Computer orOther Host
Parallel Link
Nodes
N N N
KFC15/KFCD15
ControlNetT T T T
With parallel half-duplex communication, a host device can sendeight bits of the DF1 message at a time to the KFC15/KFCD15module. The host device can receive four bits of a message at a timefrom the module in NIBBLE MODE. In instances where the hostdevice has a bidirectional parallel port, it can receive messages eightbits (one byte) at a time in BYTE MODE. See Chapter 4,Configuring the KFC15/KFCD15 Module for instructions on settingthe operating mode.
If you plan to use parallel port communication and your applicationrequires that you write you own driver, see Appendix D, Writing aParallel Communication Driver, for details.
Chapter 6
Publication 1770�6.5.20 - June 1997
Troubleshooting theKFC15/KFCD15 Module
Use this chapter to interpret the indicators (status LEDs andseven-segment LED displays) on the KFC15/KFCD15 module tohelp you troubleshoot problems.
Interpreting the Status LEDs
There are four, bi-color (red/green) status LEDs on the top of theKFC15/KFCD15 module. Two are for ControlNet showing physicallayer status of channels A (primary connection) and B (redundantmedia connection), one is for communication on the RS-232C orparallel port (HOST), and one is for the KFC15/KFCD15 (STATUS).These indicators can help you diagnose problems with the module’sinstallation and operation.
6–2 Troubleshooting the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Label Position
The following terms are used to describe the state of the LEDs:
solid—on continuously in the defined state
flashing—each LED alternates between the two defined states (orwith OFF if only one state is defined). This only applies to a singleLED viewed independently of the other. If both ControlNet LEDsare flashing, they flash together (in phase).
railroad —both LEDs alternate between the two defined states at thesame time. This only applies to both ControlNet LEDs when viewedtogether. The two LEDs are always in opposite states (out-of-phase).
flickering —intermittent on/off between the two states, often in anerratic pattern
Troubleshooting the KFC15/KFCD15 Module 6–3
Publication 1770�6.5.20 - June 1997
LED State Probable Cause Recommended Action
Channels Aand B
OFF No power or reset.and B(viewedtogether)
SOLID RED Failed unit Check network setup then cyclepower to the KFC15/KFCD15module. If the fault persists,contact your authorizedAllen�Bradley representative ordistributor.
RAILROADRED - GREEN
Self test None
RAILROADRED - OFF
Incorrect nodeconfiguration(duplicate node, ID,etc.)
Check network address andother ControlNet configurationparameters.
Channel Aor B(viewed
OFF Channel disabled orunused
Program network for redundantmedia if required.
(viewedseparately)
SOLID GREEN Channel gooddata isbeing received andtransmitted on thischannel
None
FLASHINGGREEN - OFF
Temporary errors ordevice is not online
None. Unit will corect itself.
FLASHINGRED - GREEN
Bad networkconfiguration
Check network setup then cyclepower to the KFC15/KFCD15module.
FLASHINGRED - OFF
Media fault or no othernodes present on thenetwork
Check media for broken cables,loose connector, missingterminators, etc.
HOST OFF No activity or no hostpresent
None
FLICKERINGGREEN � OFF
Link OKdata is beingtransmitted or receivedover the RS�232C orparallel port
None
SOLID RED Link faulttheKFC15/KFCD15 hasdetected acommunication fault
Check cable pinouts andparameter settings. If the faultpersists contact your authorizedAllen�Bradley representative ordistributor.
FLASHINGRED
Not defined None
6–4 Troubleshooting the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
LED Recommended ActionProbable CauseState
STATUS OFF No power is applied tothe KFC15/KFCD15module
None
SOLID GREEN Normal operationthemodule is OK
None
FLASHINGGREEN
The KFC15/KFCD15 isnot properly configured
Check and change parametersettings.
SOLID RED Critical faulttheKFC15/KFCD15 hasdetected anunrecoverable faultand must be replaced
Contact your authorizedAllen�Bradley representative ordistributor.
FLASHINGRED
Non�critical faulttheKFC15/KFCD15 hasdetected a recoverablefault
Reconfigure or reset theKFC15/KFCD15.
Interpreting the Seven�Segment LED Displays
Under normal conditions, the numeric displays should be off unlessyou are configuring the communication parameters. Duringoperation, the numeric displays are used to indicate hardware faultconditions. When the STATUS LED is solid or flashing red, the leftparameter display will show a number indicating the type ofhardware fault. The following table gives a description of the faults.
Troubleshooting the KFC15/KFCD15 Module 6–5
Publication 1770�6.5.20 - June 1997
ÁÁÁÁÁ
ÁÁÁÁÁ
This number: Indicates this fault: Meaning
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Processor Fault
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
A hardware fault was detected in theprocessor. This is a major fault. Return theKFC15/KFCD15 for servicing.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Invalid Firmware
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
The Flash EPROM does not contain validfirmware. New firmware must be downloadedto the unit.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁRAM Fault
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
The static RAM cannot be written to reliably ora parity error has occurred. Cycle power to theKFC15/KFCD15.If the problem persists, return theKFC15/KFCD15 for servicing.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Stuck Button DetectedÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
One or more pushbuttons are stuck on. Thiscould be caused by a mechanical problem withthe buttons, or by an object pressing on thepushbuttons. If the cause is mechanical, theKFC15/KFCD15 should be returned forservicing. Otherwise, remove the pressurefrom the pushbuttons to clear the faultcondition. The KFC15/KFCD15 will continue tocommunicate when this fault is detected, butconfiguration will not be possible.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Flash EPROM WriteFault
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
The Flash EPROM could not be programmedcorrectly during download of new firmware. This is a major fault. Return theKFC15/KFCD15 for servicing.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Flash EPROM MajorFault
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
The module was unable to write the newconfiguration to the Flash EPROM. This is a major fault. Return theKFC15/KFCD15 for servicing.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Flash EPROM MinorFault
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
On power up, the KFC15/KFCD15 detectedinvalid configuration data in the Flash EPROM.The module recovered by writing the factorydefault configuration to the Flash EPROM. Youmust power the module off and back on, andthen reconfigure it. This is not a major fault, but if the problempersists, return the KFC15/KFCD15 forservicing.
6–6 Troubleshooting the KFC15/KFCD15 Module
Publication 1770�6.5.20 - June 1997
Indicates this fault: Meaning
ÁÁÁÁÁ
ÁÁÁÁÁ
This number:
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Power Failure
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
The power supply voltage is below theminimum rating for the KFC15/KFCD15.The module will continue to communicatewhen this fault is detected, but configurationwill not be possible.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Invalid NetworkAddress
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
The chosen network address is greater thanthe highest network address ControlNet isconfigured for.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
A
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁDuplicate NetworkAddress
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
There is a device on the ControlNet networkwith the same address.
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁB
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
UnrecoverableFirmware Error
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
Failed to re�program the boot block of theFlash EPROM. Return the KFC15/KFCD15module for servicing.
If the displays show symbols other than those shown in this chapter,this also indicates that the module is malfunctioning. In this case,contact your A-B representative.
Appendix A
Publication 1770�6.5.20 - June 1997
Product Specifications
RS�232C Interface
• Start Bits 1
• Data Bits 8
• Parity None, Even, Odd
• Stop Bits 1
• Baud Rates 300, 600, 1200, 2400, 4800, 9600,19200, 38400
• Connector DB-25P (male)
• Output RS-232C
• Protocol Allen-Bradley DF1
• Cable Length Recommended maximum of 7.5 m (25 ft)at 38400 baud, or 15 m (50 ft) at lowerbaud rates
• Cable Type Shielded
Parallel Port Interface
• Connector DB-25 (female)
• Data Format DF1 Nibble or DF1 Byte transfers with handshaking
• Cable Length Recommended maximum of 3 m (10 ft)
• Cable Type Shielded
A–2 Product Specifications
Publication 1770�6.5.20 - June 1997
ControlNet Interface
• Connectors Standard BNC Connectors
• Cable RG-6 75-ohm coaxial cable
• Media Redundancy Connection for 2 independent coaxial cables
• Ground Isolation Dual transformers
Network Access Port (NAP) Interface
• Connector RJ-45 8-pin, phone jack with shield
• Ground Isolation Opto-isolated
Electrical
• KFC15 Voltage Selectable 115V ac/230V ac
• KFCD15 Voltage Nominal 24V dcOperating 18V dc to 40V dc
• Frequency 50 Hz/60 Hz
• Power 23 W
• KFC15 Fusing Double-fused -UL 198G and CSA 22.2 No. 59 rated, 5 mm x 20 mm, 0.25 A,250 V fuses
• KFCD15 Fusing 5 mm x 20 mm0.5 A, slow-blow, 250-V fuse
Product Specifications A–3
Publication 1770�6.5.20 - June 1997
Physical
• Dimensions 11.7 cm (4.6 in.) wide x 17.8 cm (7 in.) long x 5.1 cm (2 in.) high
• Weight 0.9 kg (2 lb) approximately
• Mounting Table-top wall/bracket mount
Environmental
• Operating Temperature 0�C to 60�C (32�F to 140�F)
• Storage Temperature -40�C to 85�C (-40� to 185�F)
• Operating Humidity 5% to 95% (non-condensing)
Agency Safety Certification
• CSA CSA C22.2 No. 950 (Canada)“Information Technology Equipment”File # LR 62086CSA 22.2 No. 213 - M1987“Non-Incendive Electrical Equipment for usein Class 1, Division 2 Hazardous Locations”File # LR 62086 (KFCD15 only)
• UL 1950 File # E137331 (KFC15)1950 “Information Technology Equipment”File # E 102275 (KFCD15)
A–4 Product Specifications
Publication 1770�6.5.20 - June 1997
Agency Emissions Certification
• FCC FCC Class A (USA)
• Industry Canada ICES 003, Class A (Canada) – KFCD15
European Union Directive Compliance
The following modules are marked with the
ÎÎÎÎ
ÎÎÎÎ
ÎÎ
ÎÎ mark, indicating
that they are approved for installation within the European Unionand EEA regions: 1770-KFC15 series A, Rev A; and 1770-KFCD15series A, Rev A. These modules have been designed to meet thefollowing directives.
Installation Requirements
If the KFC15/KFCD15 is installed within the European Union orEEA regions, the following regulations apply.
EMC Directive—This product is tested to meet Council Directive89/336/EEC Electromagnetic Compatibility (EMC) and thefollowing standards, in whole or in part, documented in a technicalconstruction file:
• EN 50081-2 EMC – Generic Emission Standard, Part 2 –Industrial Environment
• EN 50082-2 EMC – Generic Immunity Standard, Part 2 –Industrial Environment
The product is intended for use in an industrial environment.
Product Specifications A–5
Publication 1770�6.5.20 - June 1997
Low Voltage Directive—The KFC15/KFCD15 is also designed tomeet Council Directive 73/23/EEC Low Voltage, by applying thesafety requirements of EN 61131-2 Programmable Controllers, Part2 – Equipment Requirements and Tests.
For specific information required by EN 61131-2, see the appropriatesections in this publication, as well as the following Allen-Bradleypublications:
• Industrial Automation Wiring and Grounding Guidelines,publication 1770-4.1
• Automation Systems Catalog, publication B111
Appendix B
Publication 1770�6.5.20 - June 1997
Cabling and Pinouts
This appendix contains the pinout and wiring information required ifyou need to construct cables before installing the KFC15/KFCD15 toa host device.
Cabling and Pinouts for RS�232C Connection
The KFC15/KFCD15 RS-232C connector is a DB-25 male with thefollowing EIA standard pinout:
Signal I/O Pin
GND Chassis ground . 1
TXD Transmitted data O 2
RXD Received data I 3
RTS Request to send O 4
CTS Clear to send I 5
DSR Data set ready I 6
COM Signal common . 7
DCD Data carrier detect I 8
DTR Data terminal ready O 20
The following diagrams illustrate wiring for a three-wire cable and acable with handshaking lines. The maximum recommended cablelengths are:
• baud rates ≤ 19200 15 m (50 ft)
• baud rates = 38400 7.5 m (25 ft)
B–2 Cabling and Pinouts
Publication 1770�6.5.20 - June 1997
Figure B.1 Three Wire Connections to IBM Computers(25�pin)
11008
Shield
TXD 2 3 RXD
1770�KFC15/KFCD15
RXD 3
GND 7
2 TXD
7 GND
Host Computer
1
Figure B.2 Three Wire Connections to IBM Computers(9�pin)
11009
Shield
TXD 2 2 RXD
1770�KFC15/KFCD15
RXD 3
GND 7
3 TXD
5 GND
Host Computer
1
If you require active DSR and CTS signals and you don’t requirehandshaking lines from the KFC15/KFCD15 module, add jumpers tothe computer connections as shown in the next two illustrations.
Figure B.3 Jumper Positions for DSR and CTS Lines (25�pin)
11012
Shield1
TXD 2 3 RXD
1770�KFC15/KFCD15
RXD 3
GND 7
2 TXD
7 GND
Host Computer
4 RTS
5 CTS
6 DSR
8 DCD
20 DTR
Cabling and Pinouts B–3
Publication 1770�6.5.20 - June 1997
Figure B.4 Jumper Positions for DSR and CTS Lines (9�pin)
11013
Shield1
TXD 2 2 RXD
1770�KFC15/KFCD15
RXD 3
GND 7
3 TXD
5 GND
Host Computer
7 RTS
8 CTS
6 DSR
1 DCD
4 DTR
If you are using handshake signals with your computer, use pinoutsas shown in the next two illustrations.
Figure B.5 Connection to IBM Computer with HandshakeSignals (25�pin)
11034
Shield1
TXD 2 3 RXD
1770-KFC15/KFCD15
RXD 3
RTS 4
2 TXD
5 CTS
Host Computer
CTS 5
GND 7
4 RTS
7 GND
DSR 6 20 DTR
DCD 8
DTR 20
6 DSR
8 DCD
B–4 Cabling and Pinouts
Publication 1770�6.5.20 - June 1997
Figure B.6 Connection to IBM Computer with HandshakeSignals (9�pin)
11033
Shield1
TXD 2 2 RXD
1770-KFC15/KFCD15
RXD 3
RTS 4
3 TXD
8 CTS
Host Computer
CTS 5
GND 7
7 RTS
5 GND
DSR 6 4 DTR
DCD 8
DTR 20
6 DSR
1 DCD
The KFC15/KFCD15 module is connected to a modem through theRS-232C serial port.
Figure B.7 Connection between the KFC15/KFCD15 and aModem
11014
Shield1
TXD 2 2 RXD
1770�KFC
RXD 3
RTS 4
3 TXD
4 RTS
Modem
CTS 5
DSR 6
5 CTS
6 DSR
GND 7 7 GND
DCD 8
DTR 20
8 DCD
20 DTR
Cabling and Pinouts B–5
Publication 1770�6.5.20 - June 1997
Cabling and Pinouts for Parallel Port Connection
The parallel port interface connector is a DB-25 female with theCentronics standard pinout shown in the table below. The polarity inthe fourth column applies when a signal is active. Negative polarityindicates an active low signal, while positive polarity indicates anactive high signal.
Signal I/O Pin Polarity
Strobe I 1 -
Data 0 I/O 2 +
Data 1 I/O 3 +
Data 2 I/O 4 +
Data 3 I/O 5 +
Data 4 I/O 6 +
Data 5 I/O 7 +
Data 6 I/O 8 +
Data 7 I/O 9 +
Acknowledge O 10 -
Busy O 11 +
P. End O 12 +
Select O 13 +
Auto Feed I 14 -
Error O 15 -
Initialize Printer I 16 -
Select Input I 17 -
Ground . 18 � 25 .
B–6 Cabling and Pinouts
Publication 1770�6.5.20 - June 1997
The following diagram illustrates the wiring for a cable to connectthe KFC15/KFCD15 to a host computer through the parallel port.A shielded cable must be used.
Figure B.8 Connection to IBM Computer through the ParallelPort (25�pin)
11003
Male DB�25Connectorto 1770�KFC15/KFCD15
- Strobe DB�25Connector toIBM�CompatibleHost Computer
1 1
+ Data 02 2
+ Data 13 3
+ Data 24 4
+ Data 35 5
+ Data 46 6
+ Data 57 7
+ Data 68 8
+ Data 79 9
- Acknowledge10 10
+ Busy
+ P. End11 11
12 12
+ Select13 13- Auto Feed
- Error
14 14
15 15
- Initialize Printer16 16
- Select Input
Ground17 17
18-25 18-25
Appendix C
Publication 1770�6.5.20 - June 1997
DF1 Diagnostic CommandSupport
The information in this appendix deals with DF1 communicationsbetween the host processor and KFC15/KFCD15 module. TheKFC15/KFCD15 module interprets and responds to the followingdiagnostic commands from the host:
Description Command Byte Function Code (hex)
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
Diagnostic Loop ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
06 ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
00
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
Diagnostic Read Counters ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
06 ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
01
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
Diagnostic Status ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
06 ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
03
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
Reset Diagnostic Counters ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
06 ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
07
In the Command and Reply Format tables below, all values are inhex and the following abbreviations are used:
ADDR—address of data to be readCMD—command codeFNC—function codeSTS—status codeTNS—transaction number
C–2 DF1 Diagnostic Command Support
Publication 1770�6.5.20 - June 1997
Diagnostic Loop
You can use this command to check the integrity of the transmissionsover the communication link. The command message transmits up to243 bytes of data to a node interface module. The receiving moduleshould reply to this command by transmitting the same data back tothe originating node.
Table C.A Command Format
1 byte 1 byte 2 bytes 1 byte 243 bytes max
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
CMD06
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
STS ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
TNS ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
FNC00
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
DATA
Table C.B Reply Format
1 byte 1 byte 2 bytes 243 bytes max
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
CMD46
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
STS ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
TNS ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
DATA
Diagnostic Read Counters
This command reads the diagnostic counters from theKFC15/KFCD15 module. The format of these counters is givenbelow. The address and size fields can have any value (but they mustbe included).
Table C.C Command Format
1 byte 1 byte 2 bytes 1 byte 2 bytes 1 byte
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
CMD06
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
STS
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
TNS
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
FNC01
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ADDR0000
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
SIZE00
DF1 Diagnostic Command Support C–3
Publication 1770�6.5.20 - June 1997
Table C.D Reply Format
1 byte 1 byte 2 bytes 16 bytes
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
CMD46
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
STS ÁÁÁÁÁÁ
ÁÁÁÁÁÁTNS ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
DATA
Table C.E Reply Values
ÁÁÁÁ
ÁÁÁÁ
1
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total DF1 packets received, low byte
ÁÁÁÁ
ÁÁÁÁ
2
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total DF1 packets received, high byte
ÁÁÁÁ
ÁÁÁÁ
3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total DF1 packets transmitted, low byte
ÁÁÁÁ
ÁÁÁÁ
4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total DF1 packets transmitted, high byte
ÁÁÁÁ
ÁÁÁÁ
5
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of DF1 retries
ÁÁÁÁ
ÁÁÁÁ6
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of DF1 packets where the retry limit was exceeded
ÁÁÁÁ
ÁÁÁÁ7
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of DF1 NAKs sent
ÁÁÁÁ
ÁÁÁÁ
8
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of DF1 NAKs received
ÁÁÁÁ
ÁÁÁÁ
9
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of DF1 bad messages receivedÁÁÁÁ
ÁÁÁÁ
10
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of RS�232C line errors
11 Total good ControlNet packets received, low byte
12 Total good ControlNet packets received, high byte
13 Total bad ControlNet packets received, low byte
14 Total bad ControlNet packets received, high byte
15 Total ControlNet packets transmitted, low byte
16 Total ControlNet packets transmitted, high byte
C–4 DF1 Diagnostic Command Support
Publication 1770�6.5.20 - June 1997
Diagnostic Status
This command requests a block of status information from anRS-232C device. The reply contains the information in its DATAfield. The status information varies from device to device. The statusblock is shown below.
Table C.F Command Format
1 byte 1 byte 2 bytes 1 byte
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
CMD06
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
STS
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
TNS
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
FNC03
Table C.G Reply Format
1 byte 1 byte 2 bytes 24 bytes
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
CMD46
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
STS ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
TNS ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
DATA
Table C.H Reply Values
Data Byte Description Status Reply
1 Mode/Status Byte 00 (No Modes)
2 Interface/Processor Type Bits 0 � 3: Interface type(E = Extended)Bits 4 � 7: Processor type(F= Computer)
FE (Extended)
3 Extended Interface Type 5F (KFC15) 60 (KFCD15)
4 Online/Offline Mode 0 = online; 1 = offline
DF1 Diagnostic Command Support C–5
Publication 1770�6.5.20 - June 1997
Data Byte Status ReplyDescription
5 Series/RevisionBits 0�4:
Bits 5�7:
0 = Revision A1 = Revision B, etc.0 = Series A1 = Series B, etc.
6 � 16 Bulletin Name = ASCII
�1770�KFC15 "
�1770�KFCD15 "
17 � 24 Reserved for factory use only Values may vary
Diagnostic Counter Reset
This command resets the diagnostic counters listed above.
Table C.I Command Format
1 byte 1 byte 2 bytes 1 byte
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
CMD06
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
STS
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
TNS
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁ
FNC07
Table C.J Reply Format
1 byte 1 byte 2 bytes
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
CMD46
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
STS ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
TNS
Appendix D
Publication 1770�6.5.20 - June 1997
Writing a ParallelCommunication Driver
The KFC15/KFCD15 supports both full-duplex and half-duplex DF1protocol over the RS-232C link. For details of the protocol format,refer to the document Allen-Bradley Data Highway/Data HighwayPlus/DH-485 Communication Protocol and Command Set ReferenceManual (1770-6.5.16).
DF1 Parallel Communication
To communicate over the parallel port between a host computer andthe KFC15/KFCD15 use the link layer protocol of half-duplex DF1.In this setup, the computer is the host device and theKFC15/KFCD15 is the peripheral.
If the host supports bidirectional data on the parallel port you can usethe Byte Transfer Mode. If the host supports output data only on theparallel port use Nibble Transfer Mode.
In Byte Transfer Mode, the host transmits and receives data one byte(eight bits) at a time. In Nibble Transfer Mode, the host transmitsdata one byte at a time, but receives data from the KFC15/KFCD15one nibble (four bits) at a time.
The physical interface consists of eight data lines and ninehandshaking lines. Four of the handshaking lines are controlled bythe host and five by the KFC15/KFCD15. The table below showshow the lines of the parallel port are used for both Byte and Nibblemodes.
D–2 Writing a Parallel Communication Driver
Publication 1770�6.5.20 - June 1997
Pin Pin Notation BYTE Mode NIBBLE Mode
1 Strobe Host Data Clock/
Acknowledge (ACK)
Host Data Clock/
Acknowledge (ACK)
2 Data 0 Data 0 to/from
KFC15/KFCD15
Data 0 to
KFC15/KFCD15
3 Data 1 Data 1 to/from
KFC15/KFCD15
Data 1 to
KFC15/KFCD15
4 Data 2 Data 2 to/from
KFC15/KFCD15
Data 2 to
KFC15/KFCD15
5 Data 3 Data 3 to/from
KFC15/KFCD15
Data 3 to
KFC15/KFCD15
6 Data 4 Data 4 to/from
KFC15/KFCD15
Data 4 to
KFC15/KFCD15
7 Data 5 Data 5 to/from
KFC15/KFCD15
Data 5 to
KFC15/KFCD15
8 Data 6 Data 6 to/from
KFC15/KFCD15
Data 6 to
KFC15/KFCD15
9 Data 7 Data 7 to/from
KFC15/KFCD15
Data 7 to
KFC15/KFCD15
10 Acknowledge KFC15/KFCD15 Data
Clock/
Acknowledge (ACK)
KFC15/KFCD15 Data
Clock/
Acknowledge (ACK)
11 Busy KFC15/KFCD15 Flow
Control
(BUSY)
Data 3/Data 7/BUSY
from KFC15/KFCD15
12 P. End KFC15/KFCD15 End of
Transmission (EOT)
Data 2/Data 6/EOT from
KFC15/KFCD15
13 Select Data 1/Data 5 from
KFC15/KFCD15
14 Auto Feed Host Flow Control
(BUSY)
Host Flow Control
(BUSY)
15 Error KFC15/KFCD15 End of
Transmission (EOT)
Data 0/Data 4/EOT from
KFC15/KFCD15
16 Initialize
Printer
Host Initialization of
KFC15/KFCD15 (INIT)
Host Initialization of
KFC15/KFCD15 (INIT)
Writing a Parallel Communication Driver D–3
Publication 1770�6.5.20 - June 1997
Pin NIBBLE ModeBYTE ModePin Notation
17 Select Input Host Transmit Control
(Host/KFC15/KFCD15)
Host Transmit Control
(Host/KFC15/KFCD15)
18�25 Ground Ground Ground
The host communication software must turn on pin 17 (HostTransmit Control) to transmit data and reset it to receive data fromthe KFC15/KFCD15 module. Every byte transmitted to theKFC15/KFCD15 module must be clocked with a positive transitionon pin 1. Every byte or nibble sent from the KFC15/KFCD15module must be clocked with a positive transition on pin 10.
The status indicators signify the following:
BUSY—a device is busy processing
EOT—a device has completed transmission
ACK —a transmission has been received
To reset parallel communications at any time, the host should resetpin 14 (Auto Feed) and set its data clock (pin 1). Then, the hostdevice follows by resetting both pin 17 (Select Input) and pin 16(Initialize Printer). The KFC15/KFCD15 module shouldacknowledge by resetting its Busy and its Acknowledge lines.
The host should set Busy whenever it is reading a byte or nibble sentto it from a KFC15/KFCD15 module, resetting it when ready for thenext piece of the DF1 message.
D–4 Writing a Parallel Communication Driver
Publication 1770�6.5.20 - June 1997
In Nibble mode, receiving data from the KFC15/KFCD15 module isa little more complex. The lower nibble of a byte is sent first, thenthe upper nibble on the next data block. After the host acknowledgesthe upper nibble, the KFC15/KFCD15 acknowledges by setting thedata clock (pin 10) high. At this point, the status indicators Busy (pin11) and EOT (pins 12 and 15) from the KFC15/KFCD15 can be readby the host device. The status indicators are overwritten with thenext piece of data when the host Busy pin is reset.
Data Transmission
The following describes the actions that should be taken by both thehost and KFC15/KFCD15 to send and transmit data. Note that 1means logical 1 or high, regardless of whether or not the signal isnormally active high or active low.
On power up, the host should do the following to initializecommunication:
1. Set pin 1 (Strobe) to 1 and pin 14 (Auto Feed) to 0.
2. Set pin 17 (Select Input) and pin 16 (Initialize Printer) to 0. Thesetwo lines must be be held low for a minimum of 50 ms to allowthe KFC15/KFCD15 to detect them.
To send data from the host computer to the KFC15/KFCD15 the hostshould:
1. Set pin 17 (Select Input) and pin 16 (Initialize Printer) to 1.
2. Check that the KFC15/KFCD15’s pin 11 (Busy) is set to 0.
3. Place data on the data lines.
4. Set pin 1 (Strobe) to 0 then 1.
Writing a Parallel Communication Driver D–5
Publication 1770�6.5.20 - June 1997
To receive data from the host, the KFC15/KFCD15:
1. Sets pin 11(Busy) to 1.
2. Reads data.
3. Sets pin 10 (Acknowledge) to 0 then 1.
4. Sets pin 11 (Busy) to 0.
At this point if the host has more data to send, it can repeat the aboveprocedure until the entire packet is sent. Then, if data is expectedfrom the KFC15/KFCD15, the host should set pin 17 (Select Input)to 0 to enter either Byte or Nibble mode.
Data Transfer in Byte Mode
To send data in Byte mode from the KFC15/KFCD15 to the host, theKFC15/KFCD15:
1. Checks that the host’s pin 14 (Auto Feed) is set to 0.
2. Places data on the data lines.
3. Sets pin 10 (Acknowledge) to 0 then 1.
To receive data in Byte mode, the host:
1. Sets pin 14 (Auto Feed) to 1.
2. Reads the data.
3. Sets pin 1 (Strobe) to 0 then 1.
If there is more data to send, the KFC15/KFCD15:
� Sets pin 15 (Error) and pin 12 (P. End) to 0.
and the host should:
� Set pin 14 (Auto Feed) to 0, then repeat its receive procedure.
D–6 Writing a Parallel Communication Driver
Publication 1770�6.5.20 - June 1997
If there is no more to send, the KFC15/KFCD15:
1. Sets pin 15 (Error) and pin 12 (P. End) to 1.
2. Sets pin 10 (Acknowledge) to 1.
and the host sets pin 17 (Select Input) to 1.
Data Transfer in Nibble Mode
To send data in Nibble mode from the KFC15/KFCD15 to the host,the KFC15/KFCD15:
1. Checks that the host’s pin 14 (Auto Feed) is set to 0.
2. Places the lower nibble on the handshaking lines.
3. Sets pin 10 (Acknowledge) to 0 then 1.
To receive the lower nibble, the host:
1. Sets pin 14 (Auto Feed) to 1.
2. Reads the data.
3. Sets pin 1 (Strobe) to 0 then 1.
4. Sets pin 14 (Auto Feed) to 0.
To send the upper nibble, the KFC15/KFCD15:
1. Checks that the host’s pin 14 (Auto Feed) is set to 0.
2. Places the upper nibble on the handshaking lines.
3. Sets pin 10 (Acknowledge) to 0 then 1.
Writing a Parallel Communication Driver D–7
Publication 1770�6.5.20 - June 1997
To receive the upper nibble, the host:
1. Sets pin 14 (Auto Feed) to 1.
2. Reads the data.
3. Sets pin 1 (Strobe) to 0 then 1.
At this point the KFC15/KFCD15 sets pin 11 (Busy) to 0. Thiscompletes the transmission of one byte. If there is more data to send,the KFC15/KFCD15:
� Sets pin 15 (Error) and pin 12 (P. End) to 0.
and the host:
� Sets pin 14 (Auto Feed) to 0, then repeats its receive procedure.
If there is no more to send, the KFC15/KFCD15:
1. Sets pin 15 (Error) and pin 12 (P. End) to 1.
2. Sets pin 10 (Acknowledge) to 1.
and the host sets pin 17 (Select Input) to 1.
Numbers
1770�KFC15/KFCD15Communication Interface. See
KFC module
A
ACK, D-3See also Acknowledge
Acknowledge, D-2
advanced parametersconfiguring, 4-8description, 4-9
B
basic parameters, description, 4-6
BUSY, D-3
Byte Transfer Mode, D-1, D-5
C
cablingparallel port, B-5RS�232 connection, B-1
command support, DF1 diagnostic, C-1
communication parameters, 4-1advanced, 4-8basic, 4-4changing, 4-1configuring, 4-2, 4-4
communication protocolmaintenance transmission, 1-2
overview, 1-2scheduled data, 1-3scheduled tranmissions, 1-2unscheduled data, 1-3unscheduled transmissions, 1-2
configurationdisplays, 4-2overview of procedures, 4-1
configuration mode, KFC, 4-1
ControlNet, P-3communication protocol, 1-2connecting to, 3-7network architecture, 1-1, 1-3overview, 1-1
D
Data Highway Plus. See DH+
data transfer mode, 4-6byte, 1-4nibble, 1-4
DF1, P-3, 1-4, 2-3, 3-3diagnostic command support,
C-1diagnostic counter reset, C-5
command format, C-5reply format, C-5
diagnostic loop, C-2command format, C-2reply format, C-2
diagnostic read counters, C-2command format, C-2reply format, C-3reply values, C-3
diagnostic status, C-4command format, C-4
Index
IndexI–2
reply format, C-4
DF1 communication, 5-1
DF1 Parallel Communication, D-1data transmission, D-4initialize communication, D-4
DF1 port, 4-6
DH+, P-3, 1-1
E
EOT, D-3
F
factory defaults, setting, 4-13
flashing LED, 6-2
flickering, 6-2
full duplex, P-3serial protocol, 5-2setting, 4-6
H
half duplex, P-3parallel protocol, 5-4serial protocol, 5-2setting, 4-6
host cable system, planning, 1-3
Host Data Clock, D-2
I
invalid firmware, 6-5
K
KFC15/KFCD15 Data Clock, D-2
KFC15/KFCD15 moduleattaching to wall or mounting
bracket, 3-9compatibility, 2-4configuration
exit without saving, 4-12saving, 4-10
configuration mode, 4-1configuration overview, 4-1configuring basic parameters,
4-5configuring with pushbuttons,
4-4connecting to ControlNet, 2-2,
3-7connecting to end device, 1-3installation overview, 3-2overview, 2-1pushbuttons, 4-3related products, P-2run mode, 4-1setting factory defaults, 4-13
L
LED displayscommunication, 6-1ControlNet, 6-1description, 6-3flashing, 6-2interpreting, 6-1railroad, 6-2solid, 6-2status, 6-1
LEDsdisplaying basic parameters, 4-5function, 2-3
N
NAP, P-3, 2-3
Index I–3
NAP connection, 3-5cable requirements, 3-5
network, P-3
network access port. See NAP
network address, P-4, 2-4, 4-6
network architecture, 1-1, 1-3
network update time. See
Nibble Transfer Mode, D-1, D-6
node, P-4
numeric displaysdescription, 6-5interpreting, 6-4
NUR, 1-2maintenance portion, 1-2scheduled data, 1-3scheduled portion, 1-2unscheduled data, 1-3unscheduled portion, 1-2
NUT, P-4
P
parallel port, P-4, 2-3activity indicator, 3-4
parallel port connection, 3-4cable requirements, 3-4cabling, B-5connector, 3-4half duplex, 1-4pinouts, B-5planning, 1-4
PCCC, P-4, 5-1
pinoutsparallel, B-5serial port, B-1
primary connection, 6-1
processor fault, 6-5
product specificationsagency emissions certification,
A-4agency safety certification, A-3ControlNet interface, A-2electrical, A-2environmental, A-3NAP interface, A-2parallel port interface, A-1physical, A-3RS�232C interface, A-1
programmable controllercommunicaitons commands.See PCCC
pushbuttonsconfiguring the KFC module,
4-4DATA, 4-3EXIT, 4-3operation, 4-3VIEW, 4-3
R
raildroad LED, 6-2
RAM fault, 6-5
redundant connection, 6-1
redundant media, 2-2, 3-8
Remote Input/Output. See RIO
repeater, P-4, 1-1
RIO, P-4, 1-1
RS�232, baud rate, 4-6
RS�232 port, 2-3activity indicator, 3-3baud rates, 3-3
RS�232C port. See RS 232 port
run mode, KFC, 4-1
IndexI–4
S
scheduled data, 1-3
segment, P-4, 1-1, 3-8
serial communication, 5-2
serial port, P-5See also RS 232 port
serial port connection, 3-3cable requirements, 3-3cabling, B-1connector, 3-3half duplex, 1-5, 1-6pinouts, B-1planning, 1-5
solid LED, 6-2
Strobe, D-2
subnet, P-5, 1-1
T
tap, P-5
terminator, P-5
troubleshooting, 6-1
trunkline, P-5section, P-5
U
unscheduled data, 1-3
1784�6.5.19�RN1October 1995
Worldwide representation.
Argentina • Australia • Austria • Bahrain • Belgium • Brazil • Bulgaria • Canada • Chile • China, PRC •Colombia • Costa Rica • Croatia • Cyprus • Czech Republic • Denmark • Ecuador • Egypt • El Salvador •Finland • France • Germany • Greece • Guatemala • Honduras • Hong Kong • Hungary • Iceland • India •Indonesia • Ireland • Israel • Italy • Jamaica • Japan • Jordan • Korea • Kuwait • Lebanon • Malaysia •Mexico • Netherlands • New Zealand • Norway • Pakistan • Peru • Philippines • Poland • Portugal •Puerto Rico • Qatar • Romania • Russia-CIS • Saudi Arabia • Singapore • Slovakia • Slovenia • South
Africa, Republic • Spain • Sweden • Switzerland • Taiwan • Thailand • Turkey • United Arab Emirates •United Kingdom • United States • Uruguay • Venezuela • Yugoslavia
Allen�Bradley Headquarters, 1201 South Second Street, Milwaukee, WI 53204 USA, Tel: (1)
414 382�2000 Fax: (1) 414 382�4444
Publication 1770�6.5.20 - June 1997 PN 956119�02Copyright 1997 Allen�Bradley Company, Inc. Printed in Canada