Networking Essentials Version1 04

Networking Essentials
Version: 1
2004, TAC
All Rights Reserved
No part of this publication may be reproduced, read or stored in a retrieval system, or transmitted, in
any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without
prior written permission of TAC.
Produced in the United States of America.
Infinity is a trademark of TAC. All other trademarks are the property of their respective owners.
Continuum Networking Essentials
January, 2004
TAC Part Number: 31-3001-763 Version: 1
The information in this document is furnished for informational purposes only, is subject to change
without notice, and should not be construed as a commitment by TAC. TAC assumes no liability for
any errors or inaccuracies that may appear in this document.
TAC
1 High Street
N. Andover, MA 01845
(978) 470-0555
fax: (978) 975-9797
www.tac.com
Content
Ch 01: Introduction to Networking
Ch 02: BACnet Basics
Ch 03: Ethernet
Ch 04: TCP/IP
Ch 05: Continuum IP
Ch 06: BACnet IP
Ch 07: RS-485
Ch 08: Infinet
Ch 09: Continuum IO Bus
Ch 10: MS/TP
TAC
Networking Essentials
Ch 1
Introduction to
Networking
Contents
Introduction
Data Communications
LANs
Hardware
Cables & Connectors
Full / Half Duplex
Drivers / Receivers / Transceiver
Base / Broad Band
Repeaters / Hubs
Topologies
Propagation Delay
Packets & Protocols

Packets / CRC / Segmentation
ACK (Acknowledged) & NACK (Unacknowledged)
Point-to-Point Vs. Broadcast / Multicast
Source / Destination
Logical Vs. Physical Addressing
Protocols
OSI Model
Seven Layers
1-2
Introduction to Networking
Introduction
Data Communications
The need for data communications is important to any technology that utilizes
distributed computer systems that need to share information.
Data is stored within a computer as a series of electrical signals that represent one of
two possible states, referred to as binary digits or bits.
A conversion between how the computer represents the data and how the data needs
to be represented for successful transmission is always needed. This is due to the fact
that the characteristics and requirements of a computer's internal data representation
and communications differ from that required for computer-to-computer
communications.
There are two methods in which data can be transmitted:
Parallel
Serial
Parallel:
Parallel communications is when data is distributed via multi-conductor paths. It is
used internal to computers and also within short distances such as to a local printer
through a computers parallel port.
The number of wires in the path are usually equal to at least the number of bits that
the computer can manipulate at one time (often called word size).
For example, bit one is communicated via conductor one, bit two via conductor two,
etc.
TAC
1-3
Introduction
Data Communications
Serial:
Serial communications is when data is distributed over longer distances such as a
LAN and is placed on the media one bit at a time.
The physical cabling over which data is transferred is called the communications
media.
Typical communications media types are:
Shielded Twisted Pair wire
Un-shielded Twisted Pair wire
Coaxial cable
Fiber Optic cable
Wire pairs are inherently noise immune if twisted or in a coaxial form. Parallel Word
Bits are placed on the medium one at a time in a serial fashion. The device that
performs this task is called a serial interface.
A serial interface also needs to perform some other important tasks:
1. Convert the rate at which the computer internally transmits bits to that
compatible with the medium.
2. Convert the bits into signals compatible with the medium.
3. Signal the receiving computer so that it is prepared to receive the data.
1-4
Introduction
Data Communications
Serial:
The effective operation of an Energy Management and Control System (EMCS)
depends on the ability of the various system components to communicate with one
another rapidly and reliably.
As the number of sensors and control points increases:
The speed of data transmission must be increased

or
Intelligence, i.e., computing capacity must be more widely distributed

throughout the system.
Three aspects of the data communications problem represent the communications

protocol and determine the degree to which components of one system may be
interfaced to components of another system.
1. The physical connection, or link, and the methods of controlling the end-to-end
error-free transmission of information along it
2. The encoding of the message data
3. The content and structure of the messages themselves
TAC
1-5
Introduction
Data Communications
Serial:
The types of tasks usually involved in the layers of a communication's architecture
include:
Error Control - Detecting data errors and repairing them
Segmentation - Breaking blocks of data into pieces that can be handled by the
communications system
Flow Control - Controlling transmitted data so that the receiver is not

overwhelmed with data at a rate at which it cannot be processed
Ordered Delivery - Delivering blocks of data in the proper order
Headers - Accompanying data with address and identification information (in

a header) so that the correct receiver knows that the data is being sent to it and
what the receiver should do with the data
The specific approaches chosen to perform the above tasks, along with the physical
media used and the application services provided, defines the system's
communications protocol.
These tasks have the goal of reliably encoding application data and services to bits
that can be communicated over the media and decoded so that the receiver gets the
message intended.
The more thoroughly the above tasks are handled, the more of the system's bandwidth
is taken up in the form of overhead with a commensurate reduction in the throughput
of data. Therefore no one communications protocol can meet all communications
needs.
The layered architecture approach to a protocol can provide choices at each layer to
allow the protocol to meet different needs.
1-6
Introduction
LANs
A local area network (LAN) is a group of computers and associated devices that share
a common communications line or wireless link and typically share the resources of a
single processor or server within a small geographic area (for example, within an
office building).
Usually, the server has applications and data storage that are shared in common by
multiple computer users. A local area network may serve as few as two or three users
(for example, in a home network) or as many as thousands of users (for example, in
an FDDI network).
The main local area network technologies are:
Ethernet
Token Ring
ARCNET
FDDI (Fiber Distributed Data Interface)
A LAN is the perfect method for connecting;
Building Automation Systems
Process Control Systems
Security System
All devices on a LAN share the transmission path, meaning that only one device can
be transmitting information at a time. If two or more devices transmit
simultaneously, the electrical signals will collide and destroy the data contents.
TAC
1-7
Hardware
Cables & Connectors
There are three basic cable types used in Ethernet networking:
1. Twisted Pair
- Shielded
- Unsheilded
2. Coaxial
- Thinnet
- Thicknet
3. Fiber Optic
Twisted Pair
Twisted Pair cable use pairs of wires that are twisted around one another. Each pair
consists of two insulated copper wires twisted together. The wire pairs are twisted
because it helps reduce cross-talk and noise susceptibility.
High quality twisted pair cables have about 1 to 3 twists per inch. For best results,
the twist rate should vary significantly between pairs in a cable.
1-8
Hardware
Cables & Connectors
Shielded Twisted Pair (STP)
Twisted pair cable that contains a foil shield along with a shield (drain) wire.
The shielded wire (drain wire) must be grounded on one end only.
The shielding is designed to minimize EMI radiation and susceptibility to crosstalk.
Foil Shield
Drain Wire
Shielded Twisted Pair Cable
Unshielded Twisted Pair (UTP)

Twisted pair cable that contains no shield.
Unshielded Twisted Pair Cable
TAC
1-9
Hardware
Cables & Connectors
RJ-45 Connector
An RJ-45 connector has 8-pins, and may also be referred to as an "8-pin Modular
Connector".
A male RJ-45 plug is mounted on each end of Twisted Pair cable.
A female RJ-45 jack or "receptacle" is integrated into an Ethernet Hub or
Network Interface Card (NIC).
Twisted Pair cable
RJ-45
plug
RJ-45 Connector
D Style Connectors
These connectors are available in different sizes and pin-outs, which can be used
with Unshielded Twisted Pair cable.
15 Pin AUI D style Male Connector
1-10
Hardware
Cables & Connectors
Proprietary Connectors
A plug-in screw terminal type connector used with Shielded Twisted Pair cable.
They are available in different sizes.
TAC
1-11
Hardware
Cables & Connectors
Coaxial Cable
Coaxial cable is a type of cable in which a solid center conductor is surrounded by
an insulating spacer, which in turn is surrounded by a tubular outer conductor
(usually a braid, foil or both). The entire assembly is then covered with an
insulating and protective outer layer.
Coaxial cables have a wide bandwidth and are capable of carrying many data,
voice, and video conversations simultaneously.
The characteristics of a coaxial cable are:
Low attenuation loss at high frequencies produce a wide bandwidth
Shield conductor minimizes electromagnetic interference (EMI)
Thinnet Coax - A 50-ohm "thin" (5mm) coaxial cable.
Thinnet Coaxial Cable
BNC Connector
A British Naval Connectors (BNC), used with Thinnet cabling.
BNC style connector
1-12
Hardware
Cables & Connectors
Fiber Optic Cable
Fiber optic cabling is a technology where electrical signals are converted into
optical signals, transmitted through a thin glass fiber, and re-converted into
electrical signals.
Fiber optic cable is constructed of 3 concentric layers:
1. The core is the central region of an optical fiber through which light is
transmitted.
2. The cladding is the material in the middle layer. It has a lower index of
refraction than the core, which serves to confine the light to the core.
3. An outer "protective layer", or buffer, serves to protect the core and
cladding from damage.
Fiber Optic Cable
TAC
1-13
Hardware
Cables & Connectors
Fiber Optic Cable cont
Multi-mode Fiber
Multi-mode fiber optic cable allows many "modes", or paths, of light to propagate
down the fiber optic path.
The relatively large core of a multi-mode fiber allows good coupling from
inexpensive LEDs light sources, and the use of inexpensive couplers and
connector.
Two types of multi-mode fiber exist with a refractive index that may be graded or
stepped:
With graded index fiber the index of refraction of the core is lower
toward the outside of the core and progressively increases toward the
center of the core, thereby reducing modal dispersion of the signal.
With stepped index fiber the core is of uniform refractive index with a
sharp decrease in the index of refraction at the core-cladding interface.
Stepped index multi-mode fibers generally have lower bandwidths than
graded index multi-mode fibers.
Graded and Stepped Fiber Optic Cables
1-14
Hardware
Cables & Connectors
Fiber Optic Cable cont
Multi-mode Fiber cont
You can use three types of fiber optic cable for data communications. The
diameter of the core and the diameter of the cladding define each type:
62.5/125 microns
50/125 microns
100/140 microns
62.5/125 Fiber:
Recommended for your applications and the most frequently used
The basis of all specified distance limits that are published for Infinity
fiber optic networks
ST & SMA Connectors

Used with multimode fiber optic cable.
ST Style
TAC
SMA Style
1-15
Hardware
Cables & Connectors
Fiber Optic Budget
Every fiber optic communications device has an associated fiber budget.
A fiber budget is the total amount of signal loss (light) that can occur between the
transmitter and the receiver.
Fiber Optic signal loss (light) is measured in decibels (dB).
Light Loss for 62.5/125 Fiber = 1.2 dB/1000 ft
Note:
The recommended 62.5/125 fiber optic cable functions properly with up to 10 dB
of signal loss. If this limit is exceeded, Andover Controls cannot guarantee
proper operation.
In general, fiber budgets for Fiber Optic Communication Devices range between
10-12 dB of signal loss.
Each subsequent connection increases the amount of light loss.
1-16
Hardware
Half & Full Duplex
The term Duplex means that communications can travel in two directions (to and
from).
Simplex means that communications can travel in only one direction. A TV
transmission is considered as simplex communications, where the signal is traveling
in only one direction.
Half Duplex
Half Duplex is communications in both directions, but only one direction at a time.
A conversation between two people is considered to be Half Duplex communications,
where person 1 would talk and person 2 would listen and then person 2 talks while
person 1 listens.
Full Duplex
Full Duplex is communications in both directions and both directions can happen at
the same time.
Note: Some communication types support Full Duplex, others support Half
Duplex and some can utilize both types.
TAC
1-17
Hardware
Drivers / Receivers / Transceivers
The driver puts the signal on the wire and the receiver takes the signal off of the wire.
Both are doing a conversion from whatever signaling method is used on the wire to a
digital logic level that can be interoperated by the microprocessor.
Some communication systems use Drivers and Receivers and others use Transceivers,
one placed at each end.
Drivers, Receivers and Transceivers are hardware level devices (layer 1 of the OSI
model) independent of what type of protocol is being used.
Driver
A Driver is an electronic device that converts Transmitting Data Signals from a
digital level to whatever type of signal is used to transmit the information across the
wire. A driver can be perceived as the talking device.
Receiver
A Receiver is an electronic device that receives data that was sent by the driver and
converts that data back to a standard digital signal level. A receiver can be perceived
as the listening device.
Transceiver
A Transceiver is a single device that acts as both a driver and a receiver. Depending
on the network type, the transceiver may be able to communicate in both directions at
the same time or only one direction at a time.
1-18
Hardware
Drivers / Receivers / Transceivers
The Concept Using Drivers & Receivers

Driver
TD
Receiver
The driver converts a

digital signal to a signal
that is supported on that
network
The supported signal

traveling on the network
The receiver converts the

supported signal for that
network back to a digital
signal
Receiver
RD
RD
Driver
TD
The same process occurs in both directions
The Concept Using Transceivers
Transceiver
Transceiver
TD
TD
RD
The transceiver converts a

digital signal to a signal
that is supported on that
network
TAC
T
The supported signal
traveling on the network
RD
The transceiver converts

the supported signal for
that network back to a
digital signal
1-19
Hardware
Baseband / Broadband Networks
Baseband - A transmission method in which the entire bandwidth of the
transmission medium is used to transmit a single digital signal. The signal is driven
directly onto the transmission medium without modulation of any kind
The transmission of either analog or digital signals over the medium without
modulating a carrier.
One message is sent at a time over the network.
The characteristics of baseband are:
Digital signaling
Original signal is transmitted, no modulation is involved
Transmission distances of a few kilometers
Passive media coax or twisted pair
Bus connections easily made
Simplified maintenance
Lower cost
Broadband - A transmission method where signals are modulated into noninterfering frequencies before being sent over the cables so that many signals can be
sent at once.
Broadband is a transmission facility having a bandwidth sufficient to carry

multiple voice, video or data channels simultaneously.
Each channel occupies (is modulated to) a different frequency bandwidth on

the transmission medium and is demodulated to its original frequency at the
receiving end.
Channels are separated by "guardbands" (empty spaces) to ensure that each

channel will not interfere with its neighboring channels
The characteristics are:
1-20
Uses CATV components: Coax and Modems

High transmission rates
RF transmission yield high noise immunity
Difficult to engineer network
Frequency modulation allows for multiple channels
Each node requires costly interface
Hardware
Repeaters / Hubs
Repeater
A repeater is a device that amplifies an electronic signal so it can travel further down
the cabling. This allows for longer cable runs, extending the specified limitation
required.
Hub
A hub is a device that has two functions on the Ethernet:
TAC
Retransmit messages to every node on the network
Isolates network nodes so that a fault on a node or cable does not effect the
rest of the network (each node connects to a single port on an active hub)
1-21
Hardware
Topologies
A Topology is the physical layout of the network hardware.
The topology governs how nodes are arranged and connected.
There are two topologies that Andover Controls supports:
Bus
Star
* Ring
A Hybrid is a combination of topologies

Different networks discussed support different sub-sets of these topologies.
* Not all networks support all topologies.
Bus (Point-to-Point)
All devices are connected to a single common coax cable (communications link)
using Tee connectors.
Any computer on the network can talk as long as no other computer is talking.
The more computers that are talking on a bus, slows down the overall performance of
that network.
A bus sends each message to all nodes at once. This system of transmission is called a
broadcasting system.
If one node powers down, the rest of the network is un-effected.
A bus network can be extended beyond its limitations with the use of repeaters.
Vulnerability Failure of the bus will bring down the entire network. Failure of a
single workstation will not usually affect the entire network.
1-22
Hardware
Topologies cont
Star
All computers on the network connect to a central hub.
If the central hub goes down, all nodes attached to that hub stop communicating.
The failure of one node does not usually affect the rest of the network.
Idealized Star Topology Network
Star networks seldom have a symmetrical

shape in which the hub is located an equal
distance from each computer. The hub often
resides in a location separate from the
computers that are attached to it
In a star topology contention rules dictate that only one station can talk at any given
time and any station may talk providing the network is quiet. This access method
eliminates the need for pooling and vastly improves throughput and performance.
Hubs can be expanded to handle hundreds of devices without performance
degradation. Expansion is easily accomplished by simply plugging in a connection at
the concentrator.
Vulnerability Failure of the hub can bring that section of the network down. Some
manufacturers allow for redundant backup of the hub and multiple loads sharing
power supplies to eliminate a single point of failure. The failure of a node will not
normally affect network operation.
TAC
1-23
Hardware
Topologies cont
Hybrid
A Hybrid network is a combination of topologies.
Hybrid networks may use a combination of point-to-point and multi-point connection
techniques.
Hybrid Network - Combining Bus and Star Topologies
* Ring
Very few network types support Ring Topologies
Ring Topology
1-24
Hardware
Propagation Delay
Propagation Delay is the amount of time it takes a signal to get from point A to point
B.
The following contribute to Propagation Delay:
The time it takes for the signal to go down the wire
Passing through a communications device like a repeater
The longer the cable segments and the more devices on the network, the longer it
takes for a signal to propagate from one end of the network to the other.
The time it takes a signal to travel between the two stations that are furthest apart in
the network is known as the maximum "propagation delay" of the network.
Delays vary depending on the installed hardware. Delays associated with wire differ
from delays associated with fiber optic:
Twisted Pair = 1.7 microseconds / 1000 ft
Fiber Optic = 1.5 microseconds / 1000 ft
Propagation Delays significantly impact a network when:
TAC
Attempt to run long distances
1-25
Packets & Protocols

Packet
A packet is a message that is being sent across a wire from one device to another.
A packet contains a To (Destination) and a From (Source), as well as the

Communications Message being sent.
Packets are defined by:

-
The physical type of network
The protocol used
A combination of both the physical type and the protocol
CRC (Cyclic Redundancy Check)

A CRC is a detailed calculation performed on the data within the packet.
A mathematical calculation is performed on each packet and the result of the
calculation is placed at the end of the packet.
The end of a packet may contain a (CRC) Cyclic Redundancy Check
The Sending Device:
Calculates the CRC as its sending the data out and places the result at the end
of the packet
The Receiving Device:
1-26
Performs the same calculation, and compares its result with the result that was
placed on the end from the sender.
If the results match, it is accepted as a good packet
It the results do not match, the packet is rejected
Packets & Protocols

Segmentation
The physical type of network and/or the protocol determines what the maximum size
of a packet can be.
At times messages need to be sent that are larger than the maximum packet size.
If messages are larger than the packet size, they will have to be sent out in a
segmented method where the packet does not contain the entire message but only a
segment of the total message. This is common procedure when computers are sending
large files across the network.
The Segmenting Process:

The first packet sent will indicate that the message is only segment 1 of 15 segments.
The second package will indicate segment 2 of 15, etc until all the packets are
received.
When all the packets are received, the receiving device will assemble all of the 15
segments into one complete packet.
Not all Protocols Support Segmentation

Infinet does not require segmentation because all the messages are small in size
TAC
1-27
Packets & Protocols

(ACK) Acknowledged Vs. (NACK) Unacknowledged
Packets are sent as either acknowledged (ACK) or unacknowledged (NACK)
messages.
1-28
ACK: An acknowledged (ACK) message requires a receipt (an actual

message coming back saying that yes I received that correctly or no I did not
receive that correctly). When CRCs are used and the message is received
correctly, the receiving device calculates the same CRC value as the sending
device and will send back an acknowledgement that the message was received
correctly.
NACK: If it is not received correctly, it will send out a negative

acknowledgement (NACK). If a NACK is received, the sending device will
resend the packet. The protocol defines how packets are handled.
Packets & Protocols

Point-to-Point Vs. Broadcast / Multicast
When data communications is sent across the wire some messages will go out as a
broadcast message and others will go out as point-to-point.
Broadcast / Multicast Messages are sent to all devices on the network
Point-to-Point Messages are sent to a specific device on the network
On certain networks, even though the message is going out as a broadcast/multicast,

there may still be within the message, a logical addressing that is still point-to-point.
Source & Destination

Every message that is sent across a network contains a source and destination.
The source and destination will be the address of the device thats sending (source)
and the address of the device thats receiving (destination).
Logical Vs. Physical Addressing

On some networks the address is a physical address and on other networks they are
logical addresses.
Physical Address: A hard-coded number that comes from the manufacturer

An internal NIC card in a computer has a physical
address burned into its chip
Logical Address: An assigned number to a computer
TCP/IP uses a logical address. The IP address is not burned into the Ethernet card but
rather assigned to a computer making it a logical address.
When sending a message from a computer, it is going out with a physical address
(from the network card physically located on the computer) and a logical address
(from the IP address assigned to the computer).
Logical Addressing is handled at the Protocol Layer
TAC
1-29
Packets & Protocols

Protocols
A Protocol is a set of rules that are recognized by two or more devices so they can
communicate with each other through a medium.
There are different types of protocols that are used for networking such as:
TCP/IP: The most widely used protocol suite because of Internet support
NetBEUI: A non-routable protocol developed by IBM
DLC: A protocol used to connect main-frame hosts
NWLink: A Microsoft developed protocol
Protocols define issues like:
Where and how to send messages
How to reply to a message
The way messages are packaged and unpacked
The accuracy of message delivery (error checking)
Flow control (managing who talks and when)
Keeping track of the quality and usability of network links
Without a common shared protocol between two devices, these devices would not be
able to communicate with one another.
1-30
OSI Model
In recognition of both the need for communications standards and the need for a
layered architecture, the ISO (International Organization for Standardization)
developed a standard in 1984 defining a model for a general purpose data
communications architecture.
The model is called the Open Systems Interconnection Basic Reference Model [ISO
7498] or OSI Model and contains seven layers that represent the categories of logical
functions involved in data communications.
The OSI model is a standard tool that displays how network

communications are structured and how they behave.
TAC
1-31
OSI Model
The OSI Model consists of seven layers (working from the bottom up):
Physical Layer (1):

This is the layer where the network hardware operates. Rules for this layer govern:
Types of connectors used
Types of signaling techniques for carry data across the network
Types of cable or other networking media that the physical part of the network
uses
In a sense, this is the only part of the OSI model you can actually see and touch.
Data Link Layer (2):

This layer handles communications with the network hardware.
For outbound messages, the Data Link layer enables the conversion of the bits
that computers use to represent data into equivalent signals needed to move
data across the network.
For inbound messages, it reverses the process by enabling the conversion of

