Metasys Integrator 300 Series Commissioning

Transcription

1 Metasys Connectivity Technical Manual Section Technical Bulletin Issue Date 0900 TECHNICAL BULLETIN 300 Series Commissioning 300 Series Commissioning...3 Introduction...3 Key Concepts...5 Related Information... 5 Software... 5 Component Requirements... 5 Port Connections... 6 VT100 Terminal Emulator Setup... 8 Vendor Communication Tables (.VCT)... 8 Advanced Diagnostics... 9 Procedure Overview...10 Detailed Procedures...11 Inspecting the Installation Configuring a VT100 Terminal Emulator for the Unit Using the Commissioning Menu Setting Up Ports Installing DOWNPC and Vendor Communication Tables (.VCT) Downloading Vendor Communication Tables (.VCT) Connecting Vendor-Specific Cabling Adding Vendor Devices to the Network Deleting Vendor Devices Modifying Vendor Devices Verifying Vendor Device Communications Johnson Controls, Inc. Code No. LIT

2 2 Verifying Point Data Saving Configuration Restarting Software Troubleshooting...26 Verifying N2 Bus Communication Using the N2 Bus Checkout Tool Using the Serial Data Analyzers Collecting Screen Data Using Advanced Diagnostics Troubleshooting Commissioning Problems... 34

3 300 Series Commissioning Series Commissioning Introduction Commissioning the unit begins after the installation procedures are complete. For information on those procedures, refer to the 300 Series Installation Technical Bulletin (LIT ) in this manual. This document explains commissioning of 300 Series. Use this document with the vendor-specific application notes, which contain specific details about integrating vendor equipment (e.g., cable pinouts and point mapping tables). For information on vendor controllers, see vendor documentation (obtainable from your vendor representative). This technical bulletin describes how to: inspect the installation configure a VT100 Terminal Emulator for the unit use the Commissioning menu set up ports install DOWNPC and vendor communication tables (.VCT) download vendor communication tables connect vendor-specific cabling add vendor devices to the network delete vendor devices modify vendor devices verify vendor device communications

4 4 verify point data save configuration restart software After commissioning the hardware and software, map the vendor controller points to the Metasys controller. These procedures are described in the various network setup technical bulletins. For information on installing a unit and setting up a site, please refer to Table 1.

5 300 Series Commissioning 5 Key Concepts Related Information Table 1: Related Information Table 1 describes where to find information on how to perform tasks other than commissioning a unit. Description Tab Document Mounting an EN-EWC25-0 Enclosure Installing a Unit UPM Universal Packaging Module Technical Bulletin (LIT , FAN 636.3) 300 Series Installation Technical Bulletin (LIT , FAN 629.5) Point Mapping 300 Series Point Mapping Technical Bulletin (LIT , FAN 629.5) Specific Vendor Application Information The appropriate vendor application note (FAN 629.5) Software The firmware on the electronics board contains: commissioning software (for defining and downloading vendor configuration) vendor and N2 open protocol support software In addition, there is one CD-ROM containing the download software,.vct files, the N2 Bus Checkout Tool, and software models in DDL syntax for all applications. The Performance Support Tool (TL-PSTMIG-0) is also available. This tool is a full-featured electronic performance support system that supports the installing, commissioning, and servicing of the unit and standard Metasys Integrator applications. Component Requirements Besides the properly installed vendor equipment and Metasys Integrator unit, the following is required: software CD-ROM labeled Tables and Models. Use software CDs with a revision number that matches the firmware revision number shown on the top line of the commissioning interface.

6 6 N2 Bus for connecting the unit to the Metasys or Metasys Companion Network. See the N2 Communications Bus Technical Bulletin (LIT ) in the Metasys Companion Technical Manual (FAN 628.1) for information. RS-232 cable for connecting the unit to vendor equipment. You will find pinouts for this cable in the vendor-specific application note. (For example, cable pinouts for connecting Fireye equipment are in the Fireye Application Application Note [LIT ] located in the Metasys Connectivity Technical Manual [FAN 629.5].) portable DOS-compatible Personal Computer (PC) with hard drive (4 Mb available disk space) VT100 Terminal emulation software for commissioning and setup of panel or Performance Support Tool (PST) RS-232 cable for connecting the portable PC to the Metasys Integrator unit. The pinouts for this cable are described in Terminating Wire Connections in the 300 Series Installation Technical Bulletin (LIT ). Port Connections The unit has an N2 port, a commissioning port, and two vendor ports. It connects to the Metasys N2 bus via the N2 terminal block. An external 24 VAC power supply is connected to the power connector. 24 VAC N2 Port Commissioning Port (Port 1) Vendor Port A (Port 2) Vendor Port B (Port 3) 300_side.cdr Figure 1: Unit Connections

7 N Series Commissioning 7 Commissioning Port Cabling Figure 2 shows an overview of how to connect a Personal Computer (PC) with a VT100 Terminal Emulator to the commissioning port on the unit. PC with VT100 Terminal Emulator 9-pin to 9-pin Null Modem Cable 300cable Figure 2: Cabling Overview An RS-232 cable is required between the Commissioning Port and the portable PC s serial port, (for example, COM1). Direct connections between the unit and the portable PC can have a distance of up to 13 feet. Figure 1 shows the location of the commissioning port (Port 1) on the electronics board. Figure 3 shows cable pinouts for a portable PC with either a 9-pin serial port or a 25-pin serial port. If the PC has a 9-pin port, use this cable: If the PC has a 25-pin port, use this cable: Terminal Port on Serial Port 1 or 2 on Portable PC Terminal Port on Serial Port 1 or 2 on Portable PC DB-9 Female DB-9 Female DB-9 Female DB-25 Female Signal DCD RD TD DTR GND DSR RTS CTS Pin RS-232 (13 ft maximum) Pin Signal DTR TD RD DCD GND DSR CTS RTS Signal DCD RD TD DTR GND DSR RTS CTS Pin RS-232 (13 ft maximum) Pin Signal DTR TD RD DCD GND DSR CTS RTS intech9 Figure 3: Unit to PC Cable Pinouts

