Echelon LONWORKS User Manual

®

LONW ORKS

Router

User’s Guide

Revision 3

@

EEEE CCCC HHHH EEEE LLLL OOOO NN

C o r p o r a t i o n

078-0018-01D

NN

®

No part of this publication may be reproduced, stored
in a retrieval system, or transmitted, in any form or by
any means, electronic, mechanical, photocopying,
recording, or otherwise, without the prior written
permission of Echelon Corporation.

Echelon, L

ON, LONWORKS, LonBuilder, LonManager,

LonTalk, LonUsers, Neuron, 3120, 3150,and the Echelon
logo are trademarks of Echelon Corporation registered
in the United States and other countries. LonLink,
L

ONMARK , LonSupport, LonMaker, the LONMARK logo,

and the LonUsers logo are trademarks of Echelon
Corporation.

Document No. 79100

Printed in the United States of America.
Copyright ©1992 - 1995 by Echelon Corporation

Echelon Corporation
4015 Miranda Avenue
Palo Alto, CA, 94304, USA

FCC NOTICE

Note: This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses, and can radiate
radio frequency energy and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications. However, there is no
guarantee that interference will not occur in a particular installation. Operation of
this equipment in a residential area is likely to cause harmful interference in which
case the user will be required to correct the interference at his own expense.

Caution: Changes or modifications not covered in this manual must be approved in
writing by the manufacturer’s Regulatory Engineering department. Changes or
modifications made without written approval may void the user’s authority to operate
this equipment.

VDE NOTICE

This product complies with VDE 0870 Part 30 as a peripheral device. To ensure
continued compliance, this product should only be used in conjunction with other
compliant devices.

CANADIAN DOC NOTICE

This digital apparatus does not exceed the Class A limits for radio noise emissions from
digital appararatus set out in the Radio Interference Regulations of the Canadian
Department of Communications.

Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les
limites applicables aux appareils numériques de la classe A prescrites dans le
réglement sur la brouillage radioélectrique édicté par le Ministére des Communications
du Canada.

Contents

Notices i

1 Introduction

Audience 1-4
Content 1-4
Related Documentation 1-4

1-1

2 Theory of Operation 2-1

LonTalk
Looping Topologies 2-2
Power Line Routers 2-3
Routing Algorithms 2-4

Message Buffers 2-7

®

Protocol Support for Routers 2-2

Repeater 2-4
Bridge 2-4
Configured Router 2-4
Learning Router 2-5

3 Packaged Router Overview 3-1

Mechanical Description 3-2

Switches, Indicators, and Connectors 3-3

ESD Warning 3-4

4 RTR-10 Overview 4-1

Mechanical Description 4-2
RTR-10 Power Requirements 4-5

Power Supply Decoupling and Filtering 4-5
Low Voltage Protection 4-5

Electrical Interface 4-5

ACLK2, BCLK1, and BCLK2 4-7
ACP[4..0] and BCP[4..0] 4-7
~ASVC and ~BSVC 4-7
AXID[4..0] and BXID[4..0] 4-7
PKT 4-8
~RESET 4-9
~SERVICE 4-9

5 Developing a Router with the RTR-10 Module 5-1

Overview 5-2
Using Predefined Transceivers 5-2
Using Custom Transceivers 5-4

LONWORKS Router User’s Guide v

6 RTR-10 Design Issues

EMI Design Issues 6-2
Designing Systems for EMC (Electromagnetic Compatibility) 6-2

EMC Design Tips 6-2

ESD Design Issues 6-3

Designing Systems for ESD Immunity 6-3

6-1

7 Installing a Router 7-1

Introduction 7-2
Defining a Network Topology 7-2
Attaching the Router to a Network 7-2
Connecting Power 7-4
Installing the Router on a Network 7-5

Router Installation with Network Management Messages 7-6
Router Installation with the LonMaker® Installation Tool 7-6
Router Installation with the LonManager

