adept technology GadgetGateway User manual

Adept Systems, Inc.
360 W . 920 N., Orem, UT 84057
Ph: 801.226.7607 Fax: [phone]
http://www .adeptsystemsinc.com
G ADGET G ATEWAY I
U SER G UIDE
V ersion 2.41

i
T echnical Support Information
W eb: www.GadgetTek.com/support
Email: [email protected] or [email protected]
Phone: [phone]
Copyright © 2001 , 2003 by Adept Systems, Inc. All Rights Reserved.
Printed in USA.
Version 1, December 2001.
Version 2, May 2003.
Version 2.3, September 2003
This document, the associated software, and the associated online documentation are the property of Adept
Systems, Inc. and are loaned to the user under the terms of the End User License Agreement. No title to or
ownership of the software described in this document or any of its parts is transferred to customers. Unau-
thorized copying or use of the software or any associated materials is contrary to the property rights of Adept
Systems, Inc. and is a violation of state and federal law. This material must be returned to Adept Systems
upon demand.
Information in this document is subject to change without notice. No part of this document may be repro-
duced or transmitted in any form or by any means without the express written permission of Adept Systems,
Inc.
T rademarks
GadgetStack and the Adept Systems Logo are registered trademarks of Adept Systems, Inc.
GadgetGateway, GadgetNode, GadgetNIC, and GadgetTek are trademarks of Adept Systems, Inc.
NETsilicon and NET+Works are trademarks of NETsilicon, Inc.
All other product and company names are trademarks or registered trademarks of their respective holders.
Disclaimer
Adept Systems mak es no representations or warranties regarding the contents of this document. Information
in this document is subject to change without notice and does not represent a commitment on the part of
Adept Systems, Inc.

ii
T ABLE OF C ONTENTS
Chapter 1 About this Guide
1.1 Guide Structure 1-2
1.2 Guide Conventions 1-2
1.2.1 Special Characters and T ypographical Conventions 1-2
1.2.2 Screen Shots 1-2
1.3 Customer Support 1-3
Chapter 2 GadgetGateway Overview
2.1 Introduction 2-2
2.1.1 Gateway Parameters 2-3
2.1.2 Gateway Modes of Operation 2-5
2.1.3 Uses for the GadgetGateway 2-6
2.2 System Requirements 2-7
2.3 Needed Hardware 2-8
2.4 Connectors and Indicators 2-9
2.5 Redundant T win Mode 2-9
2.5.4 Definitions 2-13
2.5.5 Status SNVT 2-13
2.5.6 Alarm SNVT 2-14
2.5.7 Status Report UNVT 2-14
2.6 852 to 852 Bridge Mode 2-15
Chapter 3 GadgetGateway Startup Guide
3.1 Hardware Setup 3-2
3.2 Default Password 3-2
3.3 Configuring in Manual Mode 3-3
3.4 Configuring with the i.LON 1000 TM Configuration Server 3-4
3.5 Configuring with the Coactive Router -LL 3-6
3.5.1 Manual Mode 3-6
3.5.2 Router -LL Configuration Server Mode 3-6
3.6 Using GadgetGateway with LonMaker over IP 3-7
3.6.3 Using the i.LON Configuration Server 3-7
3.7 Configuring GadgetGateways with NA T Routers 3-1 1
3.8 Configuring GadgetGateways with DDNS Routers. 3-13
3.9 Configuring GadgetGateways in Redundant T win Mode. 3-14