8 8 Vendor Port Cabling An RS-232 cable is required between Vendor Ports A and B (P2 and P3) and the vendor communications interface. For pinouts for this cable, see the vendor-specific application note for the vendor equipment you are integrating. The RS-232 cable length between the unit and the vendor communications interface may not exceed 50 feet. IMPORTANT: For baud rates faster than 19,200 bps, the serial cables must be shorter than 4 m (13 ft). VT100 Terminal Emulator Setup The Performance Support Tool (MS-PSTMIG-0) includes a VT100 Terminal Emulator that is already configured to communicate with the unit. You can use any terminal emulation software, provided that it supports the VT100 Terminal type. Table 2: VT100 Terminal Emulator Configurations Field Value Data Bits 8 Parity Stop Bits 1 Baud Rate Flow Control No Same baud rate as the unit (57,600 default) Software flow control Vendor Communication Tables (.VCT) The.VCT files contain information that allows the unit to communicate with vendor equipment. The unit can contain up to 36.VCT files. See the vendor-specific application documents for the name of the.vct files you will need to download.

9 300 Series Commissioning 9 Advanced Diagnostics You can view the unit s operational status by selecting Advanced Diagnostics from the main menu. Resetting the Unit Advanced Diagnostics in the main menu provides a reset function to restart the software. See the Restarting Metasys Integrator Software section in this document. The Error Log screen will help you to determine the cause of the last reset. Recommissioning the Unit The unit must be recommissioned in the following circumstances: upgrading to a new firmware revision (refer to Project Builder User s Guide [LIT ]) located in the M-Tool Manual [FAN 693] for information on how to download code to a unit) downloading updates to an application previously downloaded The downloaded vendor communication tables (.VCT files) are stored in backed-up Random Access Memory (RAM) (provided the battery is good). Error Log Pressing F2 from the Advanced Diagnostics screen can access the Error Log screen. The Error Log displays the cause of the last reset, as well as any other serious errors that may have occurred since the log was last cleared. Note: If the error log contains an Exception Occurred! error, contact the Field Support Center. The log contains up to 256 entries. Once the error log contains 256 entries, it will no longer add new entries. A full error log must be cleared by selecting Yes from the Clear Error Log prompt before it will log any more errors.

10 10 Procedure Overview Table 3: 300 Series Commissioning To Do This Inspect Installation Configure a VT100 Terminal Emulator for the Metasys Integrator Unit Use the Commissioning Menu Set Up Ports Install DOWNPC and Vendor Communication Tables (.VCT) Download Vendor Communication Tables (.VCT) Connect Vendor-specific Cabling Add Vendor Devices to the Network Delete Vendor Devices Modify Vendor Devices Verify Vendor Device Communications Verify Point Data Save Configuration Restart Software Follow These Steps: Remove the enclosure door. Examine the N2 terminal block. Check the wire insulation. Verify the wire polarity of the N2 Bus connection. Verify that the power cable is properly connected. Configure the VT100 Terminal Emulator. Connect the VT100 Terminal Emulator to the commissioning port. Press Enter when the option you choose is highlighted, or type the first letter of the menu option. From the Commissioning menu, select Port Configuration. Enter information in fields. Match the settings you enter to the vendor equipment settings. Save the information to database. Insert the CD-ROM labeled Tables and Models. Run the setup.exe file on the CD-ROM and follow the on-screen instructions. Make sure the portable PC is properly connected to Commissioning Port. Exit the terminal emulation software and go to DOS. Change the directory to the directory where you installed the DOWNPC software. Type DOWNPC. Accept the default serial port or select the port on the PC that connects to Commissioning Port. Press Enter when the correct port displays. Select the correct baud rate and press Enter. Select the.vct file to be downloaded. Press Y to confirm the file. When the download is complete, press any key. Restart the VT100 Terminal Emulation software. Enter F1 to refresh the main menu. Refer to the vendor-specific application notes for the cable pinouts. Assemble and connect the cabling. Disconnect the N2 Bus connection from unit until proper communication with the vendor equipment has been verified. From the Commissioning menu, select the Network Modify/Add/Delete option. Specify the network configuration for each of the vendor devices. To display the next screen of network addresses, press F3. To go to a specific N2 address, press F4. Save the information to database and return to the Commissioning menu. Move the cursor to the Interface Type field of the device you want to delete. Scroll through the options until a blank name is selected. Save the changes. Move the cursor to the Interface Type field of the device whose settings you want to change. Scroll through the options until a blank name is selected. Delete the device. Add the device. Save the changes. Display the Device Diagnostics screen. Enter the device s N2 address and press Tab or Enter twice. Press F2 to display the device specific data analyzer. Press F3 to view statistics for the next N2 address. Display the Vendor and N2 Port Diagnostics screen if no devices for the vendor port are online. Press F2 or F3 to display the port analyzer. From the Commissioning menu, select the Show Point Data option. Enter the point s network address, point type, and point address. To accept the default, press Enter. After you specify the point, press Enter. After viewing the points you wish to see, return to the Commissioning menu. Collect screen data. From the Advanced Diagnostics screen, press F3. Change the reset option. Press Enter to select and execute the option.

11 300 Series Commissioning 11 Detailed Procedures Inspecting the Installation To inspect the connections and wire terminations on the electronics board: 1. If the unit is enclosed, remove the enclosure door. 2. Examine the N2 terminal block for stray wire strands, loose screw terminals, and nicked, loose, or broken wires. 3. Check the wire insulation to ensure that it has not been stripped back so far as to cause a short, or that it is not tucked under a screw terminal. 4. Verify the wire polarity of the N2 Bus connection. (Check that each screw terminal of the N2 block has the same wire color entering as it does exiting.)! CAUTION: Ground yourself before handling the electronics board. 5. Verify that the power cable is properly connected. Configuring a VT100 Terminal Emulator for the Unit A pre-configured VT100 Terminal emulator is available in the Performance Support Tool (PST). You can use any terminal emulation software, provided that it supports the VT100 Terminal type. Terminal emulation software that has been successfully used is shown in Table 4. For more information on terminal emulation software setup, see the respective terminal emulator literature.