Router Installation with the LonBuilder
Testing Router Installation 7-8
Building a Router Mounting Bracket 7-8

®

API 7-6

®

Developer's Workbench 7-7

8 Network Management Messages 8-1

Introduction 8-2
Standard Messages 8-2
Router Specific Messages 8-4

Router Specific Network Management Messages 8-5

Set Router Mode 8-5
Group or Subnet Table Clear 8-5
Group or Subnet Table Download 8-5
Group Forward 8-6
Subnet Forward 8-6
Group No Forward 8-7
Subnet No Forward 8-7
Group or Subnet Table Report 8-7
Router Status 8-8
Far Side Escape Code 8-8

Router Options Set with Write Memory 8-8

Set Routing Algorithm 8-9
Set Buffer Size 8-9
Set Priority Output Buffer Queue Count 8-10

Set Input and Non-Priority Buffer Queue Count 8-11

Appendix A Communications Parameters A-1

Appendix B Software License and Patent Agreement B-1

vi Echelon

1

Introduction

LONWORKS Routers connect two communications channels,
and route LonTalk messages between them. Routers connect
two communication channels and route LonTalk
between them. They support the installation of both small and
large networks with dozens to thousands of nodes.

The following figure illustrates a typical installation with free
topology, power line, and 78kbps bus topology channels
connected to a 1.25Mbps backbone twisted pair channel using
three routers. Because of the routers, the applications on all six
nodes in this example can communicate transparently as if they
were installed on a common channel.

®

messages

TP/XF-1250 Backbone Channel

TP/XF-1250
to
TP/FT-10
Router

TP/FT-10 Channel 1

Node 2

Figure 1.1 Sample Router Installation

TP/XF-1250
to
PL-10
Router

PL-10 Channel 2

TP/XF-1250
to
TP/XF-78
Router

TP/XF-78 Channel 3

Node 5 Node 6Node 3 Node 4Node 1

LONWORKS Router User’s Guide 1-1

Routers are used to:

• Extend the limits of a single channel. A router may be used to add a channel to a

L

ONWORKS network to support additional nodes or extend the maximum channel

length. Multiple routers may be added, depending on the capacity or distance
needed.

• Interface different communication media, or bit rates, in a L

ONWORKS network.

For example, it may be desirable to trade data rate for distance on portions of the
network, or to use a 1.25Mbps backbone twisted pair channel to connect several
78kbps free topology and link power channels. Alternatively, it may be desirable
to use power line for a portion of the network where the nodes are subject to
frequent physical relocation, or if cable installation is difficult. In all of these
cases, a router must be used to connect the dissimilar L

ONWORKS channels.

• Enhance the reliability of the LONWORKS network. The two channels connected

to a router are physically isolated, so a failure on one channel does not affect the
other. For example, in an industrial control network, isolation among connected
cells may be desirable to prevent a failure in a single cell from bringing down
multiple cells. This would be achieved by dedicating channels to individual cells
and isolating them from one another with routers.

• Improve overall network performance. Routers can be used to isolate traffic

within subsystems. For example, in a cluster of industrial cells, most of the
communications may be with nodes within cells rather than across cells. Use of
intelligent routers across cells will avoid forwarding messages addressed to nodes
within a cell, thus increasing the capacity and decreasing the response time of
the overall network.

The use of routers across channels is transparent to the application programs within
nodes. Thus, application development can be done independently, without knowledge
of the workings of the routers. Routers need to be taken into account only when
determining the network image of a node. If a node is moved from one channel to
another, only the network image must be changed. Network images are managed by a
network services tool such as the LonManager

®

LonMaker® Installation Tool.

L

ONWORKS routers are offered in a variety of options so that they can be tailored for

specific uses. Options include the following:

• Integration. Router components are available for embedding in OEM products. An