signals into their equivalent bits.
The Data Link layer is also where low-level hardware addresses for individual
network interface cards (NICs) and other devices are handled.
Network Layer (3):

This layer routes the messages between senders and receivers. It handles translation
between human-readable network addresses and computer-readable network
addresses (which are not the same as the hardware addresses that the Data Link Layer
handles).
Each message that passes through this layer includes the senders and receivers
addresses in order to identify the parties involved. The Network layer moves data
from sender to receiver when they arent both attached to the same cable segment.
1-32
OSI Model
Transport Layer (4):
This layer chops up large messages into so called Protocol Data Units (PDUs), or
packets, and sends them across a network. It also puts PDUs back together to
reconstitute messages upon receipt. The Transport layer can also include data
integrity checks by adding a bit pattern to each message based on a mathematical
calculation before sending. This same calculation is repeated by the sender, and the
result is compared to the value calculated beforehand. If both values agree, the
Transport layer assumes the transmission was accurate and correct; if they dont
agree, the Transport layer requests the PDU be re-sent. This integrity function is
optional; therefore, some Transport layer protocols include an integrity check,
whereas other such protocols dont.
Session Layer (5):

This layer sets up ongoing network conversations (called sessions) between sender
and receiver. This kind of ongoing connection makes it easier for computers to
exchange large amounts of data, or to make a connection when data moves regularly
between both parties to a session. Therefore, the Session layer handles session setup
(which is just like dialing a phone), session maintenance (just like a phone
conversation), and session termination or teardown (which is just like ending a phone
conversations and then hanging up the phone).
Presentation Layer (6):

This layer converts data for network delivery. The assumption that drives this
activity is that the sender and receiver may not share a common set of data
representations. Therefore, the Presentation layer converts data from formats created
by the sender into a generic format for network transit and then converts that generic
form into a format specific to the receiver upon delivery, This conversion process
allows programmers on both sides of the network connection to assume generic
formats for network data, and the handle the details necessary to deliver that data to a
specific client more easily.
Application Layer (7):

This layers name is something of a misnomer. It doesnt refer to the application or
service that seeks to send or receive data across a network. Rather, it refers to an
interface between the protocol stack and applications or system services. The
Application layer defines the methods by which applications or system services can
request network access and by which they can obtain access to incoming data from
the network.
TAC
1-33
OSI Model
Each layer functions more or less independently of the others.
The job of any given layer is to provide services for the layer above it and to deliver
data to the layer below. (the lowest level of the OSI model, the Physical layer, simply
sends data on to a receiver or to the Data Link layer, depending on whether the
communication is coming or going.)
The encoding that a layer does on the sending side is decoded by the same layer on
the receiving side. Therefore, the layered OSI model helps emphasize that protocols
on the sending end accept data from application, convert that data into generic form,
manage conversations, prepare data to be sent across the network, address and route
data, and then convert that data into signal for transmission across the network.
On the receiving end, the process is reversed: The protocols convert signals into data,
figure out where that data is to be delivered, reconstitute incoming messages into their
original containers, manage conversations, prepare the data for the client computer,
and deliver that data to an application.
1-34
Ch 2
BACnet Basics
Contents
What is BACnet
History of BACnet
Andover Controls & BACnet
BACnet Objects
BACnet Properties
BACnet Protocol Architecture
Services
Basic Services
Application Layer Model
Client Server Model
- Confirmed Services
- Unconfirmed Services
BACnet Message Size
Transmission of BACnet APDUs
Network Layer
Service Specifications
Network Numbering
Transport Options
2-2
BACnet Basics
What is BACnet?
BACnet is a Data Communications Protocol designed to enhance interoperability.
BACnet stands for Building Automation and Control network.
BACnet was developed by the American Society of Heating, Refrigerating and AirConditioning Engineers, Inc. (ASHRAE) that allows products made by different
manufacturers to be integrated into a single building automated control system. This
means that different manufacturers products can seamlessly communicate data to
each other over a network.
The types of products include controllers, workstations, actuators and sensors.
Within the BACnet world, each of these products is referred to as a device.
In order for communications to occur between two different systems, a common
network technology is required. BACnet supports five different types of networks:
Ethernet (Supported with Continuum version 1.6)
MS/TP (Supported with Continuum version 1.6)
ARCNET
Point-to-Point
LonTalk
With Continuum Version 1.6, Andover selected MS/TP, a twisted-pair cabling
arrangement based on the RS-485 standard, for its BACnet networking requirements
and Ethernet IP.
BACnet is an Application Language made up of:
Objects
Services
BACnet
Common messages, consisting of Objects and Services, are communicated from

device to device via Transports:
LANs
WANs
TAC
BACnet
2-3
History of BACnet
BACnet is the result of nearly eight and a half years of toil, on the part of a dedicated
group of about twenty ASHRAE volunteers, who had been assembled into a Standard
Project Committee known as SPC 135P.
Volunteers came from all segments of the building controls industry including:
Universities
Control Manufacturers
Government Agencies
Consulting Firms
Their task was to adopt or develop a standard method by which all computers used in
building automation and control could exchange information.
2-4
BACnet Basics
Andover & BACnet

Connectivity has never been a problem for Andover systems. Special interfaces
called X-Drivers have been available that allow Infinity and Continuum systems to
interoperate with dissimilar systems from companies like; Carrier, McQuay, Grinnell
and others.
More and more construction projects are beginning to specify control equipment that
operates on the BACnet standard.
Andover Controls has now integrated Native BACnet into its line of building
automation solutions. With this introduction, Andover becomes the manufacturer
with the most complete line of automation products available that comply with the
BACnet standard.
CyberStation 1.6 is a BACnet Workstation:
-
Includes all necessary BACnet classes

Provides all necessary BACnet services
Additional attributes need to be added (properties)
COV subscriptions for Events
Andover Controls BACnet Controllers:
TAC
B4920 - Router from BACnet/IP (Ethernet) to BACnet MSTP (RS485)
B385x - BACnet Terminal Controller
2-5
Andover & BACnet
NetController
CyberStation 1.6
I2 Devices
B4920
Delta Orca View
Delta DSC
MS/TP B385x
Mix of Engineering Environments

- i2 supports Dumb Terminal, B-AAC does not
Alarms are Mixed
- B-AAC Uses BACnet Alarms
- i2 Uses Infinity Alarms
Schedules, Groups and Graphics are Unchanged
Automatic Data Exchange Determination
- Based on Controller Type and Need
All existing Libraries and Engineering Tools will Function Unchanged
BACnet is here to stay and Andover Controls is committed to competing in the
industry with products compliant with the standard.
2-6
BACnet Basics
BACnet Objects
The BACnet protocol is based on:
Objects
Services
Transport
Objects are the logical representation of system data.
Objects may represent single physical points or logical groupings / collections of
points that perform a specific function.
Standard Objects
The data structures used in a device to store information are a local matter. In
order to exchange that information with another device using this protocol, there
must be a "network-visible" representation of the information that is standardized.
An object-oriented approach has been adopted to provide this network-visible
representation.
This clause defines a set of standard object types. These object types define an
abstract data structure that provides a framework for building the application layer
services. The application layer services are designed, in part, to access and
manipulate the properties of these standard object types.
BACnet defines a collection of 23 Standard Object Types (127 Possible):

Binary Input
Binary Output
Binary Value
Analog Input
Analog Output
Analog Value
Averaging
LifeSafetyZone
TAC
Multi-State Input
Multi-State Output
Multi-State Value
Loop
Calendar
Notification Class
Command
LifeSafetyPoint
File
Program
Schedule
Trend Log
Group
Event Enrollment
Device
2-7
BACnet Objects
Standard Objects
The BACnet Standard Objects that Continuum 1.6 supports are:
Binary Input
Binary Output
Binary Value
Analog Input
Analog Output
Analog Value
Device
Event Enrollment
Multi-State Input
Multi-State Output
Multi-State Value
Notification Class
Subsequent versions of Continuum (1.62 and beyond) will support BACnet Calendar
and BACnet Schedule objects.
Non-Standard Objects
Not all object types defined in this standard need to be supported in order to conform
to the standard. Some properties of particular object types are optional.
It is intended that the collection of object types and their properties defined in this
standard be comprehensive, but implementors are free to define additional
nonstandard object types or additional nonstandard properties of standard object
types. This is the principal means for extending the standard as control technology
develops. Innovative changes can be accommodated without waiting for changes in
the standard. This extensibility could also be used to adapt this standard to other types
of building services.
All objects are referenced by their Object_Identifier property.
Each object within a single BACnet Device shall have a unique value for the
Object_Identifier property. When combined with the system-wide unique
Object_Identifier of the BACnet device, this provides a mechanism for referencing
every object in the control system network.
Nonstandard object types are required to support the following properties:
Object_Identifier
Object_Name
Object_Type
BACnetObjectIdentifier
CharacterString
BACnetObjectType
These properties shall be implemented to behave as they would when present in

standard BACnet objects. This means that the Object_Identifier and Object_Name
properties shall be unique within the BACnet device that maintains them. The
Object_Name string shall be at least one character in length and shall consist only of
printable characters.
2-8
BACnet Basics
BACnet Objects
Object Properties
A BACnet standard object shall support all required properties specified in the
standard. It may support any optional properties specified in the standard or
properties not defined in the standard.
Required Properties
A required property shall function as specified in the standard for each object of that
type. If properties that are defined as optional in the standard are supported, then they
shall function as specified in the standard.
A required property shall be present in all objects of that type.
Optional Properties
An optional property, if present in one object of a given type, need not be present in
all objects of that type.
Supported Properties
A supported property, whether required or optional, shall return the data-type
specified in the standard.
A supported property, whether required or optional, is not required to be able to
return the entire range of values for a data-type unless otherwise specified in the
property description.
TAC
2-9
BACnet Properties
Objects are examined and controlled by a set of Properties that belong to each object.
BACnet properties are equivalent to attributes in Continuum.
Examples of object properties are: Name, Type, Present Value, Status Flags, High
Limit, Low Limit, and so forth. The most commonly used property for
interoperability is Present Value.
Each BACnet device also has a device object containing properties that can be used
to verify communications, identify the vendor, identify software and firmware
revision and other characteristics of the device. The device objects properties
represent the externally visible characteristics of a BACnet device.
Mandatory BACnet Properties are:
Object Identifier
Name
Type
Property Identifiers (0-511) ASHRAE, (512-4194303) Proprietary
0 acked-transitions
1 ack-required
2 action
3 action-text
4 active-text
5 active-vt-sessions
6 alarm-value
7 alarm-values
8 all
9 all-writes-successful
10 apdu-segment-timeout
11 apdu-timeout
12 application-software-versio
13 archive
14 bias
15 change-of-state-count
16 change-of-state-time
17 -18 -19 controlled-variable-reference
20 controlled-variable-units
2-10
21 controlled-variable-value
22 cov-increment
23 datelist
24 daylight-savings-status
25 deadband
26 derivative-constant
27 derivative-constant-units
28 description
29 description-of-halt
30 device-address-binding
31 device-type
32 effective-period
33 elapsed-active-time
34 error-limit
35 event-enable
36 event-state
37 event-type
38 exception-schedule
39 fault-values
40 feedback-value
41 file-access-method
42 file-size
43 file-type
44 firmware-revision
45 high-limit
46 inactive-text
47 in-process
48 instance-of
49 integral-constant
50 integral-constant-units
51 issue-confirmed-notification
52 limit-enable
53 list-of-group-members
54 list-of-object-property-references
55 list-of-session-keys
56 local-date
57 local-time
58 location
59 low-limit
60 manipulated-variable-references
61 maximum-output
BACnet Basics

BACnet is based on a four-layer collapsed architecture that corresponds to the
physical, data link, network, and application layers of the OSI model.
The application layer and a simple network layer are defined in the BACnet standard.
BACNet Layers
Equivalent
OSI Layers
BACNet Application Layer
Transport
BACNet Network Layer
Network
ISO 8802-2 (IEEE 8802.3)

Type 1
ISO 8802-3
IEEE 802.3
ARCNet
MS/TP
Data Link
PTP
LonTalk
EIA-485 EIA-232
Physical
BACnet Collapsed Architecture
BACnet provides five options that correspond to the OSI Data Link and Physical
Layers:
Option 1 is the logical link control (LLC) protocol defined by ISO 8802-2 Type 1,
combined with the ISO 8802-3 medium access control (MAC) and physical layer
protocol. ISO 8802-2 Type 1 provides unacknowledged connectionless service only.
ISO 8802-3 is the international standard version of the well-known "Ethernet"
protocol.
Option 2 is the ISO 8802-2 Type 1 protocol combined with ARCNET (ANSI/ATA
878.1).
Option 3 is a Master-Slave/Token-Passing (MS/TP) protocol designed specifically
for building automation and control devices as part of the BACnet standard. The
MS/TP protocol provides an interface to the network layer that looks like the ISO
8802-2 Type 1 protocol and controls access to an EIA-485 physical layer.
Option 4, the Point-To-Point protocol, provides mechanisms for hardwired or dialup serial, asynchronous communication.
Option 5 is the LonTalk protocol. Collectively these options provide a master/slave
MAC, deterministic token-passing MAC, high-speed contention MAC, dial-up
access, star and bus topologies, and a choice of twisted-pair, coax, or fiber optic
media.
TAC
2-11

BAC networks are Local Area Networks (LAN). This is true even though in some
applications it is necessary to exchange information with devices in a building that is
very far away. This long-distance communication is done through telephone
networks. The routing, relaying, and guaranteed delivery issues are handled by the
telephone system and can be considered external to the BAC network.
BAC devices are static. They don't move from place to place and the functions that
they are asked to perform do not change.
BACnet Specific Layers From The OSI Protocol
Physical Layer - Provides a means of connecting the devices and transmitting the
electronic signals that convey the data.
Data Link Layer - Organizes the data into frames or packets, regulates access to the
medium, provides addressing, and handles some error recovery and flow control.
Network Layer - Functions provided by the Network Layer include translation of
global addresses to local addresses, routing messages through one or more networks,
accommodating differences in network types and in the maximum message size
permitted by those networks, sequencing, flow control, error control, and
multiplexing.
BACnet is designed so that there is only one logical path between devices,
thus eliminating the need for optimal path routing algorithms.
For some BACnet systems, the network layer is a necessity. This is the case
when two or more networks in a BACnet Internet use different MAC layer
options. When this occurs, there is a need to recognize the difference between
local and global addresses and to route messages to the appropriate networks.
BACnet provides this limited network layer capability by defining a Network

Layer header that contains the necessary addressing and control information.
Application Layer - Provides the communication services required by the

applications to perform their functions, in this case monitoring and control of
HVAC&R and other building systems. Clearly an application layer is needed in the
protocol.
2-12
BACnet Basics

Non BACnet Specific Layers From The OSI Protocol
Transport Layer - Responsible for guaranteeing end-to-end delivery of messages,
segmentation, sequence control, flow control, and error recovery. Most of the
functions of the transport layer are similar to functions in the data link layer, though
different in scope.
Guaranteed end-to-end delivery and error recovery are provided in the

BACnet application layer via message retry and timeout capabilities.
However, sequence control is required in order to properly reassemble
segmented messages. This is provided in the BACnet application layer within
the segmentation procedure.
Since BACnet is based on a connectionless communication model, the scope

of the required services is limited enough to justify implementing these at a
higher layer, thus saving the communication overhead of a separate transport
layer.
Session Layer - Used to establish and manage long dialogues between

communicating partners. Session layer functions include establishing synchronization
checkpoints and resetting to previous checkpoints in the event of error conditions to
avoid restarting an exchange from the beginning. Most communications in a BAC
network are very brief. For example, reading or writing one or a few values, notifying
a device about an alarm or event, or changing a set-point. Occasionally longer
exchanges take place, such as uploading or downloading a device.
Presentation Layer - Provides a way for communicating partners to negotiate the
transfer syntax that will be used to conduct the communication. This transfer syntax is
a translation from the abstract user view of data at the application layer to sequences
of octets treated as data at the lower layers. If only one transfer syntax is permitted,
then the presentation layer function reduces to an encoding scheme for representing
the application data. BACnet defines such a fixed encoding scheme and includes it in
the application layer, making an explicit presentation layer unnecessary.
TAC
2-13

In summary
The resource and overhead costs for implementing a full OSI seven layer architecture
make it impractical for current building automation devices.
Following the OSI model offers advantages in terms of adopting existing computer
networking technology. This can result in cost savings and make integration with
other computer network systems easier.
The expectations and environment of building automation systems permit
simplification of the OSI model by eliminating the functionality of some of the
layers.
A collapsed architecture made up of the Physical, Data Link, Network, and
Application Layers is the optimum solution for today's building automation systems.
BACnet Topology
In the interest of application flexibility, BACnet does not prescribe a rigid network
topology.
BACnet devices are physically connected to one of four types of Local Area
Networks (LANs) or via dedicated or dial-up serial, asynchronous lines.
These networks may then be further interconnected by the use of BACnet routers.
In terms of LAN topology, each BACnet device is attached to an electrical medium or
physical segment.
A BACnet segment consists of one or more physical segments connected at the
physical layer by repeaters.
A BACnet network consists of one or more segments interconnected by bridges that
connect the segments at the physical and data link layers and may perform message
filtering based upon MAC addresses.
Multiple networks, possibly employing different LAN technologies, may be interconnected by BACnet routers to form a BACnet inter-network.
2-14
BACnet Basics

BACnet Topology
In a BACnet inter-network, there exists exactly one message path between any two
nodes.
A BACnet Inter-network, Illustrating the Concepts of:
- Networks
- Segments
- Physical Segments
TAC
- Bridges
B = Bridge
- Repeaters
R = Repeater
- Routers
RT = Router
- Half Routers
RT = Half Router
2-15
Services
In order for two different devices to interoperate, a common set of services is
required. BACnet services provide messages for accessing and manipulating
properties of device objects.
For example, the devices need to identify themselves (I Am, Who Is), read and write
data (Read Property, Write Property), and so forth.
BACnet defines 35 basic services that are grouped into 5 categories:
1) Object Access
AddListElement
RemoveListElement
CreateObject
DeleteObject
ReadProperty
ReadPropertyConditional
ReadPropertyMultiple
WriteProperty
WritePropertyMultiple
2) Alarm and Event
AcknowledgeAlarm
ConfirmedCOVNotification
ConfirmedEventNotification
GetAlarmSummary
GetEnrollmentSummary
SubscribeCOV
UnconfirmedCOVNotification
UnconfirmedEventNotification
2-16
BACnet Basics
Services
3) Remote Device Management
DeviceCommunicationControl
ConfirmedPrivateTransfer
UnconfirmedPrivateTransfer
ReinitializeDevice
ConfirmedTextMessage
UnconfirmedTextMessage
TimeSynchronization
Who-Has and I-Have
Who-Is and I-Am
4) File Transfer
AtomicReadFile
AtomicWriteFile
5) Virtual Terminal
VT-Open
VT-Close
VT-Data
TAC
2-17
Services
The purpose of the Application Layer Model is to describe and illustrate the
interaction between the application layer and application programs, the relationship
between the application layer and lower layers in the protocol stack, and the peer-topeer interactions with a remote application layer.
An Application Process is that functionality within a system that performs the
information processing required for a particular application. All parts of the
Application Process outside the Application Layer, (i.e., those that do not concern the
communication function) are outside the scope of BACnet. The part of the
Application Process that is within the Application Layer is called the Application
Entity. In other words, an Application Entity is that part of the Application Process
related to the BACnet communication function. An application program interacts
with the Application Entity through the Application Program Interface (API). This
interface is not defined in BACnet, but it would probably be a function, procedure, or
subroutine call in an actual implementation.
Model of a BACnet Application Process

The gray shaded region indicates the portion of the Application Process that is within
the BACnet Application Layer.
Application
Program
Application
Process
Application Layer
Application Program
Interface
BACnet
User Element
Application
Entity
BACnet
ASE
NSAP
2-18
BACnet Basics
Services
The Application Entity is itself made up of two parts:
BACnet User Element
BACnet Application Service Element (ASE)
The BACnet User Element carries out several functions:
TAC
It represents the implementation of the "service procedure" portion of each

application service
It is responsible for maintaining information about the context of a

transaction, including generating invoke IDs and remembering which invoke
ID goes with which application service request (response) to (from) which
device
It is responsible for maintaining the time-out counters that are required for the
retrying of a transmission
It also presides over the mapping of a device's activities into BACnet objects
2-19
Services
Client / Server Model (Confirmed Application Services)
BACnet defines Confirmed Application Services based on a client and server
communication model.
A client requests service from a server via a particular service request instance.
The server provides service to a client and responds to the request.
server
client
ReadProperty(msg#123
objectid=AnalogInput 29
propertyid=Present_Value)
ReadProperty(msg#123
objectid=AnalogInput 29
propertyid=Present_Valuevalue=72.0)
or
Error(msg#123 class=object
code=NoSuchObject)
2-20
BACnet Basics
Services
Client / Server Model
Confirmed Services
The BACnet-user that assumes the role of a client is called the "requesting
BACnet-user" and the BACnet-user that assumes the role of the server is called
the "responding BACnet-user."
Client
Server
Requesting
Responding
Sending
Request
PDU
Receiving
Receiving
Respond
PDU
Sending
Client and Server Relationship
1) A requesting BACnet-user issues a CONF_SERV request primitive, which

causes a request PDU to be sent.
2) When a response PDU arrives, the requesting BACnet-user receives a
CONF_SERV confirm primitive.
3) When a request PDU arrives, the responding BACnet-user receives a
CONF_SERV indication primitive.
4) The responding BACnet-user issues a CONF_SERV response primitive,
which causes a response PDU to be sent. Thus, the requesting BACnet-user
and the responding BACnet-user play a role in both sending and receiving
PDUs.
Sending BACnet-User - Applies to a BACnet user that initiates the sending of