12 12 1. To configure a VT100 Terminal Emulator for the Metasys Integrator unit: Table 4: Terminal Emulation Software Setup Parameters Setting Value Command Used ProComm Plus for DOS by Datastorm Technologies, Inc. Baud Rate 57,600 Data Bits 8 Line/Port Setup (Alt-P) Parity Stop Bits 1 Flow Control Terminal Emulation None Xon/Xoff VT100 or VT102 Setup Facility, Terminal/General Options (Alt-S) ProComm Plus for Windows by Datastorm Technologies, Inc. Baud Rate 57,600 Data Bits 8 Parity None Setup/Extended Menu/Port Setting Stop Bits 1 Flow Control Xon/Xoff Current Terminal VT100 Setup/Extended Menu/Terminal Options HyperTerminal for Windows 95 by Hilgraeve, Inc. Bits Per Second 57,600 Data Bits 8 Parity None Stop Bits 1 Flow Control Xon/Xoff Emulation VT100 Properties/Settings Terminal for Windows by Microsoft Corporation Baud Rate 57,600 Data Bits 8 Properties/Phone Number/Configure/Port Settings Parity None Settings/Communications Stop Bits 1 Flow Control Xon/Xoff Emulation DEC VT100 Settings/Terminal Emulation 2. Connect the VT100 Terminal Emulator to the commissioning port (Port 1).

13 300 Series Commissioning 13 Using the Commissioning Menu When you connect a portable PC with VT100 Terminal emulation software to the unit, the Commissioning menu shown in Figure 4 appears. Use this menu to set up the unit. Commissioning Menu REL 9.00 Mon Aug 16, :47 Show Point Data Network Modify/Add/Delete Port Configuration Device Diagnostics Vendor and N2 Port Diagnostics Advanced Diagnostics Quit Standard Firmware F1 Refresh Menu Press F1 to refresh or to return to this menu at anytime. Figure 4: Commissioning Menu To move the highlight between menu options, use the arrow keys or the space bar. To select a menu option, press Enter when the first letter of the menu option is highlighted, or type the first letter of the menu option. (For example, type S to choose Show Point Data.)

14 14 Table 5: Commissioning Menu Options Menu Option Description Commissioning Show Point Data Displays data about available points in vendor device. Allows you to verify proper operation of vendor equipment (e.g., whether points are online and normal). Network Modify/Add/Delete Port Configuration Device Diagnostics Vendor and N2 Port Diagnostics Advanced Diagnostics Quit Allows you to add vendor devices to the network. You specify the interface type, vendor address, trunk, timeout, and poll delay for each N2 address. Allows you to set up ports for communication with the portable PC (commissioning device) and two vendor trunks. You specify baud rate, word length, stop bits, parity, and interface type for each vendor port. Displays statistics for communications between the Metasys Integrator unit and vendor device at a specified N2 address (e.g., writes, commands, and retries). Helps you verify network communication and diagnose problems. Allows you to reset statistics and activate serial data analyzer for a specific device. Displays communication statistics for each vendor port and the N2 port. Serial data analyzers, which display all activity on an entire vendor port, are also available. Displays the operational status of the unit, and provides access to the Error Log and Reset screens. Exits Commissioning menu.

15 300 Series Commissioning 15 Setting Up Ports To set up the port and baud rate for communication between the unit and the vendor devices: 1. From the Commissioning menu, select Port Configuration. The Port Configuration screen appears, as shown in Figure 5. Port Configuration REL 9.00 Mon Aug 16, :47 Port/Usage Baud Rate Word Length Stop Bits Parity Interface PO - N2 [ 9600] [8] [1] [None] [RS485] P1 - Commissioning [57600] [8] [1] [None] [RS232] P2 - Vendor A [ 9600] [8] [1] [None] [RS232] P3 - Vendor B [ 9600] [8] [1] [None] [RS232] F1 Cancel F2 Save Select baud rate (300,600,1200,2400,4800,9600,19200,38400,57600) Figure 5: Port Configuration Screen 2. Either type the information or use the space bar to scroll through the valid options to enter information in a field. To move between fields, press Enter or Tab, or use the arrow keys. The help line at the bottom of the screen displays information about the field where the cursor is. The N2 Port (P0) has fixed settings. Changing the P1 commissioning port settings can prevent you from communicating using the VT-100 Emulator software. For Vendor Ports A and B (P2 and P3), make sure the settings you enter match the vendor equipment settings. The vendor equipment settings are listed in the vendor-specific application note. If your application has an RS-485 interface, set the vendor port to RS-485, and use an external RS-232 to RS-485 converter. This converter is described in the vendor-specific application note. 3. Press F2 to save the information to database. The Commissioning menu appears.

16 16 Installing DOWNPC and Vendor Communication Tables (.VCT) Install the DOWNPC software on your portable PC before downloading the.vct files. Have the CD-ROM labeled Tables and Models on hand. To install the download software on your portable PC: 1. Insert the CD-ROM labeled Tables and Models in the CD-ROM drive. 2. Run the setup.exe file on the CD-ROM and follow the on-screen instructions. Alternatively, you can manually copy the files that you need from the Tables and Models CD-ROM. If you do not know what files you need, run setup.exe. Downloading Vendor Communication Tables (.VCT) After installing the DOWNPC software, download the appropriate.vct files to the unit. Up to 36.VCTs may be downloaded. To download the.vct files: 1. Make sure the portable PC is properly connected to Metasys Integrator commissioning port. 2. Exit the terminal emulation software and go to DOS. 3. Change to the directory where you installed the DOWNPC software. The default is C:\\MIG9\Tables. 4. Type DOWNPC (not case sensitive). The following appears: Download Utility (c) Johnson Controls Inc. Revision 9.00 Serial Port: COM1 (COM1 or COM2) Select Baud: (9600, 19200, 38400, 57600) File Name:.VCT (Select from the list) 5. Accept the default (COM1) serial port or type COM2 to select the port on the PC that connects to commissioning port. Press Enter when the correct port displays.