iii
3.9.4 Using the Serial Console Menu 3-14
Chapter 4 GadgetGateway Serial Interface
4.1 Introduction 4-4
4.2 GadgetGateway IP Configuration 4-4
4.3 GadgetGateway Main Menu 4-6
4.3.1 Set Router Mode 4-7
4.3.2 Enable 852 to 852 Mode 4-7
4.3.3 Reboot GadgetGateway 4-8
4.3.4 Save Configuration to Flash 4-8
4.4 709.1/IP Gateway Setup Menu 4-8
4.4.5 Set Router Name 4-9
4.4.6 Set 709.1 Router Type 4-10
4.4.7 Set Node Type 4-10
4.4.8 Set Gateway IP Port 4-12
4.4.9 Set NATRouter WAN Address 4-12
4.4.10 Enable/Disable NATRouter Support 4-13
4.4.11Set HTTP/WebServer Port 4-13
4.4.12 Set Configuration Server Address 4-14
4.4.13 Set Configuration Server Port 4-14
4.4.14 Configuration Server Compatibility Mode 4-15
4.4.15 Send Registration to Configuration Server 4-15
4.5 DDNS Setup Menu 4-15
4.5.16 Set DDNS Name 4-16
4.5.17 Set DDNS State 4-16
4.5.18 Set DDNS Refresh time 4-17
4.5.19 Set DNS Servers 4-17
4.5.20 Lookup DDNS IP Address 4-17
4.5.21 Reboot GadgetGateway 4-17
4.6 Channel Detail Menu in Normal Mode 4-18
4.6.22 Channel Name 4-19
4.6.23 Update Channel Member Names 4-19
4.6.24 Accessing Device Details 4-19
4.7 Channel Detail Menu in Manual Mode 4-19
4.7.25 Change Channel Name 4-20
4.7.26 Change Channel Timeout 4-20
4.7.27 Change Channel Address Mode 4-20
4.7.28 Set Multicast Address 4-21

iv
4.7.29 Add a Device to the Channel 4-22
4.7.30 Delete a Device from the Channel 4-22
4.7.31 Update Channel Member Names 4-22
4.7.32 Access Device Details 4-22
4.8 Device Details Menu 4-23
4.8.33 View Device Interface Menu 4-23
4.8.34 Fetch Device Data 4-23
4.9 709.1 Parameter Menu 4-24
4.9.35 Access Interface Details 4-24
4.9.36 Change Subnet Number 4-25
4.9.37 Change Node Number 4-25
4.9.38 Change Domain 4-26
4.9.39 Change Subnet Forwarding Table 4-26
4.9.40 Change Group Forwarding Table 4-27
4.9.41 Change Node State 4-27
4.10Redundant Twin Configuration Menu 4-28
4.10.42HeatBeat Time 4-29
4.10.43TimeOut Cushion 4-29
4.10.44AutoSync Time 4-29
4.10.45Diagnostic Retries 4-30
4.10.46Initial Arbitration Count 4-30
4.10.47Power up in Forward Mode 4-31
4.10.48Status SNVT update time 4-31
4.10.49Status SNVT propagate on update. 4-32
4.10.50Twin Configuration IP Address and Port 4-32
4.10.51Domain-Subnet-Node Address 4-33
4.10.52Sync Data From Twin & Sync Data To Twin 4-33
4.10.53Clear Twin 709 Configuration 4-33
4.10.54Enable/Disable Twin Mode 4-34
4.10.55Twin Mode Status Menu 4-34
4.11Tools and Diagnostic Menu 4-35
4.11.56Reset 852 Configuration Data 4-36
4.11.57Set Web User ID and Password 4-36
4.11.58Set Current Date and Time 4-36
4.11.59Set Loop Detection Frequency 4-37
4.11.60Statistics Menu 4-37
4.11.61Print Abort Error Log 4-38
4.11.62Print Watch Dog Time Out Debug Log 4-39