RTR-10 router and two transceiver modules, one to handle each of two channels
connected by the router, may be mounted on a motherboard, along with a power
supply and two network connectors. This sub-assembly constitutes a custom router.
It can be packaged in an enclosure to meet unique form factor and environmental
requirements. Depending on the application, the package may contain a single
router sub-assembly, or may include other application-specific hardware. See
figure 1.2 for a block diagram of a router based on the RTR-10 router. Multiple
routers may be packaged together for some applications, e.g., a backbone
connecting multiple channels.

1- 2 Introduction

Packaged routers, FCC- and VDE-certified to comply with conducted and

k

k

y

radiated emissions specifications and UL-certified for safety, with optional
wall-mount power supplies, are also available from Echelon. These eliminate
the need to build hardware and obtain the necessary electrical interference and
safety certifications. Thus, they allow direct, off-the-shelf integration into the
user's L

ONWORKS network.

Service Button/LEDs

Power

Suppl

RTR-10 Router Core Module

Side A

Transceiver

Side A Networ

Connector

Side B

Transceiver

Side B Networ

Connector

Figure 1.2 Router Assembly Using the Router Core Module

• Routing Algorithm. Routers can use one of four routing algorithms: configured router,
learning router, bridge, or repeater. These options allow system performance to be

traded for ease of installation. Configured and learning routers fall into a class of
routers referred to as intelligent routers, which use routing intelligence to
selectively forward messages based on the destination address. A bridge forwards
all packets that match its domain(s). A repeater forwards all valid packets.

A network services tool such as the LonMaker Installation Tool is used to select the
routing algorithm and calculate network topology as well as layer 4 timing
parameters. Both sides of a router must use the same algorithm. LonBuilder

®

,
LonMaker, or a tool based on the LonManager API is required to install a configured
router.

LONWORKS Router User’s Guide 1-3

Audience

Content

The LONWORKS Router User’s Guide provides user instructions for users of

ONWORKS routers and for developers who plan to integrate the RTR-10 router into

L
embedded or standalone routers.

This manual provides detailed information about the hardware and firmware for

ONWORKS routers.

L

• Chapter 1 introduces the LONWORKS routers.

• Chapter 2 discusses a theory of router operation and describes repeaters, bridges,
configured routers, and learning routers.

• Chapter 3 provides an overview of the Model 71000 L

• Chapter 4 provides an overview of the Model 61000 RTR-10 Router Core module.

• Chapter 5 describes how to build a custom router using RTR-10 routers.

• Chapter 6 examines a number of design issues that should be considered when
designing hardware based on the RTR-10 module.

• Chapter 7 lists installation instruction for routers.

• Chapter 8 describes network management services for routers.

• Appendix A lists the default communications parameters for L

• Appendix B includes a copy of the router software license and patent agreement.

Related Documentation

The following Echelon documents provide more information on the router:

• The LonTalk Protocol engineering bulletin summarizes the services available at
each of the seven layers of the LonTalk protocol included with every Neuron
Chip.

• The LonManager LonMaker Installation Tool User’s Guide describes how to
install a router using the LonMaker Installation Tool.

• The LonBuilder User's Guide describes installing a router in a development
network.

• The LonManager Profiler User’s Guide describes how to import a router interface
(.RIF) file to create a router type for LonMaker.

• The LonManager API Programmer's Guide for DOS and the LonManager API
Programmer’s Guide for Windows describe how to install a router using the
LonManager API.

ONWORKS Router.

ONWORKS routers.

®

1- 4 Introduction

• The Neuron Chip Data Book describes the Neuron Chip. Descriptions cover
CPUs, memory subsystems, LonTalk protocol, network communications port,
programming model, application I/O, and additional functions.

• The L

ONWORKS TPT Twisted Pair Transceiver Module User's Guide describes

the L

ONWORKS twisted pair transceivers. This is useful for the OEM

implementing a router to interface with a twisted pair channel.

• The L

ONWORKS FTT-10 Free Topology Transceiver User's Guide describes the