17 300 Series Commissioning Select the correct baud rate to match the baud rate of the commissioning port on the unit and press Enter. The screen shown in Figure 6 appears, displaying currently available vendor communication table files. Download Utility (c) Johnson Controls Inc. Revision 9.00 Serial Port:COM1 (COM1 or COM2) Select Baud:57600 (9600, 19200, 38400, 57600) File Name:.VCT (Select from the list) Vendor Communication Table Files (.VCT) AD_AUTPX CA_DUAL CA_S2100 CA_SIGL CB_HAWK CB_NHBP CB_NHGP CC_FHVC CC_FRPC FE_E501 FE_E503 GE_EPIC IQ_1000 IQ_ADVA IQ_AEM IQ_AEMDI IQ_AEMDP IQ_DATA IQ_GENE LI_LEV0 LI_LEV1 LI_LEV2 MS_CHILL SG_CENC SG_RCPC SG_RTUA SG_UVNT SG_WSHP SG_XLWC SQ_CM100 TA_FHVC TS_8650 TS_8670 VM_EVPCD VM_RECIP VM_SSCRW M_TSCRW..End.. Page 1 of 1 Figure 6: Download Screen 7. Select a.vct file to download in one of two ways: Type the name of the file to download in the File Name field. This name must match the name in the.vct file list displayed on the Download screen. Select the file name from the.vct file list by pressing the Tab key once, then using the function keys listed in Table Press Enter. The screen shown in Figure 7 displays for.vct files, briefly describing the selected file. Table 6: Download Select Function Keys Key Tab Backspace A through Z PGUP (Page Up) PGDN (Page Down) Space Bar F1 Key or Esc Function Highlights the next file name in the list. Highlights the previous file name in the list. Highlights the first file name beginning with that letter, if one exists. Displays the previous page of file names. Displays the next page of file names. Highlights the next file name in the list. Exits without downloading.

18 18 Download Utility (c) Johnson Controls Inc. Revision 9.00 Set to Download table to Integrator Panel Carrier DC Chiller OK To Download (Y/N) Figure 7: Download Confirm Screen 9. Press N to return to the.vct file name list shown in Figure 6. Press Y to begin downloading. The screen in Figure 8 displays. Download Utility (c) Johnson Controls Inc. Revision 9.00 Serial Port: COM1 Select Baud: Word Length: 8 Stop Bits: 1 Parity: None File Name: CA_DUAL.VCT Table Size: 1048 ooooooooooooooooooooooooooooooooooooooooo 0 Percent Complete Figure 8: Download in Progress Screen The solid bar moves right across the screen as the download continues. When complete, the following appears: Download completed without errors Press Any Key To Exit Download Note: If there is an error, attempt the download again. 10. Press any key. To download another table, type DOWNPC and start the procedure again. Note: Do not download the same table more than once. A single table can be used for multiple vendor devices of the same type. 11. Restart the VT100 Terminal emulation software.

19 300 Series Commissioning Press F1 to refresh the Commissioning menu. Connecting Vendor-Specific Cabling To connect vendor-specific cabling: 1. Refer to the vendor-specific application notes for the cable pinouts. 2. Assemble and connect the cabling between the unit and the vendor equipment. Adding Vendor Devices to the Network See the vendor-specific application note for the correct vendor address and timeout values. To add a vendor device to the network, you must have already downloaded its vendor communication table (.VCT file). To add the device to the network: 1. To avoid annoying messages at the Metasys system, disconnect the N2 Bus connection from the unit until proper communication with the vendor equipment has been verified (see Verifying Vendor Device Communications and Verifying Point Data in this document). 2. From the Commissioning menu, select the Network Modify/Add/Delete option. The screen shown in Figure 9 appears. Network Modify/Add/Delete REL 9.00 Mon Aug 16, :47 N2 Address Interface Type Vendor Address Port Timeout Poll Delay Retry 0 [ ] [ ] [A] [ ] [ ] [ 3] 1 [Carrier DC Chiller] [A ] [A] [ 8000] [ 550] [ 3] 2 [Carrier SC Chiller] [B ] [A] [ 8000] [ 550] [ 3] 3 [CB Hawk Boiler Ctl] [0,1 ] [B] [ 5000] [ 55] [ 3] 4 [ ] [ ] [A] [ ] [ ] [ 3] 5 [ ] [ ] [A] [ ] [ ] [ 3] 6 [ ] [ ] [A] [ ] [ ] [ 3] 7 [ ] [ ] [A] [ ] [ ] [ 3] Available Vendor Interface Types Carrier DC Chiller Carrier SC Chiller CB Hawk Boiler Ctl F1 Cancel F2 Save F3 More F4 Go to N2 Address Select a vendor interface type from the list Note: Make sure these N2 addresses match the N2 addresses defined at the Metasys system. Figure 9: Network Modify/Add/Delete Screen