a PDU.
Receiving BACnet-User - Applies to a BACnet-user that receives an
indication that a PDU has arrived.
TAC
2-21
Services
Client / Server Model
Unconfirmed Services
The client and server model, and the terms "requesting BACnet-user" and
"responding BACnet-user," do not apply to Unconfirmed Services.
The terms "sending BACnet-user" and "receiving BACnet-user" do apply and
are used to define the service procedure for unconfirmed services.
2-22
BACnet Basics
Services
The client-server model supports such services as AcknowledgeAlarm and
ConfirmedCOVNotifications and UnconfirmedCOVNotifications. Both confirmed
and unconfirmed alarms and COV's are local subnet broadcasts and will require the
use of a BACnet Broadcast Management Device to transmit beyond the local subnet.
For the Alarm and COVNotification Services, with the delivery of the first alarm or
COVNotification, the b4920 or b3xx builds an internal device binding table (similar
to an address book) as the result of an initial Who is/I am. This table gets updated
based on changes in alarm delivery or COVnotifications. Subsequent
Alarms/COVnotifications use this table for additional deliveries. Each time the
controller is powered down or reloaded, however, the table must rebuild beginning
with the first Alarm/COVnotification delivery.
If a BACnet device attempts to deliver an alarm or a COVnotification and does not
get a response it sets that device to an offline status and continues to try and send
WHO IS messages until the device returns to an online status.
The only difference between confirmed and unconfirmed services is that the
confirmed results in an ACK response primitive being sent to the client device.
TAC
2-23
Services
BACnet Messages - Packet Size
To provide for messages that are longer than the maximum length supported by a
communications network, or by the sending or receiving device, BACnet provides a
method to perform application layer segmentation. In BACnet, only ConfirmedRequest and Complex-ACK messages may be segmented. Segmentation is an
optional feature of BACnet.
Message Segmentation - This sub-clause prescribes rules for dividing a message
into segments.
Segmenting APDU Data Streams - Each BACnet message is encoded into a
sequence of tags and values.
The following rules apply to segmenting this data stream:
If possible, an entire message shall be sent in a single APDU.
If an entire message cannot be sent in a single APDU, the message shall be

segmented into the minimum number of APDUs possible.
Messages shall be segmented only at octet boundaries.
Maximum APDU Length - The maximum length of a BACnet APDU shall be the
smallest of:
2-24
The maximum APDU size transmittable by a device, which may be restricted

by local buffer limitations and is a local matter;
The maximum APDU size conveyable by the inter-network to the remote

device, which is constrained by the maximum NPDU length permitted by the
data links used by the local, remote, and any intervening networks.
The maximum APDU size accepted by the remote peer device, which must be
at least 50 octets.
BACnet Basics
Services
BACnet Messages - Packet Size
If the sending device is the requesting BACnet-user, i.e., the message to be sent is a
Confirmed-Request; then the maximum number of segments accepted by the remote
peer device is specified in the Max_Segments_Accepted property of the remote peer's
Device object.
If the sending device is not the requesting BACnet-user, i.e., the message to be sent is
a Complex-ACK; then the maximum number of segments accepted by the remote
peer device is specified in the 'Max Segments Accepted' parameter of the BACnetConfirmed-Request-PDU for which this is a response.
The value determined by the above constraints will be designated the maximumtransmittable-length. Note that maximum-transmittable-length will not be a constant
unless minimum values are used for each constraint.
Maximum Segments Accepted - The maximum number of segments transmitted

in a Confirmed-Request or ComplexACK
message shall be the smallest of:
TAC
The maximum number of segments transmittable by a device, which may be

restricted by local limitations and is a local matter
The maximum number of segments accepted by the remote peer device
2-25
Services
Transmission of BACnet APDUs
Upon transmitting a complete un-segmented Confirmed-Request message or upon
receiving the SegmentACK, acknowledging the final segment of a segmented
Confirmed-Request message, a client device shall start a timer that indicates the
length of time the message has been outstanding.
The timer shall be canceled upon the receipt of an Error, Reject, Abort, SimpleACK
or ComplexACK APDU for the outstanding Confirmed-Request message and the
client application shall be notified.
If the timer exceeds the value of the APDU_Timeout property in the client's Device
object, then the complete Confirmed-Request message shall be retransmitted and the
timer shall be reset to zero.
All retransmitted Confirmed-Request messages shall follow this same procedure until
the message has been retransmitted the number of times indicated in the
Number_Of_APDU_Retries property of the client's Device object.
If, after the Confirmed-Request message is retransmitted the appropriate number of
times and a response is still not received, the message shall be discarded and the
client application shall be notified.
2-26
BACnet Basics
Network Layer
The purpose of the BACnet network layer is to provide the means by which messages
can be relayed from one BACnet network to another, regardless of the BACnet data
link technology in use on that network.
Whereas the data link layer provides the capability to address messages to a single
device or broadcast them to all devices on the local network, the network layer allows
messages to be directed to a single remote device, broadcast on a remote network, or
broadcast globally to all devices on all networks. A BACnet Device is uniquely
located by a network number and a MAC address.
BACnet Routers - Devices that interconnect two disparate BACnet LANs, e.g.,
ISO 8802-3 and ARCNET, and provide the relay function described in this clause are
called "BACnet routers." Devices that interconnect two disparate BACnet networks
through a point-to-point (PTP) connection are also BACnet routers.
BACnet Routers build and maintain their routing tables automatically using the
network layer protocol messages. Network layer protocol messages facilitate both the
auto-configuration of routers and the flow of messages to, and between, routers.
BACnet routing capability may be implemented in stand-alone devices or,
alternatively, in devices that carry out other building automation and control
functions.
Some Functions of the Network Layer are Not Required in BACnet:
TAC
One such function involves selecting a communications path between source

and destination machines based on an optimization algorithm. This is not
required because BACnet internetworks shall be designed and installed with at
most a single, active path between any two devices, a constraint that greatly
reduces the complexity of the network layer.
Another common network layer function is message segmentation and

reassembly. To obviate the need for these capabilities at the network layer,
BACnet imposes a limitation on the length of the NPDU in messages passed
through a BACnet router. The maximum NPDU length shall not exceed the
capability of any data link technology encountered along the path from source
to destination.
2-27
Network Layer
A list of the maximum Network Protocol Data Units (NPDU) lengths for BACnet
Data Link Technologies:
2-28
BACnet Basics
Network Layer
Service Specification
Conceptually, the BACnet network layer provides an unacknowledged connectionless
form of data unit transfer service to the application layer. The primitives associated
with the interaction are the N-UNITDATA request and indication. These primitives
provide parameters as follows:
N-UNITDATA.request (
destination_address,
data,
network_priority,
data_expecting_reply
)
N-UNITDATA.indication (
source_address,
destination_address,
data,
network_priority,
data_expecting_reply
)
TAC
2-29
Network Layer
Service Specification
The 'destination_address' and 'source_address' parameters provide the logical
concatenation of:
An optional network number

The MAC address appropriate to the underlying LAN technology
The link service access point
A network number of X'FFFF' indicates that the message is to be broadcast "globally"