L

ONWORKS FTT-10 free topology transceiver. This is useful for the OEM

implementing a router to interface with a TP/FT-10 free topology channel.

• The L

ONWORKS LPT-10 Link Power Transceiver User's Guide describes the

ONWORKS LPT-10 link power transceiver. This is useful for the OEM

L
implementing a router to interface with a link power channel.

• The L

ONWORKS PLT-10A Transceiver User's Guide describes the LONWORKS

PLT-10A Power Line Transceiver. This is useful for the OEM implementing a
router to interface with a PL-10 power line channel.

• The L

ONWORKS PLT-20 Transceiver User's Guide describes the LONWORKS

PLT-20 Power Line Transceiver. This is useful for the OEM implementing a router
to interface with a PL-20 power line channel.

• The L

ONWORKS PLT-30 Transceiver User's Guide describes the LONWORKS

PLT-30 Power Line Transceiver. This is useful for the OEM implementing a router
to interface with a PL-30 power line channel.

• The Junction Box and Wiring Guidelines for Twisted Pair L

ONWORKS Networks

engineering bulletin describes the different types of junction boxes and
interconnections that may be used in twisted-pair L

ONWORKS networks.

• The LONW ORKS Interoperability Guidelines provide the guidelines that are the
basis for obtaining the L
L

ONWORKS interoperable.

ONMARK

™

logo, which indicates that a product is

LONWORKS Router User’s Guide 1-5

2

Theory of Operation

This chapter describes the router theory of operation. An
overview is first presented of how the LonTalk protocol
supports routers. This is followed by a discussion of looping
topologies and how they are handled by routers. Then, routing
algorithms are described, followed by a discussion of buffer usage
within routers.

LONWORKS Router User’s Guide 2-1

LonTalk Protocol Support for Routers

The LonTalk protocol is designed to provide transparent routing of messages between
nodes that communicate via routers. To increase the efficiency of routers, the LonTalk
protocol defines a hierarchical form of addressing using domain, subnet, and node
addresses. Subnets do not cross intelligent routers, which allows intelligent routers to
make a routing decision based on the subnet component of a node's logical address. To
further facilitate the addressing of multiple dispersed nodes, the LonTalk protocol
defines another class of addresses using domain and group addresses. Intelligent
routers also can be configured to make a routing decision based on the group addressing
component of a message.

In general, a network services tool such as the LonMaker Installation Tool, is
responsible for domain, subnet, node, and group address assignments.

See the LonTalk Protocol engineering bulletin (005-0017-01) for a further description of
the LonTalk protocol. See the L
further description of the installation scenarios.

ONW ORKS Installation Overview (005-0006-01) for a

Looping Topologies

A looping topology is a network topology that has the potential for message loops. A
loop is a path through two or more routers that forwards a message from a channel
back to the same channel. For example, figure 2.1 shows a looping topology with two
channels and two routers. A message on channel A could be forwarded by router 1 to
channel B, then the same message could be forwarded by router 2 back to channel A,
starting an endless loop of forwarded messages.

Channel B

Router 1

Channel A

Figure 2.1 A Looping Topology

The LonTalk protocol does not support topologies where loops can occur. However,
looping topologies may be desirable for the following reasons:

• Increased Reliability. Redundant routers may be used to increase system reliability
by providing multiple paths between two channels.

Router 2

2-2 Theory of Operation

• Support for Open Media. Open media such as RF may require redundant routers
with overlapping coverage to ensure complete coverage of an area.

Configured routers can be used to support looping topologies, by configuring the routers
to prevent message loops. For example, the topology in figure 2.1 can be supported if
both routers are configured to forward all messages addressed to subnets on channel B
from channel A; and all messages addressed to subnets on channel A from channel B.
Any groups with members on both channels can only be forwarded by one of the two
routers.