20 20 Deleting Vendor Devices Modifying Vendor Devices 3. Specify the network configuration for each of the vendor devices. To enter information in a field, you can either type the information or use the space bar to scroll through the valid options. To move between fields, press Enter or Tab, or use the arrow keys. The help line at the bottom of the screen displays information about the field where the cursor is. Note: N2 Address 0 can be defined at the unit, but cannot be used at the Metasys system. 4. To display the next screen of network addresses, press F3. Pressing F3 also saves the current screen of data. 5. To go to a specific N2 address, press F4. Pressing F4 will save the current screen of data. 6. To save the information to database and return to the Commissioning menu, press F2. To delete a device: 1. Move the cursor to the Interface Type field of the device you want to delete. 2. Press the space bar to scroll through the options until a blank name is selected. 3. Press F2 to save the changes. Note: If a scan is in progress for a deleted device, it will be deleted after the scan is complete. To modify the settings for a vendor device, delete the device and add the device with the new settings: 1. Move the cursor to the Interface Type field of the device whose settings you want to change. 2. Press the space bar to scroll through the options until a blank name is selected. 3. Press F2 to delete the device. 4. Add the device by filling in the new settings. 5. Press F2 to save the changes. Note: If communication is still in progress with the device deleted in Step 3, the unit will display the following error message: cannot add until previous delete is completed.

21 300 Series Commissioning 21 Verifying Vendor Device Communications To verify vendor device communication: 1. Display the Device Diagnostics screen (Figure 10). 2. Enter the device s N2 address and press Tab or Enter twice. 3. If the vendor device is offline, press F2 to display the device specific data analyzer to determine if there is any communication. 4. Press F3 to view the statistics for the next N2 address that has been defined at this unit. 5. If no devices for the vendor port are online, display the Vendor and N2 Port Diagnostics screen (Figure 11) for vendor port statistics. 6. From the Vendor and N2 Port Diagnostics screen, press F2 or F3 to display the port analyzer. This will help you to determine if there is any communication with any vendor device on the port. Device Diagnostics REL 9.00 Mon Aug 16, :47 N2 Address [ 1] Reset Statistics [No ] CB Hawk Boiler Ctl at N2 Address [ l] on Vendor Port A: Online [Yes] Transmissions/Minute [ 5] Writes [ 17] Scan Time (seconds) [ 12] Commands [ 2] Retries [ 1] Offline [ 0] Errors [ 1] F1 Cancel F2 Data Analyzer F3 Next N2 Address Select an N2 address (0-255) Figure 10: Device Diagnostics Screen

22 22 Port Diagnostics REL 9.00 Mon Aug 16, :47 Reset Statistics [No ] Vendor Port A Vendor Port B N2 Port Transmissions/Minute [ 38] [ 0] Scan Time (seconds) [ 2] [ 0] Port Buffer Overruns [ 0] [ 0] [ 0] LINE STATUS ERRORS *Suspect Bytes Received [ 0] [ 0] [ 0] *Framing Errors [ 0] [ 0] [ 0] *Parity Errors [ 0] [ 0] F1 Cancel F2 Port A Analyzer F3 Port B Analyzer Select from (No, Yes) Figure 11: Vendor and N2 Port Diagnostics Screen For additional information on diagnostics fields, see Table 7 and Table 11. For additional information on the serial data analyzer, see the Using the Serial Data Analyzers section in this technical bulletin.

23 300 Series Commissioning 23 Table 7: Diagnostics Fields Field Description Normal Readings Device Vendor and N2 Port Vendor Device Statistics for Selected N2 Address N2 Address Online Writes Selected N2 Address (with vendor table name) Indicates whether device is currently online Number of general communications messages Commands Number of commands to device X Retries Errors Offline Reset Statistics Transmissions Per Minute Point Scan Time (seconds) Port Buffer Overruns LINE STATUS ERRORS: Suspect Bytes Received Framing Errors Parity Errors Number of retries for polls and writes for online devices only Number of times a returned message from vendor device had an error (for example, a CRC or checksum error) Number of online to offline transitions for device at this vendor address Yes 0 is ideal. X 0 is ideal. X 0 is ideal. X Allows you to reset statistics to zero No is default. X X Port Statistics Number of polls and writes that occurred in last minute Number of seconds it takes for all points on this vendor trunk to be scanned Number of Vendor Port A, Vendor Port B, and N2 Port input buffer overruns on the UART s First In-First Out (FIFO) Number of line status errors in general Number of line status errors caused by framing errors Number of line status errors caused by parity errors Depends on vendor device response time and poll delay Depends on transmissions per minute, vendor device response time, and poll delay 0 is ideal. X 0 is ideal. X 0 is ideal. X 0 is ideal. X X X X X X X X

24 24 Verifying Point Data Before mapping vendor points to the Metasys Network, verify that vendor equipment and processes are operating properly. To view point data use the Show Point Data screen, which displays current point data in the vendor controllers: 1. From the Commissioning menu, select the Show Point Data option. The following fields appear, prompting you to specify a point: N2 Address [ 1] Point Type [AI ] Point Address [ 1] 2. Enter the point s network address, point type, and point address. To accept the default, press Enter. (If the cursor is in the N2 Address field, press Enter three times to accept the default.) To move between fields, press Enter or Tab, or use the arrow keys. To scroll through the Point Type options (AI, BI, AO, BO, ADF, ADI, BD), press the space bar repeatedly when the cursor is in the Point Type field. 3. After you have specified the point, press Enter. The Show Point Data screen appears. Figure 12 shows an example of a Show Point Data screen for an AI point. (Each Show Point Data screen displays data appropriate to the point type.) Show Point Data REL 9.00 Mon Aug 16, :47 Network Address: N2 Address [ 1] Point Type [AI ] Point Address [ 1] N2 Address [ 1] Point Type [AI ] Point Address [ 1] Point Label LCW TEMP Value High Alarm Limit Undefined High Warning Limit Undefined Differential Undefined Low Warning Limit Undefined Low Alarm Limit Undefined COS Enable False Alarm Enable False Warning Enable False Unreliable False Override Active False Out-of-Range High False Out-of-Range Low False COS Status Normal F1 Cancel F3 More Select a N2 network address (0-255) Figure 12: Show Point Data Screen

