Page 1
Metasys Ethernet Router
JC-MER-CXB
User Manual
#TD060100-0MA
Version 1.1
Page 2
Trademarks
Contemporary Controls, ARC Control, ARC DETECT and
EXTEND-A-BUS are trademarks or registered trademarks of
Contemporary Control Systems, Inc. ARCNET is a registered
trademark of Datapoint Corporation. Other product names may be
trademarks or registered trademarks of their respective companies.
Copyright
© Copyright 1998-2006 by Contemporary Control Systems, Inc.
All rights reserved. Metasys
®
is a registered trademark of Johnson
Controls, Inc. © 2007 Johnson Controls, Inc. No part of this
publication may be reproduced, transmitted, transcribed, stored in
a retrieval system, or translated into any language or computer
language, in any form or by any means, electronic, mechanical,
magnetic, optical, chemical, manual, or otherwise, without the prior
written permission of:
Contemporary Control Systems, Inc. Contemporary Controls Ltd
2431 Curtiss Street Sovereign Court Two
Downers Grove, Illinois 60515 USA Univ. of Warwick Science Park
Tel: +1-630-963-7070 Sir William Lyons Road
Fax: +1-630-963-0109 Coventry CV4 7EZ UK
E-mail: info@ccontrols.com +44 (0)24 7641 3786
WWW: http://www.ccontrols.com: +44 (0)24 7641 3923
Fax:
Tel:
E-mail: info@ccontrols.co.uk
Disclaimer
Contemporary Control Systems, Inc. reserves the right to make
changes in the specifications of the product described within this
manual at any time without notice and without obligation of
Contemporary Control Systems, Inc. to notify any person of such
revision or change.
TD060100-0MA
2
Page 3
Contents
Chapter 1 Introduction......................................................... 6
Description ................................................................... 6
Specifications ............................................................... 7
Connector Information ................................................. 8
Mechanical Drawing .................................................... 9
Ordering Information .................................................. 9
Chapter 2 Operation .......................................................... 10
Description ................................................................. 10
Theory of Operation.................................................... 11
Setup and Addressing........................................... 11
Protocols ............................................................... 11
Subnet Communication Upon
Network Failure.................................................... 12
Hardware Requirements ............................................. 12
Design Considerations ................................................ 13
NCM Compatibility .............................................. 13
Quantity of Routers Needed ................................. 13
Physical Considerations ....................................... 13
Design Summary .................................................. 13
Design Restrictions .............................................. 15
Network Management Staff Involvement ............ 16
Metasys May Be Affected..................................... 16
Chapter 3 Installation and Commissioning ........................ 17
Hardware Installation ................................................. 17
Mounting ............................................................... 17
Powering ............................................................... 18
Indicator Lights and Booting ................................ 20
Bash Prompt & JC-MER-CXB Commands .......... 20
Configuring the JC-MER-CXB .................................. 21
Connecting Field Cables............................................. 22
Reconfiguring the System .......................................... 24
Adding a New NCM or PMI/OWS to
an Existing Subnet ............................................... 24
Moving an Existing NCM or
PCI/OWS to a Different Subnet ........................... 25
Adding a New Metasys ARCNET Subnet ................. 26
Changing the Ethernet Network ................................. 28
Changing the Layout of the
Metasys Network .......... 28
TD060100-0MA
3
Page 4
Chapter 4 Troubleshooting ................................................ 30
Booting Up the Router ............................................... 30
Debugging Ethernet Failures ..................................... 30
Ping Command .............................................. 32
Ipstat Command .............................................. 33
Testnet Command .......................................... 33
General Problem Prevention...................................... 33
Debugging ARCNET Failures .................................. 34
Debugging Router Failures........................................ 34
JC-MER-CXB Does Not Run When Booted ...... 34
Status Screen Indicates Failure Number 113 ...... 34
Status Screen Indicates Failure Number 101 ...... 34
Status Screen Indicates Invalid Messages........... 34
Metasys Devices Do Not Respond....................... 35
All the Devices on One ARCNET
Segment Do Not Respond ................................... 35
Multiple ARCNET Segments
Do Not Respond .................................................. 35
JC-MER-CXB Does Not
Respond to Ping Requests ................................... 35
N1 Communications Are
Occasionally Unreliable ...................................... 36
Data Cannot Be Viewed on OWS
Across Network ................................................... 36
...
...
...
...
Chapter 5 Service ............................................................... 37
W arranty..................................................................... 37
Technical Support ...................................................... 38
Warranty Repair ......................................................... 38
Non-Warranty Repair ................................................ 38
Returning Products for Repair................................... 39
TD060100-0MA
4
Page 5
Appendices
Appendix A: Metasys Router Planning Forms............. 40
Appendix B: Common Commands and
Software Switches .................................................. 42
JC-MER-CXB Program (router) ............................ 42
Ethernet Communications Tests (testnet) .............. 42
Determining the MAC Address (getmac) ............... 42
Configuration Download (download) .................... 43
Software Switches ................................................... 43
Other Linux Commands .......................................... 45
FTP Files from JC-MER-CXB ................................ 45
Appendix C: Statistics Screen Information .................... 46
Appendix D: Setting Up HyperTerminal ....................... 47
Appendix E: Field Connections ...................................... 48
Appendix F: UDP Port Address Assignments ............... 49
Appendix G: Linux Trademark Information .................. 50
Figures
2: 3-Pin Connector .......................................................... 8
3: DB9 Connector ........................................................... 8
1: RJ-45 Connector ......................................................... 8
4: Null-Modem Cable Wiring ......................................... 8
5: JC-MER-CXB Dimensions ......................................... 9
6: Sample Layout of Metasys Ethernet Router ............. 14
7: Using the Panel-Mounting Brackets ......................... 17
8: DC Powered .............................................................. 18
9: Redundant DC Power ............................................... 18
10: AC Powered ............................................................
11: AC Power with Grounded Secondary ..................... 19
12: AC Power with Battery Backup ..............................
13: Bash Prompt for the JC-MER-CXB ........................ 20
14: Configuration Screen .............................................. 21
15: Statistics Screen available at COM2 ....................... 31
16: Example of Testnet Results Screen .........................
17: Example of Statistics Screen ...................................
19
19
42
46
Tables
1: Common Ethernet Errors ........................................... 32
TD060100-0MA
5
Page 6
1 Introduction
Description
The Metasys Ethernet Router (JC-MER-CXB) provides either router
or gateway connectivity between ARCNET and Ethernet networks.
Sometimes in router/gateway applications, a desktop PMI/OWS
compatible computer is dedicated to the task of executing the application program from either a hard disk or floppy disk. On the PMI/OWS
motherboard, two network interface modules are used to connect to
the two networks of interest. With the JC-MER-CXB, this same
functionality can be provided in a compact and reliable configuration.
On the front panel of the JC-MER-CXB is a BNC connector for the
ARCNET and an RJ-45 connector for the Ethernet.
Resident in the JC-MER-CXB is an embedded computer with a solidstate flash disk capable of executing an application program. This usersupplied application program routes packets between ARCNET and
Ethernet networks that utilize the same network layer or serve as a
gateway between different protocols used by the ARCNET and
Ethernet networks. For example, a popular transport layer for
Ethernet is TCP/IP. To route between ARCNET and Ethernet at the
network layer (IP), ARCNET would need to be operating a TCP/IP
stack as well. For all other situations where different higher-level
protocols are involved, a gateway program would be needed to effect
connectivity between ARCNET and Ethernet. Either situation can
be addressed by the JC-MER-CXB.
To provide ARCNET-to-Ethernet connectivity within a Metasys
system, the JC-MER-CXB was created by installing the necessary
application program onto the flash disk. This product replaces the
JC-MH-16, JC-EP-RG and JC-EP-CS version or model of the
Ethernet router. To configure the JC-MER-CXB, a laptop computer
running a terminal emulation program, like HyperTerminal, is
attached to one of the COM ports using a null-modem cable. Once
configured, the program runs continually.
TD060100-0MA
6
Page 7
SPECIFICATIONS
DC AC
Electrical
Input voltage: 10–36 volts 8–24 volts
Input power: 8 W 8 VA
Input frequency: N/A 47–63 Hz
Environmental
Operating temperature: 0°C to +60°C
Storage temperature: –40°C to +85°C
Humidity: 10% to 95%, non-condensing
Ethernet Data Rates
10/100 Mbps
ARCNET Data Rate
2.5 Mbps
Shipping Weight
1 lb. (.45 kg)
Compatibility
ANSI/ATA 878.1 and IEEE 802.3
Regulatory Compliance
CE Mark
CFR 47, Part 15 Class A
UL 508 Listed Device
cUL 22.222 #14
(intended for use with Class 2 circuits)
LED Indicators
Status —
multicolor (see page 20 for details)
ARCNET Ethernet
RX —
ACT —
green LINK/ACT — green/yellow
yellow DUP — green/yellow
TD060100-0MA
7
Page 8
Connector Information
Ethernet Socket Pin Assignments (RJ-45 Connector)
1 TD+
2 TD–
3 RD+
6 RD–
(all other pins are unused)
Figure 1 — RJ-45 Connector
ARCNET Socket Pin Assignments (RJ-45 connector)
4 Line – (Phase B)
5 Line +
(all other pins are unused)
ARCNET Socket Pin Assignments (3-pin screw terminal connector)
(Phase A)
485 485X
SH Shield Shield
B Line – Line
A Line + Line
Figure 2 — 3-pin Connector
COM1 & COM2 Pin Assignments (DB9 connectors)
PIN Signal Function
2 RXD Receive Data
3 TXD Transmit Data
5 GND Ground
(all other pins are unused)
Figure 3 — DB9 Pins
COM1 & COM2 EIA-232 Communication Parameters (DB9 connectors)
Baud Rate 57,600 bps
Data Bits
Parity
Stop Bit
8
No Parity
1
Figure 4 — Null-Modem Cable Wiring
TD060100-0MA
8
Page 9
Mechanical
Figure 5 — JC-MER-CXB Dimensions
Metasys Ethernet Router Ordering Information
JC-MER-CXB Coaxial Cable Dipulse Transceiver
ELECTROMAGNETIC COMPATIBILITY
JC-MER-CXB units comply with Class A radiated and conducted
emissions as defined by CFR 47, Part 15 and by EN55022. This
equipment is intended for use in non-residential areas.
Warning
This is a Class A product as defined in EN55022. In a domestic
environment this product may cause radio interference — in which
case the user may be required to take adequate measures.
TD060100-0MA
9
Page 10
2 Operation
Description
The JC-MER-CXB integrates Metasys N1 LAN segments with an
Ethernet network that uses the TCP/IP (Transmission Control
Protocol/Internet Protocol) suite. The router provides the physical
connection between a Metasys ARCNET segment and the Ethernet
network. It takes advantage of a customer’s existing Ethernet
network, while maintaining the dedicated Facility Management
System (FMS) communications necessary for complex, time-critical,
local control strategies.
With the JC-MER-CXB, Metasys controllers communicate transparently
over Ethernet, using standard components and maintaining complete
compatibility with existing network equipment. From an operator’s
view, this coupling of the N1 LAN to Ethernet creates a single large
network. No special commands are necessary to switch between
networks; data automatically transmits between networks without
operator knowledge or intervention.
The JC-MER-CXB communicates over an Ethernet network using the
TCP/IP protocol. Two networked JC-MER-CXBs pass ARCNET
data between themselves using the User Datagram Protocol (UDP)
service provided by TCP/IP. On the Ethernet network, the router is
seen as a workstation passing messages to another workstation. If a
power failure occurs, the router automatically restarts communications
once power is restored.
The JC-MER-CXB is derived from an earlier version of this device that
was an expansion module that occupied two slots of a Contemporary
Controls MOD HUB ARCNET Modular Active Hub. The new device
can be powered from an available low-voltage source or with an
optional wall-mount transformer. The ARCNET and the Ethernet
connections are made through ports on the front panel of the device.
Unlike a PMI/OWS, the JC-MER-CXB has no monitor or keyboard.
Instead, the monitor/keyboard functionality is done by an external
laptop or desktop computer running a terminal emulation program (like
HyperTerminal), while connected to COM ports on the JC-MER-CXB.
TD060100-0MA
10
Page 11
The JC-MER-CXB program is accessed via COM2. The embedded
operating system is accessed via COM1. If a terminal emulation
program is attached to COM2, real-time routing statistics can be
observed. But once the router is started, no such cable connection is
required for continued operation.
Theory of Operation
Setup and Addressing
The method of linking the two networks is to separate the N1 LAN
into a number of ARCNET subnets. (In this document, the terms
“subnet” and “ARCNET segment” are the same.) Each ARCNET
subnet then connects to the customer’s Ethernet network via a single
JC-MER-CXB.
The router uses the N1 network addressing scheme to route messages
among the various ARCNET segments. Dividing Metasys into
multiple subnets has no affect on existing Ethernet communications,
and again, remains transparent to the operator.
To the operator, the router is simple to use and maintain. Once it is
configured to the customer’s network, the router works on its own,
uninterrupted. Branch office personnel configure the unit (via
HyperTerminal) by accessing a single screen. Once set, the data is
saved to a flash disk. Upon power up, the program and configuration
data is executed without any intervention. There are no moving
storage devices on the unit.
Protocols
The JC-MER-CXB uses the UDP/IP communications protocol to
transmit messages across the Ethernet network. This is important
because it allows the router to easily integrate into existing customer
networks that comprise multiple Internet (TCP/IP protocol suite)
networks.
TD060100-0MA
11
Page 12
Even though the JC-MER-CXB looks like a data router to the Metasys
Network, most communications experts would call it a network
gateway. To the Ethernet network, the router looks like a normal
IBM
PMI/OWS workstation. Unlike typical network gateways and
routers, the JC-MER-CXB does not process:
• routing protocols used by standard network routers, except for
UDP/IP communications from other JC-MER-CXB units
• messages not generated by Metasys
The JC-MER-CXB responds to TCP/IP “ping” commands, allowing
you to verify that the router is operational and properly connected to
the Ethernet network. However, the ping could fail if a firewall
blocks it from reaching the intended target.
Subnet Communication Upon Network Failure
If the Ethernet network goes down, or the router disconnects or fails,
each Metasys subnet continues to function on a standalone basis. A
JC-MER-CXB: failure looks like a general failure of the Metasys N1
network. Devices on a subnet are still able to communicate with other
devices on that subnet, but devices on a different subnet are offline.
Hardware Requirements
The following are other hardware requirements of the JC-MER-CXB:
• Metasys Network with NCM200 or NCM300 or NCM4500 at
any revision; or, NCM101/NCM401at Revision K or later
• 10BASE-T/100BASE-TX Ethernet connection
• ARCNET connection (i.e., Metasys N1 LAN)
• 10–36 VDC or 8–24 VAC power at each JC-MER-CXB location
TD060100-0MA
12
Page 13
Design Considerations
NCM Compatibility
The JC-MER-CXB is compatible with all versions of the NCM200,
NCM300 and NCM4500. If NCM101s/401s are used, they must be
Revision K or later. EPROM chips in older NCM101s/401s can be
upgraded for compatibility with the JC-MER-CXB. For information
about upgrading, contact Field Support Services. (The NCM102 does
not contain an N1 connection.)
Quantity of Routers Needed
The quantity of JC-MER-CXBs you need is identical to the number of
ARCNET segments connected through the Ethernet system. For
example, two units are required to connect two ARCNET segments
over one Ethernet segment (see Figure 6). A router is placed at each
location where the Ethernet segment meets the ARCNET segment.
Up to 50 JC-MER-CXB units can be used on each Metasys Network
(i.e., all ARCNET segments).
Physical Considerations
The router can be installed in a variety of ways, depending on the job
site. When selecting a location, consider the following:
1. The location must have access to the customer’s Ethernet
network, the ARCNET segment being serviced, and power.
2. A JC-MER-CXB can be panel-mounted or DIN-rail mounted.
3. Need power: either 10–36 VDC or 8–24 VAC.
Design Summary
Use these steps as a guideline when designing a JC-MER-CXB
Network, referring to Figure 6 for an example:
1. Lay out the network as you would a normal Metasys N1
Network. Determine the number and location of NCMs and
Operator Workstations that will service the facility.
2. Determine which portions of the network will use ARCNET and
which will use Ethernet. The network layout must consist of
multiple ARCNET segments connected by the customer’s
Ethernet network.
The Ethernet network must be a single Local Area Network
(LAN) that can interconnect all of the ARCNET segments.
TD060100-0MA
13
Page 14
Note: If the Ethernet network consists of multiple Ethernet segments,
the segments must be connected using LAN Routers that
support the TCP/IP protocol suite. Intermediate networks
that use other communications technology (FDDI, Token
Ring) are acceptable if the intermediate networks are high
speed. Low speed networks (e.g., 9600-baud serial lines) will
cause unacceptable delays to Metasys N1 communications.
The resulting network layout will be similar to the sample
network shown in Figure 6. Each ARCNET segment will have
one JC-MER-CXB attached to it. The ARCNET node address
on each JC-MER-CXB has been preassigned 255.
3. Assign a subnet address to each ARCNET segment. We
recommend using the subnet address “1” for the primary
ARCNET segment, or the segment that has the most devices
attached to it. Assign a unique node address to each NCM or
Operator Workstation attached to the N1 network. Node
addresses must be unique even if the NCMs are attached to
different subnets. Record the subnet and node address
information on the JC-MER-CXB Planning Form A.
(See Appendix A: Metasys Ethernet Router Planning Forms.)
Figure 6 — Sample Layout of the JC-MER-CXB
TD060100-0MA
14
Page 15
4. Have the customer’s network communications staff assign IP
addresses and provide IP routing information for each
JC-MER-CXB. Record this information on the JC-MER-CXB
Planning Form B. (See Appendix A: Metasys Ethernet Router
Planning Forms.) Append the ARCNET Subnet addresses from
Form A to Form B.
5. Using the JC-MER-CXB Planning Form B, configure each
router by accessing its configuration screen. (See Chapter 3.)
6. Use the assigned subnet and node addresses to address each of
the Metasys NCMs and PMI/OWSs. When creating the DDL
files for the system, use the subnet and node addresses in the
NETWORK and GLOBAL DDL files.
Note: Since you are converting multiple standalone networks into
one large network, verify that no duplicate system names
exist. If duplicates exist, you must change them to unique
system names in both DDL and GPL.
If you are converting an existing system to use JC-MER-CXB units,
you’ll need to update and recompile the DDL files when the routers
are installed. Be sure to recompile all of the DDL files, including
all of the NC files. Failure to recompile all of the DDL files and
download ALL devices could result in application failures for those
NCMs located on new ARCNET segments.
Note: Global and Model DDL file must be the same at all of the
OWS (Operator Work Stations).
Design Restrictions
1. The system should not use any realtime control strategies that
require data transfers across the Ethernet network. Because the
Ethernet network may experience delays and down time caused
by non-Metasys equipment, the network is subject to variations
in performance.
Realtime control strategies can be used between NCMs located
on a common ARCNET segment.
2. Use caution when defining critical alarm reports that must cross
the Ethernet. Avoid alarms related to life safety because they
may not arrive at the Operator Workstation or printer if the
customer’s Ethernet network is down.
TD060100-0MA
15
Page 16
3. Use of a customer’s Wide Area Network (WAN) is not
recommended. The delays associated with Wide Area Networks
may be unacceptable for operation of the Metasys Network.
4. If the system contains a JC/85 Gateway, the Gateway points should
not be mapped to objects that reside in NCMs located on different
subnets.
The JC/85 Gateway obtains the status for all objects that are
defined in the Gateway at frequent intervals (every 1-5 seconds).
This creates a large amount of message traffic on the N1
network. If this message traffic is routed across the Ethernet, it
will (a) add excessive loading to the customer’s Ethernet
network, (b) slow down the operation of the JC/85 Gateway, and
(c) result in sporadic offline reports for objects located in the
remote NCMs.
5. For the same reasons, if the system contains a Network Port, the
Network Port cannot map its analog data points to objects that
reside in NCMs located on different subnets.
6. As with all Metasys networks, each NCM and PCI/OWS in the
network must use a common time zone, even if the devices
physically reside in different time zones.
Network Management Staff Involvement
When installing the JC-MER-CXB, work closely with the network
management staff at the job site. They will know the intricacies of
the Ethernet network to which you will be connecting. Get them
involved as much as possible. They should be able to provide you
with the following:
• Ethernet connections
• assignment of IP addresses
• debugging expertise during installation and commissioning of
the JC-MER-CXB
Metasys May Be Affected
Realize that the Ethernet network will affect the Metasys N1
Network. It can do so in these ways:
• Ethernet traffic may slow down the performance of the Metasys
N1 Network.
TD060100-0MA
16
Page 17
3 Installation and Commissioning
Hardware Installation
Mounting
The JC-MER-CXB is designed for mounting in an industrial enclosure
or wiring closet using either set of provided mounting hardware listed
below. The unit can also rest unsecured on a flat surface, if desired.
TS-35 DIN Rail Mounting Panel Mounting
DIN rail clip
DIN rail clip support bracket
4-40 screws, pan-head (2)
For quick snap-mounting to 35 mm DIN rail, a reinforced DIN rail clip
is pre-attached to the back of the enclosure with two #4-40 pan-head
screws. If the clip is removed, the unit can be panel-mounted by
extending the top and bottom brackets which are shipped in retracted
position. The extended brackets can then anchor the unit to a wall or
other flat vertical surface with two #8 pan-head screws (
The left illustration of Figure 7 shows a rear view of the unit with the
brackets in retracted position. The right illustration of
the brackets extended and secured to the unit enclosure with the same
screws that were used in the retracted position.
Panel mounting brackets
4-40 screws, flat-head (4)
#8 screws, pan-head (2)
also provided).
Figure 7 shows
Figure 7 — Using the Panel-Mounting Brackets
TD060100-0MA
17
Page 18
Powering the JC-MER-CXB
To operate, the JC-MER-CXB requires low-voltage AC or DC power
provided to its four-pin removable keyed connector. Consult the
specifications for power requirements. There are several means for
providing power.
DC Powered
Make connections as shown in the diagram. The
converter that accepts a wide range of voltage (10–30 VDC) which it
converts for internal use. The “0Vdc” connection is connected to
chassis within the unit. Input connections are reverse-voltage protected.
Figure 8 — DC Powered
Redundant DC Powered
Redundant diode-isolated DC power inputs are provided on the
when a concern exists that the unit remain operational in the event of
a primary power failure. Make connections as shown in the diagram.
Each power supply must be capable of powering the
assume that input currents from the two supplies will be balanced.
unit uses a DC-DC
unit
unit. Do not
Figure 9 — Redundant DC Power
TD060100-0MA
8
1
Page 19
AC Powered
If only AC power is available, the
the secondary of a low-voltage transformer whose primary is
connected to the AC mains. The secondary must be 8–24 VAC and
ungrounded. When using a grounded secondary transformer, refer to
Figure 11. For convenience, two auxiliary power supplies are
available from Contemporary Controls: the AI-XFMR is for 120 VAC
primary power and the AI-XFMR-E uses 230 VAC.
JC-MER-CXB can be powered by
Figure 10 — AC Powered
Figure 11 — AC Power with Grounded Secondary
AC Powered with Battery Backup
The JC-MER-CXB can also be powered from both an AC and DC source.
Usually the DC source is from a battery connected as the DC powered
option. Refer to Figure
not charge the battery, so separate provisions are required for charging.
If the AC source fails, the unit will operate from the battery.
12 for details. In this application the unit does
Figure 12 — AC Power with Battery Backup
TD060100-0MA
19
Page 20
Indicator Lights and Booting
STATUS: At power on, this LED briefly glows red as a test. Then
while Linux boots (about 16 seconds), it flashes green. It then glows
solid to indicate Linux is operational — although another 16 seconds
must pass before ARCNET is functional. If this LED glows red during
normal operation, a power supply problem is indicated; if the external
power source is within specification, the
JC-MER-CXB needs service.
ARCNET: If the unit is connected to a working ARCNET network,
the
“RX” LED glows green whenever the unit receives data — otherwise
the “RX” LED will remain unlit. If the
etwork, the “RX” LED will glow by default. The “ACT” LED flashes
n
yellow whenever the
JC-MER-CXB is engaged in ARCNET activity.
unit is disconnected from the
Ethernet: After 2–3 seconds into the boot process (and thereafter), the
“LINK/ACT” LED will glow if a valid link exists to an working Ethernet
device. It indicates speed by color
10 Mbps. It flashes
to indicate activity. The “DUP” LED glows green to
indicate full-duplex operation and y
Bash Prompt and JC-MER-CXB Commands
: green for 100 Mbps and yellow for
ellow for half-duplex.
The JC-MER-CXB uses the Linux operating system. When the Linux
command line is displayed on screen, a special "bash" prompt appears.
Because it is derived from the Bourne shell, the prompt is known by
the pun: Bourne Again Shell, or bash. It is the standard command-line
interface on most Linux machines. All command-line entries for the
JC-MER-CXB must use lower case letters! The bash prompt for the
JC-MER-CXB is shown below.
Figure 13 — Bash Prompt for the JC-MER-CXB
TD060100-0MA
20
Page 21
Configuring the JC-MER-CXB
The JC-MER-CXB consists of a computer running Linux. It has an
Ethernet port, ARCNET port and a flash disk that emulates a disk
drive. The router program is preloaded at the factory but must be
configured. For this, Planning Forms are provided in Appendix A.
You can monitor JC-MER-CXB statistics (if monitoring has been
enabled) by connecting a null-modem cable from COM2 on the front
of the unit to a COM port on a laptop or desktop computer running a
terminal- emulation program like HyperTerminal. You configure the
parameters by connecting to COM1. Remember: monitor on COM2
and configure on COM1. See Appendix D for using HyperTerminal.
Once the terminal emulator is ready, connect it to COM2 (to monitor
the boot process) then apply power to the JC-MER-CXB. After the
Statistics Screen (see Figure 15 on page 31) appears and the "Idle"
fields begin to count, move the cable to COM1, type config and press
ENTER to access the configuration screen. The bottom of the screen
displays information on using certain keys to perform editing tasks.
The left side of the screen displays the JC-MER-CXB IP address,
Subnet Mask and Existing LAN Router IP address (network gateway,
if one exists). On the right side are switches (e.g., "/S") and all
ARCNET subnet addresses and associated JC-MER-CXB IP addresses.
All of this information is stored to non-volatile memory and, except
switch settings, must be identical on all JC-MER-CXBs.
Figure 14 — Configuration Screen
TD060100-0MA
21
Page 22
There is a provision for setting the Extended Timeout value of the
ARCNET subnet. The default is 0 (meaning normal timeouts) and in
the majority of applications, it should be left at 0. Extended timeouts
are only required on large fiber optic installations where the ARCNET
network diameter exceeds 5 km.
Using the JC-MER-CXB Planning Form B in Appendix A, add to
your right-side screen data with the ARCNET Subnet Address
(Column 1) and IP Address (Column 2) of each Metasys Ethernet
device to be connected. Enter these two addresses on the same line
above the “000” terminating flag at the end of the list. The # symbol
means that the text following the # is a remark. The following is an
example for three Metasys Ethernet devices:
1 192.168.20.91
2 192.168.20.23
3 192.168.20.56
Save the configuration screen data by simultaneously pressing the Ctrl
and "K" keys, then release both keys and press the "S" key to save the
data and automatically reboot the JC-MER-CXB with the new settings.
The RX LED on the ARCNET port should glow and the ACT LED
should flash as the ARCNET port searches for other ARCNET nodes.
Note: When entering IP addresses, care should be taken to avoid a
trailing space which, although invisible onscreen, will
nevertheless cause the address to be incorrect.
Verify no configuration errors exist by typing cat router.err.
Connecting Field Cables
The JC-MER-CXB connects to N1 ARCNET via coaxial as described
in Appendix E. The unit connects to N1 Ethernet via an RJ-45 jack.
1. Connect the ARCNET cable from the Metasys N1 ARCNET
subnet to the port on the JC-MER-CXB. If there is activity on the
subnet, then the ACT LED on the unit should glow.
2. Connect the cable from the Ethernet network to the unit's
Ethernet port. If the cabling is correct and there is a working
Ethernet device on the other end of the cable, the green Link
LED should glow. If so, proceed to the next step.
TD060100-0MA
22
Page 23
3.
With HyperTerminal (or similar application) active and the
JC-MER-CXB booted, attach the null-modem cable to COM2 then
type “Q” to terminate the application and exit to Linux.
4.
At this point, the null-modem cable must be moved from COM2
back to COM1 to access Linux. Once the cable is attached to
COM1, the bash prompt should be visible after the ENTER key
is pressed. You can clear the screen by typing clear (lower case)
and pressing ENTER.
5. Verify that the router is communicating with Metasys by using
testnet to read the configuration data and then ping each listed
device. You will notice the ACT LED near the Ethernet port
will flash, indicating a proper transmission. Run testnet by
typing the following at the bash prompt:
testnet
This will report the communication status for each listed N1
device which could be an NCM, OWS, NIE or JC-MER-CXB.
Example:
Status of the Metasys Ethernet Devices:
Device 192.168.20.91 is responding
Device 192.168.23.23 is responding
Device 192.168.20.56 is responding
Copy the configuration file to every JC-MER-CXB in the network
using the download utility or enter the data manually into each router
(for information on using the download utility see page 43). The
configuration file content must be identical for all routers on the job.
Once the download has been accomplished, execute the router
program by typing router then press ENTER.
Note: The router used for the download will need to be rebooted by
typing reboot or by recycling power the router.
To view router statistics, the null-modem cable must be reattached to
the COM2 port. If the resulting display is garbled, refresh the screen
by pressing the "R" key. When connected to COM2, the "R" key will
"refresh" the screen and the "C" key will "clear" the statistics counters.
If the router configuration was not set up properly, the router will
stop running and continuously display an error message with the
instruction to press “Q” to quit. To determine the problem, refer to
Chapter 4: Troubleshooting.
TD060100-0MA
23
Page 24
Reconfiguring the System
Over time, a Metasys Network that uses JC-MER-CXB devices may
have to be reconfigured to account for additions and changes to the
system. The reconfigurations that a system may undergo can be
classified as:
• adding a new NCM or PMI/OWS
• moving an NCM or PMI/OWS
• adding a new Metasys ARCNET subnet
• changing the Ethernet network
• changing the layout of the N1 network
This section describes the steps necessary to perform each of these
different types of reconfigurations.
Adding a New NCM or PMI/OWS to an Existing Subnet
Adding a new NCM or PMI/OWS to Metasys does not require any
changes to the JC-MER-CXB hardware or software. An NCM101/401
that is added to a JC-MER-CXB system must be Revision K or later.
All NCM200s and NCM300s are compatible with the JC-MER-CXB.
To add a new NCM or PMI/OWS to an existing subnet:
1. Determine the correct subnet and node address for the new NCM
PMI/OWS. The subnet address must match the subnet address
for the ARCNET segment to which the NCM or PMI/OWS
connects. The node address must be unique. You cannot duplicate
any node address, even if the two devices reside on different subnets.
2. If the device is an NCM, determine the correct subnet and node
address for its archive device.
3. Set the device subnet and node address as you normally do.
• For a PCI/OWS, set the node address using the switches on the
ARCNET card (note: PS/2 system cards do not have
switches, so PS/2 users can ignore this) and specify the
subnet and node addresses in the DDL network
configuration file.
• For an NCM, use WNCSETUP to set the subnet and node
addresses. When using WNCSETUP, don’t forget to specify
the correct subnet and node address for the archive device.
TD060100-0MA
24
Page 25
4. Add the device to the system database, either by updating the
DDL global file or by using a device definition window.
5. Physically attach the new NCM or PCI/OWS to the ARCNET
segment that you have selected.
6. You do not need to make any changes to the JC-MER-CXB. The
router automatically routes messages correctly using subnet
address for the new device.
Moving an Existing NCM or PCI/OWS or NIE to a Different
ARCNET Subnet
You may want to change the ARCNET segment to which an NCM or
PCI/OWS is attached. This may be required because an NCM or PCI/
OWS is moved to a new location or because the ARCNET cable layout
has been changed. Moving an NCM or PCI/OWS to a different subnet
does not require any changes to the JC-MER-CXB software. To move
a device to a different subnet, follow these steps:
1. Determine the new subnet and node address for the NCM or the
PCI/OWS. You will probably use the same node address for the
device, but if you decide to change the node address, it must be
unique. You cannot duplicate any node addresses, even if the two
devices reside on different subnets. The device’s subnet address
will have to change to match the subnet address for the
ARCNET segment to which the device will be moved.
2. If the device is an NCM, you may want to change its archive
device. If you decide to change the archive device for the NCM,
determine the subnet and node address for the new archive device.
3. Change the subnet and node address for the device as you
normally do.
• For a PCI/OWS, set the node address using the switches on
the ARCNET card (note: PS/2 system cards do not have
switches, so PS/2 users can ignore this) and specify the
subnet and node addresses in the DDL network
configuration file.
• For an NCM, use NCSETUP to set the subnet and node
addresses. Once the subnet address for an NCM is changed,
you will not be able to communicate with the NCM over the
N1 network until it is physically attached to its new subnet.
When using NCSETUP, don’t forget to specify the correct
subnet and node address for the archive device.
TD060100-0MA
25
Page 26
4. Change the subnet and node addresses for the device in the
Metasys database by updating the DDL Global file, compiling it
and downloading it to all devices.
5. Physically attach the device to its new ARCNET segment.
6. You do not need to make any changes to the JC-MER-CXB. The
router automatically routes messages correctly based on the new
subnet address for the device.
Adding a New Metasys ARCNET Subnet
When a new device cannot be attached to one of the existing ARCNET
segments, a new subnet and a new JC-MER-CXB must be added. To
add a new subnet, do the following:
1. Determine a location for the new JC-MER-CXB. It must have
access to electrical power, a connection to the customer’s Ethernet
network, and a connection to the new ARCNET segment.
2. Select a new subnet address for the new ARCNET segment.
The subnet address must be unique (not previously used for a
different ARCNET segment).
3. Obtain Internet address information for the new JC-MER-CXB
from the customer’s communications/computer support staff. The
information should include an IP address for the JC-MER-CXB,
the subnet mask that is used, and an IP address for the customer’s
existing LAN Router (if the customer’s Ethernet network uses
LAN Routers).
4. Obtain another JC-MER-CXB unit.
5. Install the new JC-MER-CXB and attach it to the Ethernet network
and to the ARCNET network. Verify that the JC-MER-CXB is
communicating by “pinging” it from another Ethernet-equipped
device. This can be done from another JC-MER-CXB that has a
terminal emulator attached or from any Ethernet device that has
TCP/IP communications software. For example, to ping a new
router with IP address 192.168.22.236, enter:
ping 192.168.22.236
The response to the PING command should indicate that the
new router is communicating.
TD060100-0MA
26
Page 27
6. Modify the information in each JC-MER-CXB using the
configuration program. Add a new line to the screen that lists
the subnet address and the IP address for the new router. For
example, if you are adding subnet number 12 with IP address
192.168.22.236, add the following line:
12 192.168.22.236
Add the new line before the line containing the three zeros (000).
After you have edited the screen, save its information using the
save command (Ctrl-K, S). Then use the download program to
copy the new address information to all of the JC-MER-CXB
devices used in the system.
To download the new information, reboot the JC-MER-CXB that
contains the new configuration and after the router has started
running, enter download at the prompt. Follow the instructions
provided and note any messages displayed. After the new
configuration has been successfully downloaded to all other
routers, reboot the originating router by typing in reboot.
Note: The IP address of the router with the new configuration
must appear in the configuration screen of every other
JC-MER-CXB in the network. A receiving router will
not accept information from a device that is not listed
in its existing configuration screen.
7. Add the new NCM or PCI/OWS to the new ARCNET segment
by following the procedures for adding an NCM or PCI/OWS to
an existing ARCNET segment, as described previously.
TD060100-0MA
27
Page 28
Changing the Ethernet Network
Occasionally, the customer’s communications/computer staff may
decide to rearrange their Ethernet network. Normally this will not
impact the operation of the JC-MER-CXB, except that it may result
in a temporary loss of communications with one or more of the
routers. Should this happen, each NCMs and PCI/OWS on those
subnets will go offline. If the customer decides to change the
configuration of their Ethernet network, you may have to change the
IP address information stored in each router. To do this, you will
have to change the configuration for each router.
If the IP address for the JC-MER-CXB was modified, you must
update the configuration screen. Change the IP address as needed.
Then use the download program to update all other routers.
Changing the Layout of the Metasys Network
In some situations you may want to reorganize the Metasys Network.
This may involve joining two existing ARCNET subnets into a
single subnet, splitting an existing subnet into two subnets, or
adding new subnets. If you are performing a major reconfiguration
of the network, follow these steps:
1. Determine the new network layout for Metasys. The new
network layout should show a number of ARCNET subnets that
are connected using JC-MER-CXB units and the customer’s
Ethernet network. Assign a unique subnet number to each
ARCNET segment.
2. Using the new network layout, determine where the JC-MER-CXB
devices will be located. For each router, determine if it is an
existing router or a new router. If you will be installing new
routers, you will have to obtain them.
3. Fill out a set of JC-MER-CXB planning forms for the new
network layout. You should have filled out a set of forms when
the routers were first installed. The JC-MER-CXB Planning
Form B will be used to configure each of the JC-MER-CXB
units. If you will be installing new routers, follow the procedures
beginning on page 13.
TD060100-0MA
28
Page 29
4. Use the JC-MER-CXB Planning Form B to generate a new
router file. The file should be a list of subnet address and IP
address pairs of the form:
nnn xxx.xxx.xxx.xxx
where “nnn” is the subnet address and “xxx.xxx.xxx.xxx” is the
IP address for the JC-MER-CXB attached to that subnet. The
last line of the router file should be a line containing “000.”
Once you have built a new router file that lists all of the subnets,
a copy must be placed in each JC-MER-CXB attached to the
system.
5. Configure the new hardware and install it as described in a
previous section, Adding a New Metasys ARCNET Subnet.
6. Use the JC-MER-CXB Planning Form B to update the TCP/IP
configuration on each of the existing JC-MER-CXB units. The
procedure for updating the TCP/IP information is described in a
previous section, Changing the Ethernet Network.
7. To update the DDL files for Metasys, use the JC-MER-CXB
Planning Form A. The only changes you should have to make
are to the Network Definition and the Global Definition DDL
files to change the subnet addresses for each NCM and each
PCI/OWS. If you add new NCMs to the system, you will most
likely update the DDL files to add the data base information for
the new NCMs when you update the subnet and node addresses
for the Metasys devices.
TD060100-0MA
29
Page 30
4 Troubleshooting
Because the JC-MER-CXB hardware consists of an embedded
computer, knowledge of Linux will help in troubleshooting the system.
Booting Up the Router
When first activated, the JC-MER-CXB computer runs through a self
test. If an error is detected, the router will stop operating then repeatedly
display an error message advising the operator to press “Q” to end the
router program and exit to Linux.
Note: Move the null-modem cable from COM2 to COM1 so that
so that Linux commands can be entered. At the bash prompt
type router or reboot.
Debugging Ethernet Failures
Software tools are provided with the product for checking Ethernet
network errors. These include the programs ping, ipstat, testnet and
a router statistics mode. The nature of the ping and ipstat programs
should be familiar to someone with previous experience with
TCP/IP software.
Prior to using the router statistics mode tools, you may need to
modify the router configuration file (router). Add the following
three switches (upper case letters only) if they are not already
present:
/A
/S
/M
When the router is running, it displays statistical information as
shown in the example of Figure 15 — providing the null-modem
cable is attached to COM2. This display shows ARCNET and
Ethernet message counters.
TD060100-0MA
30
Page 31
The statistics screen normally shows the ARCNET and network
message Idle counters rapidly incrementing. The counters for
Invalid, Retry, and Failure messages should be zero. The ARCNET
and network Normal counters and the ARCNET and Ethernet
Broadcast counters increment as messages are received.
Figure 15 − Statistics Screen available at COM2
• If an Invalid message counter is non-zero, it indicates that an
Invalid Metasys message was detected. The last Metasys
message that was invalid is displayed.
• To clear or reset the statisics screen counters, press "C".
• To refresh the statisics screen, press "R".
• A non-zero Failure counter indicates an Ethernet problem, and
results in the display of an error number. Common Ethernet
error numbers are listed on the following page.
TD060100-0MA
31
Page 32
Error Number Meaning
98 Address already in use
102 Network dropped connection
74 Not a data message
112 Host is down
104 Connection reset by peer
101 Ethernet Network Unreachable
(typically a customer LAN Router failure)
113 Host unreachable (a remote Metasys
Ethernet device such as an NCM, OWS
or JC-MER-CXB is off-line)
110 Connection timed out
111 Connection refused
Table 1 — Common Ethernet Errors
If a defined router is offline when another router boots up, error 113
displays on the statistics screen. This error just means that a router
at one of the defined IP addresses did not respond as expected. The
router software flags this router as offline and will not send any
messages to it until it comes back online.
The other three Ethernet debugging tools are executed from the bash
prompt once the router program has been stopped. After stopping
the router by hitting the “Q” on the keyboard, switch the nullmodem cable to COM1 to exercise Linux control.
Note:
Once “Q” is hit, the router software stops transmitting
Metasys messages, and its subnet loses communications
with the rest of the Metasys Network. To restart the router
program from the bash prompt, type router.
Ping Command
The ping command verifies that messages can be sent and received
over the Ethernet network by transmitting continuous pings. The
basic command format is:
ping
xxx.xxx.xxx.xxx
where “xxx.xxx.xxx.xxx” is the IP address of a device on the Ethernet
network. Other JC-MER-CXB units and TCP/IP-compatible device
systems send back a response. The pinging will continue until you
press Ctrl-C.
TD060100-0MA
32
Page 33
Failures are caused by cable problems, device driver configuration
problems, or devices being offline. The display indicates if the ping
was successful and the approximate response time. A normal
response time for Ethernet is 25 to 50 milliseconds.
If there are any Ethernet communications errors, they are noted. If
the Ethernet network is running properly, no errors are reported.
Ipstat Command
The program ipstat reports various useful statistics. To launch
ipstat, type the following at the bash prompt:
ipstat
The resultant display reports the routing table, packet count, detected
errors and memory usage. If the Ethernet is operating properly, the
ipstat statistics should not report any errors.
Testnet Command
The testnet command reads the configuration data and attempts to
ping each device that is listed. The command format is:
testnet
Testnet lists the communication status for each device. If testnet can
talk to some devices but not others, the configuration data may
contain inaccurate information, such as a wrong address. To correct
bad addresses, access the configuration screen by running the config
command.
General Problem Prevention
1. Configure the Metasys Ethernet Router’s IP address, existing
LAN Router IP address, and subnet mask using information
from the customer’s network manager.
2. The Metasys ARCNET subnet addresses need to match the
router configuration screen data. Each ARCNET segment needs
a unique subnet address. The Metasys DDL files must use the
correct subnet addresses.
3. All of the Metasys devices on one ARCNET segment need to
have the same subnet address. Although ARCNET hubs and
links result in multiple ARCNET segments, for the purposes of
the JC-MER-CXB, it is all considered one subnet.
4. Time-critical control strategies should not cross Ethernet segments.
TD060100-0MA
33
Page 34
Debugging ARCNET Failures
Use standard Metasys debugging tools to diagnose and correct
suspected ARCNET failures. The JC-MER-CXB displays message
statistics. The router should increment the ARCNET message counter
(broadcast) when it is connected to any ARCNET NCM or workstation.
This counter will increment even if multiple subnets are not defined.
If this counter does not increment, there may be a problem with the
router itself.
Debugging Router Failures
Several of the difficulties discussed in this section may be caused by
a global DDL file that is inaccurate or has not been downloaded.
Therefore, before going on, verify that the current global file is
up-to-date and fully downloaded.
JC-MER-CXB Does Not Run When Booted
The configuration screen should be examined for errors.
Status Screen Indicates Failure Number 113
One or more JC-MER-CXB units were offline when this router
started. Normal communication resumes when the other routers
come online.
Status Screen Indicates Failure Number 101
This is caused by the customer’s existing LAN Router being offline.
Verify that the existing LAN Router IP address is correct. Check
with the customer’s LAN manager to determine the condition of the
existing LAN Router.
Status Screen Indicates Invalid Messages
1. An operator tried to access an NCM defined in the DDL, but the
NCM is on a subnet that does not appear in the configuration
screen. Update the screen to include the undefined subnet.
2. The Metasys Network generated a message that contained an
invalid address. Write down the message information that
appears on the screen and call Field Support Services.
TD060100-0MA
34
Page 35
Metasys Devices Do Not Respond
If any other node on the same ARCNET segment responds normally,
the router is not at fault. The problem could be caused by a Metasys
device failure or an ARCNET cable problem. Check the device for
any malfunctions, and use troubleshooting information from the N1
Local Area Network Technical Bulletin (in LIT-636017).
All the Devices on One ARCNET Segment Do Not Respond
1. If other ARCNET segments are working, the problem is isolated
to the failing segment. Use ping to find out if the suspect router
responds to Ethernet messages. (Firewalls may cause issues with
the ping command.)
2. If the router responds, look at the ARCNET cable and Metasys
equipment.
3. If the router does not respond, look at the router and the
Ethernet network. (See JC-MER-CXB Does Not Respond to Ping
Requests, further on.)
Multiple ARCNET Segments Do Not Respond
This could be caused by a router configuration problem or an
Ethernet problem. Use testnet to determine which routers respond.
Verify that the configuration screen entries are correct. Check the
Metasys DDL files for correct subnet/node addresses. Check the
configuration at each failing router. Check the Ethernet LAN for
failures.
JC-MER-CXB Does Not Respond to Ping Requests
This could be caused by problems with the router or problems on the
Ethernet LAN. Check the router configuration screen to see that all
addressing is correct for this router. Use ipstat to look for errors in
connecting to the Ethernet. If the router is running and appears to be
configured properly, the problem is probably due to an Ethernet
failure. Check with the network administrator to verify that the
network has not been changed and is functional.
TD060100-0MA
35
Page 36
N1 Communications Are Occasionally Unreliable
1. Ethernet communications may be unreliable. Use ipstat or ping
to check for Ethernet errors. If transmit or receive errors are
indicated, check with the network administrator for the Ethernet
network to determine if they have been experiencing Ethernet
downtime or excessively heavy network traffic.
2. ARCNET communications may be unreliable. Check the
ARCNET cables for any subnets that are experiencing problems.
3. Metasys N1 communications may be timing out. If you have
eliminated the other possible causes of this problem, contact
Field Support Services for assistance.
Data Cannot Be Viewed on OWS Across Network
The Metasys Operator Workstation (OWS) can be improperly configured so that it transmits broadcast ARCNET messages, but not point-
to-point ARCNET messages. The symptoms are as follows:
• No nodes come online at the OWS.
• The OWS cannot open any focus windows that require data
from a remote node.
• The OWS is online to the rest of the system, but cannot access
any data over the network.
• The JC-MER-CXB statistic screen shows broadcast traffic
from the OWS but not any normal message traffic.
• Other nodes may transmit Retry messages to the OWS.
These problems are caused by an IRQ conflict at the OWS. The
normal IRQ setting for the ARCNET card is 7. Some system BIOSes
will conflict with this setting. To resolve the conflict, change the
ARCNET IRQ to a different IRQ setting that is not currently in use.
TD060100-0MA
36
Page 37
5 Service
Warranty
Contemporary Controls (CCSI) warrants its product to the original
purchaser for two years from the product’s shipping date. If a CCSI
product fails to operate in compliance with its specification during
this period, CCSI will, at its option, repair or replace the product at
no charge. The customer is, however, responsible for shipping the
product; CCSI assumes no responsibility for the product until it is
received. This warranty does not cover repair of products that have
been damaged by abuse, accident, disaster, misuse, or incorrect
installation.
CCSI’s limited warranty covers products only as delivered. User
modification may void the warranty if the product is damaged during
installation of the modifications, in which case this warranty does
not cover repair or replacement.
This warranty in no way warrants suitability of the product for any
specific application.
IN NO EVENT WILL CCSI BE LIABLE FOR ANY DAMAGES
INCLUDING LOST PROFITS, LOST SAVINGS, OR OTHER
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT
OF THE USE OR INABILITY TO USE THE PRODUCT EVEN IF
CCSI HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES, OR FOR ANY CLAIM BY ANY PARTY OTHER
THAN THE PURCHASER.
THE ABOVE WARRANTY IS IN LIEU OF ANY AND ALL
OTHER WARRANTIES, EXPRESSED OR IMPLIED OR
STATUTORY, INCLUDING THE WARRANTIES OF
MERCHANT ABILITY, FITNESS FOR PARTICULAR PURPOSE
OR USE, TITLE AND NONINFRINGEMENT.
Repair or replacement as provided above shall be the purchaser’s
sole and exclusive remedy and CCSI’s exclusive liability for any
breach of warranty.
TD060100-0MA
37
Page 38
T echnical Support
Contemporary Controls (U.S.A.) will provide technical support on
its products by calling +1-630-963-7070 each weekday (except
holidays) between 8:00 a.m. and 5:00 p.m. Central time.
Contemporary Controls Ltd (U.K.) will provide technical support on
its products by calling +44 (0)24 7641 3786 each weekday (except
holidays) between 8:00 a.m. and 5:00 p.m. United Kingdom time. If
you have a problem outside these hours, leave a voice-mail message
in the CCSI after hours mailbox after calling our main phone number.
You can also fax your request by calling +1-630-963-0109 (U.S.) or
+44 (0)24 7641 3923 (U.K.), or contact us via e-mail at
info@ccontrols.com or info@ccontrols.co.uk. You can visit our web
site at www.ccontrols.com. When contacting us, please leave a
detailed description of the problem. We will contact you by phone
the next business day or in the manner your instructions indicate. We
will attempt to resolve the problem over the phone. If unresolvable,
the customer will be given an RMA number in order that the product
may be returned to CCSI for repair.
Warranty Repair
Products under warranty that were not subjected to misuse or abuse
will be repaired at no charge to the customer. The customer, however,
pays for shipping the product back to CCSI while CCSI pays for the
return shipment to the customer. CCSI normally ships ground.
International shipments may take longer. If the product has been
found to be misused or abused, CCSI will provide the customer with a
quote for repair. No work will be done without customer approval.
Non-Warranty Repair
CCSI provides a repair service for all its products. Repair charges are
based upon a fixed fee basis depending upon the complexity of the
product. Therefore, Customer Service can provide a quotation on the
repair cost at the time a Returned Material Authorization (RMA) is
requested. Customers pay the cost of shipping the defective product
to CCSI and will be invoiced for the return shipment to their facility.
No repair will be performed without customer approval. If a product
is determined to be unrepairable, the customer will be asked if the
product can be replaced with a refurbished product (assuming one is
available). Under no circumstances will CCSI replace a defective
product without customer approval. Allow ten working days for
repairs.
TD060100-0MA
38
Page 39
Returning Products for Repair
To schedule service for a product, please call CCSI Customer Service
support directly at +1-630-963-7070 (U.S.) or +44 (0)24 7641 3786
(U.K.). Have the product model and serial number available, along
with a description of the problem. A Customer Service representative
will record the appropriate information and issue, via fax, an RMA
number — a code number by which we track the product while it is
being processed. Once you have received the RMA number, follow
the instructions of the Customer Service support representative and
return the product to us, freight prepaid, with the RMA number
clearly marked on the exterior of the package. If possible, reuse the
original shipping containers and packaging. In any event, be sure
you follow good ESD-control practices when handling the product,
and ensure that antistatic bags and packing materials with adequate
padding and shock-absorbing properties are used. CCSI is not
responsible for any damage incurred from improper packaging.
Shipments should be insured for your protection.
Ship the product, freight prepaid, to the location from which it was
purchased:
Contemporary Control Systems, Inc.
2431 Curtiss Street
Downers Grove, IL 60515
U.S.A.
Contemporary Controls Ltd
Sovereign Court Two
University of Warwick Science Park
Sir William Lyons Rd.
Coventry CV4 7EZ
U.K.
TD060100-0MA
39
Page 40
Appendices
Appendix A: Metasys Ethernet Router Planning Forms
Metasys Ethernet Router Planning Form A
ARCNET ARCNET NCM/ Description
Node Subnet OWS (Optional)
Address Address
TD060100-0MA
40
Page 41
TD060100-0MA
41
Page 42
Appendix B: Common Commands and Software Switches
JC-MER-CXB Main Program (router)
The JC-MER-CXB is set up to automatically load and run all of the
TCP/IP and router software when the computer is booted. The unit's
software first loads some Metasys kernel software. The router
program, router, is then run.
If a terminal emulator is attached to COM2, a startup screen
displays when the JC-MER-CXB is booted. Once the router software
is running, an operator can type “Q” on the keyboard to terminate the
router program. To restart the router software, either type router at
the bash prompt or recycle power.
Ethernet Communications Tests (testnet)
The testnet program looks at the list of Metasys Ethernet devices
defined in the configuration screen and attempts to communicate
with each of them by issuing TCP/IP ping commands. The program
produces a summary of the communications with each Metasys
Ethernet device as shown below.
Figure 16 — Example of Testnet Results Screen
If a device is not responding to testnet, either the Ethernet or the device
has failed. Test the Ethernet link, then check connections to the device.
Finally, verify each item in the configuration screen.
Note: A firewall can prevent an OWS from responding to the
ping command.
Determining the MAC Address of the JC-MER-CXB (getmac)
Sometimes your IT staff may need to know the MAC address of the
JC-MER-CXB. This is reported on screen by entering the command
getmac at the bash prompt.
TD060100-0MA
42
Page 43
Configuration Download (download)
This program downloads the router configuration from one router to
all of the other JC-MER-CXB units. When the download program is
run, it will prompt for additional information. It will also indicate
which routers were downloaded successfully. If a download fails,
rerun the download program.
The download program must be run from a router whose IP address
is listed on the configuration screen of each destination router. A
router will not accept communication from any device whose address
is not in the router's configuration screen.
Software Switches
/A or /B The "/A" switch and the "/B" switch control the way
that ARCNET broadcast messages are handled by the
JC-MER-CXB If neither of these switches are defined,
the JC-MER-CXB sends one IP message to each IP
address listed in the configuration screen, for every
ARCNET broadcast message received. This mode will
generate a lot of Ethernet traffic and can cause Metasys
nodes to have off-line problems if any IP address defined
in this screen is not present on the network. Including one
of these two switches causes the JC-MER-CXB to send
one broadcast message to all nodes within the broadcast
domain of the unit. Additional messages are sent to each
of the remaining devices that do not receive the broadcast
message. The two switches control how the broadcast
message is sent on the Ethernet network. The "/A" switch
sends broadcast messages to the all-ones IP address
(255.255.255.255). The "/B" switch sends broadcast
messages to the network directed address. The "/B" switch
should be used on networks that do not pass all ones
broadcast messages to all parts of a single IP network.
Ask your network administrator which type of broadcast
message the network supports — all ones ("/A" switch) or
network directed ("/B" switch). The "/A" switch is set
as the default condition. Do not set both switches active at
at the same time on a single router.
TD060100-0MA
43
Page 44
/D This switch is used for diagnostic purposes. Using
this option displays the contents of all the messages
received by the JC-MER-CXB.
Note: The "/D" switch cannot be used in combination
with the "/S" switch.
/M Monitor statistics. This outputs statistics to the
statistics screen, but only if the "/S" switch has been
set to display a template by which the statistics may
be meaningfully viewed.
/S Statistics screen. This displays the router statistics
screen via the COM2 port. If the "/M" switch is set to
monitor statistics, the statistics are reported onscreen.
If the "/M" switch is not set, the statistics screen is still
displayed, but no statistics are reported. Once per day
the statistics counters are zeroed. When statistics are
updated to the monitor, router operation does slow down
For optimum performance, turn the statistics display off.
If "/S" is not on, the Johnson Controls copyright page is
continuously displayed at COM2, but router operation
can still be confirmed by the activity of the LEDs.
For more Statistics Screen information, see Appendix C.
/T Test option. Causes the router program to evaluate the
contents of the configuration data and report errors. The
router halts after this process ends — therefore, do not
use "/T" in an operating router. Type router to restart.
/U This switch is used to allow Multi-Metasys N1
networks to exist on the same Ethernet network.
When configuring the JC-MER-CXB to run in a
Multi-network configuration, the configuration screen
must contain the “/U nnnnn” switch. Replace the nnnnn
characters with the UDP port address that was used to
configure other Metasys Ethernet devices that will exist
within the target Metasys network. DO NOT use this
switch unless you are configuring a Multiple Metasys N1
Network configuration. See Appendix F for more UDP
information.
The configuration screen must be the same (except for switch settings)
for all JC-MER-CXB units in the system. If the configuration screen
is updated, it must be copied into each router.
This can be done using
the download command.
TD060100-0MA
44
Page 45
Other Linux Commands
The following Linux commands are used less-frequently by operators
of the JC-MER-CXB. However, they are listed here for those who
may find them useful in certain circumstances.
cat [filename] This command will print the contents of a file to the
screen.
cd This command will change the current directory.
clear This command will clear the display screen.
ifconfig This command will display network and hardware addresses.
ls This command will list the current directory contents.
ls -l This command will list the current directory contents in detail.
reboot This command will stop the system, power off and reboot.
FTP Files from JC-MER-CXB
Using a PC on the same subnet as the JC-MER-CXB, you can use a
web browser to FTP files from the router. In the browser address field,
enter:
ftp://xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP address of the JC-MER-CXB. When
this browser command is executed, you will be prompted for a user ID
and for a password. For both response, type the word "root". If done
properly, the root directory of the JC-MER-CXB will be displayed. At
this point, use normal Windows actions to locate and copy the desired
files from the router to your PC. Often, the file of most interest is
router.err which is in the root directory.
You should never FTP files into the JC-MER-CXB unless directed to do
so by Contemporary Controls. If you accidentally disturb the files in the
JC-MER-CXB, just reboot the unit to restore normal operation.
TD060100-0MA
45
Page 46
Appendix C: Statistics Screen Information
A sample statistics output (viewed on COM2) is shown below:
Figure 17 — Example of Statistics Screen
The left column shows the number of ARCNET messages received
by the router. The right column shows the number of Ethernet
messages received by the router. The Idle counters are incremented
when the router has no messages to process and is idle. Whenever
statistics are displayed, the Idle counter increments continuously.
Note: Use the Idle counter only as an indication that the router is
running. It does not provide an accurate estimate of percent
idle time for the router.
The Normal message counters indicate the number of Normal
(non-broadcast) messages received by the router. The Broadcast
message counters report the number of Broadcast messages received
by the router and destined for all nodes in Metasys. The Retry
message counter tracks the number of RTOS (Real Time Operating
System) messages retransmitted; low numbers reflect stable N1
communications.
Invalid counters report the number of Invalid messages received.
Invalid messages contains invalid addresses. These counters should
always be zero during normal operation — otherwise, the latest
Invalid message is displayed on the screen below the statistics.
The ARCNET Failure counter indicates the number of times an
ARCNET message could not be delivered to its destination due to
Ethernet errors. While this counter should normally be zero, it will
increment if one of the other JC-MER-CXB units is offline.
TD060100-0MA
46
Page 47
Appendix D: Setting Up HyperTerminal
HyperTerminal is a terminal-emulation program included with
Windows®. To communicate with the JC-MER-CXB you will need
to configure HyperTerminal. First run HyperTerminal and then:
• Choose the File menu item.
• Choose the Properties menu item.
• In the “Connect using” box select the COM port you are
using to communicate with the JC-MER-CXB.
• Press the Configure button.
• Select the Port settings tab.
• Set the Bits per second to 57600.
• Set the Data bits to 8.
• Set the Parity to None.
• Set the Stop bits to 1.
• Set the Flow control to None.*
• Press the OK button.
• Select the Settings tab.
• Choose the “Terminal Keys” option.
• In the Emulation box select ANSI.
• Press the OK button.
* "Hardware" flow control could cause unreliable communication.
If you connect to a running JC-MER-CXB you may need to refresh
the screen. While the router program is executing, press “R” to
redraw the screen.
TD060100-0MA
47
Page 48
Appendix E: Field Connections
The JC-MER-CXB transceiver presents a high-impedance connection
in both the powered and unpowered states. Although nominally a bus
device, it can be used in either bus or star ARCNET topologies that
use RG-62/u coaxial cable.
Regardless of the topology implemented, the coaxial port will require
a BNC Tee connector with at least one leg of the connector fastened
to coaxial cable. If the unit passes traffic from one portion of an
ARCNET bus to another, the remaining leg of the Tee connector will
tie to another coaxial cable. But if the unit occupies the end of a bus
segment, the remaining leg of the Tee connector must be fitted
with a BNC-style terminator having 93 (nominal) ohms of resistance.
The m
aximum ARCNET segment length is 1000 feet and the
maximum
segment beyond 1000 feet, an active hub is required. The coaxial
cable
connector
number of nodes per segment is eight. To extend a bus
should attach directly to the hub port without using a BNC Tee
since the port internally terminates the end of a bus segment.
TD060100-0MA
48
Page 49
Appendix F: UDP Port Address Assignments
Metasys Ethernet networks use a default value of 11001 for the UDP
port address (UDPPA) and NCMs automatically configure themselves
to use this value. Since each N1 network must have a unique UDPPA,
other values must be used when multiple N1 networks are involved.
Any UDPPA from 2050 to 65535 (except 11002) can be used, but it is
best to start numbering networks in a Multinetwork configuration with
11003 and continue sequentially.
Ask the Network Administrator or the customer’s Ethernet network
support provider if they know of any reason why any UDDPA you
have chosen should not be used on their network.
For more information, refer to the following document:
LIT-6360175 N1 Ethernet/IP Network Technical Bulletin.
TD060100-0MA
49
Page 50
Appendix G: Linux Trademark Information
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation’s software and to any other program whose authors commit
to using it. (Some other Free Software Foundation software is covered
by the GNU Lesser General Public License instead.) You can apply it
to your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Preamble
TD060100-0MA
50
Page 51
Also, for each author’s protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on,
we want its recipients to know that what they have is not the original,
so that any problems introduced by others will not reflect on the
original authors’ reputations.
Finally, any free program is threatened constantly by software patents.
We wish to avoid the danger that redistributors of a free program will
individually obtain patent licenses, in effect making the program
proprietary. To prevent this, we have made it clear that any patent must
be licensed for everyone’s free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING,
DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The “Program”, below,
refers to any such program or work, and a “work based on the Program”
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it, either
verbatim or with modifications and/or translated into another language.
(Hereinafter, translation is included without limitation in the term
“modification”.) Each licensee is addressed as “you”.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program’s
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
TD060100-0MA
51
Page 52
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work u nder the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcemen t, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
TD060100-0MA
52
Page 53
In addition, mere aggregation of another work not based on the
Program with the Program (or with a work based on the Program) on a
volume of a storage or distribution medium does not bring the other
work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software
interchange; or,
b) Accompany it with a written offer, valid for at least three years, to
give any third party, for a charge no more than your cost of
physically performing source distribution, a complete machinereadable copy of the corresponding source code, to be distributed
under the terms of Sections 1 and 2 above on a medium customarily
used for software interchange; or,
c) Accompany it with the information you received as to the offer to
distribute corresponding source code. (This alternative is allowed
only for noncommercial distribution and only if you received the
program in object code or executable form with such an offer, in
accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to control
compilation and installation of the executable. However, as a special
exception, the source code distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
TD060100-0MA
53
Page 54
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is void,
and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying the
Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients’ exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
TD060100-0MA
54
Page 55
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to be
a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain
countries either by patents or by copyrighted interfaces, the original
copyright holder who places the Program under this License may add
an explicit geographical distribution limitation excluding those
countries, so that distribution is permitted only in or among countries
not thus excluded. In such case, this License incorporates the limitation
as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new
versions of the General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may differ in
detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and “any
later version”, you have the option of following the terms and
conditions either of that version or of any later version published by the
Free Software Foundation. If the Program does not specify a version
number of this License, you may choose any version ever published by
the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the
author to ask for permission. For software which is copyrighted by the
Free Software Foundation, write to the Free Software Foundation; we
sometimes make exceptions for this. Our decision will be guided by
the two goals of preserving the free status of all derivatives of our free
software and of promoting the sharing and reuse of software generally.
TD060100-0MA
55
Page 56
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF
CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO
THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT
WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM
“AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AN D
FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK
AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE,
YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW
OR AGREED TO IN WRITING WILL ANY COPYRIGHT
HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED
ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING
ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES
SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF
THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
TD060100-0MA
56
Page 57
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it free
software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
“copyright” line and a pointer to where the full notice is found.
<one line to give the program’s name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or (at
your option) any later version.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty
of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software Foundation, Inc.,
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Also add information on how to contact you by electronic and paper
mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for
details type `show w’. This is free software, and you are welcome to
redistribute it under certain conditions; type `show c’ for details.
The hypothetical commands `show w’ and `show c’ should show the
appropriate parts of the General Public License. Of course, the
commands you use may be called something other than `show w’ and
`show c’; they could even be mouse-clicks or menu items—whatever
suits your program.
TD060100-0MA
57
Page 58
You should also get your employer (if you work as a programmer) or
your school, if any, to sign a “copyright disclaimer” for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
program `Gnomovision’ (which makes passes at compilers) written
by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your
program into proprietary programs. If your program is a subroutine
library, you may consider it more useful to permit linking proprietary
applications with the library. If this is what you want to do, use the
GNU Lesser General Public License instead of this License.
TD060100-0MA
58
Loading...