Network services tools such as the LonMaker Installation Tool or custom tools based on
the LonManager API can automatically set up the forwarding tables for configured
redundant routers.

Power Line Routers

A looping topology can be inadvertently created when using power line media.
Passive coupling between different phases of a power line system can cause packets
transmitted on one phase to be received by nodes installed on another phase. A loop
can be formed when active coupling provided by a router is combined with passive
coupling. Figure 2.2 illustrates an example looping topology.

Phase A
to Phase B
Router

Power Line Phase A

▼

▲

▼

Passive
Coupling

▼

Power Line Phase B

Figure 2.2 A Looping Topology with One Router

Routers can be used between power line channels only if the two channels are fully
isolated. This is generally not the case between two phases on the same circuit, but
may be the case between phases on different distribution transformers. Echelon’s
PLCA-10, PLCA-20, or PLCA-30 Power Line Communication Analyzers should be used
to confirm isolation between power line channels before installing power line to power
line routers.

LONWORKS Router User’s Guide 2-3

Routing Algorithms

LONWORKS Routers can be installed to use one of four types of routing algorithms:
configured router, learning router, bridge, and repeater. This selection allows system

performance to be traded for ease of installation. The configured router and learning
router algorithms are used to create intelligent routers that selectively forward
messages based on network topology. This section describes the four algorithms. Both
sides of a router must use the same routing algorithm.

The following general rules apply to all four routing algorithms:

• For a message to be forwarded, it must fit into the router's input and output message
buffer. A free input message buffer must be available.

• For a message to be forwarded, it must have a valid CRC code.

• Priority messages are forwarded as priority messages, but with the priority level
of the transmitting side rather than the priority level of the originator of the
message. If the transmitting side has not been installed with a priority value, then
priority messages are not forwarded in a priority slot. The priority message is still
flagged as a priority message, so that if it passes through a second router that is
installed with a priority level, the second router transmits the message in a
priority slot.

Repeater

A repeater is a router which forwards all messages across in both directions,
regardless of the destination or domain of the message. Any valid message (i.e. any
message with a valid CRC code) received will be forwarded.

Bridge

A bridge is a router which forwards all messages received on either of the router's
domains regardless of the message's destination. A bridge is used for spanning one or
two domains.

Configured Router

A configured router is a router which forwards only messages received on either of the
router's domains and which meet the forwarding rules described in figure 2.3. A
forwarding table is used for each domain on each side of the router. Each forwarding
table contains a forwarding flag for each of the 255 subnets and 255 groups in a domain.
As described in figure 2.3, these flags determine whether or not a message should be
forwarded or dropped based on the destination subnet or group address of the message.

The forwarding tables are initialized by a network services tool using the network
management messages described in Chapter 8. By configuring the routing tables based
on network topology, a network services tool can optimize network performance and
make the most efficient use of available bandwidth. As described in the previous
section, configured routers should be used for looping topologies.

2-4 Theory of Operation

There are two sets of forwarding tables, one in EEPROM and one in RAM. The
EEPROM table is copied to the RAM table when the router is initially powered-up,
after a reset, and when the router receives the Set Router Mode command with the
Initialize Routing Table option. The RAM table is used for all forwarding decisions.

Several of the operations in figure 2.3 help prevent message loops for service pin
messages. Service pin messages require special handling since they are broadcast to
all nodes on the zero-length domain, and have a source subnet ID of zero. When a
router receives a service pin message with a source subnet ID of zero, the router
modifies the source subnet field of the message to be the router's subnet on the receiving
side. If the receiving side is installed in two domains, two service pin messages are
forwarded, one for each domain. This allows the router to drop the service pin
message if a loop causes the message to be received again on the same side.

Learning Router

A learning router is a router which forwards only messages received on either of the
router's domains and which meet the forwarding rules described in figure 2.2.
Forwarding tables are used as with configured routers, except that the subnet
forwarding tables are updated automatically by the router firmware, rather than
being configured by a network services tool. The group forwarding tables are
configured to always forward (flood) all messages with group destination addresses.