to all devices on all currently reachable networks. Currently reachable networks are
those networks to which an active connection is already established within the
BACnet internet. In particular, a global broadcast shall not trigger any attempts to
establish PTP connections.
The 'data' parameter is the network service data unit (NSDU) passed down from the
application layer and is composed of a fully encoded BACnet APDU.
The 'network_priority' is a numeric value used by the network layer in BACnet
routers to determine any possible deviations from a first-in-first-out approach to
managing the queue of messages awaiting relay.
The data_expecting_reply parameter indicates whether (TRUE) or not (FALSE)
a reply data unit is expected for the data unit being transferred.
Upon receipt of an N-UNITDATA request primitive from the application layer, the
network layer shall attempt to send an NSDU. Upon receipt of an NSDU from a peer
network entity, a network entity shall either:
Send the NSDU to its destination on a directly connected network
Send the NSDU to the next BACnet router en route to its destination
If the destination address matches that of one of its own application entities, issue an
N-UNITDATA indication primitive to the appropriate entity in its own application
layer to signal the arrival of the NSDU
2-30
BACnet Basics
Network Layer
Unique Network Number
Each BACnet Network must have a unique Network Identification number.
Andover uses an algorithm to assign a unique Network number to each of its BACnet
Networks. The algorithm uses the hexadecimal version of ACC (2764) and the
ACCNet ID of the b4920 to create a unique number. Because of this unique
algorithm, the likelihood of conflict with third party BACnet networks is minimized.
This only works if the Administrator does not set the MS/TP Net Id and accepts the
default value assigned through this algorithm.
The Algorithm formula: (2764) + (b4s Acc Net Id #)
Acc in Hexadecimal
In the unlikely event of duplication of Network Ids, the administrator is given the
opportunity to change the Network ID in the editor of the b4920. If the Administrator
configures the MS/TP Net Id, the formula is over-ridden by the new value.
b4920 Editor View
Web Server View
Unique MS/TP Net Id #
TAC
2-31
Transport Options
Supported Protocols showing Cost Vs Speed
Ethernet
Cost
ARCNET
LonTalk
MS/TP
Speed
2-32
BACnet Basics
Transport Options cont

Continuum version 1.6 is a BACnet compliant system allowing the integration of
BACnet devices through the following transport technologies:
Master Slave Token Passing (MS/TP) (Continuum 1.6)
A token Passing network that also supports slave devices that will only
respond to a poll
Any device that Token Passes is considered a MASTER
All Continuum BACnet controllers are masters:

- b - 4920 controller
- b - 3 series controllers
All devices are of equal priority (unlike Infinet)
All devices have equal access to the network
Token Passing is performed by ID and proceeds around a logical ring
MS/TP supports up to 127 devices
MS/TP is standard RS-485
BACnet/IP (B/IP) (Continuum 1.6 / Xdriver 1.5 and Higher)

A BACnet/IP network is a collection of one or more IP sub-networks (IP domains)
that are assigned a single BACnet network number. A BACnet inter-network
consists of two or more BACnet networks.
TAC
BACnet/IP is a standard BACnet message encapsulated within an IP packet
Allows for connecting the control system to the standard corporate network
Continuum 1.6 utilizes BACnet/IP with communications between

Cyberstation, BACnet/IP controllers and Gateways.
2-33
Transport Options
Transport Options not supported by Continuum 1.6 or requires an Xdriver:
- Point-to-Point (PTP) (RS-232 Serial Communications / Xdriver Only)
- Ethernet LAN (Non-Routable / Standard Ethernet Networking / Xdriver Only)
- ARCNET LAN (Not Supported / Token Passing Buss / Use of Gateways)
- LonTalk LAN (Not Supported)
2-34
BACnet Basics
Ch 3
Ethernet
Contents
Ethernet Intro / Overview
What is Ethernet
History of Ethernet
IEEE Project 802.xx
Layer 1
Cables & Specifications
-
10Base-T
10Base-2
10Base-5
10Base-FL
100Base-TX
100Base-FX
1000Base-T
1000Base-FX
Layer 2
CSMA/CD
Ethernet / MAC Addressing
Ethernet Binary Signal
IEEE 802.3 Data Packet
Extending Ethernet Beyond Cable Specs (Repeater)
Propagation Delay
Collision to Jam
Bridges & Switches
3-2
Ethernet

What is Ethernet?
Ethernet is a Local Area Network (LAN) technology that allows a variety of
computers to be connected together and communicate with one another.
Ethernet data transmission rate is 10 Megabits per second (Mbps)
Fast Ethernet operates at 100 Mbps
Gigabit Ethernet operates at 1000 Mbps or 1 Gigabit per second (Gbps)
History of Ethernet?
Ethernet was invented at Xerox Corporation's Palo Alto Research Center in the early
1970s. Digital Equipment Corporation, Intel Corporation and Xerox later cooperated
to devise a production standard that was informally called DIX Ethernet. The last
version of the DIX standard was released in 1982.
The Institute of Electrical and Electronic Engineers (IEEE, referred to as I-triple-E)
is a standards organization that establishes standards for Ethernet. In 1983, the
Institute of Electrical and Electronic Engineers (IEEE) released their first version for
Ethernet technology. IEEE now controls Ethernet standards.
TAC
3-3

IEEE Project 802.xx
IEEE Project 802 is responsible for networking standards for all network access
methods. Different access methods are the responsibility of various workgroups. The
individual workgroups are identified by a numerical suffix as .3, .4, .5, etc.
Below is a list of current Project 802 workgroups:
802.1
802.2
802.3
MAC Layer Bridges and Bridge Management

Logical Link Control
CSMA/CD (Ethernet)
10Base5
10Base2
10BaseT
10Broad36
802.4 Token Bus (MAP/TOP)
802.5 Token Ring (IBM 4 or 16Mbs)
802.6 Metropolitan Are Networks (MAN)
802.7 Broadband Local Area Network
802.8 Fiber Optic CSMA/CD
802.9 Integrated Voice and Data Systems
802.10 Standard for interoperable LAN Security (SILS)
802.11 Wireless
802.12
IEEE 802.3 defines the requirements for Ethernet.

Ethernet is Physical Layer standard for Local Area Networks using a bus topology
with a Carrier Sense Multiple Access with Collision Detection (CSMA/CD) access
method.
IEEE 802.3 provides specifications for all components of an Ethernet LAN, as well as
rules for interconnection of components, numbers of connections to the bus, total
number of user devices and allowable signal delays.
3-4
Ethernet
Layer 1
Cables & Specifications
10BaseT
Topology: Bus / Star
Cable Type: Category 3, 4 or 5 Unshielded Twisted Pair (UTP)
Terminator Resistance: 100 Ohm (internal to the transceiver)
Maximum Segment Length: 327 ft. (100 meters)
Maximum Stations Per Cable Segment: 2
Connector Type: RJ-45
Repeater
/
Hub
RJ-45
NIC
Card
TAC
UTP Cable
328 ft. max.
3-5
Layer 1
Cable Specifications cont
10Base2
Topology: Bus
Cable Type: RG-58 Thinnet coaxial
Terminator Resistance: 50 Ohm (required at each end of segment)
Maximum Segment Length: 606 ft. (185 meter)
Minimum Segment Length: 20 inch. (0.5 meters)
Maximum Total Network Length: 3,035 ft. (925 meters)
Maximum Connected Segments: 5 (using 4 repeaters) only 3 segments can
contain computers
Connector Type: BNC-T
606 ft. max. (Total Cable Run)
NIC
Card
BNC-T
50 ohm Termination
@ Both Ends
RG-58 Thinnet
Coaxial Cable
20 inch. min. (Per / Segment)
3-6
Ethernet
Layer 1
10Base5
Topology: Bus
Cable Type: Thicknet - 3/8 Shielded Transceiver
Terminator Resistance: 50 Ohm (required at each end of segment)
Maximum Segment Length: 1,640 ft. (500 meter)
Minimum Segment Length: 8.2 ft. (2.5 meters)
Maximum Total Network Length: 8,000 ft. (2,460 meters)
Maximum Connected Segments: 5 (using 4 repeaters) only 3 segments can
contain computers
Connector Type: DIX / AUI / N-series
10BaseFL
Cable Type: 62.5/125 Micron Multi-Mode Fiber Optic Cable
Maximum Segment Length: 6,561 ft (2,000 meters)
Connector Type: ST / SMA
TAC
3-7
Layer 1
100BaseFX
Cable Type: 62.5/125 Micron Multi-Mode Fiber Optic Cable
Maximum Segment Length: Full Duplex = 6,561 ft. (2,000 meters)
Half Duplex = 1,351 ft. (412 meters)
100BaseTX
Cable Type: Unshielded Twisted Pair (CAT 5) 2 Pairs
Terminator Resistance: 100 ohm
Connector Type: RJ-45 (CAT 5)
3-8
Ethernet
Layer 1
1000BaseT
Cable Type: Unshielded Twisted Pair (CAT 5)
Terminator Resistance: 100 ohm
Connector Type: RJ-45
1000BaseFX
Cable Type: Multi-Mode / Single-Mode Fiber Optic cable
Maximum Segment Length: Mulit-mode = 1,351 ft. (220meters)
Single-mode = 16,404 ft. (5,000 meters)
Minimum Segment Length: Mulit-mode = 6.5 ft. (2 meters)
Single-mode = 6.5 ft. (2 meters)
TAC
3-9
Layer 2
CSMA/CD (Carrier Sense Multiple Access)
An Ethernet network does not have a centralized controller that tells each computer
how to take turns using the shared cable. Instead, all computers attached to the
Ethernet participate in a distributed coordination scheme called Carrier Sense
Multiple Access (CSMA).
The scheme uses electrical activity on the cable to determine status. When no
computer is sending a frame, the Ethernet does not contain electrical signals. During
frame transmission, a sender transmits electrical signals used to encode bits.
Although the signals differ slightly from the modulation high frequency carrier
waves, they are also referred to as a carrier. To determine whether the Ethernet
cable is currently being used, a computer can check for a carrier. If no carrier is
present, the computer can transmit a frame. If a carrier is present, the computer must
wait for the sender to finish before proceeding.
Checking for a carrier wave is called carrier sense, and the idea of using the
presence of a carrier signal to determine when to transmit is called Carrier Sense
Multiple Access, or CSMA.
3-10
Ethernet
Layer 2
CSMA/CD (Collision Detection)
CSMA cannot prevent all possible conflicts on the cable.
As an example, if two computers at opposite ends of an idle cable both have a frame
ready to send at the same time and both check for a carrier and find none, they begin
transmitting simultaneously. The signals reach the same point on the cable and
interfere with each other.
The interference between two signals on an Ethernet cable is called a collision. It
produces a garbled transmission that prevents either of the two frames from being
received correctly. Each sending computer monitors the signals on the cable. If the
signal on the cable differs from the signal that the sending computer transmitted, it
means that a collision has occurred. The sending computer immediately stops
transmitting.
This technique of monitoring the cable during transmission is called Collision Detect
(CD).
The combined Ethernet mechanism of Carrier Sensing and Collision Detection is
referred to as Carrier Sense Multiple Access with Collision Detect (CMSA/CD).
Recovering from a Collision:
When a signal collision occurs, the sending computers must wait for the cable to
become idle again before retransmitting their frames. However if they begin to
transmit as soon as the Ethernet becomes idle, it possible that another collision will
occur. To avoid this situation, the Ethernet standard requires each computer to delay
after a collision before attempting to retransmit. The standard specifies a maximum
delay d, and forces each computer to choose a random delay less than the d.
In most cases, when a computer chooses a delay at random, it will select a value that
differs from any of the values chosen by the other computers. The computer that
chooses the smallest delay will proceed to send a frame and the network will return to
normal operation.
The above explanation is a simplistic explanation of how collision recovery (referred
to as exponential back-off) occurs on an Ethernet network. Exponential back-off
means that the Ethernet network can recover quickly after a collision because each
computer agrees to wait longer times between attempts when the cable becomes busy.
TAC
3-11
Layer 2
The Ethernet/ MAC Address consists of two parts:
The first set of octets - define the Unique Manufacturers Id
The second set of octets - define the Serial Number of the Network
Interface Card (NIC)
Specific Addressing:
IEEE specifies that each addressable network device will have a unique hardware
address that is made up of 6 bytes of information. The address is hard-coded into
every network interface controller card during manufacturing. IEEE strictly controls
the availability of addresses.
IEEE assigns each network hardware manufacturer a unique manufacturer identifier
and a block of numbers that the manufacturer usually assigns sequentially to each
piece of hardware. The combination of the Manufacturer ID and the serial number of
the NIC make up the common 48-bit (6-byte) Ethernet / MAC address.
The first 3 bytes of the address contain the manufacturer identifier and the last 3 bytes
contain the NIC serial number. The numbering scheme is given in hexadecimal
format (0-9 hex and A-F hex).
Andover Controls
Manufacturers ID
Network Interface Card

Serial Number
00:40:11:0C:8D:2C
Unique Ethernet / MAC Address
The 00-40-11 manufacturers ID belong to Andover Controls.

Always an even number
When a specific Ethernet address is used as the destination address in a packet, only
the station with that specific address will decode that packet.
3-12
Ethernet
Layer 2
Multicast Addressing:
At times it is necessary to communicate with many devices on a network
simultaneously. A network management station might poll or query a group of
devices to determine their status. Instead of keeping a list or table of unique
addresses, a group address can be used. This type of group addressing is
accomplished using a Multicast address. The first byte of the destination ID is always
an odd number.
Broadcast Addressing:
A broadcast address is an address thats meant to be heard by all stations on the
network. Certain protocols running on workstations will occasionally send out
broadcast messages to servers on the network to let the servers know that the node is
on line. A broadcast address contains F hex characters in both the manufacturer ID
and sequential number area of the address.
TAC
3-13
Layer 2
IEEE 802.3 Data Packet
The IEEE 802.3 Ethernet Standard provides a very definitive packet description.
Destination
Address
Preamble
7
1
SFD
Field
Length
6
Source
Address
CRC
46 - 1500
Data Field
Preamble:
The preamble indicates the beginning of packet transmission. The preamble allows
for packet timing at the receiving station (s). The signal pattern is
1010101010binary for a total of 56 bits (7 bytes).
Start Frame Delimiter (SFD):
The SFD signal pattern is 10101011 for a total of 8 bits (1 byte). It follows the
preamble and indicates the start of information by the last two bits, 11.
Destination Address:
The address of the station, or stations, that the data packet is intended. It follows the
SFD and is 48 bits (6 bytes) 1.
Source Address:
Follows the destination address and indicates the address of the station initiating the
transmission. The source address is 48 bits (6 bytes) in length1.
Length Field:
Then length field follows the source address and indicates length of data field. The
length field is 16 bits (2 bytes) in length. In Ethernet version 1.0 or version 2.0, this
field is called a Type field. The Type field will usually indicate the packet protocol
(e.g., TCP/IP, XNS, DECNet, Novell IPX, etc.)
Data Field:
The data field follows the length field. It is 46 bytes minimum to a maximum of 1500
bytes in length. This field contains the actual data being sent across the network
along with some control information. If the data to be sent is less than 46 bytes, a
special bit pattern called PAD is used to fill in up to the 46 byte minimum.
Cyclic Redundancy Check (CRC):
The CRC follows the data field and is 32 bits (4 bytes) in length. Also known as the
Frame Check Sequence (FCS), this field insures that the transmitted data that is
received is the same as the data that was originally sent.
3-14
Ethernet
Layer 2
IEEE 802.3 Data Packet cont
Packet Size
IEEE defines both a minimum and maximum packet size:
Minimum - 64 bytes (12 address bytes, 2 length bytes, 46 data bytes and 4
CRC bytes).
Maximum - 1,518 bytes (same overhead information as the minimum packet

size but with a 1,500-byte data field).
Minimum Packet Size

The minimum packet size has been determined to give the best response time on
heavily used networks by minimizing the amount of time a station must defer to other
transmissions.
The minimum packet size also plays an important role in the detection of collisions
(more than one station trying to transmit at the same time) and determining the
maximum network size.
In order to detect a collision, a station must still be transmitting its state to realize that
it was involved in the collision and not just viewing a collision between two other
stations on the network.
A minimum size packet is 64 bytes in length, which equates to 512 bits (8 bits per
byte), and that each bit time is 0.1 sec. Multiplying 512 bits by 0.1 sec yields
51.2 sec to transmit a 64-byte minimum size packet.
TAC
3-15
Layer 2
Inter-Frame Gaps
In order to distinguish one Ethernet packet from another, a quiet period called the
Inter-frame Gap, occurs at the end of each packet.
The Inter-frame gap:
Ensures that a definite quiet period of 9.6 ms occurs between packets to allow
for identification of the next packet.
Provides the time needed for the transit station to apply a Signal Quality Error
(SQE) test to the transceivers collision detection circuitry at every node.
Frame
Frame
Packet
Packet
Inter-frame Gaps
9.6s
3-16
Ethernet
Layer 2
Extending Ethernet Beyond Cable Specs (Repeater)
Distance limitations in LANs arise because the electrical signal becomes weaker as it
travels along a wire. To overcome such limitations, some LAN technologies allow
two cables to be joined together with a device known as a Repeater.
A repeater is usually an analog electronic device that continuously monitors electrical
signals on a cable. When it senses a signal on one cable, the repeater transmits an
amplified copy to the other cable.
Maximum
Ethernet Section 1
Maximum
Ethernet Section 2
Repeater (R) Connecting Two Ethernets
The 4 Repeater Rule:

The four repeater rule states that no more than 4 repeaters can be used in series
TAC
When using 4 repeaters, the fourth must be an Inter-Repeater Link (IRL) that
connects two repeaters but has no controllers or workstations on it
IRLs can be of any supported cable type, but cannot exceed the maximum
segment length for that cable
3-17
Layer 2
Propagation Delay
The signals transmitted by Ethernet stations encounter delays as they travel through
the network. These delays consist of the time required for signals to travel across the
cable segments, and the logic delays encountered when the signals pass through
electronic components in Network Interface Cards (NICs) and repeating hubs.
The longer the cable segments and the more hubs in the network, the longer it takes
for a signal to propagate from one end of the network to the other. The time it takes a
signal to travel between the two stations that are furthest apart in the network is
known as the maximum "propagation delay" of the network.
Occurs in long fiber optic runs
Total delay cannot exceed 25.6 s
The amount of delay produced by cable type:

Cable Type
Unshielded Twisted Pair
Thin Coax RG-58
Fiber Optic 62.5 / 125 m
Standard AUI
Propagation Delay (s)

1.736 / 1000 ft. (0.0057 / m)
1.567 / 1000 ft. (0.00514 / m)
1.524 / 1000 ft. (0.005 / m)
1.567 / 1000 ft. (0.00514 / m)
Allow for 2 s per repeater
Collision to Jam Delay

Collision to Jam delay is the time required for a repeater (or transceiver) to detect a
collision and introduce the jam signal.
Collision to Jam delay is the worst possible delay generated by the equipment
and should always calculate with this possibility in mind.
When looking up the delay time for repeaters, be sure to find the Collision to
Jam Delay rather than the Device Delay.
Note: If an entire network exceeds the maximum delay allowed (25.6 s), it can be
broken into two (or more) networks using a device called a Bridge. When using a
Bridge, you start a new count of cable length, signal loss and signal delay, as if the
two network segments were entirely separate.
3-18
Ethernet
Layer 2
Bridges & Switches
Bridges and Switches segment packets according to the destination address on
individual ports.
Bridge
A bridge is an electronic device that connects two LAN segments. A bridge handles
complete frames and uses the same network interface as a conventional computer.
The bridge listens to traffic on each segment. When it receives a frame from one
segment, the bridge verifies that the frame arrived intact and then forwards a copy of
the frame to the other segment, if necessary. Two LAN segments connected by a
bridge behave like a single LAN.
A computer connected to either segment can send a frame to any of the other
computers connected to the two LAN segments without knowing that they are
connected to a bridged LAN network.
LAN Segment 1
LAN Segment 2
A Bridge (B) connecting two LAN segments
A fiber optic cable and a pair of fiber modems are used to extend LAN segments that
need to be located in two separate building.
Building 1
Converter 1
Building 2
Fiber Optic Cable

Between Buildings
Converter 2
Bridging LAN segments between buildings
TAC
3-19
Layer 2
Bridges & Switches
Bridge cont
Bridges vs. Repeaters:
Bridges have become more popular than repeaters because they help isolate problems.
If two segments are connected by a repeater and lightning causes electrical
interference on one, the repeater will propagate the interference to the other segment.
In contrast, if interference occurs on one of two segments connected by a bridge, the
bridge will receive an incorrectly formed frame, which the bridge discards. Similarly,
a bridge will not forward a collision from one segment to another.
3-20
Ethernet
Layer 2
Bridges & Switches cont
Switches
In modern networks, computers need to establish a switched connection when
they need to communicate. Each computer maintains a physical connection to the
network at all times.
However, the computer can electronically request the network to establish a
logical connection to another computer, use the connection temporarily, and then
request the network to terminate the connection.
The first arrangement (a) shows an instant where computer 1 is communicating

with 3, while computer 5 is communicating with 6.
The second arrangement (b) shows the same network later when computer 1 is
communicating with 2, and computer 3 is communicating with 5.
Advantages of Switches
TAC
The chief advantage of switched connections is flexibility and generality.
Switched connections can be created or changed electronically, there is no

need to install or change physical wiring.
A switched network needs only one physical connection per computer.
3-21
3-22
Ethernet
Ch 4
TCP/IP
Contents
TCP/IP
What is TCP/IP
History of TCP/IP
TC/IP Layering Model
IP
TCP
4-2
Host Computers
Internet Protocol Address
IP Address Hierarchy
IP Address
Subnet
Default Router
Dotted Decimal Notation
Classes of IP Addresses
Divisions of the Address Space
Address Assignment
IP Addressing for Routers
Host Suffixes
Using Ping
DHCP (Dynamic Host Configuration Protocol)
The IPCONFIG Command
TCP Message Types

User Datagram Protocol (UDP)
TCP/IP
TCP/IP
What is TCP/IP:
TCP/IP (Transport/Transmission Control Protocol / Internet Protocol) is a suite of
protocols allowing computers to communicate with one another through the Internet.
TCP is responsible for verifying the correct delivery of data from client to
server. TCP supports the detection of errors that can occur through the
medium and will retransmit data until correctly received.
IP is responsible for moving packets of data from node to node. IP forwards

the packets of data based on a four byte destination address known as the IP
number.
TCP/IP design allows the construction of very large networks with less central
management. It was initially successful because it delivered a few basic services that
everyone needs (file transfer, electronic mail, remote logon) across a very large
number of client and server systems. Several computers in a small department can use
TCP/IP (along with other protocols) on a single LAN.
History:
Work on TCP/IP began in the 1970s, approximately the same time that Local Area
Networks were being developed. The U.S. military funded much of the research on
TCP/IP and internetworking through the Advanced Research Projects Agency
(ARPA). By the mid-1980s, the National Science Foundation and other U.S.
government agencies were funding development of TCI/IP and a large internet that
was used to test the protocols.
TAC
4-3
TCP/IP Layering Model

The 7-layer OIS Reference Model was devised before internetworking was invented.
Consequently, the model does not contain a layer for internet protocols. As a result,
researchers who developed TCP/IP invented a new layering model.
The TCP/IP Layering Model, which is also, called the Internet Layering Model or the
Internet Reference Model contains four layers.
TCP/IP Layering Model
Four of the layers in the TCP/IP reference model correspond to one or more layers in
the ISO reference model
The ISO model has no Internet Layer
Physical (layer1)
Corresponds to basic network hardware
Network Interface (layer2)
Specifies how to organize data into frames and how a computer transmits frames over
a network
Internet (layer3)
Specifies the format of packets sent across an internet as well as the mechanisms used
to forward packets from a computer through one or more routers to a final
destination.
Transport (layer4)
Specifies how to ensure reliable transfer.
4-4
TCP/IP
IP
Host Computers
TCP/IP defines the term host computer as any computer system that connects to the
internet and runs applications. A host can be as small as a personal computer or as
large as a mainframe. Each host attaches to one of the physical networks in an
internet.
TCP/IP protocols make it possible for any pair of hosts to communicate, despite
hardware differences. Both hosts and routers need TCP/IP protocol software. In the
TCP/IP protocol stack, addressing is specified by the Internet Protocol (IP).
Internet Protocol Address

In the TCP/IP protocol stack, addressing is specified by the Internet Protocol (IP).
The IP standard specifies that each host is assigned a unique 32-bit number known as
the hosts Internet Protocol address.
Each packet sent across an internet contains the 32-bit IP address of the sender
(source) as well as the intended recipient (destination). In order to transmit
information across a TCP/IP internet, a computer must know the IP address of the
remote computer to which the information is being sent.
IP Address Hierarchy
Each 32-bit IP address is divided into two parts:
Prefix - Identifies the physical network to which the computer is attached
Suffix - Identifies an individual computer on the network
Each physical network in an internet is assigned a unique value known as a network

number that appears as the prefix in the IP address
Each computer on a given physical network is assigned a unique address that appears
as the suffix in the IP address
TAC
4-5
IP
IP Address
A 32 bit logical network address for the Network Interface Card (NIC). It is used to
identify separate physical networks that are interconnected through a router. The
logical IP Address identifies the destination network, along with the host address on
the network, to which the data is sent.
The TCP/IP Address consists of four numbers separated with periods:
The first number can be from 0 to 223
The last three numbers can be from 0 to 255
Net number that identifies the network's IP Address
W X
Host numbers that identifies the devices IP

Address
192.9.200.34
Together, these four numbers comprise:
4-6
Net Number - Identifies the network's IP Address
Host Numbers - Identifies the devices IP Address
TCP/IP
IP
Subnet
A Large network can be broken up into smaller logical networks called subnets and
all routed together. Multiple computers sharing the same medium with different
subnet addresses would not see one another. If the computers shared the same subnet
address, they would be able to see each other. It is easier to manage a large network
that is grouped into multiple subnets.
Subnets are necessary when working with TCP/IP. Every TCP/IP network uses a
subnet to organize its addresses.
Subnet Mask
Subnet Masks are used to define Subnets, which are just smaller logical divisions or
groups of the network.
The subnet mask is a number used to differentiate the Host ID from the Network ID.
The subnet mask indicates how much of the IP address to reserve for subdividing the
network into subnets and their hosts.
A TCP/IP node uses the subnet mask number when sending a message to another
device to determine if the device is on the local network or on a remote network.
Local / Remote Delivery of Data
The subnet mask identifies the receiving device's network as local or
remote by:
Using a logical AND to compare the masked addresses

o If the comparison results in the same number, then the device the
controller is talking to resides on the local network and the packet is sent
directly to the device.
TAC
If the comparison results in a different number, the device resides on a remote

network and the controller sends the packet to a router.
4-7
IP
Subnet Mask
The Subnet Mask is represented by the IP 32-bit address, divided into four 8-bit
decimal fields. The significance of each field is determined by its Network Class.
Network
Class
Network Address
Host Address
Example
xxx
xxx.xxx.xxx
255.0.0.0
xxx.xxx
xxx.xxx
255.255.0.0
xxx.xxx.xxx
xxx
255.255.255.0
If you set the subnet mask to 255.255.255.0 for a Class C network, then;
The first two numbers in the IP address determine the Network Number
(xxx.xxx)
The third number in the address determines the Subnet Number
The fourth number determines the Host
Network #
Subnet #
Host
255.255.255.0
Subnet Mask Address
Example: A series of controllers on Subnet 1 might be numbered:

(192.9.1.host #)
192.9.1.1
192.9.1.2
192.9.1.3
Not Setting the Subnet Mask
If you do not set the subnet mask address, the system retrieves the subnet mask from
a router on the local network, if one exists, or automatically sets the address to:
255.0.0.0 (for a Class A network)
255.255.0.0 (for a Class B network)
255.255.255.0 (for a Class C network)
4-8
TCP/IP
IP
How Subnet Masks Works
The network operating system uses the Subnet to extract the Network ID from an IP
address. This helps deliver the data to the correct Subnet.
Once the data is delivered, the Subnet Mask is used to extract the Host ID. This
procedure enables the data to go directly to the intended recipient after the data
reaches the correct Subnet.
Example:
Network 1 IP Address
Subnet Mask (Class B)
129.10.53.11
255.255.0.0
129.10.0.0
Network 2 IP Address
Subnet Mask (Class B)
129.11.53.11
255.255.0.0
129.11.0.0
129.10.0.0 = 129.11.0.0
The IP Address for network 1 does not match the IP Address of network 2 so
the packet is sent to a router.
Non-Standard Subnet Masks

Non-standard subnet masks are used when administrators subdivide their own
network.
Example:
255 . 255 . XXX . 000
XXX = 254
252
248
240
224
192
128
TAC
512
1024
2048
4096
8192
16384
32768
Number of Hosts
4-9
IP
Default Router
The route within a network consists of network addresses and paths. Network
Addresses contains encoded routing information. The default router is able to look at
this embedded information and make intelligent decisions to path the information.
Dotted Decimal Notation

Although IP addresses are 32-bit numbers, users seldom enter or read the values in
binary. So, when interacting with a user, the software uses a form that is easier to
understand called dotted decimal notation. The form expresses each 8-bit section (an
octet) of a 32-bit number as a decimal value and uses periods to separate the sections.
32-Bit Binary Number

10000001 00110100 00000110 00000000
10000000 10000000 11111111 00000000
Equivalent Dotted
Decimal
129. 52 . 6 . 0
128 . 128 . 255 . 0
The smallest possible value, 0, occurs when all bits of an octet are zero
The largest possible value, 255, occurs when all bits of an octet are one
The dotted decimal addresses a range from 0.0.0.0 through 255.255.255.255
Classes in Dotted Decimal Notation

Because dotted decimal notation does not make individual bits of an address visible.
The class must be recognized from the decimal value of the first octet.
The decimal range of values for each class:
4-10
Class
Range of Values
0 through 127
128 through 191
192 through 223
224 through 239
240 through 255
TCP/IP
IP
Division of the Address Space
The IP class scheme does not divide the 32-bit address space into equal size classes,
and the classes do not contain the same number of networks. The first bit of the
binary octet for Class A must be a zero allowing only seven remaining bits for
numbering Class A networks. (The binary equivalent would be 01111111)
Class A can only contain 128 networks.
The following table summarizes the maximum number of networks available in each
class and the maximum number of hosts per network.
Bits in
Prefix
7
Max. No. of
Networks
128
Bits in
Suffix
24
Max. No. Of Hosts

Per Network
16,777,216
14
16,384
16
65,536
21
2,097,152
256
Address Class
Address Assignment
Throughout an Internet, each network prefix must be unique. For networks connected
to the global Internet, an organization obtains network numbers from the
communication company that supplies Internet connections. Such companies are
called Internet Service Providers (ISPs). They, in turn coordinate their efforts with a
central organization, the Internet Assigned Number Authority, to ensure that each
network prefix is unique throughout the entire Internet.
When assigning a network prefix, a number must be chosen from Class A, B, or C;
the choice depends on the size of the physical network. Usually, networks are
assigned Class C addresses (maximum of 256 hosts) unless a Class B is required.
Class A is seldom justified because few networks contain more than 65,536 hosts.
TAC
4-11
IP
Address Assignment
Proxy Servers
There are many risks derived when Internet users can access an Intranet and vice
versa. Proxy Servers are used to control and manage who can come in from the
outside (internet) and who can go out from the inside (intranet). Basically, proxy
servers are used to keep intruders out, preventing them from damaging a corporate
Intranet. When an Intranet user goes out to the Internet, they dont actually contact
the Internet directly. They contact the proxy server and its the proxy server that
contacts the Internet.
Can be configured many of ways on how to manage and control user activity
Logs all traffic between the Internet and Intranet so administrators can check
and track attacks
Cache Internet web pages in memory for optimum network performance due
to the fact that Intranet speeds exceed that of the Internet
o This would not be acceptable for time sensitive (constant changing)
items (cached pages are not current versions)
Internet sharing (254 nodes / proxy server) through a single IP Address

assigned by the ISP
Specific proxy server software is required for different kinds of Internet

services
Note:
For a private Intranet, the choice of network prefix is be made by the
organization.
4-12
When using a proxy server, computers on the Intranet do not have true
Internet IP addresses
TCP/IP
IP
Address Assignment
IP Addressing for Routers
In addition to assigning an internet address to each host, the Internet Protocol
specifies that routers should be assigned IP addresses as well. In fact, each router is
assigned two or more IP addresses. To understand why, recall two facts:
A router has connections to multiple physical networks.
Each IP Address contains a prefix that specifies a physical network.
A computer (in this case, a router) with multiple network connections must be
assigned one IP address for each connection.
TAC
4-13
IP
Address Assignment
Example
An example will help to clarify IP Addressing and explain how addresses are
assigned in practice. Consider an organization that decides to form a private TCP/IP
Internet consisting of four physical networks. The organization must purchase routers
to interconnect the four networks and then must assign IP Addresses.
To begin, the organization must choose a unique prefix for each network. This is
usually done by the network administrator to ensure that numbers are not duplicated.
The administrator estimates the ultimate size of each physical network, and uses that
size to choose a prefix.
In this example, the organization expects one small network, two medium size
networks, and one extremely large network. With this information, the administrator
might choose to assign a Class C prefix to the small network, two Class B prefixes to
the two medium size networks, and a Class A prefix to the large network.
A Private Internet with Assigned IP Addresses
Host Suffixes
The IP address assigned to a host always begins with the prefix that has been assigned
to the hosts physical network.
The suffixes assigned to the hosts themselves, can be arbitrary numbers.
The two hosts attached to the 128.10 Class B network, have been assigned suffixes 1
and 2. They do not need to be assigned sequentially as indicated in the Class A
network where the hosts are identified as 37 and 49.
4-14
TCP/IP
IP
Ping (Packet Internet Grouper)
Ping is a command line utility used to test the connectivity between two devices and
most commonly used for troubleshooting purposes.
How Does Ping Work?

Ping sends a signal and listens for the echo to come back.
When using the Ping command, it's testing the very basic parts (the network
connectivity) of the TCP/IP protocol on your network.
By default, Ping sends four transmissions of 32 bytes each. This verifies that you can
connect to the host that you are pinging.
Limitations
TAC
Ping only verifies whether or not the communications protocol is functioning

at the remote node you ping.
Pinging does not deliver information about software or hardware.
A positive response from a pinged node does not mean that the all software or
hardware at the node is operating correctly.
CX/NetControllers will respond to, but cannot initiate a ping
4-15
IP
Ping Examples
Ping by IP address:
The first ping initial look-up

requires a bit more time
C:\>ping 207.76.105.9
Pinging 207.76.105.9 with 32 bytes of data:
Reply from 207.76.105.9: bytes=32 time=766ms TTL=105
Ping by host name (remote host):

C:\>ping www.andovercontrols.com
Pinging www. andovercontrols.com [207.76.105.9] with 32 bytes of data:
Ping by host name (locale host):

Note: not supported on all networks
C:\>ping CYBERSTATION254
Pinging CYBERSTATION254 [207.68.137.65] with 32 bytes
of data:
4-16
TCP/IP
IP
Using Ping
Ping Command Line Switch Options
The Ping command provides the following switch options:
ping [-t] [-a] [-n count] [-l length] [-f] [-i ttl] [-v tos] [-r count] [-s count]
[[-j computer-list] | [-k computer-list]]
[-w timeout]
destination-list
Each of these switches is described below.
-t This tells Ping to continue pinging until it is interrupted by the user. This is useful
if you suspect cable problems because you can jiggle the wires without having to
keep typing the command.
-a This tells Ping to resolve the address to a computer name and display this as well.
-n count This is the number of echo requests that the command should send. As you
have seen, the default is four.
-l length By default, Ping sends 32 bytes of data. Using this option, you can increase
the size of the echo packet that is sent. This enables you to test packets up to 8192
bytes in size, which normally causes your packets to fragment.
-f This sets the do not fragment control bit in the IP header. Using this, you can
determine the maximum size of the packet that can be sent to a remote host. This
information can be used to optimize TCP/IP.
-i ttl This sets the Time to Live in the IP header, enabling you to control how long
the packet stays on the wire. You can use this to see whether your packets are
occasionally being sent through alternate routes that are causing them to time out.
-v tos This enables you to set the Type of Service field in the IP header. This can
be used to figure out what types of service are available on remote routers and hosts.
-r count This records the route that the packet took in the record route field. This can
record from 19 computers as specified by the value given as count.
TAC
4-17
IP
Using Ping
Ping Command Line Switch Options
-s count Tells the system to keep the timestamp information for the number of hops
given.
-j computer-list These are the systems (routers) that you want to send the packet
through. They enable you to set the route that the packet takes. The maximum number
you can enter is 9. The systems listed do not have to be joined directly to each other
(there can be other hops between them).
-k computer-list This is similar to the -j option. There cannot be other hops,
however, between the computers listed with this switch.
-w timeout This specifies the period Ping waits for the reply before deciding that the
host is not responding.
Destination-list This tells Ping which computer you want it to send echo requests
to.
4-18
TCP/IP
IP
DHCP (Dynamic Host Configuration Protocol)
DHCP is a protocol that dynamically assigns IP addresses to hosts in a network.
TAC
DHCP allows for each host to extract an IP address, subnet mask and
default router from the server
Reduces the work to administer a large IP network
Requires:
-
DHCP server
Forwarding agent in each router
DHCP capability in each clients TCP/IP support
Depending on the configuration of the DHCP server, an IP address

may remain fixed once obtained or can change on each reboot
4-19
IP
IPconfig
IPconfig is a command line utility used to display the IP configuration settings of a
computer.
It is used to check that all the appropriate configuration parameters are set up in the
PC operating system (Windows).
If you just enter IPconfig without any parameters, it will return the basic TCP/IP
configuration to the screen.
You can get additional information by entering IPconfig/all
Most of the other switches (which arent described here) are useful for DHCP and
multi NIC applications.
4-20
TCP/IP
TCP
TCP Message Types
TCP (Transport / Transmission Protocol)
TCP is a protocol developed for the Internet to get data from one network device to
another. TCP retransmission strategy is to ensure that data will not be lost in
transmission.
TCP is the error checking part of the TCP/IP protocol
It is TCPs job to ensure that data is received reliably between source and
destination
Considered to be a confirmed message
UDP (User Datagram Protocol)

UDP is a connectionless protocol that provides unreliable (at this level) datagram
services and is part of the TCP/IP protocol suite.
TAC
Allows the computer the capability of sending information with out an actual
connection to another machine
All error processing and re-transmission must be taken care of from the
application program.
Considered to be an unconfirmed message due to the fact of non-connectivity

between hosts
4-21
4-22
TCP/IP
Ch 5
Continuum IP
Contents
Continuum IDs
ACCNetID / Energy Net Id
CX / NetController Settings
Cyberstation
CX 9702
Layer 5 Addressing
TCP/IP Settings
IP Address
Subnet Mask
Teach
CommStatus / MaximumResponseTime
Probe Time
CX Error log
Data Exchange in Continuum
Point-to-Point
Import / Export
5-2
Continuum IP
Continuum IDs
ACCNetID / Energy Net Id
Each Network device in a Continuum system (workstations and
CX/NetControllers) has an assigned ACCNetID number.
This ACCNetID is also referred to as Energy Net Id through the Dumb Terminal
Interface.
The ACCNetID / Energy Net Id is assigned by the Continuum Administrator.
This ACCNetID attribute is used as a Network Address in the Continuum
system. All nodes use the ACCNetID attribute in addition to the IP Address when
sending messages.
The Valid Range for the ACCNetID / EnergynetId setting:
CX/NetControls Valid Range (1 190 unique value per network)

Workstations
Valid Range (191 - 254 unique value system wide or 0)
The use of ID 0 (zero) is covered in the Administrator Class
The same NetController seen through the eyes of the Dumb Terminal (left)
and the Workstation (right)
Dumb Terminal View
(Energy Net Id)
Workstation View
(ACCNetID)
Same NetController setting
TAC
5-3
Continuum IDs cont

CX / NetController Setting
Valid Range 1 190
Set from Dumb Terminal
Cyberstation Setting
Set at time of installation
Valid range 191-254 or 0
ACCNetID attribute
of the workstation
5-4
Continuum IP
Continuum IDs cont

Layer 5 Addressing
ACCNetID is layer 5 addressing
To
From
Continuum Continuum
Layer 5 Destination
Source
DATA
Continuum
World
DATA
Software
IP Addresses
DATA
NIC
Card
To
IP
Layer 3 Destination
IP
Source
From
Layer 2
MAC
Destination
To
TAC
MAC
Source
From
5-5
TCP/IP Settings
Enter the IP Address, Subnet Mask and Default Router assigned by the Network
Administrator.
If on a private Continuum network with no routers, leave it at its default

setting of 0.0.0.0
After setting and saving the controllers TCP/IP settings, a reset must occur for the
controller to use these new settings.
Dumb Terminal View
5-6
Workstation View
Continuum IP
Teach
Teach is the application, which updates or "teaches" all Infinity controllers, including
the b4 controllers, about the Cyberstation device and teaches all Infinity controllers
about each other.
Performing a Teach on the network allows you to select from three different modes:
InfinityController Teach
Network Teach
Global Teach
When you install a workstation with an ACCNetID of 0, then it is not taught to the
CX Controllers.
Alarms and Events sent to the workstation with an ACCNetID of 0 will be forwarded
with an ACCNetID greater than 0 (191-254).
TAC
5-7
CommStatus / MaximumResponseTime
CommStatus
The CommStatus is an attribute that indicates whether a device is online or offline.
Each device on a Continuum network will maintain its own CommStatus list
of the other nodes.
CommStatus is always a local perspective of the other nodes.
The CommStatus of another node will determine whether or not an attempt

will be made to deliver a communications message.
Maximum Response Time

Maximum Response Time is the number of seconds each unit on the network should
wait for a response from another node.
When any message is sent on the Continuum IP network, a response is

required.
If a response is not received within the MaxResponseTime (default 5 sec.), a

retry of the message will occur.
If there is again no response, a second retry will occur.
If there is still no response, that node will be determined to be off-line.
PPP IP Address: If this is to be a dial-up network, you need to enter the Point-toPoint Protocol Address for the NetControllers commport3s RS-232 connection.
5-8
Continuum IP
ProbeTime
The Probe message is an are you on-line message that each node will send out
on a periodic basis.
The ProbeTime (60 sec. default) attribute of the Controller and Workstation
determines how often this takes place.
Each Controller on the Continuum Network will probe all nodes that it has been
taught that it has not heard from during that current probe cycle.
If CX/NetController 1 probes CX/NetController 2, then CX/NetController 2 will

not need to probe CX/NetController 1 as it has just heard from it.
Workstations will probe all controllers on all networks.
Increasing the probe time on all nodes will reduce the background
communications on the network. It will also increase the time it takes to discover
that a node is off-line.
Increasing the Probe Time of a single node will result in that node responding to
rather than initiating probes.
Workstation
Probe Time Attribute Setting
TAC
CX/NetController
Probe Time Attribute Setting
5-9
CX Error Log
CX controllers maintain an error log in memory. This may be requested by tech
support when assisting with site related problems
Can maintain a maximum of 255 entrees
Accessed for reading only (you can not edit this error log)
Resetting the CX/NetController clears the error log
Retrieving the Error Log

1. From HyperTerminal, edit the controller you are physically connected to.
2. Press the F2 key on your keyboard to retrieve the error log.
5-10
Continuum IP

When a program is written in the CX/NetController, the programmer determines
which method of communications is going to be used, based on how they wrote the
program.
There are two methods in which data is exchanged on a Continuum Network:
Point-to-Point
Import / Export
Point-to-Point
Data is retrieved / sent on demand (as-needed basis)
Used when:
-
Referencing an objects attribute

Setting a remote object
Referencing in an indirect manner such as using the GetName
keyword or using OpenList / GetObject programs
Supported by Cyberstation & CX / NetControllers
Cyberstation - All data exchange in Cyberstation is via Point-ToPoint

-
Retrieval of attribute values

Setting of remote objects
CX / NetController - Data retrieval occurs when the attribute of an

object, (value, state), is referenced from a Plain English Program.
LocalOAT = CX1 OAT (Import / Export)
LocalOAT = CX1 OAT Value
TAC
(Point-to-Point)
Value is the
attribute of OAT
Every time the Plain English Programs statement is executed,

a message will be sent across the network to retrieve that
particular attributes value of that object
Failure to receive a valid response will result in the program

either disabling or go to Line E
5-11

Point-to-Point
There are 4 types of messages that the CX / NetController initiates to the

Cyberstation:
-
Probe
Delivering Alarm Messages
Delivering Card Access Event Messages
Delivering a Data-Base Synchronization Message
The CX / NetController can neither look at or set the value of objects in the
Cyberstation
Import / Export
Data is delivered only when an objects value changes
Used when referencing a point by its Name in a Plain English Program

LocalOAT = CX1 OAT
LocalOAT = CX1 OAT Value
(Point-to-Point)
Supported by CX/NetControllers and Infinet controllers (not the workstation)
5-12
OAT is the objects Name (Import / Export)
CX / NetController - CX/NetControllers can talk to other

CX/NetControllers
-
Can Retrieve a value on the same Continuum Network only
The Program uses the last known value

(Other controllers being off-line will not result in disabling the
program or line E)
Continuum IP

Benefits / Drawbacks & Precautions
Point-to-Point:
Benefits
o Data is retrieved only when you need it
o Retrieves any attribute of an object
Drawbacks
o Significant impact on the scan time (step 4)
The scan is suspended until the retrieval of data is

complete
Initiating many controllers within a single program

dramatically increases the scan time
o Programs disable if they fail to retrieve data
Precautions
o Always check the CommStatus of the other controller before
retrieving data
Use the If, Then or Else statements when checking for

the CommStatus of another controller
CommStatus is the result of the last probe
o Always use Line E (from a programming perspective)
TAC
5-13

Benefits / Drawbacks & Precautions
Import / Export:
Benefits
o Data is transmitted on change of value only
o Off-line controllers do not cause a program to disable or go to
line E
Drawbacks
o Can lead to significant network messages on analog values
o Freshness of data is unknown
Precautions
o Use threshold on analog inputs to reduce traffic
5-14
Continuum IP
Ch 6
BACnet IP
Contents
BACnet IP Network Definition
BACnet IP Concept
Addressing Within BACnet IP Networks
BACnet IP Broadcast Management
Single IP Subnet
Multiple IP Subnet
BACnet Broadcast Management Device Concept (BBMD)
Broadcast Distribution
Router Operations
Routing Between BACnet IP & Non-BACnet IP Networks
Routing Between Two BACnet IP Networks
BACnet IP Inter-network Design Conciderations
BACnet Over Ethernet Vs BACnet IP
Commissioning the b4920 Controller
b4920 Device Object Configuration
BACnet Device Editor
Address Resolution Protocol (ARP)
6-2
BACnet IP
BACnet/IP (B/IP) Network Definition

A BACnet/IP network is a collection of one or more IP subnetworks (IP domains)
that are assigned a single BACnet network number.
B/IP Concept
A BACnet/IP network shall function in concept identically to the other non-IP
network types with respect to directed messages and broadcast messages, including
local, remote, and global broadcasts.
A directed message shall be sent directly to the destination node
A "local broadcast" shall reach all nodes on a single B/IP network
A "remote broadcast" shall reach all nodes on a single BACnet network

with network number different from that of the originator's network
A "global broadcast" shall reach all nodes on all networks
Addressing within B/IP Networks

In the case of B/IP networks, six octets consisting of the four-octet IP address
followed by a two-octet User Datagram Protocol (UDP) port number (both of which
shall be transmitted most significant octet first) shall function analogously to the
MAC address.
This address shall be referred to as a B/IP address. The default UDP port for both
directed messages and broadcasts shall be X'BAC0' and all B/IP devices shall support
it.
In some cases, e.g., a situation where it is desirable for two groups of BACnet devices
to coexist independently on the same IP subnet, the UDP port may be configured
locally to a different value without it being considered a violation of this protocol.
An IP multicast address in conjunction with an appropriate UDP port may be used in
lieu of the B/IP broadcast address.
TAC
6-3
B/IP Broadcast Management, Single IP Subnet

In this case, the B/IP network consists of a single IP subnet. A "local broadcast" shall
use the B/IP broadcast address and the Network Layer Protocol Data Unit (NPDU)
shall be transmitted in a BACnet Virtual Link Layer (BVLL) Original-BroadcastNPDU message. Because all nodes are on a single IP subnet, such messages will
automatically reach all nodes.
A B/IP network consisting of a single IP subnet
B/IP Broadcast Management, Multiple IP Subnets

In this case, the BACnet/IP network consists of two or more IP subnets. A "local
broadcast" shall use the B/IP broadcast address, and the NPDU shall be transmitted in
a BVLL Original-Broadcast-NPDU message.
Because standard IP routers do not forward such broadcasts, an ancillary device
called a BACnet/IP Broadcast Management Device (BBMD), is required to perform
this function.
A B/IP network consisting of two IP subnets
6-4
BACnet IP
BBMD Concept
BBMD's listen for all BACnet Broadcasts which are local subnet broadcasts. Their
job is to resend these broadcasts to devices on their subnets and to pass them to other
BBMD's on other subnets for further distribution. Since BACnet messages are Local
subnet IP broadcasts, services such as WHO IS/I Am, Alarm and COVNotifications
will not work beyond the local subnet without the use of a BBMD.
There are two methods for implementing the necessary functionality of the BACnet
Broadcast Management Device (BBMD).
Method 1: One BBMD system wide
Add BACnet device register with the BBMD. This is known as Foreign
device registration
This is an inefficient method as all messages must go through the BBMD.
The Continuum Cyberstation is Andover Control's interim solution until the

release of the b4000
Method 2: One BBMD on each subnet
TAC
BBMDs only have to know about each other
All BACnet devices have their own view of the world and use the BBMD to
transmit to other devices beyond their limited view.
b4000 will be Andover's BBMD solution
Only one BBMD per Subnet in accordance with the BACnet standard.
6-5
Broadcast Distribution
B/IP Network
BBMD
BACnet
Device
BACnet
Device
BACnet
Device
BACnet
Device
BACnet
Device
IP Router
Internet
IP Router
BBMD
BACnet
Device
B/IP Remote Subnet

A BBMD sending a directed message to the BBMD on the remote subnet
6-6
BACnet IP
Router Operation
There are two possible differences:
1) On the B/IP side, the B/IP address is used in place of the MAC layer address.
2) If B/IP and non-B/IP BACnet devices reside on the same physical LAN, then all
traffic is typically sent and received through a single physical port. The collection
of B/IP devices would, in such a case, have a network number distinct from the
network number of the non-B/IP devices. Such a scenario could easily occur on an
Ethernet network where some devices are IP-capable while others are not.
Although the foreign registration process provides the ability for remote devices to
participate in a particular B/IP network, there may be occasions when it is desirable
for two collections of B/IP devices to interoperate more closely. This type of
interoperation can only produce results consistent with the assumptions and intent
contained in the original BACnet standard if the configuration of the two B/IP
networks has been coordinated.
For example, it is assumed that Device object identifiers are unique "internetwork
wide." If this is not the case, the Who-Is service will produce ambiguous results.
Similarly, the Who-Has service may be useless for dynamic configuration
applications if multiple instances of objects with identical object identifiers exist.
The BACnet standard also assumes that only a single path exists between devices on
different BACnet networks and that this path passes through a BACnet router. The
internet's web topology violates this assumption in that, apart from security
constraints such as "firewalls", any IP device can communicate directly with any
other IP device if it knows the device's IP address.
TAC
6-7
B/IP Routers
BACnet Routers are devices that interconnect two or more BACnet networks to form
a BACnet internetwork. BACnet routers make use of BACnet network layer protocol
messages to maintain their routing tables.
B/IP routers adhere to the requirements of BACnet routers with the following
differences:
1) The physical ports of standard BACnet routers are replaced by logical ports. Each
logical port is identified by the unique B/IP address of the port's connection to the
B/IP network served by the router.
2) The term "directly connected network" in BACnet implies a physical LAN
connection between a LAN segment and a physical router port. In the case of B/IP
"directly connected network" is extended to mean any B/IP network from which a
router can receive local broadcast or IP multicast messages. Such networks are:
The B/IP network on which a router resides by virtue of having an IP network