25 300 Series Commissioning Press F3 More to view the next point, which scrolls through the points. When the last point of a type is reached, the first point of the next type is displayed. 5. Press F1 Cancel to return to the Commissioning menu. Saving Configuration Record the settings for configuration. You can do this manually, or use a screen capture utility. See Collecting Screen Data in the Troubleshooting section of this document for additional information. Restarting Software To restart software: 1. From the Advanced Diagnostics screen in the main menu, press F3. The Reset screen displays. 2. Change the reset option by using the space bar. 3. Press Enter to select and execute the option you choose.

26 26 Troubleshooting This section provides troubleshooting information for the commissioning process. Verifying N2 Bus Communication The N2 network is confirmed when you invoke the head-end workstation software (for example, Metasys Operator Workstation [OWS]), define vendor devices and points, and display information about the points on the workstation screen. If something does not work correctly: 1. Verify that the vendor equipment is energized. 2. Verify that the vendor points are appropriately defined in software. 3. Recheck the N2 wiring connections throughout the network, including the N2 terminal blocks on the electronics board. Using the N2 Bus Checkout Tool Some jobs require extensive end-to-end checkout on site with vendor equipment and a supervisory system. The N2 Bus Checkout Tool allows engineers to do the checkout at the Metasys Integrator panel with a tool that uses the same table loaded in the panel. You can check out the vendor system and its interface with the unit all the way from the Metasys Integrator N2 terminals to the vendor equipment. The user interface accepts any N2 address and a Release 5.0 or greater.vct table as inputs.

27 300 Series Commissioning 27 The N2 Bus Checkout Tool requires the following: a laptop with an available serial port an RS-232 to RS-485 converter (You can use the MM-CVT101. The cable for the MM-CVT101 is defined in Figure 13.) Serial Port 1 or 2 on Portable PC DB-9 Female RS-232 Connector on MM-CVT101 Converter DB-25 Male Signal RD TD GND RTS Pin RS-232 Pin Signal RD TD GND RTS (50 ft maximum) intconv Figure 13: Cable Pinouts Between Unit and Converter The cable connects the serial port on the laptop to the 25-pin RS-232 serial connector on the MM-CVT101. The RS-485 (N2) connection from the MM-CVT101 is then attached to the panel N2 connections. See Terminating Wire Connections in Metasys Integrator 300 Series Installation Technical Bulletin (LIT ) for additional information. Table 8 shows the available mouse sensitive operation fields displayed between the dashed delimiter lines. Click the mouse on these items to execute the function. Table 8: Mouse Sensitive Function Keys Function Key AI BI AO BO ADF ADI BD RSt Operation Performed Select AI points for display. Select BI point for display. Select AO points for display. Select BO points for display. Select ADF points for display. Select ADI points for display. Select BD points for display. Reset N2 statistics. NuAdr Select a new N2 address (1 to 255). NuVct Pgdn PgUp Exit Select a new.vct file name. Page down the points list. Page up the points list. Return to DOS (the Alt-X key does the same).

28 28 Table 9 shows the statistics that are displayed on the right-hand side of the screen. The N2 Statistics values will roll over at Table 9: Point Counts and N2 Statistics Point Counts AI BI AO BO ADF ADI BD N2 Statistics Poll Data OvrC RelC COSs NAks CksE LnSE RTry OffL Description Count of Analog Inputs in current table Count of Binary Inputs in current table Count of Analog Outputs in current table Count of Binary Outputs in current table Count of Analog Data Floats in current table Count of Analog Data Integers in current table Count of Binary Data (Byte) in current table Description Number of polls Number of data requests Number of override commands Number of release commands Number of change-of-state responses Number of negative acknowledge responses Number of checksum errors Number of line status errors Number of retries Number of offline occurrences Figure 14 shows a screen snapshot of the tool in use. N2 Bus Checkout Tool at address 1 using rileyhsp.vct AI BI AO BO ADF ADI BD RSt NuAdr NuVct PgDn PgUp Exit AO PICU 1 Supply Airflow Setpoint... -Pt Count- AO PICU 1 Min Exhaust Airflow Setpoint... AI 30 AO PICU 2 Supply Airflow Setpoint... BI 16 AO PICU 2 Min Exhaust Airflow Setpoint... AO 32 AO Anteroom Supply 1 Airflow Setpoint... BO 0 AO Anteroom Supply 2 Airflow Setpoint... ADF 0 AO Anteroom Min Exhaust Airflow Setpoint. ADI 0 AO PICU 1 Pressure Setpoint... BD 0 AO PICU 2 Pressure Setpoint... AO Anteroom Pressure Setpoint... -N2 Stats- AO Iso-Tek 0 High Alarm Setpoint... Poll 0 AO Iso-Tek 0 Low Alarm Setpoint... Data 0 AO Iso-Tek 1 High Alarm Setpoint... OvrC 0 AO Iso-Tek 1 Low Alarm Setpoint... RelC 0 0 AO Iso-Tek 2 High Alarm Setpoint... COSs 0 0 AO Iso-Tek 2 Low Alarm Setpoint... Naks 0 AO PICU 3 Supply Airflow Setpoint... CksE 0 AO PICU 3 Min Exhaust Airflow Setpoint... LnSE 0 X AO PICU 4 Supply Airflow Setpoint... RTry 100 Figure 14: N2 Bus Checkout Tool Screen

