Transcript
Technical Bulletin Issue Date
August 6, 2002
Controller Access
Controller Access..................................................................................2 Introduction......................................................................................................... 2 Key Concepts...................................................................................................... 3 Direct Access .................................................................................................................... 3 RS-232 Application (DX Only)........................................................................................... 6 Auxiliary Access ................................................................................................................ 6 Connection Monitoring ...................................................................................................... 7 Stand-Alone NDM with a Passive Printer.......................................................................... 8 Stand-Alone NDM ............................................................................................................. 9 Companion/Facilitator System ........................................................................................ 10 Cable Connection............................................................................................................ 11 OWS Access ................................................................................................................... 11
Procedure Overview......................................................................................... 13 Detailed Procedures......................................................................................... 14 Connecting to a Remote NDM ........................................................................................ 14 Connecting to a Companion/Facilitator System with a Cable ......................................... 15 Connecting to a Remote NDM or Companion Site Using Auxiliary Access with a Modem.................................................................................................................. 17 Connecting to a Companion Site Using Auxiliary Access with a Cable .......................... 20 Disconnecting from a Site ............................................................................................... 20
Troubleshooting ............................................................................................... 21 Troubleshooting Chart..................................................................................................... 21
© 2002 Johnson Controls, Inc. Code No. LIT-6364013
www.johnsoncontrols.com
2
Controller Access Technical Bulletin
Controller Access
Introduction This document describes the methods available to communicate to our current controller product line. You can communicate using direct access, auxiliary access, or Operator Workstation (OWS) access. Direct access allows software Configuration Tools to directly communicate with most controllers. Specific interface hardware devices convert PC RS-232 signals to either N2 (RS-485) or Zone Bus signal levels. N2 only converter devices are the MM-CVT101 and AS-TBL485. A Zone Bus only converter is the AS-CBLPRO-x. The AS-CVTPRO connects to either the N2 Bus or Zone Bus. The Auxiliary Access feature allows the user to access many of the controllers connected to a Metasys Companion or Facilitator™ system (Personal Computer [PC] or Panel) or a remote N2 Bus monitored by a remote N2 Dialer Module (NDM). Auxiliary Access requires a modem or cable connection. OWS access provides accessibility to devices connected to a Metasys Network Control Module (NCM). Refer to the M-Tool Overview and Installation Technical Bulletin (LIT-693100) for more pass through information.
Controller Access Technical Bulletin
3
Key Concepts Direct Access Direct access allows Configuration Tools to connect to most controllers on the N2 Bus using an MM-CVT101 or AS-TBL485. Connect to the Zone Bus using an AS-CBLPRO-x. Connect to either the N2 Bus or Zone Bus using an AS-CVTPRO. The user can then upload, download, and commission Application Specific Controllers (ASCs) [Variable Air Volume (VAV), Unitary (UNT), Air Handling Units (AHUs)], TC-9102 controllers, Variable Air Volume Modular Assembly (VMA) devices, and DX-9100 controllers. N2 Bus Application (MM-CVT101 or AS-TBL485) Connect the PC to the controller N2 Bus, an MM-CVT101*, or an AS-TBL485. Configuration tool software communicates to a single controller at one time or the software can scan the entire N2 Bus for limited controller information. *
Windows 2000 and Windows NT operating systems do not work with an MMCVT101.
You can also communicate directly to DX controllers by connecting the PC’s RS-232 port to the DX controller’s RS-232 port with a null modem cable. (DX is the only controller with a built-in RS-232 port. In this case, do not use the converter. Only one master is allowed on the N2 Bus at a time.) IMPORTANT: You must disconnect the N2 Bus from the supervisory system before connecting the CVT101 or AS-TBL485 to the N2 Bus. VAV Controller
9- or 25-pin RS-232 serial port
UNT Controller
TC-9102 Controller
25-pin
N2 Bus Use 9-pin to 25-pin adapter if needed. DX-9100 Controller AHU Controller
VMA Device Local2
Figure 1: Direct Access Example (N2 Bus Application)
Note:
For more information, see HVAC PRO User’s Manual.
Controller Access Technical Bulletin
Zone Bus Application (AS-CBLPRO) Connect the PC to a controller Zone Bus using an AS-CBLPRO-x*. (Connect CBLPRO to only one controller at a time). Connect to the controller Zone Bus directly or via the TE-6400 room sensor (Metastat Series) or a TMZ1600. The Zone Bus is not available on the DX, TC, or XTM Controllers. *
The AS-CBLPRO-x is not supported by Windows NT or Windows 2000 operating system machines.
Note: If downloading, uploading, or commissioning over the Zone Bus, the device goes offline to the supervisory system if monitored over the N2 Bus. 12345678
4
TM
ANALOG INPUTS
BINARY OUTPUT
3
4
5
6
7
24VAC
2
8
24VAC
1
24VAC
ZBUS
N2+ N2REF
BINARY COM
COMMON
TO ZO NE STAT
24VAC
Z BUS
24VAC
4
24VAC
3
24VAC
2
CO M
ANALOG INPUTS
1
24VAC
123 456
BINARY INPUT
24VAC
1 2 3 4 5 6
+15VDC +15VDC
25-pin to 9-pin Adapter (if needed)
123 456
Cable PRO
ANALOG INPUTS
BINARY IN
BINARY OUTPUTS DSI
P5
P6
Power port Laptop PC (9-or 25-pin serial port)
RS-232 cable (9 Pin) (to PC)
or
6-pin to 8-pin
Zone Bus 25-pin to 9-pin Adapter (if needed)
Cable PRO 8-pin to 8-pin Laptop PC (9-or 25-pin)
Zone Bus 6-pin to 6-pin
Room Sensor (TE-6400/TMZ)
auxconn
Figure 2: Direct Access (Zone Bus Application) Typical for VAV, UNT, AHU, or VMA Devices
Controller Access Technical Bulletin
5
N2 Bus or Zone Bus (MM-CVTPRO) Note: Do not connect the CVTPRO to both the N2 Bus and Zone Bus at the same time. The CVTPRO connects to controllers via the N2 Bus or the Zone Bus (Figure 3). The CVTPRO supports multiple operating systems and offers compatibility with Palm™ Personal Digital Assistants (PDAs). Refer to the Auxiliary Gear Technical Bulletin (LIT-6363080) for more information on CVTPRO connections and operating system compatibility. Palm III, Palm V with Dock V PRO Adapter, or Palm VII device (1,2) A
N
S
CA
IO
P LI
R
P
2
d e
1
5 34
F
M
abc E NU
TE-6x00/TMZ Room Sensor RJ11 Jack, 6-Pin
LC ULAT O
C AT
I ND
CVTPRO Compatible Controller External Power (3)
Serial Port
or or
Zone Bus/ N2 Bus RJ11 Jack 6-pin
N2 Bus
DB9 Port Personal Computer (1) or
Zone Bus
RJ45 Jack, 8 Pin
N2 Bus Interface, 4-Pin N2 Socket/ 3-Pin N2 Plug with Tab
DB9 Connector
Palm m1xx or m5xx (with additional connectors) S
IO
CA
P LI
e
2 1
d
M
3
45 F
abc E NU
R
N
A
P
LC ULAT O
C AT
I ND
Notes: 1. Do not connect the CVTPRO to the Palm device and laptop/PC at the same time. 2. Unplug the Palm device from the CVTPRO when not in use (conserves battery power). 3. The CVTPRO200-0 (European version) does not ship with an external power adapter. Cvtschematic
Figure 3: CVTPRO Connections
6
Controller Access Technical Bulletin
RS-232 Application (DX Only) Connect the PC to the DX serial port connection located on the DX base with a null modem cable or a standard RS-232 cable (9-pin at DX) and a null modem adapter. This connection allows communication to a single DX-91x0 to perform download/upload (using the GX-9100) and commissioning of the DX and extension modules. The controller does not go offline if connected to the N2. Null Modem Adaptor B/S
PC
RS-232 DX-91x0 Controller Rs232
Figure 4: Direct Access (RS-232 Application)
Auxiliary Access The Auxiliary Access feature in the Configuration Tools program group allows the user to access controllers connected to a Companion/Facilitator system or a remote N2 Bus being monitored by a remote NDM. Auxiliary Access provides two methods of accessing these remote controllers: •
modem connection - the user dials out to remote controllers through a remote NDM or Companion/Facilitator system (Release 6.00 or later).
•
cable connection - the user directly connects a PC to a remote NDM or Companion/Facilitator system (Release 6.00 or later) without disconnecting the N2 Bus from the monitoring system at the remote site.
Use either the modem or cable connection feature to upload, download, and commission controllers through the N2 Bus, with a Companion/Facilitator system or NDM. For a Companion/Facilitator system, the controller must be mapped into the Companion/Facilitator database for this feature to work. Note: The NDM and the Companion/Facilitator system do not support the VMA; therefore, Auxiliary Access does not support the VMA.
Controller Access Technical Bulletin
7
Modem Connection The modem connection feature allows the user to dial out to remote controllers in three ways: •
to a stand-alone NDM with a passive printer
•
to a stand-alone NDM
•
to a remote Companion/Facilitator system
Modem connection requires a Hayes® compatible 9600 baud modem at the Configuration Tools PC and at the remote site.
Connection Monitoring During a valid remote connection, Auxiliary Access monitors the connection periodically. If communications are interrupted, a dialog box appears stating you must reconnect. The Auxiliary Access icon then changes to the inactive state. To reconnect, see the Connecting to a Remote NDM or Companion Site Using Auxiliary Access with a Modem section of this document. Note: The Companion/Facilitator system disconnects Auxiliary Access after 60 seconds without communications.
8
Controller Access Technical Bulletin
Stand-Alone NDM with a Passive Printer In a local passive printer application, a remote NDM initiates a call to a local printer to pass alarm information to the local site. To clear these alarm conditions, use the modem connection feature to dial the remote site to commission the controller in alarm. For more information, see the N2 Dialer Module (NDM) Technical Bulletin (LIT-6363065). PC Running Auxiliary Access
Local Printer (Stand-alone) Local Modem
Local Modem
Local Site Remote Site Remote Modem
VAV Controller
UNT Controller
TC-9102 Controller P w o er
METAS YS
R/ T
T9 C 1 02
N2 Bus
DX-9100 Controller AHU Controller
Remprint
Figure 5: Using Auxiliary Access to Clear Alarms in a Passive Printer Application
Controller Access Technical Bulletin
9
Stand-Alone NDM Auxiliary access can dial a stand-alone remote network. In this application, the NDM provides the modem connection to the network. PC Running Auxiliary Access
Local Modem
Remote Modem
VAV Controller
UNT Controller
TC-9102 Controller P w o er
METAS YS
R/ T
T9 C 1 02
N2 Bus
DX-9100 Controller AHU Controller
Figure 6: Stand-Alone Remote Network
Remprt2
10
Controller Access Technical Bulletin
Companion/Facilitator System In the pass-through mode available with Companion/Facilitator Release 6.00 or later, use Configuration Tools software to directly access controllers on the N2 Bus through a Companion system. Auxiliary access provides the connection link that utilizes the pass-through mode. With the modem connection feature, you initiate a call to the Companion system through a 9600 baud modem. At the remote site, if you are using a Panel version Companion/Facilitator system with a PC running VT100 emulation software, exit the emulation software, run Auxiliary Access software, and the cable connections do not change. After establishing connection and passing verification codes between the Companion/Facilitator system and Auxiliary Access which runs on the Configuration Tools PC, the Companion/Facilitator system enters the pass-through mode. At this point, you can upload, download, or commission individual controllers on the N2 Bus using Configuration Tools software; the controller maintains full functionality. You must map the controller into the Companion/Facilitator database for this feature to work. While in or out of the pass-through mode, the Companion/Facilitator system maintains full network operations and communications, including keeping the controllers online. During Auxiliary Access, if a controller resets, it goes offline to the Companion/Facilitator system. Notes:
Companion/Facilitator Release 6.02 or later must be able to download an XT-9100 Extension Module connected to DX-9100 controllers through Companion/Facilitator system. When using this feature on a Companion/Facilitator system, the supervisory system remains in control. Although the controller you are commissioning may be offline to the supervisory system, the rest of the network is still processing commands from the supervisory system. If you need the Companion/Facilitator system to reissue manual or operator override commands after commissioning, you must reset the controller.
Controller Access Technical Bulletin
11
PC Running Auxiliary Access
PC Version
Building Automation System
Panel Version
or
N2 Converter VAV Controller
UNT Controller
TC-9102 Controller
N2 Bus
DX-9100 Controller AHU Controller remprt3
Figure 7: Pass-Through Mode for a Companion/Facilitator PC or Panel Configuration
Cable Connection The cable connection feature is used to directly connect to the communications port of either a Companion/Facilitator system or NDM without having to disconnect the N2 Bus from the monitoring system at the remote site. You can upload, download, and commission the controllers through the monitoring system. Note: Remote alarms, which have triggered a dial in a passive application, cannot be cleared using this cable connection feature. You must dial using the modem connection feature of Auxiliary Access to clear alarms and enable the NDM to dial for subsequent alarms in the controller that caused the alarm.
OWS Access Note: You must have Metasys Release 6.00 or later to run Configuration Tools from the OWS. Metasys Release 9.00 or later is required to support object mapping to VMA devices.
12
Controller Access Technical Bulletin
The Configuration Tools that support access to remote controllers from the Metasys OWS are HVAC PRO software, DX Commissioning, and NDM Configurator. You can access these tools through the custom application menu or through Program Manager. Metasys Release 7.01 or later includes System 91 support for DX Commissioning and TC-9102 controllers. N1 Local Area Network (LAN)
Network Control Unit (NCU)
VAV Controller
UNT Controller
Operator Workstation
TC-9102 Controller
N2 Bus
DX-9100 Controller AHU Controller
VMA Device
owsn2
Figure 8: OWS Access
Note: The Auxiliary Access feature is not functional while running Configuration Tools on the Metasys OWS. For more information, see the HVAC PRO User’s Manual.
Controller Access Technical Bulletin
13
Procedure Overview Table 1: Controller Access To Do This
Follow These Steps:
Connect a Remote NDM.
Turn off the modem. Disconnect the cable from the modem. Connect your laptop computer to the cable on the NDM using a null modem cable. Use Configuration Tools to communicate with the remote controllers through the NDM. When finished, reconnect the modem cable to the modem. Turn on the modem.
Connect a Companion/Facilitator System with a Cable.
Connect your laptop computer to the Companion/Facilitator system using a null modem cable. Use Configuration Tools to communicate with the remote controllers through the Companion/Facilitator system.
Connect to a Remote NDM or Companion Site Using Auxiliary Access with a Modem.
On the Windows Start menu select Programs > Configuration Tools > Auxiliary Access. Select the PC Port. Select Modem in the Connection Type box. Enter the Phone Number. Click OK to confirm the modem setup strings and to return to the Auxiliary Access dialog box. Select the Connect Button to initiate or restart the dial sequence.
Connect to a Companion/Facilitator Site Using Auxiliary Access with a Cable.
On the Windows Start menu select Programs > Configuration Tools > Auxiliary Access. Select the Port. Select Cable in the Connection Type box. Select the Connect button to establish the connection.
Disconnect from a Site.
Single-click on the active Auxiliary Access taskbar to display the System menu. Select Disconnect Site. Select Close. Select Yes to terminate the connection.
14
Controller Access Technical Bulletin
Detailed Procedures Connecting to a Remote NDM To connect a remote NDM: Note: The NDM does not support VMA devices, XTM or DX-9120 Controllers. 1. Turn off the modem to reset the NDM. 2. Disconnect the cable from the modem. 3. Connect your laptop computer to the cable on the NDM using a null modem cable. Based on your PC requirements, you may need a 9-pin or 25-pin cable connection. For pinout requirements for the null modem cable, refer to Figure 9. 25-pin Female
9-pin Female Signal Pin 2 RD 3 TD RTS 7 CTS 8 DSR 6 GND 5 DCD 1 DTR 4
Pin 2 3 4 5 6 7 8 20
Cable
PC End
25-pin Female
Signal TD RD RTS CTS DSR GND DCD DTR NDM End
Signal Pin 2 TD 3 RD RTS 4 CTS 5 DSR 6 GND 7 DCD 8 DTR 20 PC End
25-pin Female Pin 2 3 4 5 6 7 8 20
Cable
Signal TD RD RTS CTS DSR GND DCD DTR NDM End ndmend
Figure 9: Null Modem Cable Pinouts for NDM
4. Use Configuration Tools to communicate with the remote controllers through the NDM. VAV Controller
UNT Controller
TC-9102 Controller Power
M ETAS YS
R/T
TC9102
N2 Bus PC Running (Auxiliary Access)
DX-9100 Controller
AHU Controller
Figure 10: Cable Connection to the NDM
5. Reconnect the modem cable to the modem.
cable2
Controller Access Technical Bulletin
15
6. Turn on the modem. If you configure the NDM with a local phone number, it dials the local site and report its online status as well as the online status of the other controllers on the N2 Bus.
Connecting to a Companion/Facilitator System with a Cable To connect a Companion/Facilitator system with a cable: 1. Connect your laptop computer to the Companion/Facilitator system using a null modem cable. For pinout requirements for the null modem cable, see Figure 11. Note: When using the Companion PC version, connect the cable to COM 2 with a null modem cable. For the Companion Panel version, connect the cable to either the local port or remote port with a null modem cable. 9-pin Female Signal Pin TD RD RTS CTS DSR GND DCD DTR PC End
3 2 7 8 6 5 1 4
9-pin Female Pin Signal 3 2 7 8 6 5 1 4
TD RD RTS CTS DSR GND DCD DTR
Companion End
9-pin Female
25-pin Female
Signal Pin RD TD RTS CTS DSR GND DCD DTR
2 3 7 8 6 5 1 4
Companion End
Cable
Pin 2 3 4 5 6 7 8 20
Signal TD RD RTS CTS DSR GND DCD DTR PC End cpn1
Figure 11: Null Modem Cable Pinouts for Companion/Facilitator System
16
Controller Access Technical Bulletin
PC Running Auxiliary Access Null Modem Building Cable Automation System PC Version
Null Modem Cable
Panel Version or Converter (MM-CVT101-0) VAV Controller
UNT Controller
TC-9102 Controller
N2 Bus
DX-9100 Controller AHU Controller cable1
Figure 12: Cable Connection to Companion
2. Use Configuration Tools to communicate with the remote controllers through the Companion/Facilitator system.
Controller Access Technical Bulletin
17
Connecting to a Remote NDM or Companion Site Using Auxiliary Access with a Modem To connect to a remote NDM or a Companion site using Auxiliary Access with a modem: 1. On the Windows Start menu select Programs > Configuration Tools > Auxiliary Access. The Auxiliary Access dialog box appears (Figure 13).
Figure 13: Auxiliary Access Dialog Box
Note: When you select Cable for the Connection Type, the Phone Number field and Modem Setup button are not used and, therefore, appear dimmed. 2. Select the PC Port. 3. Select Modem in the Connection Type box. 4. Enter the Phone Number. The previous, successful number is displayed as the default. Note: If a modem other than a Hayes compatible application is used, the modem setup may need to change. If the setup is new or has been modified, select the Modem Setup button to enter specific modem initialization character strings. The Connect Remote Site Modem Setup dialog box appears (Figure 14).
18
Controller Access Technical Bulletin
Note: Default modem setup strings are provided for a standard Hayes compatible modem. Refer to the Metasys Modems 2Resource Page for details. The telephone number, port selections, connection timeout value, and modem setup strings are preserved as defaults for any subsequent dial commands. There is room for seven setup strings, a dialing prefix, and a connection timeout.
Figure 14: Default Modem Setup Strings
5. Figure 14 shows the default modem setup strings, which are sent to the modem in the auxiliary dial application.
Controller Access Technical Bulletin
19
Table 2: Default Modem Setup Strings String
Description
&F
Recall factory settings.
E0
Disable character echo.
*L0
Low speaker volume.
N0
Lock in at speed specified in S37.
Q1
Disable result codes.
&C1
DCD tracks the carrier.
&D3
DTR signals a hard-reset of modem.
&S0
DSR is always active.
*S0 = 1
Answer after one ring.
*S8 = 4
Comma duration set at 4 seconds.
*S11 = 50
Used to increase dialing speed (tone only).
S37 = 9
Connect only at 9600 baud.
&Q0 =
Force asynchronous communications.
* Only these parameters may be changed from default values. All other listed parameters require default values for proper connection.
6. Click OK to confirm the modem setup strings and to return to the Auxiliary Access dialog box. 7. Select the Connect button to initiate or restart the dial sequence, or select the Cancel button to exit. Only one telephone number is in the Auxiliary Access initialization file. If problems arise while making a remote connection, an error message appears. Notes: All Configuration Tools must use the same port used in the Auxiliary Access application. Once a connection is made, the Auxiliary Access dialog box automatically closes and the Auxiliary Access taskbar updates to indicate which port and system type (N2 Dialer or Supervisory System) has a remote connection.
Figure 15: Updated Auxiliary Access Icon
If a communication is not established before the connection time out expires, the Auxiliary Access icon remains inactive. Check all connections and setups, then try to reconnect.
20
Controller Access Technical Bulletin
Connecting to a Companion Site Using Auxiliary Access with a Cable To connect to a Companion site using Auxiliary Access with a cable: 1. On the Windows Start menu select Programs > Configuration Tools > Auxiliary Access. The Auxiliary Access dialog box appears (Figure 13). 2. Select the Port. 3. Select Cable in the Connection Type box. The Phone Number field and Modem Setup button are not required and appear dimmed when using the cable connection. 4. Select the Connect button to establish the connection, or select the Cancel button to exit. Note: Once a connection is made, the Auxiliary Access dialog box automatically closes and the Auxiliary Access taskbar updates to indicate the selected port (Figure 15) and supervisory system.
Disconnecting from a Site The disconnect can be initiated either manually or from fault detection. 1. Single-click on the active Auxiliary Access taskbar to display the System menu (Figure 16).
Figure 16: System Menu
2. Select Disconnect Site. 3. Select Close. This completes the disconnect and terminates the Auxiliary Access icon. A Disconnect Site Verification dialog box appears. 4. Select Yes to terminate the connection. The termination interrupts any communication in progress. The Auxiliary Access icon changes to the disconnected state on the screen and remains until specifically closed through the System menu.
Controller Access Technical Bulletin
21
Troubleshooting Troubleshooting Chart Table 3: Troubleshooting Symptom
Possible Cause
Action
No communication to remote NDM, even though Port (n) Active N2 Dialer indicates connection to NDM
Incorrect modem configuration
Verify Auxiliary Access and NDM configurations for recommended Hayes Advanced Technology (AT) command strings
Cable between modem and NDM is not connected.
Verify cable connection between modem and NDM.
NDM is turned off.
Verify that NDM is turned on.
Incorrect modem configuration
Verify Auxiliary Access configurations to recommended Hayes AT command string.
No communication to supervisory system. Port (n) Active N2 Dialer is indicated instead of Port (n) Active Supervisory System. Note: If communication handshake to the supervisory system (modem or cable connection) is incorrect, the port connection message defaults to Port (n) Active N2 Dialer.
No communication to ASC devices, even though Port (n) Active Supervisory System indicates connection to supervisory system.
Controls Group 507 E. Michigan Street P.O. Box 423 Milwaukee, WI 53201
Verify supervisory system modem setup with Modem PRO for recommended local Hayes AT command strings. No cable connection and/or incorrect cable configuration between modem and supervisory system.
Verify cable connection and configuration between modem and supervisory system.
Incorrect null modem cable
Verify that the correct null modem cable is used as shown in Figure 9.
Remote supervisory system is turned off.
Verify that remote supervisory system is turned on.
ASC devices are offline to the supervisory system.
Use VT-100 emulation to verify that all ASC devices are online to the supervisory system.
ASC hardware devices are not mapped in the supervisory system.
Use VT-100 emulation to verify that all ASC hardware devices are mapped in the supervisory system.
N2 Bus problems
See the ASC and N2 Bus Networking and Troubleshooting Guide (LIT-6363003) to verify and resolve N2 Bus problem.
www.johnsoncontrols.com Printed in U.S.A.