number in common with one of the IP subnets comprising the B/IP network
A B/IP network in which the router participates as a member of an IP

multicast group
A B/IP network in which a router participates by having registered as a

foreign device with a BBMD serving that network.
3) Networks that are not directly connected are called "remote networks." Remote
networks, whether B/IP or non-B/IP, may be reachable by communicating using B/IP
with a router serving the remote network.
B/IP Router Operation

Upon start-up, each B/IP router shall search its routing table for active entries
indicating direct connection via foreign registration with a BBMD. The router shall
then proceed to register itself with each such network. At the conclusion of all such
registrations, the router shall broadcast an I-Am-Router-To-Network message
containing the network numbers of each accessible network except the networks
reachable via the network on which the broadcast is being made. Note that networks
accessed through a given active UDP port that are not directly connected, but are
reachable by means of communication with another B/IP router shall, upon router
startup, be deemed to be reachable.
6-8
BACnet IP
Router Operation
Routing Between BACnet IP & Non-BACnet IP Networks
A BACnet router can be used to convey messages between devices on a B/IP
network and non-B/IP network.
Routers re-package BACnet

messages and re-transmit
them unchanged
BACnet / IP Network
BACnet
Workstation
BACnet
Field 1
Panel
Ethernet to
ARCNET
Router
Ethernet to
MS/TP
Router
Sensors & Actuators
BACnet LAN - ARCNET

BACnet
Field
Panels
BACnet
Field
Panels
Sensors & Actuators
TAC
BACnet LAN MS/TP
Sensors & Actuators
6-9
Router Operation
Routing Between Two BACnet IP Networks
B/IP Network 1
BBMD
BACnet
Device
BACnet
Device
BACnet
Device
BACnet
Device
BACnet
Device
IP Router
Internet
IP Router
BBMD
BACnet
Device
B/IP Network 2
BACnet devices speak using IP directly
6-10
BACnet IP
B/IP Inter-network Design Considerations

This standard recognizes that BACnet internetworks containing one or more B/IP
networks can be configured in a variety of ways, depending on the requirements of an
installation. Any of these configurations shall be deemed to conform to this standard
provided they employ the techniques specified in this clause.
1) Depending on local traffic conditions and security requirements, all B/IP

subnetworks can be configured into a single B/IP network.
2) Creating two or more B/IP networks, each with a unique network number, can be
useful for limiting the propagation of local broadcast messages and for providing
security by confining traffic to a particular geographic or logical area.
3) A single device can be configured to provide all the routing for a B/IP
internetwork.
The advantages include:
Only a single routing table is required

The possibility of creating multiple paths between B/IP networks is
eliminated
The resulting star topology is easy to conceptualize
The disadvantages are
TAC
There is a single point of failure

A single device could present a traffic bottleneck under heavy load
conditions
6-11
BACnet Over Ethernet vs. BACnet IP

BACnet over Ethernet
- Special Tunneling Routers (BTR)
- Not IP friendly
WS
IP Network
Tunneling Router
BACnet Network
BACnet Device
BACnet Device
BACnet/IP
- BACnet devices are IP capable
(Do not require BTR)
WS
BACnet & IP Network
BACnet Device
6-12
BACnet Device
BACnet IP

You can not access the b4920 through a terminal emulator program, so you must
access it through its IP Address.
TAC
6-13

When you initially access the device, its configuration properties as well as other
current values and network protocols are displayed. In order to make changes to the
device you must select the Configure Controller option.
6-14
BACnet IP

Once you access the configuration editor of the device, you can make changes to
some of the properties while many others are read-only properties.
TAC
6-15

The second option available to the user is to configure login, which prompts for
password associated with the accessing of this device.
6-16
BACnet IP

All ACC BACnet objects, except alarms, are first configured as Continuum objects
and will show up as configurable BACnet objects once a Save to Database is
performed.
The basic steps for creating BACnet objects:
1. Create a New Infinity Controller
2. Make the appropriate settings from the InfinityController Editor
TAC
6-17

3. Perform a Teach
4. From the BACnet Devices, perform a Send to Database from the controller that
was just created
Once a BACnet device has been saved to the Continuum SQL database, you can
open its device editor.
6-18
BACnet IP

General Tab
To open the BACnet Device Editor, right click the device icon in the Explorers
navigation pane, and select Open from the dropdown menu. The Device editor opens
with the General tab displayed.
Note: When you are editing a BACnet Device object, fields in the editor will be
unselectable (grayed-out) for those properties that the BACnet device does not
support.
The general tab summarizes the network features of the device, most of which are
automatically supplied by the system. A few remaining inputs and actions are
supplied by the user.
Description
BACnet Network
Number
Model Name
Device Node ID
TAC
Name of the device and its node number.

Specifies the ID of the BACnet IP network
Displays a model name based on the information it
receives via the BACnet protocol.
The node ID number assigned to the device
6-19

General Tab cont
Based on the current status of the device, this displays
one of the following:
Device Status
Comm Status
Primary Access
Server
Secondary
Access Server
BACnet MAC
Address
Auto Download
Probe Time
Out of Service
6-20
Operational - Indicates the device is working and is

ready to receive or transmit data.
DownloadRequired - Indicates the device requires a
download of information
NonOperational - Indicates the device is offlline or
that a fault has been detected.
OperationalReadOnly - Indicates the device is
working and ready to transmit data.
DownloadInProcgress - Indicates a download is in
progress and the device will not be ready to transmit data
until the download is complete.
Continuum sets the comm status to OnLine or OffLine
depending on whether the workstation is in
communication with the device.
Check this checkbox to designate this workstation as the
primary access server.
Check this checkbox to designate this workstation as the
secondary access server.
The Media Access address assigned to the device.
Enables a device to auto download schedules to
controllers.
Set the interval in seconds by which the device checks
the comm status of the other connected CX series
controllers and CyberStations. When the device does not
receive a response from another CX controller or
CyberStation within the probe time, it changes their
comm status to Offline.
When checked, hides the selected device.
BACnet IP

General Tab cont
BACnet
Workstation
Location
Container Type
Default Folder
Reinitialize Device
Teach
Add check in checkbox to identify a third-party device as

a workstation. It will show up as an olive computer icon
in the Explorer.
Type in the physical location of the device (optional).
Enter up to 32 characters of text that indicates the
container type (workstation).
Specifies the default folder that the device will appear
under.
When selected, brings up the Reinitialize Device dialog.
(See below.)
Invokes the teach mode
Reinitializing b3 and b4 Controllers

Andover b3 and b4 controllers contain EPROM flash memory that can be upgraded
electronically. Whenever a reset is desired or power failure occurs, these controllers
can be reinitialized. This can be accomplished as a cold start or a warm start, defined
as follows:
Cold Start - When the controller comes up from a reset and recalls a backup copy
of the controllers original RAM database
Warm Start - When the controller comes up from a reset and recalls a copy of the
controllers database at the time the reset or power failure
occurred.
TAC
6-21

General Tab
Reinitializing b3 and b4 Controllers cont
To reinitialize a controller proceed as follows:
1) Click the Reinitialize Device button to bring up the Reinitialize Device dialog:
2) Click the State fields down-arrow button to open the dropdown menu and select
the desired reinitialize state (Coldstart or Warmstart).
3) Enter your password in the Password field. (Enter a password on third-party
BACnet devices only. Andover b3 and b4 controllers do not require a password.)
4) Click the OK button.
Teach
The Teach feature is implemented on Andover CyberStation devices only. It
is not implemented on BACnet devices.
6-22
BACnet IP

