Metasys N2, Technical Manual

Page: 47 / 67

N2 Dialer Module—N2 Dialer Module (NDM) 47
Appendix B:
Using Companion with an NDM
The N2 Dialer Module (NDM) provides a link between a Companion System (Release
6.0 or later) and a remote N2 Bus for point monitoring and change-of-state reporting.
“Local” and “remote” are the terms used when referring to the two types of NDMs. A
“local” NDM resides on the N2 Bus connected to the Companion System while the
“remote” NDM resides at an offsite location that does not have a facility management
system connected to it. Each local and remote NDM must have a unique N2 Bus address.
The minimum requirements to provide an operating system are two NDMs (one remote
and one local), a dedicated phone line, two 9600 baud Hayes Optima or 100% compatible
modems, and remote devices. See Appendix A: Supported Devices and Firmware
Revisions of this document for details regarding supported devices.
Companion Release 6.00 or later supports the N2 Dialer Module (NDM). Note that the
NDM does not support Companion features such as weekly scheduling, demand limiting,
load rolling, or trend. If these types of functions are required, it is recommended that the
dial up capabilities of a standard facility management system be installed at the local and
remote sites, without NDMs.
•
Configuring the NDM requires HVAC PRO for Windows 5.10
(or later).
•
When programming a remote NDM using HVAC PRO for Windows, it is
imperative that you properly program the N2 addresses for all devices connected to
the remote NDM. This is done by loading the remote NDM configuration, selecting
Phone Number Configuration from the Action menu, and filling in the Remote N2
Addresses field. This field must correctly list all N2 addresses for devices
connected to the remote NDM. It must not contain the address of the remote NDM
itself.
•
The local NDM can contain up to 50 remote site names and phone numbers.
Overview
Applications
Supported
Design
Considerations