Learning routers learn network topology by examining the source subnet of all messages
received by the router. Since subnets cannot span two channels connected to an
intelligent router, the router can learn which side a subnet is on whenever that subnet
ID appears in the source address.

The subnet forwarding tables are initially configured to forward all messages with
subnet destination addresses. Each time a new subnet ID is observed in the source
address field of a message, its corresponding flag is cleared (i.e., forwarding is
disabled) in the subnet forwarding table. The forwarding flag for the destination
address is then checked to determine whether the message should be forwarded or
dropped. The forwarding flags are all cleared whenever the router is reset, so the
learning process starts over after a reset.

The forwarding flag for a given subnet should never be cleared on both sides of a router.
However, this may occur if a node is moved from one side of a router to the other side.
For example, if subnet 1 is located on side A of a router, the router will learn subnet 1’s
location as soon as it receives a message generated by any node in subnet 1. If any
subnet 1 node is moved to side B without reinstalling it, the router will learn that
subnet 1 is also on side B, and will quit forwarding subnet 1 messages to side A. The
router detects this error and logs it as described in Chapter 8.

LONWORKS Router User’s Guide 2-5

Start:
Router receives
message packet

Is message
addressed to either
of the router's
domains?

No

Is message
domain length
zero, source
subnet zero,
addressed as
broadcast?

No

Substitute one or
both domains from
the router, source
subnet = our subnet,
dest subnet zero.

Forward one or
two packets

Yes

Drop
packet

Yes

No

Is message source
subnet zero?

No

Clear subnet
fwd flag *

Is message
addressed to
group?

Yes

Is the group fwd
flag of the dest.
group set to
forward?

Yes

No

No

Is message
domain length
zero, and

Yes

addressed as
broadcast?

Is message
addressed to
subnet/node?

Is the subnet fwd flag
for the dest. subnet
set to forward?

Yes

Yes

Yes

No

Set message
source subnet =
router subnet.

Message must be
addressed as
broadcast or 48-bit

No

NEURON ID

No

Is message dest.
subnet = zero?

Yes

Is the subnet fwd flag

Yes

Drop packet

* Executed only in a learning router
** Executed only in a configured router, otherwise forward

for the source subnet
set to forward ? **

No

Forward packet

Figure 2.3 Configured/Learning Router Forwarding Rules

2-6 Theory of Operation

As with configured routers, learning routers sometimes modify source addresses for
service pin messages to help prevent message loops.

Learning routers, in general, are less efficient in using channel bandwidth because they
always forward all messages with group destination addresses. Their advantage is
simplified installation since the installation tool does not need to know the network
topology to configure a learning router.

Message Buffers

As messages are received by a router, they are placed in an input buffer queue. By
default, this queue is limited to two message buffers to ensure that priority messages are
never queued behind more than one non-priority message. When forwarded to the
transmitting side of the router, priority messages have their own outgoing buffer queue.
This assures priority processing of these outgoing messages since the transmitting side
will send messages from the priority output buffer queue before sending messages from
the non-priority output buffer queue. Figure 2.4 summarizes the message flow through
the input and output buffer queues. This message flow is duplicated for messages moving
in the opposite direction, i.e., another set of input and output buffer queues exist for
messages flowing in the opposite direction.

Message Receiving Side Message Transmitting Side

Input Buffer Queue

12

Priority Output Buffer Queue

12

1 2 3 n-1 n

Normal Output Buffer Queue

.......

Direction of Message Flow

Figure 2.4 Buffering Scheme for a LONWORKS Router

The size and count of the message buffers is limited by the amount of RAM on the
router. Each router side has 1,254 bytes of buffer space available. By default, this
space is allocated as two input buffers, two priority output buffers, and 15 non-priority
buffers. The default buffers are all 66 bytes, so the total RAM usage for the default
buffers is:

LONWORKS Router User’s Guide 2-7

Queue Count Size Total Bytes

Input Buffer Queue 2 66 132
Priority Output Buffer Queue 2 6 6 13 2
Non-Priority Output Buffer Queue 15 66 990

TOTAL 1254

The default size of 66 bytes allows the router to handle packets with maximum
address overhead and data size for any network variable message and explicit
messages with up to 40 bytes of data; this is large enough for any network management
or network diagnostic message. In applications that must route large explicit messages
with more than 40 bytes of data, the buffer size must be increased, and the count of non­priority buffers decreased. See Chapter 6 of the Neuron C Programmer’s Guide to
understand how the network buffer sizes are calculated. The size and count of buffers
can be changed as described in Chapter 8 of this document. They also can be changed
using the NodeUtil node utility available on the LonLink

™

bulletin board and Internet

Host. The total memory required by the three buffer queues must not exceed 1254 bytes.

The default buffer configuration places the bulk of the buffers on the output queues of
the router. For example, the standard configuration places two network buffers on the
input queue and 17 buffers on the output queue (2 priority and 15 non-priority) of each
router side. The reasoning behind this configuration is to keep buffered packets on the
output queues, after they have been processed for forwarding. This processing includes
checking for priority packets. Priority packets are sensed and forwarded through the
router's priority output buffers. This assures that priority packets are processed as
quickly as possible, rather than allowing them to be delayed behind non-priority
packages in a large input queue.

There are applications, however, where the network traffic may be 'bursty' where
many packets appear on the network almost at the same time. In these cases the
traffic bursts may cause the input queue to become full and loose the excess packets.

In this case it may be preferable to move more of the packet buffering from the output
queue to the input queue. This can be done by increasing the size of the input queue and
decreasing the size of the output queue. A router with a larger input queue can handle
larger bursts of traffic, at the risk of priority messages being queued behind several
non-priority messages.

2-8 Theory of Operation

3

Packaged Router Overview

This chapter provides an overview of the Model 71000 LONWORKS
Router hardware. If you are using custom routers based on the RTR­10 Router Core Module, skip this chapter.

LONWORKS Router User’s Guide 3-1

Mechanical Description

The following drawings provide the front and back views of the Model 71000 router.

®

Router

Back View

ORKS

W

ON

L

3.895
[98.93]

All dimensions are in inches with
equiv. mm dimensions in brackets.

1.163 [29.54]

6.62
[168.15]

Back View

Figure 3.1 Router Views - Front and Back (rubber feet not included in the dimensions)

LONWORKS Router User’s Guide 3-1

Switches, Indicators, and Connectors

Table 3.1 describes the function of router switches, indicators, and connectors.

Table 3.1 Router Interfaces

Interface Function

Service Request Pressing this switch grounds the service pin to both sides of the

router. When this switch is pressed, both service LEDs should light
to maximum intensity. This action generates service request messages
from each side of the router. For more information, see the Neuron
Chip Data Book.

Service 1 (Yellow LED) When the service request switch is being pressed, this

LED is on at maximum intensity. If the service request switch is not
being pressed, then the LED indicates the following:

on an unrecovered error has been detected on

side one

blinking side one unconfigured; routing tables or

router node address assignment have not
been loaded

off side one configured

Power On (Green LED) Indicates that power is being supplied to the router.

Does not necessarily indicate that the power supply voltage is
within tolerance.

Status (Green LED) Flickers when a packet is being forwarded in either

direction. The rate of flashing can be used as a rough indicator of
router activity level.

Service 2 (Yellow LED) When the service request switch is being pressed, this

LED is on at maximum intensity. If the service request switch is not
being pressed, then the LED indicates the following:

on an unrecovered error has been detected on side two

blinking side two unconfigured; routing tables or router

node address assignment have not been loaded

off side two configured

LONWORKS Router User’s Guide 3-3