Details Tab
The Details tab is a read-only tab that supplies various information about the BACnet
device. The two most important items on this tab are the Supported Object Types
and the Supported Services windows, which list the objects and services that are
supported by the device:
Supported
Services
Supported Object
Types
Vendor Name
Vendor ID
Software Revision
Firmware
Revision
Protocol Version
Max APDU Length

Accepted
TAC
Lists the types of BACnet services that are supported by

the device.
Lists BACnet objects that are supported by the device.
Displays the name of the vendor who manufactured the
device.
Displays the vendor's corporate ID number.
Displays the version number of the software application
supported by this device.
Displays the version number of the devices firmware.
Displays a number that indicates which specific set of
standardized protocol services and object classes this
object supports.
Represents the maximum number of octets that may be
contained in a single, indivisible application layer
protocol
data unit.
6-23

Details Tab cont
APDU Timeout
Segmentation
Support
Segmentation
Timeout
6-24
Displays the maximum number of times that an APDU

(application protocol data unit) shall be retransmitted.
The default value is 3. If you have access permission,
you may change the number in this field.
Displays the amount of time in milliseconds between
retransmission of an APDU requiring acknowledgment
for which no acknowledgment has been received. The
default value is 60,000 milliseconds. If you have access
permission, you may change the number in this field.
Displays the amount of time in milliseconds between
retransmission of an ADPU segment. The default value is
2000 milliseconds. In order to achieve reliable
communication, all intercommunicating devices should
have the same Segment timeout value. If you have
access permission, you may change the number in this
field.
BACnet IP

Known Devices Tab
The Known Devices tab lists the BACnet devices that exist on the network that can
be monitored by this device. Entries in the list identify the actual device addresses
that are used when the device is accessed via a BACnet service request.
Displays the path of the device.

Device
BACnetNetworkNumber Specifies the ID of the BACnet IP network.
The Media Access address assigned to the device.
BACnetMacAddress
TAC
6-25

Time Tab
The Time tab is where you synchronize the BACnet device time and date to the
systems local time and date:
Local Time
UTC Offset
Enter the local time hour: minutes: seconds AM or PM

Enter the Universal Time Coordinate (UTC) offset in
minutes. This is the number of minutes difference
between your local time and Greenwich Mean Time:
300 means you are 300 minutes (5 hours) ahead
of Greenwich Mean Time.
-300 means you are 300 minutes (5 hours) behind

Greenwich Mean Time (see Note, below).
The following are UTC offsets for the Continental
United States:
Eastern Standard Time (EST) -300
Central Standard Time (CST) -360
Rocky Mountain Standard Time (RMT) -420
Pacific Standard Time (PST) -480
Enter the date month/ day/ year
Check if daylight savings time is in effect.
Local Date
Daylight Savings
Synchronize to
Use the BACnetDevice window to locate the new
Local Time and
BACnet device. (See below.)
Date
Note: ACC represents EST as UTC 300, but BACnet is the opposite. The mapping
between ACC and BACnet UTC occurs automatically.
6-26
BACnet IP

Time Tab cont
Synchronizing a New BACnet Device with the Systems
Local Time and Date
1) Scroll through the BACnetDevice window to locate the new BACnet device.
2) Click the device to highlight it.
3) Click the Add button.
4) Click the Sync Time button.
Note: To remove a BACnet devices local time and date from the system, perform
steps 1 and 2 (above), and the click the Delete button.
TAC
6-27
Address Resolution Protocol (ARP) Procedure

Procedure to Restore B4xxx Controller to Factory Default Settings
The procedure that follows will allow you to reset your controller to it's factory
default address settings:
IP Address: 169.254.1.1
Subnet Mask: 255.255.0.0
Gateway: 0.0.0.0
Webserver Port: 80
Web User Name: acc
Web User pwd: acc
EnergyNet ID: 1
BacNetMstpNetId: 2764
BacNetUDPNetId: 2765
During controller startup, there is a 2 minute window in which the controller will
be restored to factory defaults based on the following:
1. Seconds since startup is < 120
2. A Ping packet is received by the controller with a matching Ethernet
address but unmatched IP address.
3. Ping payload size of 255 bytes.
Prior to running the procedure, the controller must be on the same network as the
PC that that is used to issue commands.
Prior to running the procedure, you will need to have on hand (1) IP address that
is both valid and NOT in use on the network that the PC and Controller are
connected to.
6-28
BACnet IP

cont
1. Get Your Controllers MAC Address
Each controller has a 6 byte hardware address, also known as the MAC
address or Ethernet address.
The address is represented in HEX.
The first three bytes of the MAC address are constant and represent Andover
Controls vendor ID : 00-40-11
The last 3 bytes of the MAC address are derived from your controller's serial
number.
The controller's serial number is printed on the board and is represented as an
Integer value.
You must convert this value to HEX in order to obtain the last 3 bytes of your
controllers MAC address.
Ex. Integer Serial Number: 1033394
Converted to Hex: FC4B2
Controller's MAC: 00-40-11-0F-C4-B2
2. Create a batch file named Acc.bat with the following content:
TAC
arp -s %1 %2
ping -l %3 %1
arp -d %1
6-29

cont
3. Restart the B4xxx Controller
Within 2 Minutes of restarting, run the batch file with the 3 arguments:
Acc.bat <IP Address> 00-40-11-XX-XX-XX 255
Where IP Address = valid IP on the network
Where XX-XX-XX = last 3 bytes of controller's MAC
Where 255 = Ping Payload size
4. After issuing the command, the controller should restart and the factory default
address settings restored.
6-30
BACnet IP
Ch 7
RS-485
Contents
What is RS-485
EIA (Electronics Industry Association)
Differential Data Transmission / Balanced Differential Signal
Shielded Twisted Pair RS-485 Network Schematic
RS-485 Transceiver
Voltage Differences
RS-485 Termination
UART (Universal Synchronous Receiver Transmitter)
Data Frames
- Start & Stop bits
- Frame Errors
7-2
RS-485
What is RS-485 ?
RS485 is an EIA (Electronics Industry Association) serial line standard that specifies
2-wire, half-duplex, differential line, multi-point communications.
Maximum cable length is 1200m.
Maximum data rates are 10Mbps at 1.2m or 100Kbps at 1200m.
EIA-485 can implement a truly multi-point communications network, and specifies
up to 32 drivers and 32 receivers on a single (2-wire) bus.
Multi-Drop Network
Uses Twisted Pair Cable
Balanced Line
Low cost
RS-485 type networks are used in Andover Controls Continuum IO and Infinet
networks.
The BACNet-MS/TP Field Buss is an RS-485 network.
RS-485 defines the 2 wire balanced line differential signaling method.
The RS-485 standard is an OSI layer 1 implementation.
TAC
7-3
Electronics Industry Association (EIA)

The Electronics Industry Association (EIA) has produced standards for RS485,
RS422, RS232, and RS423 that deal with data communications.
EIA standards were previously marked with the prefix "RS" to indicate recommended
standard; however, the standards are now generally indicated as EIA or TIA to
identify the standards organization.
While the standard maintains uniformity to data communications, many areas are not
specifically covered and remain as "gray areas" for the user to design for their own
application. Gray areas include:
7-4
Protocols
Repeaters
Media Conversion
RS-485
Differential Data Transmission / Balanced Differential

Signal
When communicating at high data rates or over long distances, single-ended methods
are often inadequate. Single-Ended is 1 wire carrying a signal that is referenced to
the second wire that is grounded.
Differential Data Transmission (balanced differential signal) offers superior
performance in most applications.
Differential signals can help nullify the effects of ground shifts and induced noise
signals that can appear as common mode voltages on a network.
R1
120
RS-485 Network Schematic (Twisted Pair)
R2
120
Up to 32 Transceivers (Half Duplex Operation)
TAC
Max Common Mode Voltage:
-7V to +12V
Receiver Input Impedance:
12K ohm
Minimum Generator Load:
60 ohm
Generator Short Circuit Current:
<250mA to 7V / +12V
7-5
RS-485 Transceiver
Line drivers and receivers more frequently called transceivers, are used to
exchange data between two or more points (nodes) on a network. Reliable data
communications can be difficult in the presence of induced noise and ground level
differences.
RS-485 (differential) was designed for long distances and higher Baud rates.
Data rates of up to 128K bits / second and distances up to 4000 Ft. can be
accommodated with RS485.
A multi-drop "type" application has many desirable advantages. A true multidrop network consists of multiple transceivers connected on a single bus, where
any node can transmit or receive data.
RS-485 meets the requirements for a truly multi-point communications network,
and the standard specifies up to 32 drivers and 32 receivers on a single (2-wire)
bus. With the introduction of "automatic" repeaters and high-impedance drivers /
receivers this "limitation" can be extended to many of nodes on a network.
RS-485 extends the common mode range for both drivers and receivers in the "tristate" mode and with power off.
RS-485 drivers are able to withstand "data collisions" (bus contention) problems
and bus fault conditions.
Transceivers are in a high impedance state when in receiver mode, having very
little effect on network signals. The transceiver switches to a low impedance state
when in driver mode. Only one transceiver can be in driver mode at a time. This
must be managed in the network protocol and is not a part of the RS-485
specification.
7-6
RS-485
Voltage Differences
RS-485 uses a principle where each signal uses one line of a twisted pair (TP) cable.
For RS-485, the cable can be up to 4000 feet (1200 meters) long.
Label one of the TP wires as Plus '+' and the other as Minus '-'.
The signal is inactive when the voltage at Plus is negative and the voltage at Minus is
positive. Otherwise, the signal is active with Plus being positive and Minus being
negative. It is the difference between the wires A and B that matters.
RS-485 is used for multipoint communications: more devices may be connected to a
single signal cable.
Many RS-485 systems use Master/Slave architecture, where each slave unit has its
unique address and responds only to packets addressed to this unit. These packets are
generated by the Master, which periodically polls all connected slave units.
Communication goes over the single line in both directions. It is important to prevent
more devices from transmitting at once.
In this RS-485 network, all devices are connected to a single Twisted Pair cable.
Thus, all of them must have drivers with tri-state outputs.
For a basic RS-485 system, we need an I/O driver with differential outputs and an I/O
receiver with differential inputs.
Noise and interference is introduced into the line; however, since the signal is
transferred via twisted pair cable, the voltage difference (between Plus and Minus) of
this interference is almost zero. Due to the differential function of the RS-485 input
amplifier of the receiver, this interference is eliminated. The same is true for crosstalk from neighboring lines, as well as for any other source of interference, as long as
the absolute maximum voltage ratings of the receiver circuits are not exceeded.
Differential inputs ignore different earth potentials of the transmitter and the receiver.
Twisted Pair cables used with the correct terminations, allow data transfer over large
multi node networks.
RS-485 circuits are more complex and more expensive. Higher data transfer speeds
require correctly connected and matched terminations, which can be a problem in
systems where the number of connected devices changes.
TAC
7-7
Voltage Differences
In a balanced differential system, the transmitter generates a voltage between 2 to 7V
(approx.) between the Plus and Minus outputs. Although the transmitter and the
receiver are connected with a ground wire (GND) as well, it is never used to
determine logic levels at the Plus & Minus wires.
This implies already mentioned tolerance of different ground potentials of the
transmitter and the receiver. RS-485 transmitters have an Enable input, allowing to
set the outputs to high impedance state, allowing several devices to share a single TP
cable.
RS-485 receivers react to voltage difference between the Plus & Minus inputs. If
VPlus/Minus is greater than 200mV, a logic level is defined on the receiver output.
For VPlus/Minus less than 200mV, the logic level is opposite.
Single Ended
5 Volts
0 Volts
Differential
+ 5 Volts
0 Volts
0 Volts
7-8
5 Volts
RS-485
RS-485 Termination
For correct operation of the transmitter and the receiver, a return signal path between
the grounding of individual devices is required. The ground is usually made by a third
wire, or by grounding each device.
All Andover Controls Controllers CX Controllers & Infinet Controllers and IOU
modules must be grounded.
For RS 485, the termination is somewhat more complex. Since each device
communicates bi-directionally, we are unable to determine where the transmitter and
where the receiver is. This changes constantly, according to which device transmits
at any given point in time.
Both ends of the line have to be terminated. However, it is not that easy. Since all
device have tri-state outputs, situations occur (very often every time the transmitting
device or data direction changes), when all transmitters are in high impedance state,
and the line, due to termination resistors, is in undefined state
In the practical application it is quite simple:
TAC
Andover Controls Infinet networks are not terminated.
Andover controls RS-485 IOU networks, 120 termination is added to each

end of the network.
Andover controls FTT-10A IOU networks, termination is used, however; the

network design will determine the network termination parameters.
BACnet MS/TP Networks are terminated as a standard RS-485 network.
7-9
UART (Universal Asynchronous Receiver Transmitter)

UART stands for Universal Asynchronous Receiver Transmitter.
UART is a serial to parallel converter.
The prime reason for having a UART is that it allows for the use of single twisted
pair cable for data communications rather than sending data over 8 twisted pairs, one
for each bit.
The UART sits between the RS-485 transceiver and the microprocessor.
Often times the UART is built into the microprocessor.
7-10
RS-485

Data Frames
UART takes 8 bit wide parallel data coming off the microprocessor and converts
it to serial data, sending one bit at a time in 8 bit frames.
A data packet consists of many words (data frames).
TAC
7-11
UART (Universal Asynchronous Receiver Transmitter

Start & Stop bits
UART will send data out on the wire and frame that data. The data is framed
between the Start bit and the Stop bit.
A Start bit is always a logical high (a logical 1) and indicates the beginning of a
data word.
A Stop bit is always a logical low (a logical 0) and indicates the end of a data
word.
For the UART to receive data as a valid piece of information, the start bit must be
high and the stop bit must be low. The 8-bit word can be a value between 0 &
255, where 0 is all lows and 255 are all highs. Any combination in between can
be represented in the 8-bit word.
The UART samples on the receiver side when it is in receive mode. It samples
the data at what determines to be the center of each data bit. It does this with
timing that is baud rate specific (19.2k data being transmitted). The length of a
data bit is equal to 1 over 19,200 seconds (1 millisecond or 100 microseconds).
7-12
RS-485

UART Sampling
What the UART will do at 19.2k is;
@ 19.2k a data bit is: 1/19.2k = 100 microseconds
The UART will trigger on the leading edge of the start bit
At 50 microseconds, take the first sample
At each 100 microsecond increments, it will sample the remaining 8 bits

including the stop bit. The sample will be in the center of each bit.
This is how it makes its determination, not only for the start and stop bit, but each
individual data bit in between of what the value of each bit is.
TAC
7-13

Frame Errors
To be considered correctly formed data, the start bit must be a high and stop bit
must be a low. This allows the UART to discriminate against a noise spike on the
network from real data.
If there were a noise spike on the network, the UART would be tripped by its
rising edge. When it samples the start bit, its at a low. For the UART to receive
data as being a valid piece of information, the start bit must be at a high. This is
data that was not correctly framed and is determined to be a Framing Error.
Start Bit Low, Frame Error
7-14
RS-485

Frame Errors
The sampling of data in the middle of the data bit, as opposed to very close to the
rising edge or falling edge, allows for very accurate sampling independent on how
clean the formed data bits may be.
Because the data sampling is at dead center, we still receive a very accurate
representation of the data, even though the data signals are not that clean. This is
what allows RS-485 to be very tolerant of long wire runs and large number of
nodes on the network.
TAC
7-15
7-16
RS-485
Ch 8
Infinet
Contents
What is Infinet
Hardware Design Limitations (3 Basic Rules)
Cable Length
Maximum Nodes
Cable Specifications
Extending the Infinet
Infilink 200
Infilink 210
Signal Loss over Fiber Optic cable
Understanding / Calculating Propagation Delay
Infinet Protocol
Token Passing
Infinet ID
- Regular vs. Priority Nodes
Token Round Time
Reconfigure
Invitation
Learn
Replacing an Infinet Controller
Troubleshooting
Methodology (4 Steps)
Troubleshooting Tools and Techniques
Segmenting
InfiLink 200 LEDs
InfiLink 210 LEDs
Ringing out an Infinet Cable
Measuring Ground Potential
Evaluating Oscilloscope Signals
Testing Infinet Transceivers
Checking CX/CMX Port Configuration
8-2
Infinet
What is Infinet?
The Infinet is Andover Controls proprietary network that delivers data through a
Token Passing process.
The Infinet consists of;
Infinet Controllers
Cables and Repeaters
Communications Software
CX / NetControllers
The Infinet transmits data at a rate of up to 19.2 Kbps through twisted pair cable or a
combination of twisted pair and fiber optic cable.
The Infinet uses a Token-Passing data transmission protocol
TAC
8-3
Hardware Design Limitations

There are 3 basic rules to follow when constructing an Infinet:
1) Cable Length
4,000 ft. Maximum cable run
2) Maximum Nodes
31 controllers (nodes) per segment (32 including the CX)
3) Cable Specifications
Use the Cable Andover Controls Recommends:
- Shielded Twisted-Pair (STP)
- Nominal Impedance of 100 ohms
- Nominal Velocity of propagation of 78%
- Nominal Capacitance of 12.5 pF/ft between conductors and also 22 pF/ft
between the conductor connected to ground and the next conductor.
The wire product listed is recommended for Infinet installations and can be purchased
through Andover Controls.
Infinet Cable
PART NUMBER
GAUGE/
COND
WIRE
JACKET COLOR
24/2c
Stranded
Orange, Blue
24/2Pr
Stranded
Orange
WA241P-2000S
(12.5 pf/ft Low Cap)
WA242P-2108
(12.5pf/ft LowCap. Ind Shld)
Shield Grounding:
The Shield is Grounded at the:
CX/NetController
Infilink
The Shield is Floating at all Infinet controllers and is connected everywhere.
8-4
Infinet
Hardware Design Limitations

The Infinet does not require termination.
Non-termination allows for flexible wiring combinations of Bus and Star topologies.
Bus Topology
Terminal with Gas

Tight Connections
Bus & Star Topology
To extend the Infinet beyond this limitation, the use of Infilink/s (Repeater/s) is
required.
4,000 Ft. Maximum Run of Twisted Pair Cable
31 Infinet Controllers Per Segment (32 Including the CX / NetController)
TAC
8-5

Infilink 200
Use the InfiLink 200 if you are extending the Infinet with Shielded Twisted Pair
Cable.
Infilink 200
Shielded Twisted Pair
InfiLink 200 is both an electronic repeater and a central active hub in one device.
When acting as a central hub, the InfiLink 200 has five RS-485 ports available for
connecting several nodes.
Shield Grounding at the Infilink 200

Shield is grounded on ports 25 and floating on port 1
Note: As a general rule, you should not exceed the maximum of 10 InfiLink
200s in an entire Infinet.
8-6
Infinet
Extending the Infinet cont

Infilink 200 cont
Bus Configuration
1) Connect port 1 on the InfiLink 200 to the last node on the Infinet.
2) Connect another piece of twisted pair cable to a different port on the InfiLink
200, and connect that cable to another Infinet controller.
Infilink
200
Infinet Controllers
Using InfiLink 200 to Extend Infinet
Star Configuration
Port 1 on the InfiLink 200 must connect to an incoming signal from the
CX/NetController. Ports 2-5 are for extending the Infinet.
You can have up to 31 controllers on each of the other four ports. This means that
using one InfiLink 200 as an active hub, you can connect 127 Infinet controllers in
a star to a 9000 controller.
Infilink
200
The Infinet leg that connects from

the CX/NetController can have
only 30 Infinet controllers. The
controller and the Infilink each
count as a node, accounting for 2
of the 32 nodes allowed.
Shielded Twisted Pair Star Configuration
TAC
8-7

Infilink 210
Use Two InfiLink 210s if you are using fiber optic cable to extend the Infinet.
Infilink 210
Fiber Optic
Use fiber optic cable on that part of the Infinet that you run between buildings or
through a noisy environment.
You can extend each fiber optic cable segment up to 6,561 ft (2,000 m)
The InfiLink 210 serves as a central (active) hub, with one RS-485 port where you
wire the cable from the Infinet you are extending, and two other ports designed to
connect fiber optic cable with ST connectors.
Shield Grounding
+
Shield (Floating)
GND
Connect shield to shield if the shield is already grounded elsewhere
Connect to ground if the shield is ungrounded
Note: As a general rule, you should not exceed the maximum of 10 InfiLink
210s in an entire Infinet.
8-8
Infinet

Infilink 210 cont
Bus Configuration
1. Connect the first InfiLink 210 to the last node on the Infinet cable in the
Building, i.e. connect the Infinet cable to the InfiLinks RS-485 Infinet port.
2. Connect one end of the fiber optic cable to Port 1 or 2 on the first InfiLink 210.
3. Connect the other end of the fiber optic cable to Port 1 or 2 on the second
InfiLink 210.
You can extend a fiber optic cable segment up to 6,561 ft (2,000 m)
4. Connect cable from the RS-485 Infinet port of the second InfiLink 210 to the
first Infinet controller in Building 2.
Infilink
210s
Fiber Optic
Cable
Using Infilink 210s to extend the Infinet
Network
Segment
Fiber Optic Cable
Infinet Controllers
Infilink
210s
Infinet Controllers
Daisy-chaining Infilink 210s to extend the Infinet
TAC
8-9

Infilink 210 cont
Star Configuration
1) The Infinet port on the first InfiLink 210 must connect to the arm of the star
coming in from any 9000 series controller. You can run 4,000 ft (1,219.2 m)
of twisted pair cabling between the 9000 controller and the first InfiLink 210.
2) Port 1 and Port 2 on InfiLink 210 can then each have a single fiber optic arm
connected to it. These arms can have up to 6,561 ft (2,000 m) of fiber optic
cable.
3) The other end of each fiber optic arm must then connect to another InfiLink
210 so that you can connect twisted pair cable to the Infinet once again.
NetController
Infilink
210
Fiber Optic
Cable

Infilink
210s
Infinet Controllers
Fiber Optic Star Configuration
8-10
Infinet