29 300 Series Commissioning 29 To perform the check: 1. Remove all N2 connections other than the RS-485 connection from the MM-CVT101 that is attached to the panel. 2. Start the N2 Bus Checkout Tool from the DOS command line by typing the command N2CHECK 1 for COM1 or N2CHECK 2 for COM2. 3. Click NuAdr to select an N2 address. 4. Click NuVct to select the same.vct that you downloaded into the panel. 5. Use the mouse to select the point type you want to inspect or command. Command AO and BO point types by clicking on the point line and entering a new value. Click on the point line and pressing the Esc key to perform a release command. 6. Press the Alt+X key to exit to DOS. Using the Serial Data Analyzers The commissioning software provides serial data analyzers for troubleshooting communication between the unit and the vendor devices. The serial data analyzers collect data from the devices on a vendor port. This aids in establishing whether or not communication is occurring. To access the device specific serial data analyzer from the Device Diagnostics screen, enter F2. To access the vendor port serial data analyzer from the Port Diagnostic screen, enter F2 for Vendor Port A or F3 for Vendor Port B. To pause the flow of data, press F4. To resume the flow of data, press F4 again. To exit the serial data analyzer, press F1. To return to the Diagnostics screen, press F2. To view a log of the last abnormal events that occurred on a particular port, press F3 from that port s serial data analyzer screen. To record the data being sent to the screen in a text file, use the logging capabilities of your VT100 Terminal emulation software (for example, ProComm Plus Log File function). Note: Recording more than one screen of data requires ProComm Plus for DOS or the Performance Support Tool. If you need help interpreting the data, call your product supplier.

30 30 Collecting Screen Data You may need to collect screen data when getting help from a technical support person. The PST or ProComm Plus for DOS Version 2.01 is required for log file captures. We do not recommend ProComm Plus for Windows, HyperTerminal for Windows 95 by Hilgraeve, Inc., and Terminal for Windows by Microsoft Corporation. Table 10 shows the available Capture Data commands. Table 10: Capture Data Commands Command Used Description of Operation Performance Support Tool VT100 Emulator (Ctrl-I) Starts VT100 Terminal Emulator. Log File Pause Logging Resume Logging Create log file name, or browse to select an existing log file. Check Append to add data to end of an existing file. Click OK to start capture. All screens opened after clicking OK are saved to the log file. Pauses log file capture. Resumes log file capture. Stop Logging Stops log file capture. ProComm Plus for DOS by Datastorm Technologies, Inc. Screen Snapshot (Alt-G) Log File On (Alt-F1) System will reply: Enter log filename, or CR for default:. The default log file name is PCPLUS.LOG. The status line will show LOG OPEN. Log File Off (Alt-F1) The status line will show LOG CLOSED. The file can be found at C:\PCPLUS\PCPLUS.LOG if default file name was used. ProComm Plus for Windows by Datastorm Technologies, Inc.* Online / Capture (Alt-F1) Status line shows Capture File Opened - pwxx.cap where pwxx is the capture file name defaulted by the system. Online / Capture (Alt-F1) Status line shows Capture File Closed File can be found at C:\PROWIN2\CAPTURE\PWxx.CAP * Captures only the first screen of analyzer data.

31 300 Series Commissioning 31 Performance Support Tool To collect data with the PST VT100 Terminal Emulator: 1. Press the F1 key to return to the Commissioning menu. 2. Click on the Data Logging menu of the VT100 Terminal Emulator. 3. Click on Start. 4. Enter a log file name and click OK to start the log file capture. We recommend giving the file name a.log extension (filename.log) to make it easier to find later. Note: Click the Browse button to select the path to the log file. You can name the log file anything and save it anywhere. 5. Cycle through each menu item starting with Port Configuration and Network Modify/Add/Delete for each N2 address for which data must be collected. 6. For each N2 address: a. Bring up the Diagnostic menu for the N2 address. This displays the current number of offlines, retries, and errors. These statistics are available only for previously defined N2 addresses. b. Set the Serial Data Analyzer to Yes. This will show the actual communications between the vendor device and the panel. c. Bring up the Diagnostic menu for the N2 address again. This displays the number of offlines, retries, and errors that can be used to determine how many of these errors occurred while saving the analyzer data. Note: Try to ensure that the collected data includes a sample of the problem you want to investigate. For example, if you are collecting data to determine the cause of offline/online transitions, ensure that the number of offlines has increased. If not, continue to collect analyzer data. 7. When all the data has been collected, click on the Data Logging menu of the VT100 Terminal Emulator. 8. Click Stop to end the log file capture. Note: The log file can be found at C:\Program Files\Johnson Controls\ Performance Support Tool\MIGData.log if the default directory and recommended file name extension were used. Otherwise, the file will appear in the directory you chose.

32 32 9. Send these files to your technical support representative via The Advisor or . ProComm Plus for DOS To collect the data with ProComm Plus for DOS: 1. Press the F1 key to return to the Commissioning menu. 2. Press Alt-F1 to start the log file capture. Note: You can name the log file if you choose; otherwise, the default name is PCPLUS.LOG. 3. Cycle through each menu item starting with Port Configuration and Network Modify/Add/Delete for each N2 address for which data must be collected. 4. For each N2 address: a. Bring up the Diagnostic menu for the N2 address. This displays the current number of offlines, retries, and errors. b. Set the serial data analyzer to Yes. This will show the actual communications between the vendor device and the panel. c. Bring up the Diagnostic menu for the N2 address again. This displays the number of offlines, retries, and errors that can be used to determine how many of these errors occurred while saving the analyzer data. Note: Try to ensure that the collected data includes a sample of the problem you want to investigate. For example, if you are collecting data to determine the cause of offline/online transitions, ensure that the number of offlines has increased. If not, continue to collect analyzer data. 5. When all the data has been collected, press Alt-F1 to close the log file and end the capture. Note: The log file can be found at C:\PCPLUS\PCPLUS.LOG if the default file name was used. Otherwise, the file appears in the PCPLUS directory under the name you assigned it. 6. Send these files to your technical support representative via The Advisor or .