v
4.11.63Print Debug Log 4-39
4.11.64Clear Logs 4-39
Chapter 5 Gadget Gateway Web-based Interface
5.1 Introduction 5-2
5.2 Accessing the Web-based Interface 5-2
5.3 Gateway Status Page 5-3
5.4 Router Setup Page 5-4
5.5 IP Setup Page 5-8
5.6 Channel List Page 5-10
5.6.1 The Channel List in Normal Mode 5-10
5.6.2 The Channel List in Manual Mode 5-13
5.6.3 Device Detail Page 5-16
5.7 Diagnostics Page 5-17
5.8 DDNS Setup Page 5-18
5.9 Twin Mode Setup Page 5-19
5.10Twin Mode Status Page 5-21
5.11Contacts Page 5-23
Chapter 6 GadgetGateway Firmware Upgrade
6.1 Firmware Upgrade Instructions 6-2
6.2 Upgrading From Versions 2.0b9 though 2.25 to Version 2.3 or higher Firmware6-5
6.3 Upgrading From Version 1.x Firmware 6-6
6.4 Restoring Node IDs or MAC Addresses in Version 2.xx Firmware 6-7
6.4.1 Restoring Node IDs 6-7
6.4.2 Restoring the Ethernet Mac Address 6-7
6.5 Current Firmware Features and Updates 6-8
6.5.3 Changes in Latest Version 6-8

1
1.1 Guide Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.2 Guide Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.2.1 Special Characters and Typographical Conventions 1-2
1.2.2 Screen Shots 1-2
1.3 Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
ABOUT THIS GUIDE

1.1 Guide Structure
1-2
About this Guide
Chapter 1: About this Guide
1.1 Guide Structure
This guide is organized as follows:
Chapter 2, “GadgetGateway Overview”: Contains a brief functional overview to the Gad-
getGateway, its modes of operation and uses. This chapter also lists system requirements
and gives a description of the Gateway connectors, ports, and indicators.
Chapter 3, “GadgetGateway Startup Guide”: Provides step-by-step instructions for easy
installation and configuring of the GadgetGateway in various scenarios.
Chapter 4, “GadgetGateway Serial Interface”: Familiarizes the user with the screens used
in the Serial Interface to configure the GadgetGateway for operation.
Chapter 5, “Gadget Gateway Web-based Interface”: Familiarizes the user with the various
pages of the Web-based Interface and describes the steps necessary for changing configu-
ration data.
Chapter 6, “GadgetGateway Firmware Upgrade”: Provides instructions for upgrading the
Gateway firmware for enhancements and features that may become available in the future.
Appendix A: Contains errata information on the current software versions.
1.2 Guide Conventions
1.2.1 Special Characters and Typographical Conventions
Note:Introduces important additional information.
Monospace text represents either a function or text/code that appears on a
terminal screen.
Bold textRepresents a file or folder name.
1.2.2 Screen Shots
The values represented in screen shots (e.g., version numbers and configuration parame-
ters) represent typical data and may be different than those displayed on a particular Gad-
getGateway.

1-3
About this Guide 1.3Customer Support
1.3 Customer Support
Adept Systems, Inc. invites your comments and recommendations about both our products
and our documentation. Please refer any questions or technical problems concerning this
product to the contacts listed below.
Web:www.GadgetTek.com/support
Email:[email protected] or [email protected]
Phone:[phone]

1.3 Customer Support
1-4
About this Guide

2
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.1 Gateway Parameters 2-3
2.1.2 Gateway Modes of Operation 2-5
2.1.3 Uses for the GadgetGateway 2-6
2.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.3 Needed Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
2.4 Connectors and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.5 Redundant Twin Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
2.5.4 Definitions 2-13
2.5.5 Status SNVT 2-13
2.5.6 Alarm SNVT 2-14
2.5.7 Status Report UNVT 2-14
2.6 852 to 852 Bridge Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
GADGETGATEWAY
OVERVIEW