Signal Loss Over Fiber Optic Cable
Since fiber optic cable transmits light to carry data, it can carry data over a longer
distance than other types of cable.
The loss of light intensity is increased when you extend fiber optic cable over a
long distance and each time you connect fiber optic cable into a patch panel.
The recommended 62.5/125 diameter fiber optic cable functions properly with up
to 10 db signal loss.
To ensure you do not have more than the maximum signal loss allowed for the
fiber optic cable, you should determine how much light intensity the cable is
losing by applying the following rules:
Cable usually loses 1.2 db (light intensity) per 1,000 ft length (4 db/km), but
the amount varies depending on the grade of cable and the manufacturer
Cable loses .25 to 1 db per connection to a patch panel
So if you have 4,000 ft of the recommended fiber optic cable connected into 6
patch panels, the total loss of light intensity is as follows:
Loss for length =1.20 4 = 4.8
Loss for patch panels =0.25 6 = 1.5
Total loss of intensity = 6.3 db
Since 6.3 db is within the limitation of up to 10 db signal loss, the fiber optic
cable will perform reliably with this much loss of intensity.
TAC
8-11

Understanding Propagation Delays
A propagation delay is the total of combined measurable delays that occur as

information travels through the network between the sending and receiving
nodes.
Delays vary depending on the hardware you install. For example, delays
associated with wire differ from delays associated with fiber optic cable.
Propagation delays significantly impact the network when:

o You attempt to run Infinet long distances (more than 10 miles).
o The maximum propagation delay for the entire network exceeds 140 s at
19.2 KBps.
Calculate propagation delays whenever:
8-12
You install line drivers
The network includes more than 10 InfiLinks
Using the Infilink 200s RS-232 port
Infinet

Calculating Propagation Delays
CX / NetController
InfiLinks
Seg-5
Seg-6
Seg-4
i2-Series
Seg-7
Seg-3
Line Driver
Seg-8
Line Driver
Seg-2
SCX
Seg-9
Seg-1
Table of Delays by Segment
The calculations listed in the table

and the calculations shown below
indicate that, because the total
propagation delay is less than 140
sec, the maximum node distances
are at acceptable lengths.
8 InfiLinks @1 s each
2 Line Drivers @ 6 s each
---------------------------------Total
20 s
63.71
8
12
-----------83.71 s Total Propagation Delay
Note: Allowable propagation delay of 140 ms is based on Infinet at 19.2K baud.

The network can withstand a delay of up to 280 ms if you reduce your Infinet
baud rate to 9.6K. Reducing the baud rate slows overall network response time.
TAC
8-13
Infinet Protocol
Token Passing
Token Passing is a system governing network data transmission.
The token is an electronic signal.
1. The token passing protocol sends a single token (an electronic signal) to
each controller sequentially.
2. Token Passing is managed by the CX / NetController.
3. When an Infinet controller receives the token, it immediately transmits all
of its new exports, alarms, and access events.
4. The export data broadcasts over the network and is heard by all other
controllers.
5. The token then passes back to the CX / NetController, where the process
repeats. If an Infinet controller has no data to transmit, it passes the token
back to the CX / NetController.
6. An Infinet controller can issue a response to a request from a CX /
NetController without having the token.
Infinet ID#
The Infinet ID number is a unique number assigned to Infinet controllers (nodes)
during the Learn process that is performed through Continuum Software.
Infinet Controllers (nodes) fall under two categories; Regular & Priority.
The range of the Infinet ID number assigned is different depending on which
category the node fall under.
8-14
Infinet
Infinet Protocol
Infinet ID#
Regular Nodes
Most Infinet Controllers are regular nodes
Infinet ID numbers assigned to regular nodes fall between 1 and 127
(The number 0 is reserved for controllers not yet assigned an ID)
TCX 800
ID#
1
2
TCX 850
CX/NetController
ID#
2
3
4
ID#
255
TCX 870
ID#
3
6
7
8
TCX 810
ID#
4
TAC
8-15
Infinet Protocol
Infinet ID#
Priority Nodes
Priority nodes are Infinet controllers that require quicker access to the Infinet than
other nodes.
Infinet token passing gives priority controllers more frequent access to the token
than regular controllers have.
The following are Priority Nodes:
CX / NetController
(255 is reserved for the 220/240 series or 9000 series controllers)
250 programmable touch screen controllers
700 series access controllers
280 laptop tools

(251 - 254, are used by 280 laptop tools if available)
Infinet ID numbers assigned to priority controllers fall between 224 and 254
8-16
Infinet
Infinet Protocol
Infinet ID#
Regular & Priority Nodes
Token Passing sequence on a network that contains both Regular and Priority Nodes.
Regular
Nodes
TCX 800
ID#
1
1
Priority
Nodes
CX/NetController
TCX 850
ID#
255
ID#
2
5
TCX 870
3
ID#
3
ACX 781
ID#
224
TCX 810
7
TAC
ID#
4
8-17
Infinet Protocol
Token Round Time
The time for a token to go through all of the controllers on an Infinet at 19.2 Kbps is
the Token Round Time. Token round time is a function of:
The number of nodes on the network
How many of the nodes have messages to send
How many point requests are coming from the CX (due to activity on a
Graphic, updating of a List View or a Group Member list).
For a CX controller with 127 regular Infinet controllers attached, the Token Round
Time can range from 6 to 15 seconds, depending on the amount of network traffic.
If an Infinet controller cant respond to the token, then the CX/NetController cant
receive the alarm, which in turn will not be delivered to the workstation for time
stamp and database logging.
Reconfigure / Polling
Infinet reconfigure is the polling process that determines which nodes will participate
in token passing. Anytime the token passing process is interrupted, a reconfigure will
occur. The following will lead to a reconfigure:
An Infinet controller no longer on the network (power down or

disconnected)
A response to the Invitation message
Network data corruption
The CX/NetController will make up to 6 attempts to communicate with the Infinet

controller. If at that point it does not communicate, a reconfigure will take place.
Reconfigure is managed by the CX/NetController and is an attribute of the comm
port. It will poll all Ids for both regular and priority nodes.
There are 2 sets of Id ranges that are polled:
8-18
Ids 1 127 (Regular Nodes)
Ids 223 254 (Priority Nodes)
Infinet
Infinet Protocol
Reconfigure / Polling
Any nodes with a non-zero id will respond to the poll and be passed the token when
token passing resumes. The CX/NetController will update the CommStatus attribute
to online or offline for all Infinet controllers on that Infinet, based on whether or not
there was a response to the poll. Those that are online will participate in the token
passing.
If an Id number does not exist on the network, that particular Id will be polled for
twice before continuing on to the next Id number. Non-existing Id numbers are stored
within the CX / NetController for comm status and potential issue to new Infinet
controllers joining the Infinet.
At the completion of the polling process, the CX/NetController will broadcast the
current Date & Time and then initiate token passing.
If there is no CX/NetController on the Infinet, the lowest ID Infinet controller will
initiate the polling process and upon completion the token passing will resume.
Import/Export will continue to occur between those Infinet controllers. However,
alarms that occur can not reach the CX / NetController and will not be delivered to
the Workstation
Each time there is a reconfigure, the reconfiguration attribute of the commport will
increment by one. The reconfiguration attribute will max out at 255 and will need to
be reset before it will again increment.
TAC
8-19
Infinet Protocol
Invitation
At the end of each token round, the CX/NetController will send out an Invitation
message. This allows any Infinet controller not currently token passing (just
powered up) to respond. Any response to the invitation (including a framing
error) will lead to the CX/NetController initiating a reconfigure.
Learn
The learn process is a method of automatically assigning Infinet Ids to newly
added Infinet Controllers whose Ids are currently zero.
The CX/NetController performs a binary search by serial number for all Infinet
controllers attached to that comport. As the CX/NetController identifies each
Infinet controller, it follows this sequence:
Request of Infinet ID
o Is ID 0?
Yes CX/NetController assigns next available Infinet ID and

populates the database.
No Does this controller exist?
o Yes Insure that Infinet ID matches database.
o No Is this ID currently unused?
o Yes Populate in database with this ID
o No Populate in database with ID zero, Learn again to set
ID non-zero
The Learn process Ids new Infinet Controllers and does not affect existing
controller Ids. Ids will be assigned in order of Serial number, from lowest to
highest, of those new controllers.
Learn is only for adding new controllers, not for replacement.
8-20
Infinet
Replacing an Infinet Controller

Follow this procedure when replacing an Infinet controller:
1. Power down the Infinet controller you want replaced
2. Disconnect the wiring and remove the controller
3. Install the replacement controller and connect the wiring
4. Apply power
5. From Continuum Explorer, open the replacement controllers editor
6. From the Run Time page, enter the serial number of the replacement controller
and then click the Apply button
7. From the General page, click on the Window Refresh button
At this point, the replacement controller should be displayed as On-line
If the controller is on-line, the procedure was performed correctly
If the controller is off-line:

o Check the serial number from the editor for typing errors
o Make sure the wiring has been properly connected
8. Reload the Controller
Note: A Learn is Not performed when replacing an Infinet controller.
TAC
8-21
Infinet Troubleshooting
Methodology (4 Steps)
The troubleshooting methodology shows you how to efficiently identify problems
and their causes throughout the network.
The first two steps in troubleshooting require the most time, but are the most
crucial. The more thoroughly and accurately you complete steps 1 and 2, the
sooner you can isolate, correct the problem and minimize the amount of time that
the impaired network leg is disabled.
1. Define the Problem

The first step in troubleshooting a communications problem is to define the
problem. To do this, you must know how your network is configured. This is
a good time to review the network documentation. The documentation should
include:
The exact wiring configuration, with approximate distances for all

lengths of cable.
Notes detailing any deviations from specified cable types.
A list of all symptoms. Run tests to make sure the symptoms list is as
complete as possible. This list and the network documentation
combined enable you to define the problem and focus your
troubleshooting.
2. Identify the Cause

You need to isolate each problem and associate it with an individual device or
wire segment. You can accomplish this only by:
Segmenting the network to eliminate the symptom

or
8-22
Using test equipment to identify the problem
Infinet
Methodology (4 Steps) cont
3. Fix the Problem
Once you know the wire segment or device (controller or InfiLink, for
example) that is causing the problem, you can fix the problem by repairing or
replacing the malfunctioning device or defective cable.
4. Verify the Solution
Now is the time to verify that your solution has really fixed the problem.
To verify the solution, you need to:
Rerun tests for communications problems

and
Compile a new symptoms list
If your tests and symptoms list identify no symptoms, then the problem has
been fixed.
If symptoms persist, repeat the troubleshooting process from the beginning.
TAC
8-23
Defining the Problem on Infinet
Defining any communications problem within Infinet requires preparing a
network asbuilt map, compiling a list of symptoms and comparing the two
documents.
Preparing an Asbuilt Map
An asbuilt map documents every network component and presents the
network as it is actually constructed, identifying:
Every network connection in the order of its installation.
Approximate distances of all twisted pair and fiber optic cable runs
throughout the network.
The part or model number of every cable.
An asbuilt map differs from the network map that usually reflects the
networks configuration guide. Preparing and thoroughly documenting an
asbuilt map can save you time when troubleshooting and becomes particularly
useful when you need to:
8-24
Segment the network to isolate problems.
Verify that no wiring rule violations exist.
Infinet
Defining the Problem on Infinet cont
Recognizing Symptoms Common to Infinet Problems
The most common symptoms pointing to a problem with Infinet
communications are:
Random or constant Infinet reconfigures
Infinet controller randomly or constantly off-line
Group of Infinet controllers randomly or constantly off-line
Replaced Infinet controller off-line
The CX/NetControllers inability to locate newly added Infinet

controllers during LEARN
Data corruption errors, also known as invalid Cyclic Redundancy

Check (CRC) errors
Programs that use point-to-point communications disabling
Some Infinet controllers are missing Export information
The Infinet controller fails to come back online after a PowerFail
Recognizing Infinet Error Messages

The CX/NetController logs two types of Infinet error messages:
TAC
Failed to respond to token pass
Received invalid CRC
8-25
Compiling a Symptoms List
A symptoms list helps you:
Focus troubleshooting efforts in the area of the network where the

problem actually occurs.
Determine the actions you need to take or tools you need to apply to
isolate the problem.
You can generate a complete symptoms list in the following ways:
Using system information.
Running a Plain English program that monitors the following object

attributes:
Comm port Reconfigures
Infinet Controller Attributes:
8-26
InfinetError
InfinetErrCount
InfinetErrTime
Running a program that disables itself.
Infinet
Point-to-Point Communication
Programs that utilize point-to-point communications may disable in response
to unsuccessful attempts at retrieving information.
Unsuccessful attempts at retrieving information can include, for example,
trying to retrieve information that the controller cannot have or attempting to
perform an illegal function such as dividing by zero.
When unsuccessful, the program sets its own state to Disable.
TAC
Point-to-point communication occurs whenever a program on one

controller requests a points attribute (the points actual value or state,
for example) from the controller where the point resides.
When the program refers to a points attribute, the program directly

contacts the controller where that point resides and requests the current
information for the point.
Programs that use point-to-point communication automatically disable

if the controller you are retrieving the points attribute information
from does not respond.
8-27
Identifying the Cause of an Infinet Problem
Once you have your symptoms list, you can try to identify the cause of the
problem.
Identifying the Problem Type

Use the data from the symptoms list and the asbuilt map to determine if the
problem belongs to one of the following:
Single node
Network segment
Global network
Knowing Common Causes of Infinet Problems

Common causes of Infinet problems include the following:
8-28
Wiring open (physical break in the network wiring)
Wiring short (wiring physically connects to other wiring or shield, or

shorts to ground)
Cabling rule violation
Controller at different ground potential
InfiLink set to incorrect baud rate
Controller in hardfail (software making the controller shut itself down)
Duplicate ID due to incorrect replacement procedure
Controller constantly resetting
Controller hardware failure
Infinet
Troubleshooting Tools and Techniques
Use the following tools and techniques to help identify the causes of Infinet
communications problems:
Segment the Infinet.
Observe LEDs on InfiLinks and on Infinet controllers.
Verify the integrity of the wire run (also called ringing out cable runs)
with a meter.
Measure ground potential with a meter.
Observe Infinet waveforms with an oscilloscope.
Test Infinet controller transceivers with a meter.
Test other communication devices.
Note: The order in which you apply troubleshooting tools and techniques
depends on the symptoms that you identify.
For example, if a controller does not come on line, you might first look at LEDs
on that controller. However, if you know that the wiring preceding the controller
is not defective, then you might choose to segment the network beyond the
controller as a first step.
TAC
8-29
Segmenting the Infinet
Segmenting the network is a technique that helps you identify the location and
cause of the problem. The easiest method to follow when segmenting is to
disconnect one leg of the InfiLink at a time. With each disconnect, determine if
the symptoms disappear. Continue segmenting until you can isolate the problem.
To segment a network, disconnect one leg of the network at a time.