33 300 Series Commissioning 33 Using Advanced Diagnostics Table 11 provides information on advanced diagnostics fields. Table 11: Advanced Diagnostics Fields Field Description Normal Readings 300 Flash Statistics MAC Address Startup Checksum/Revision Boot Code Checksum/Revision Main Code Checksum* Softscope Enabled/Disabled on Vendor Port A or B Softscope Stop at Startup? Similar to a serial number, every 300 Series has a unique 6-byte Media Access Control (MAC) address (displayed in dotted-decimal notation). Identifies the code that runs at initial power up or after a reset. Identifies the code that runs when the Metasys Integrator unit is reset to allow new main code to be downloaded. Checksum for the code. Indicates if debugging tool is enabled. If enabled, vendor communications is disabled on that port. If Yes, the unit will stop running after it is reset xxx.xxx.xxx Disabled No is default. Date of Manufacture Last four numbers represent the year that the unit was manufactured. Leading numbers represent the day of the year. CPU Utilization CPU Usage Percentage of total task utilization 0 to 100 Allocated Memory Statistics** Current Free** N2 Database Using Memory available for tables and N2 database in bytes, and as a percentage of the total allocated Memory used for the N2 database in bytes and as a percentage of total allocated. The N2 database stores point data for all vendor points. Memory is used as follows: 119 bytes overhead for each N2 address added, plus: 27 bytes for each AI point 5 bytes for each ADF point 3 bytes for each BI point 3 bytes for each BO point 3 bytes for each ADI point 7 bytes for each AO point 2 bytes for each BD point VCTs Using Amount of memory used for the downloaded vendor communication control tables in bytes and as a percentage of total allocated * The main code checksum can be verified to determine if this is standard vs. custom code. Also see the Commissioning menu, which indicates standard or custom firmware is downloaded. ** The current free allocated memory should not be less than 10%.

34 34 Figure 15 shows an example of an Advanced Diagnostics screen. Advanced Diagnostics REL 9.00 Sun Aug 15, : MAC Address: Date of Manufacture: [ ] Startup Checksum: [23E7] Startup Revision: [1.1] Boot Code Checksum: [6DB8] Boot Code Revision: [1.1] Main Code Checksum: [787B] SoftScope ENABLED on Vendor Port B. SoftScope Stop at Startup? [No]... : : : CPU Usage: [ 3.8] % : : : :...:... : M : ALLOCATED (Bytes) (%) : ACQUIRED (Bytes) (%) : : E : Current Free [475356] 95.1 : Current Free [150000] : : M : N2 Database Using [ 160] 0.0 : Largest Block Free [150000] : : O : VCTs Using [ 1599] 0.3 : Total [150000] : : R : Total [500000] : Lowest Free [149878] 99.9 : : Y : Lowest Free [475356] 95.1 : : :...:...:...: F1 Cancel F2 Error Log F3 Reset Press <TAB> or <ENTER> to refresh statistics. Figure 15: Advanced Diagnostics Screen Example Troubleshooting Commissioning Problems Table 12 lists some possible commissioning problems and solutions. Table 12: Possible Commissioning Problems Condition Problem Solution VT100 Terminal Emulation software is unable to connect to the Metasys Integrator unit. Continued on next page... There are incorrect communication settings. There is incorrect cabling. Verify that the portable PC s settings match the commissioning port settings (baud rate, bits, stop bits, parity). The default for the commissioning port is 57600,8,1,N. Verify that the Terminal emulation mode is set to VT100. Verify that the portable PC is connected to the commissioning port (P1 connector) on the electronics board. Verify that the RS-232 cable pinouts are correct as described in Figure.

35 300 Series Commissioning 35 Condition (Cont.) Problem Solution The unit cannot talk to the vendor device. Port 2 or Port 3 LED remains on. Point is unreliable (use Show Point Data menu option). Point values are incorrect, but point is reliable. The unit resets automatically. The unit resets cyclically. Continued on next page... Cable is not connected. Incorrect cable is being used. Incorrect settings are on the Port Configuration screen. An incorrect vendor address is entered in the Network Modify/Add/Delete screen. Softscope might be enabled for that port. The device is offline. The point does not exist at the vendor device. Custom firmware has not been downloaded. Commissioned with an incorrect.vct. Vendor equipment setup is incorrect. The unit has encountered a serious software error. The unit has encountered a serious software error. Verify that the cables are properly plugged into vendor ports. Verify that the vendor device is connected and powered up. Verify that the cable between the unit and vendor device matches the cable specified in the vendor application document. Verify that the vendor port setup matches the settings specified in the vendor application document. Verify that the vendor address entered in the Network Modify/Add/Delete screen is left justified. Call Field Support Center. Verify that the device is online. Verify that the point exists at the vendor device. If using a custom application that requires custom firmware, verify that this firmware has been downloaded. Verify that the correct vendor communication table (.VCT) is being used. Refer to vendor documents. View the Error Log screen (from the Advanced Diagnostics screen, press F2). Call the Field Support Center. Locate a blue button labeled SW2 on the unit circuit board. You must watch the LEDs to determine when to press the blue button. The startup sequence begins when all the LEDs light up at the same time. Each LED then lights up, individually. When the last LED turns off, wait about two seconds and then press the button. The startup sequence then should start over. When this sequence is complete, the red Fault LED turns on. Turn the unit off and then back on. It should come up with the factory default settings (no VCTs downloaded). Press A, then F2 to view the Error Log, and call the Field Support Center.

36 36 Condition (Cont.) Problem Solution Device repeatedly toggles online and offline. Database memory is not retained. Continuous line status errors occur for an RS-485 vendor trunk. Commissioned with incorrect.vct. The 485 converter is malfunctioning. The vendor device does not support commands. Battery may be dead. See the 300 Series Installation Technical Bulletin for startup Light-Emitting Diode (LED) battery failure indication. The vendor communication trunk is experiencing excessive noise or is unbalanced. Verify that the correct application for the device is being used. If a 485 or 422 port-powered converter is being used, use a converter that includes a power supply. If you are sending commands, verify that the device is commissioned to support commands. Be aware that the Auto Restore functions of Metasys NCM, Companion, or N30 will resend commands as devices report online. Replace the battery and recommission the Metasys Integrator unit. Verify End-of-Line (EOL) resistor and cable shield requirements and installation. Controls Group FAN E. Michigan Street Metasys Connectivity Technical Manual P.O. Box 423 Release 9.0 Milwaukee, WI Printed in U.S.A.