2.1 Introduction
2-2
GadgetGateway Overview
Chapter 2: GadgetGateway Overview
2.1 Introduction
The GadgetGateway router forwards packets that use the ANSI/EIA 852 and ANSI 709.1
protocols between an 852 based Internet Protocol (IP) channel (using Ethernet) and a
ANSI/EIA 709.1 (LonTalkTM) channel (using TPFT-10 or TPXF-1250 transceivers). The
GadgetGateway has a presence, or physical connection, to both networks. The Gateway
takes ANSI/EIA 709.1 messages from the ANSI/EIA 709.1 network and transports them
through the IP network wrapped in an ANSI/EIA 852 packet. The ANSI/EIA 709.1 pack-
ets, or messages, cannot travel over IP by themselves, so an alternate means of transport is
necessary. ANSI/EIA 852 acts as the transport service to convey ANSI/EIA 709.1 mes-
sages over IP networks to other 709.1 to IP routers or devices. The messages are then
unwrapped back into native ANSI/EIA 709.1 messages and sent on their way. The 852
protocol is a generic tunneling protocol and is not limited to ANSI 709.1 (LonTalk). In
852 parlance the tunneled protocol is a Component Network or CN protocol. In some of
the figures CN or CN/IP is used to represent a Component Network or Component Net-
work to IP connection or network.
This technique of using another protocol (i.e., ANSI/EIA 852) to transport a message over
an alternate media is often referred to as “tunneling.” ANSI/EIA 852 not only provides the
vehicle to transport ANSI/EIA 709.1 messages across IP, but it also provides management
of these connections or routes. The ANSI/EIA 709.1 messages have no information or
awareness of the tunneling process, so when a message arrives at a 709.1 to 852/IP router,
an independent management process from ANSI/EIA 852 must determine whether and
where to deliver the ANSI/EIA 709.1 messages.
Both the ANSI/EIA 709.1 and ANSI/EIA 852 are open standard protocols defined as part
of a committee hosted by the Consumer Electronics Association. For more details see
ce.org.
Network connection devices can operate at different layers of particular networks protocol
stack. ANSI 709.1 is an OSI 7 Layer type protocol. Whereas the internet protocol has only
4 layers. See Figure Figure 2.1 for a diagram of the different layers of the two protocols. A
network connector is a device that joins different parts of a network. Connectors have a
specific name that is dependent on the layer at which the connector operates. For example
a router operates at the network layer and a gateway at the application layer. Because
higher layers of the protocol do not have access to some of the information stripped away
by lower layers, network connector s operating at different layers have different capabili-
ties. There is also some abuse of terminology so that the descriptions of network connec-
tors from different manufacturers may be confusing. For example, a repeating router may
be called a repeater for short. Although a repeating router acts similarly to a physical layer

2-3
GadgetGateway Overview 2.1Introduction
repeater, it operates at the network layer and is not equivalent. It is usually best to find out
at which layer a network connector operates.
The GadgetGateway router is a more complex connector because is connects two different
protocols and also connects the protocols at different layers. On the IP side the Gadget-
Gateway operates at the application layer and so is appropriately called an IP Gateway. On
the 709.1 (LON) side the GadgetGateway operates at the network layer and is appropri-
ately called a LON router. So depending on the user’s perspective the GadgetGateway
could be called a gateway or router or a router/gateway. (See Figure 2.3) The Gadget-
Gateway router also employs a web server for configuration purposes. (See Figure 2.4)
2.1.1 Gateway Parameters
The information required for successful ANSI/EIA 709.1 transport can be broken up into
the following two categories: device parameters and channel parameters.
Device parameters include information such as:
•IP address,
FIGURE 2.1 . Network protocol layers
FIGURE 2.2 Protocol layer a network connector operates on.

2.1 Introduction
2-4
GadgetGateway Overview
•IP port,
•Name,
•Type of gateway, and
•Address of configuration server.
A channel is a logical grouping of IP to 709.1 gateways. The minimum requirement for
tunneling ANSI/EIA 709.1 data is the use of two gateways. Gateway A sends data to Gate-
way B and vise versa. However, gateways can also send data to more than one gateway. In
such a case, Gateway A sends data to Gateways B, C, and D, which in turn send data back.
FIGURE 2.3 LON to IP to LON tunnel using two GadgetGateway routers.
FIGURE 2.4 GadgetGateway router architecture.

2-5
GadgetGateway Overview 2.1Introduction
A channel, then, is defined as a group of gateways that all send information to each other.
The lines of communication are open in both directions and to all members—a complete
mesh of connections.
Typically, channels are managed through the use of a configuration server (called Normal
mode see below). The configuration server informs all members in the channel about the
channel information, which includes the adding and removing of channel members. Con-
figuration servers are capable of managing multiple channels, while gateways belong to
only one channel at a time.
709.1 to IP gateways can also be managed manually by configuring each device uniquely
(called Manual mode, see below). In such a manual configuration, for proper operation,
devices must have mutual membership in each other’s channel lists. That is if Device A is
in Device B’s channel list then Device B must be in Device A’s channel list. However if
Device C is in Device B’s channel list, Device C does not have to be in Device A’s channel
list.
2.1.2 Gateway Modes of Operation
The GadgetGateway can operate in one of two modes:
•Manual
•Normal
Manual Mode
In Manual mode the user has control over the GadgetGateway's configuration only. The
user can change the GadgetGateway's operating information and determine to whom the
Gateway will send information. In Manual mode the GadgetGateway will honor read
requests from other devices or configuration servers, but it will block requests to write or
change internal parameters. This is a more secure mode and may be preferred on open net-
works.
Normal Mode
Normal mode allows the user to view configuration data and channel data set by a remote
configuration server such as an i.LONTM configuration server. The configuration server
sets some of the operating parameters of the GadgetGateway. Configuration servers
mostly manage the device's channel. The channel is made up of other devices to which the
GadgetGateway will tunnel or send ANSI/EIA 709.1 data. In Normal mode the adding and
deleting of devices is managed exclusively by the assigned configuration server, the con-
figuration server providing a single interface to add and delete devices. Finally, Normal
mode permits read access to information by other devices and write access to information
for the assigned configuration server.

2.1 Introduction
2-6
GadgetGateway Overview
Note: Echelon’s LNS based VNI interface (LonMakerTM) only works in Normal mode. In
order for a GadgetGateway to communicate directly over an IP channel to VNI interface
requires that the GadgetGateway be in Normal mode.
2.1.3 Uses for the GadgetGateway
The interfaces described here provide the management necessary for the ANSI/EIA 852 to
tunnel ANSI/EIA 709.1 packets successfully over IP. This ability provides wide area net-
work (WAN) support to ANSI/EIA 709.1 networks.
Furthermore, since the IP networks can support much higher traffic capacity, GadgetGate-
ways can also be used to aggregate ANSI/EIA 709.1 traffic in traffic volumes higher than
in normal ANSI/EIA 709.1 networks. The ability to aggregate larger ANSI/EIA 709.1
traffic volumes allows GadgetGateway and other 709.1 to IP gateways to be used as net-
work backbones for 709.1 networks.
Finally, 709.1 to IP gateways may be connected to specialized IP applications instead of to
other gateways. Connecting an IP application to a GadgetGateway provides these special-
ized applications with roaming capabilities which would be difficult if these applications
were required to be directly connected to the 709.1 network (e.g., GadgetAnalyzer, Lon-
Maker-3, etc.). An example of how several GadgetGateway routers can be interconnected
to support an IP backbone for several LON networks is show in Figure 2.5.
The GadgetGateway router uses one of two forms of IP addressing. Uni-cast and Multi-
cast. The multi-cast currently only works when in manual mode. The advantage of multi-
FIGURE 2.5 GadgetGateway routers for IP backbone of LON Network.

2-7
GadgetGateway Overview 2.2System Requirements
cast is that for networks with multiple Gateways especially in flood mode, multi-cast may
be more efficient. The disadvantage of multi-cast is that some internet routers do not sup-
port it. The following figures illustrate the differences between multi-cast and uni-cast.
2.2 System Requirements
To use the GadgetGateway, you will need any one of the following systems to communi-
cate with the Gateway:
•An additional GadgetGateway,
•An Echelon i.LONTM,
•A Coactive Router-LL, or
•Any 852-compliant node (this can be a computer running LonMakerTM or other
LNS VNI based tool).
Note: The GadgetGateway and Router-LL can interoperate in either Manual mode or with
the Router-LL configuration server.
FIGURE 2.6 Uni-cast communications on IP backbone.

2.3 Needed Hardware
2-8
GadgetGateway Overview
To configure the GadgetGateway, you will need:
•A computer with a serial port and a serial communications program (i.e., Windows
HyperTerminal);
•Optionally, once the GadgetGateway is on the IP network, a Web browser can be
used for most of the configuration (i.e., Netscape or Internet Explorer).
2.3 Needed Hardware
The Adept Systems GadgetGateway needs the following hardware.
•Serial Interface Cable
•5-Volt Power Supply
•ANSI/EIA 709.1 Interface Connector
Up to date documentation and firmware is available on Adept's web site (http://www.gad-
gettek.com/support.psp).
FIGURE 2.7 Multi-cast communications on IP backbone.

2-9
GadgetGateway Overview 2.4Connectors and Indicators
2.4 Connectors and Indicators
1. Serial/Counsel Setup Port: Interface to the Serial Setup Menus.
2. Ethernet/IP connector: Used to connect the Gateway to an IP network.
3. Ethernet Link Indicator LED: The indicator turns green when the Gateway has a valid
physical connection to the IP network and goes off when there is no connection.
4. Service Pin 1: Service Pin used for installation of the GadgetGateway router.
5. Service Pin 1 LED indicator: The indicator flashes orange when Service Pin 1 is
pressed.
6. Service Pin 2 LED indicator: The indicator flashes orange when Service Pin 2 is
pressed.
7. Service Pin 2: Alternate service Pin used for installation of the GadgetGateway router
when not in Twin Mode. When in Twin mode, service pin used for installing the monitor-
ing application.
8. Power Supply Input: Used to attach the power supply to the Gateway.
9: Power Indicator: The indicator turns red when power is being provided to the Gateway.
10. Orange LED: Reserved for future use.
11. Green LED: Reserved for future use.
12. Network Traffic Indicator: The indicator flashes green when network traffic is detected
on the LON side network.
13. ANSI/EIA 709.1 Interface: Used to connect the Gateway to the LonWorks network.
2.5 Redundant Twin Mode
The Twin Redundancy mode enables two GadgetGateway routers to operate as a redun-
dant pair for high availability applications. This enhanced capability increases reliability
and eliminates some single mode failure sources.

2.5 Redundant Twin Mode
2-10
GadgetGateway Overview
Although 709.1 and some network management tools allow for a pair of conventional
709.1 routers to be identically configured and connected between the same two channels,
this configuration induces a doubling of the traffic between those two channels. The built-
in duplicate detection mechanism in 709.1 discards the duplicate packets at each receiving
node. However, the extra traffic (double) could tax network bandwidth and create other
problems.
In Twin Redundant Mode both routers are identically configured connected between the
same two channels as per the case described above but unlike the case above only one of
the two routers is forwarding packets. This feature achieves the increased system reliabil-
ity of having a redundant backup router without the drawbacks of doubled traffic. The
Twin Mode routers monitor each others health and operational status and dynamically
activate forwarding as needed should one of the other fail. Failures are detected, diag-
nosed, and reported so that repairs can be made to maintain continuous availability.
Should there be a fault in either interface then both routers will go active and forward traf-
fic until the fault has been healed.
In addition, the router configuration is periodically automatically synchronized between
the two routers to reduce fail-over time and increase the fidelity between the backup and
primary router operation. Also supported is manual synchronization which makes it more
convenient to field replace one of the redundant pair and replicate its configuration. A high