You usually break the network at equal intervals, as follows:
1. Check your network documentation to determine the best location to segment
the network. If your network is wired as a:
Bus - Disconnect approximately half way
Star or Distributed Star - Disconnect a single star
2. Segment the network at or near its center to disable the far end of the network
(segment #1 in the example shown)
a. If the problem goes away, you know that you are close to the exact location
in the network where the problem exists. Reconnect and segment further out.
b. If the problem continues after you disconnect part of the network, then
continue segmenting until the problem no longer occurs (segment #2 in the
example shown)
3. Continue segmenting the network in this manner until you identify the
controller or cable that is causing the problem.
8-30
Infinet
Segmenting the Infinet cont
4. When you identify the offending leg, further segment that leg (segments #3
and #4 in the example shown) continuing the process until you can isolate the
problem to:
TAC
Defective length of cable

Defective connection
Malfunctioning equipment
8-31
Troubleshooting From the InfiLink 200 LEDs
Understanding the functionality of the LEDs on the Infilink 200 will help when
troubleshooting the Infinet.
RD & TD for RS-232 (Top of InfiLink)

Represent activity to and from a device connected to the RS-232 port.
RD & TD for Ports 2 through 5
Indicate that their corresponding ports are receiving and transmitting Infinet
signals.
RD & TD for Port 1
Indicates that the CX/NetController is receiving and transmitting Infinet
signals.
You must use Port 1 for the incoming Infinet cable and at least one of the
other four ports (or RS-232 port) for an outgoing Infinet cable. If Port 1 does
not connect to a CX/NetController or another InfiLink 200, move the cables so
it does.
8-32
Infinet
Troubleshooting From the InfiLink 200 LEDs cont
Baud Rate
The baud rate set on the InfiLink 200 should match the rate set for Infinet in
the software.
Check the comm port Baud attribute setting using PRINT on the
Command line
or
Open the comm port window using FileOpen from the menu bar.
Check the baud rate setting on the front of InfiLink 200
Fuses
If AC power to the InfiLink 200 fails but power is actually available, check the
3A, 250V, 3AG, slow blow fuse.
You can use the 3A slow blow fuse on 115 V links as well as on 230 V links.
TAC
8-33
Understanding the functionality of the LEDs on the Infilink 210 will help when
troubleshooting the Infinet.
Three pairs of green and yellow LEDs appear on the front of the 210 enclosure:
The top pair of (green and yellow) LEDs indicates the status of fiber optic
Port 1.
The middle pair indicates the status of fiber optic Port 2.
Top bottom pairs indicates the status of the Infinet port.
TD LED
Each yellow light, labeled TD, flashes to indicate that data is being
transmitted over the fiber optic cable or through the Infinet port.
RD LED
Each green light, labeled RD, flashes to indicate data is being received over
the fiber optic cable or through the Infinet port.
Power
The single red light labeled POWER indicates the InfiLink 210 is receiving
power.
8-34
Infinet
Baud Rate Setting
The baud rate set on the InfiLink 210 should match the rate set for Infinet in
the software.
Check the comm port Baud attribute setting using the PRINT
Command
or
Open the comm port window using FileOpen from the menu bar.
Check the baud rate setting on the front of InfiLink 200
Test Mode Switch

Set the InfiLink 210 to test mode to produce a continuous transmission of
signals from the fiber port.
If a leg of the network contains more than one InfiLink 210, you can use the
test mode to aid in verifying the integrity of the fiber connections and the
InfiLinks by setting both InfiLinks to test mode.
If both InfiLinks and their connecting fiber are functioning properly, their RD
lights remain on continuously while both devices are in test mode.
TAC
8-35
Ringing Out an Infinet Cable
Method 1:
A common practice for verifying that a length of cable works is to twist the two
conductors together at one end, go to the other end of the cable, and Ohm out the
run to see a short (0 ).
Method 2:
Place one resistor (250), between plus (+) and minus () at one end of the cable
Place the second resistor (500), between the plus (+) and shield of the cable
Go to the other end of the cable and ohm out plus to minus (+ to ) and plus (+) to
Shield.
STP Cable
+
Shield
250
500
Use this process to test for the following conditions:
8-36
Open: Plus (+), minus (), or Shield
Short: Plus (+) to minus ()
Short: Plus (+) to shield
Short: Minus () to shield
Infinet
Measuring Ground Potential
Signal Potential refers to the horizontal plane along which signals are sent and
received with respect to ground.
RS-485 requires that all devices communicating with each other be at a
reasonable ground potential.
To measure the ground potential of any Infinet controller:
Use a voltmeter to measure between the earth ground connection (for

power) and the Infinet shield connection.
This process lets you measure the ground difference between the Infinet
controller and the ground at the InfiLink or CX/NetController where the
shield connects to ground.
Measure each voltage; AC as well as DC.

A reading higher than 2 to 3V on either voltage indicates a grounding
problem.
Measure combined voltages using the formula below.

(If the result is greater than 7V, a grounding problem exists)
(1.4 x ACV) + DCV
TAC
8-37
Evaluating Infinet Signal Levels with an Oscilloscope
An oscilloscope is a valuable tool for troubleshooting Infinet, and can also improve
your efficiency in solving intermittent wiring problems.
When using the oscilloscope, be sure you begin testing at the CX/NetController or at
an InfiLink port.
Infinet Signal Basics
Infinet is an RS-485 local area network operating at 19.2 Kbps
RS-485 is a differential, 0 to 5 V signal
All Infinet devices have series 27 resistors

Older Infinet Controllers
New I2 Infinet Controllers
8-38
Infinet
The Ideal Signal
5V
0V
2V/Div
5V
0V
.1 ms/Div
Ideally, RS-485 signal levels are approximately .5 to 4.5V, with the negative
connection appearing as a true representation of data (data 0 = low; data 1 = high)
and the positive connection being the opposite (inverted) of the negative
connection.
On long cable runs with many Infinet devices attached, signal levels often
attenuate (weaken). This situation does not present any problems as long as the
positive (low) signal has lower amplitude than the negative (high) signal.
You can use a protocol analyzer to check the RS-485 signal level (rather than an
oscilloscope), since you are only concerned with the effects of attenuation on the
signal levels at this time.
TAC
8-39
Short on the Minus (-) to Ground
5V
+
0V
2V/Div
5V
0V
.1 ms/Div
The signal trace shown indicates a short from ground or a short to ground exists
on the leg of the Infinet.
8-40
Infinet
Shorted Transceiver on an Infinet Device
5V
0V
2V/Div
5V
0V
.1 ms/Div
The signal trace shown indicates that at least one Infinet controller has a shorted
transceiver (+).
TAC
8-41
Infinet Device at a Different Ground Level
5V
2V
0V
2V/ Div
5V
2V
0V
.1 ms/Div
Signal potential refers to the horizontal plane along which signals are sent and
received with respect to ground.
Signal transmission and receipt must occur within the same range of potential.
8-42
Infinet
Open on the Plus (+) Signal
5V
0V
2V/Div
5V
0V
.1 ms/Div
A signal with an open on the positive (+) connection (or an open 27 resistor)
displays a disintegrating signal trace.
TAC
A predominantly disintegrating trace pattern displaying on the

oscilloscope indicates that you have segmented beyond the problem.
Segment closer to the CX/NetController
A predominantly non-disintegrating trace pattern displaying on the

oscilloscope indicates that you have segmented between the
CX/NetController and the problem.
8-43
Testing Infinet Transceivers
Voltage spikes appearing on the Infinet can damage Infinet transceivers. You can
use a voltmeter to easily test transceivers for damage, as follows:
1. Disconnect the controller from Infinet.
2. Connect an input to the plus (+) connection.
3. Record a DC voltage reading between plus (+) and ground and between minus
() and ground.
Either reading occurring outside a range of 1.5 to 3.5 volts DC indicates a
damaged transceiver.
Note: To achieve a valid reading, you must measure within ten seconds of reset.
You can take the measurement while holding down the RESET button.
Testing Other Communications Devices

You must test other communications devices, such as line drivers, separately with
a laptop personal computer.
If you are using line drivers connected to the InfiLink RS-232 port, use a loop
back test.
8-44
Infinet
Checking CX/CMX Port Configuration
Checking Port Connection with a CyberStation
1. From the object tree, double left click the CommPort object class to open
the list of the controllers comm ports.
2. Look for Autoset comm ports.
3. Double left click the desired port to open the Object Configuration window.
4. Click Details to open the Communication Configuration window.
5. Check the Baud Rate.
Make sure that Track CXD is not selected and that Flow Control is set for
NoFlowControl.
6. If it is not possible to check the controllers comm ports through a
CyberStation, check the controllers Installation Guide for port defaults.
Checking Port Configuration with a Command Terminal

1. Set the command terminals communication setting to match the Baud Rate
of the Autoset port.
2. Make the connection to an Autoset port on the controller.
3. If necessary, check the controllers Installation Guide for information on
which port is an Autoset port.
TAC
8-45
8-46
Infinet
Ch 9
Continuum
IO Bus
Contents
Introduction:
IO Bus System Description

Two Network Interfaces
RS-485 IO Bus Communication Design Rules

Terminating the RS-485 IO Bus
LON FTT-10A
Cable Specs
Cable Termination
- Free Vs Doubly
IO Protocol
Adding / Replacing IO Modules
I/O Module Configuration / Commissioning:
New IO Module
Replacement IO Module
Defining Program ID
9-2
Continuum I/O Bus
Introduction
IO Bus System Description
The Continuum IO Bus is Andover Controls proprietary network that allows
communications to the NetController (CPU).
Network Interfaces
There are 2 networking interfaces available for Continuum IO modules:
TAC
RS-485 (Standard Network Interface)
FTT-10A (Discussed at end of chapter)
9-3
RS-485 IO Bus Communication Design Rules

Since remote IO modules are terminated, cable specs are not as critical as that of the
Infinet
Maximum Length of Cable: 2,000 ft.
Maximum Modules Allowed: 32
Repeaters: No
Cable Type: Shielded Twisted Pair (Pins 1, 2 & 3)
Termination: 2 - 120 resistors required only when modules are remotely
located
2,000 ft. (610 m) Max.

32 Modules Max.
Note:
For IO Bus power specifications, refer to the Continuum Hardware manual.
9-4
Continuum I/O Bus
Terminating the RS-485 IO Bus

The Continuum IO Bus network allows IO modules to be placed in a remote location
from the CPU (NetController).
Long cable lengths used in RS-485 networks can cause signal communication
problems along the IO bus.
It is necessary to add external 120 terminating resistors to the bus.
Termination must be connected at both ends of the bus for proper operation
The 120 termination resistors are placed across the communication lines
pins 1&2
Local IO modules do not require termination
NetController
Local
IO
Local
IO
Local
IO
Local
IO
Local
IO
Local
IO
(CPU)
Remote IO Modules Require termination
NetController
(CPU)
5
4
3
2
1
5
Local
4
IO
Modules 3
2
1
120
Resistor
Remote
IO
Modules
5
4
3
2
1
Remote
IO
Modules
120
Resistor
Note:
If no local Modules exist, termination will occur across pins 1&2 at the
NetConroller (CPU).
TAC
9-5
LON FTT-10A
The FTT-10A transceiver option for the IO Bus allows for flexible wiring
configurations.
Both NetController and IO modules must be ordered with the same

transceiver option
FTT-10A and RS-485 IO modules are not interchangeable
LON FTT-10A Cable

The installer may choose a variety of twisted pair cables for communications.
Performance varies with cable type. Data transmission depends on factors such as
resistance, capacitance and the velocity of propagation. Andover Controls has
documented system performance on cable types listed in the Continuum IO System
Reference manual.
LON FTT-10A Cable Length
Network lengths vary for Doubly Terminated vs. Free Topology
Network lengths vary based on cable type
FTT-10A has two specifications for a free topology network:

-
Total Wire Length
Node-to-Node Wire Length
Doubly Terminated specs allow for Bus Topology

Max. Bus Lengths
Cable Type
(Meters)
Belden 85102
2700
Belden 8471
2700
Level IV, 22AGW
1400
JY (St) Y 2x2x0.8
900
TIA Category 5
900
Free Topology specs allow s for Star, Ring & Hybrid configurations
Max. Node-to-Node
Max. Total Wire
Cable Type
Distance (Meters)
Length (Meters)
Belden 85102
500
500
Belden 8471
400
500
Level IV, 22AGW
400
500
JY (St) Y 2x2x0.8
320
500
TIA Category 5
250
450
9-6
Continuum I/O Bus
Connecting Remote FTT-10A Modules

FTT-10A Cable Termination
When remotely locating an I/O module on a FTT-10A network, it is necessary to add
terminating resistors.
Free Topology Segment
In a free topology segment, only one termination is required and may be placed
anywhere on the free topology segment. Using 24 AWG cable the maximum loop
impedance is 75 ohms.
Resistor = 52.30 1%, 1/8W
R1
52.3 1%
Doubly Terminated Bus Topology Segment

In a doubly terminated bus topology, two terminations are required, one at each
end of the bus. Using 24 AWG cable the maximum loop impedance is 150 ohms.
Resistor = 105 1%, 1/8W
R1
TAC
105 1%
9-7
FTT-10A Termination Examples

Free Topology
Power Supply
CPU
I/O
I/O
Doubly Terminated
I/O
I/O
I/O
52.3
Power Supply
CPU
105
1
I/O
Power Supply
CPU
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
2
3
I/O
105
1
52.3
Free Topology
Doubly Terminated
I/O
I/O
3
2
I/O
52.3
I/O
105
4
3
105
1
Power Supply
CPU
Power Supply
I/O
9-8
CPU
I/O
I/O
I/O
I/O
I/O
I/O
I/O
Continuum I/O Bus
FTT-10A Termination Examples

Free Topology
I/O
Doubly Terminated
I/O
I/O
I/O
I/O
I/O
Power Supply
I/O
I/O
I/O
I/O
I/O
I/O
CPU
I/O
Power Supply
CPU
52.3
1
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
Free Topology
I/O
Doubly Terminated
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
1
I/O
1
105
I/O
Power Supply
CPU
I/O
105
I/O
I/O
I/O
105
I/O
I/O
2
I/O
105
I/O
52.3
Power Supply
CPU
I/O
I/O
I/O
1
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
I/O
TAC
I/O
I/O
9-9
IO Protocol
The I/O utilizes a polling protocol in which information is retrieved from I/O
modules. The poll is asynchronous to the NetController scan. A poll is different
from Infinet token passing in that information is pulled from the I/O modules. They
are not given the opportunity to talk on the bus.
The NetController polls each I/O module on the bus by ModuleID number and
retrieves sensed input values and selected output status such as override conditions.
The polling interval is predictable based on the number of modules the NetController
must poll.
I/O modules are polled at a 50ms rate. If less than four modules are involved the
polling rate is 200ms.
The actual setting of the outputs is synchronized with the NetController scan. On
step 5 of the scan, the NetController sends out a message to each of the outputs on the
I/O bus, setting their values in accordance with schedule or program updates.
The Access Controls series module is treated differently in that it gains immediate
communications access to send unsolicited messages on the I/O bus to request card
validation information from the NetController. Its access to the Network is collision
based (like the Ethernet) and occurs between polls.
9-10
Continuum I/O Bus
Replacing or Adding IO Modules

There are two methods used when replacing or adding IO modules.
Conforming to these methods will minimize the potential of damaging equipment.
Method 1: Removing all power

1. Turn the power supply off
2. Disconnect the batteries
3. Replace or add the IO module
4. Turn power supply on
5. Reconnect batteries
6. Reload NetController
Method 2: Removing power from the IO Bus only

1. Ensure that batteries are connected and fully charged
2. Turn power supply off
3. On the CyberStation, CD to the appropriate controller.
4. In the Command Line type: set IOUPower = off
The battery will now only power the CPU and modem if applicable
5. Replace or add the IO module
6. Restore power
7. If the NetController version is prior to 1.03, type: set IOUPower = on in the
command line on the CyberStation
TAC
9-11
IO Module Configuration / Commissioning

After installing new IO modules, you must configure and commission the module
before it can be seen within Continuum and operate properly on the IO Bus network.
Before starting the configuration process, you must:
Be logged onto Continuum with configuration capabilities
The NetController connecting to the IO module has already been configured
If the module is in a remote location, the person configuring the module has
written down the Module Id # that located on the inside cover of the module
Configuring / Commissioning a New IO Module

1. Open Continuum Explorer.
2. Locate the NetController that the IO module is connected to and right click on
it.
3. From the pop-up menu, select; New > IOU Module
The New dialog box appears
4. In the Object Name text box, enter a name for the IOU module and then select
the Create button.
9-12
Continuum I/O Bus

The IOUModule editor appears
5. In the Description text box, type a description for the IO module.

6. In the IOU dialogue box, enter the IOU module number.
You must manually assign a unique number, between 1 and 32, for each IO
module and is a wise idea to physically label the IO module with the assigned
number.
7. Select the Learn button.
A window appears requesting you to press the Commission button on the IO
module
8. If the IO module is local, press the Commission button on the front panel of
the module.
When a module is commissioned, information is sent from the module to the
workstation
The dialog box that appeared on the CyberStation screen should disappear
indicating that it received all the information from the module
TAC
9-13

9. If the module is in a remote location, enter the Module Id # into the Module ID
text box.
10. Select the Apply button.
11. Select the Refresh button.
The Model: and Program ID: fields are automatically entered, and the
Comm Status: should indicate On-line
12. Select the OK button to save the IO module object
Wink
The Wink button is used to confirm that your system recognizes the IO module.
Note:
This procedure is used for all modules except when replacing an AC-1 with an AC-1
Plus.
1. Re-open the IOUModule editor.
2. Click the Wink button.
The Status light on the IOU module should flash which indicates that the IOU
module was successfully configured
9-14
Continuum I/O Bus

Commissioning a Replacement IO Module
If the event that one of your IO modules is physically damaged, their is no need for
the reconfiguration process.
1. Replace the module using method 2 from Replacing or Adding an IO Module
2. From CyberStation, open the IOModule Editor for that particular module and
select the Learn button
a. If the IO module is local, press the Commission button on the front face of
the module.
b. If the module is in a remote location, enter the Module ID # into the
Module ID text box. (The Module ID # is located on the inside cover of the
module)
3. Select the Apply button
4. Select the Refresh button.
The Model: and Program ID: fields are automatically entered, and the Comm
Status: should indicate On-line
6. Select the OK button.
Note:
For the AC-1 Access module, reload the door.
TAC
9-15
Defining Program ID
The Program ID Displays the number that Andover Controls has assigned this
particular module.
Continuum will fill this number in for you. The only time you will need this number
is when speaking to an Andover Support Representative.
Program Id can define the IO modules software revision.
Program_id example: bb:Aa:qq:Mm:NI:NO:NR:NK
Each field depicted is a 2-digit hex value and defined as:
9-16
bb
the board identification number
Aa
the board revision number and the application image type
qq
the qualifier specifying build parameters
Mm
the major and minor version numbers of the application image
NI
the number of input channels
NO
the number of output channels
NR
the number of card readers
NK
the number of keypads
Continuum I/O Bus
Ch 10 MS/TP
Contents
MS/TP Overview
Physical Layer
Media & Characteristics
Connections & Terminations
Repeaters
Andover & MS/TP
Polling Issues
Assigning / Duplicate Ids on the MS/TP Network
Adding Andover Devices
MS/TP Enhanced Mode
Identifying BACnet IP & MS/TP Network Numbers
BacMaxMaster
10-2
MS/TP
MS/TP (Master Slave Token Passing)

Overview
MS/TP is a Token Passing network that controls access to a bus network. A
master node may initiate the transmission of a data frame when it holds the token.
Both master and slave nodes may transmit data frames in response to requests
from master nodes.
After a node passes the token, it listens to see if the intended receiver node begins
using the token.
When a request that expects a reply is sent to an MS/TP node, the sender shall
wait for the reply to be returned before passing the token. If the responding node
is a master, it may return the reply or it may return a Reply Postponed frame,
indicating that the actual reply will be returned later, when the replying node
holds the token.
TAC
10-3
Physical Layer
Media & Characteristics of an MS/TP Network
Shielded Twisted Pair Cable (foil or braided shields are acceptable)

-
Distributed capacitance between conductors:

-
Less than 100 pF per meter (30 pF per foot)
Distributed capacitance between conductors and shield:

-
Impedance between 100 & 130 ohms
Less that 200 pF per meter (60 pF per foot)
The maximum recommended length of an MS/TP segment:

-
4,000 ft (1200 meters) with AWG 18 Cable

(The use of greater distances and/or different wire gauges shall comply
with the electrical specifications of EIA-485)
The maximum number of nodes per segment:

-
32 Per Segment (Additional nodes may be accommodated by the use of

repeaters)
Because MS/TP uses NRZ encoding, the polarity of the connection to the
cable is important. The non-inverting input of the EIA-485 transceiver is
designated in this specification as plus "+" and the inverting input as minus "".
It is recommended, but not required, that the black or red insulated wire of the
twisted pair be designated as the "plus" and the white, clear, or green insulated
wire be designated as the "minus."
Termination:
-
10-4
120 ohm + or - 5% connected at each of the two ends of the segment

medium
MS/TP
Physical Layer
Connections & Terminations
RS-485 MS/TP Network
For any physical segment that runs between buildings there shall be at least 1500 V of
electrical isolation between the EIA-485 signal conductors and the digital ground of
any node on that physical segment.
The shield shall be grounded at one end only to prevent ground currents from being
created.
TAC
10-5
Repeaters
To exceed MS/TP segment limitations, one or more repeaters are required.
An MS/TP EIA-485 Repeater is defined as an active device that provides selective
interconnection between two or more segments of MS/TP cable. The repeater
contains a logic that detects and passes signals received from one segment onto all
other segments.
The segment from which signals are received is determined according to a priority
algorithm.
B-Link (RS-485 Repeater)

- MS/TP only
- Four RS-485 ports
- 120/240VAC & 24VDC versions
BACnet/IP & Ethernet TCP/IP
B4920
System Controller / Router
MS/TP
RS-485
10-6
B-Link
MS/TP
Andover Controls & MS/TP

Baud Rate of the MS/TP Network
Beginning with Continuum 1.62 and beyond, the baud rate of the commport1 of the
b4920 increases to 76.8K.
MS/TP Polling Issues
A periodic poll for masters that take place every 40 Token rounds.
Any device that is not passing the token to an ID of one above its own, will
poll for all IDs between its own and the one it is next to pass to.
- This can be problematic on a small MS/TP network where the highest ID
will periodically poll for all IDs up to 127
- You can set a MAX ID for the MS/TP network to reduce this unnecessary
polling
TAC
10-7

Assigning / Duplicate IDs on the MS/TP Network
The assignment of ID numbers (1-127) is the same as Infinet. When performing
Find BACnet Devices from Continuum Explorer, it will go out on the bus and use
a searching algorithm that will pull in one serial number at a time and store them
within the b4 controller. MS/TP will discover duplicate Ids based on the serial
numbers stored within the b4 controller. When adding a b3 series controller and
during the learn process it encounters another device with the same Id, the second
device will get assigned the next free (unused) Id.
The Id number in third party devices cant be changed within the Continuum world.
Third party Ids must be changed through its own preparatory software. If a third
party device is added to a network that already has an Id assigned to it, and another
device has already been assigned that Id, there is no way to detect this. Once the Ids
are assigned, its up to the person that installed the bus to make sure that any third
party devices do not have duplicate Ids.
From the factory the b3s do not have any Id (Id 0). If you have an out-of-the-box b3
that has zero (0) for an Id, it will be assigned the next free available Id during the
learn.
Adding Andover Devices to an MS/TP Network

1. Perform a Find BACnet Devices to see what devices are out there
2. Perform a Learn to join Andover devices to the network
This approach will assign ids that are not currently on the bus, eliminating duplicate
Id issues.
Note: It is a wise idea to write down all the type of devices that reside on the
MS/TP network along with their assigned Id numbers.
b3s require a b4 -920 as the router ( they cannot be assigned to an MS/TP
network under a third party router)
10-8
MS/TP

MS/TP Enhanced Mode
When selecting MS/TP Enhanced Mode, there is a change in the token passing
sequence where the b4 is treated like a priority controller. On the MS/TP bus, the
token goes around the whole bus. If you have five Ids, the Token goes from 0 to 1, 1
to 2, 2 to 3 and from 3 to 4. The b4 always has an Id of zero (0).
In Regular Mode, the b4 gets the token just as everyone else does.
In Enhanced Mode, the b4 receives the token every other time. Selecting Enhanced
Mode treats the b4 like a priority node.
For example, graphics within CyberStation require a lot of polling of data to the b4.
The b4 must receive the token more frequently or else graphics would be very slow.
MS/TP Enhanced Mode

Selection Box
BACnet MS/TP Net Id = 2763 + ACCNet ID
TAC
With multiple Continuum Networks, this may need to be changed
10-9

Identifying BACnet IP & MS/TP Network Numbers
Take the simple case of one sub-net with BACnet IP devices:
By default each device will be assigned the same UDP (User Datagram
Protocol) port number.
Each MS/TP bus is to have a unique BACnet Network Number. This will
put all the BACnet IP devices on the same network.
The BACnet MS/TP Network Id must be unique because they are

separate networks. Andover Controls performs a proprietary algorithm to
ensure a unique BACnet MS/TP Network Id assignment.
All BACnet IP devices should have the same BACnet Network Number
on that sub-net.
Same UDP BACnet Network Number
10-10
MS/TP

BacMaxMaster
By properly setting the BacMaxMaster (127 max), you are able to increase system
performance.
In MS/TP, the way a device gets in the loop is with the Poll for Master protocol.
For example, three nodes exist on a network and their Ids are set to 1, 5 and 10. Id
number 1 has to perform a poll for master periodically after 50 token passes. Id
number 1 will automatically poll for Ids 2 through 4 before passing the token to Id
number 5. When it reaches Id number 10, 10 now has to poll up to the Max Master of
127. These empty pockets steel bandwidth away from the network. If the Maxs
Master is set to 10 in this network, you will increase system performance because
after passing to Id number 10, it will go right back to Id 1.
For best performance on an MS/TP bus, make sure that your Ids are sequential (1, 2,
3, 4 and the BacMaxMaster is set to 4).
If you do set the BacMaxMaster and then someone adds another device, you must go
back and reset the BacMaxMaster to account for the higher number of nodes on the
MS/TP network.
TAC
10-11
10-12
MS/TP
TAC
1 High Street North Andover, Massachusetts 01845 USA
Tel: 978 470 0555 Fax: 978 470 0946
http://www.tac.com
TAC Ltd.
Smisby Road Ashby-de-la-Zouch Leicestershire LE65 2UG, England
Tel: 01530 417733 Fax: 01530 415436
TAC GmbH
Am Seerhein 8 D-78467 Konstanz, Germany
Tel: 07531 99370 Fax: 07531 993710
TAC S.A.
93 Avenue de Fontainebleau 94270 Le Kremlin-Bicetre, France
Tel: 49 60 63 63 Fax: 49 60 62 71
TAC
707 Chinachem Golden Plaza 77 Mody Road, Tsimshatsui East
Kowloon, Hong Kong
Tel: 2739 5497 Fax: 2739 7350
Copyright 2006, TAC
Data subject to change without notice.
All brand names, trademarks and registered trademarks are the property
of their respective holders.
Document Number: 31-3001-763 Version: 1

Networking Essentials Version1 04

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Networking Essentials Version1 04

Caricato da

Copyright:

Formati disponibili

Networking Essentials

Packets & Protocols

Shielded Twisted Pair wire

Un-shielded Twisted Pair wire

Fiber Optic cable

The speed of data transmission must be increased

Intelligence, i.e., computing capacity must be more widely distributed

Three aspects of the data communications problem represent the communications

Error Control - Detecting data errors and repairing them

Flow Control - Controlling transmitted data so that the receiver is not

Ordered Delivery - Delivering blocks of data in the proper order

Headers - Accompanying data with address and identification information (in

A LAN is the perfect method for connecting;

Building Automation Systems

Process Control Systems

Shielded Twisted Pair Cable

Unshielded Twisted Pair (UTP)

Unshielded Twisted Pair Cable

15 Pin AUI D style Male Connector

Low attenuation loss at high frequencies produce a wide bandwidth

Shield conductor minimizes electromagnetic interference (EMI)

Thinnet Coax - A 50-ohm "thin" (5mm) coaxial cable.

Thinnet Coaxial Cable

BNC style connector

Fiber Optic Cable

Graded and Stepped Fiber Optic Cables

Recommended for your applications and the most frequently used

ST & SMA Connectors

Light Loss for 62.5/125 Fiber = 1.2 dB/1000 ft

The Concept Using Drivers & Receivers

The driver converts a

The supported signal

The receiver converts the

The same process occurs in both directions

The Concept Using Transceivers

The transceiver converts a

The transceiver converts

One message is sent at a time over the network.

The characteristics of baseband are:

Broadband is a transmission facility having a bandwidth sufficient to carry

Each channel occupies (is modulated to) a different frequency bandwidth on

Channels are separated by "guardbands" (empty spaces) to ensure that each

The characteristics are:

Uses CATV components: Coax and Modems

Retransmit messages to every node on the network

A Hybrid is a combination of topologies

Idealized Star Topology Network

Star networks seldom have a symmetrical

Hybrid Network - Combining Bus and Star Topologies

The time it takes for the signal to go down the wire

Passing through a communications device like a repeater

Twisted Pair = 1.7 microseconds / 1000 ft

Fiber Optic = 1.5 microseconds / 1000 ft

Propagation Delays significantly impact a network when:

Attempt to run long distances

Packets & Protocols

A packet contains a To (Destination) and a From (Source), as well as the

Packets are defined by:

The physical type of network

The protocol used

A combination of both the physical type and the protocol

CRC (Cyclic Redundancy Check)

The Sending Device: