Bacharach LonWorks FT-10 manual

1 of 18 3015-4568 Revision 0 9/11/03 Installation Guide Bacharach HGM300 to LonWorks FT-10 Communications Adapter Introduction The Bacharach HGM300 to LonWorks Comm unications Adapter enables an HGM300 Refrigerant Monitor to communicate with a LonWorks FT-10 Free Topology network. Zone PPM readings, flow status, refrigerant selections, and HGM inte[...]

2 of 18 front side of the door. Position the adap ter board over the s tandoffs mounted on the HGM door. Install the five remaining 6- 32 screws through the board and into the standoffs and tighten. Connect power wiring from the HGM300’s 120V Auxiliary Power term inal block to the adapter board’s POWER terminal block. Use UL approved wire. W ir[...]

3 of 18 If an RDM800 remote display IS to be used w ith the adapter, refer to Figure 3 for wiring details. Note that when the RDM800 is used, TWO RS-485 cables must be run betw een the HGM300 and RDM800, so plan accordingly. In either case, be sure to set the HGM300’s in ternal “Terminator” s lide switch next to the RS-485 terminal block to t[...]

4 of 18[...]

5 of 18 Setting HGM Communication Address On Adapter See Figure 4 for the location of adapter dipswitch ‘A’. Switches 5-8 on the adapter’s ‘A ’ dipswitch are used to matc h the node address set on the HGM’s address dipswitch (on HGM main boa rd). Values from 0-15 are possible: HGM address A5 A6 A7 A8 ----------------- ------------------[...]

6 of 18[...]

7 of 18 Configuring the HGM300 with RDM800 or Laptop PC The only HGM parameters that are cha ngeable through LonWorks are the alarm thresholds. Configuring the HGM for refriger ant type and length of tubing for each zone (zero length to disable a zone ) must be done with the RDM800 remote display or a laptop PC. Refer to the appropriate Bacharach i[...]

8 of 18 HGM Alarm Acknowledge Options Two alarm acknowledge options are s upported—Auto Acknowledge and Network Acknowledge. In the Auto Acknowledge mode, the HGM will clear its alarm outputs the next tim e the alarmed zone is sampled and its PP M has dropped below the alarm thresholds. No intervention from the LonW or ks network is necessary. In[...]

9 of 18 LonWorks Objects and Network Variables The adapter contains one Node Object, sixteen Zone Objects, one Ge neral Status Object, and one Alarm Control Object. There is one Zone Object fo r each refrigerant sampling zone. Object 0 – The Node Object Network input variable nviRequest allows the user to requ est information from different objec[...]

10 of 18 Network output variable nvoStatus returns the information requested by nviRequest. The status response will indicate the status of the object that received the request. The status bits supported are list ed above under RQ_REPORT_MASK. One nvoStatus response will be returned for each nviRequest. The configuration variable nciMaxStsSendT can[...]

11 of 18 Objects 1-16 – Zone Objects There is one Zone Object for each sampling zone in the HGM300 (16 total): Network output variable nvoHgmZonePPM shows the m easured gas concentration for a particular zone. The value will range from 0-65535 PPM. Network output variable nvoHgmZoneStatus is a text string that displays inform ation about the zone[...]

12 of 18 CRITICAL FAULT Some critical fault pr events normal zone PPM m easurement. (View nvoHgmFaults for details on fault type) HGM BUSY Occurs with RDM800 insta lled when certain scr eens are displayed. COMM FAULT 1 Comm failure between HGM and adapter. COMM FAULT 2 Comm failure between adapter internal processors. HGM WARMING UP HGM must go thr[...]

13 of 18 Object 17 – General Status Objec t The General Status Object provides info rmation about any HGM300 internal faults present and shows which zone is currently being sampled: Network output variable nvoHgmFaultAlert reports whenever ANY fault is detected within the HGM or adapter. It is of type S NVT_switch. It is useful for binding to a F[...]

14 of 18 HGM Busy (if RDM800 attached a nd showing certain screens)(bit 4) Comm Fault 1 (communications fail ed between HGM and adapter)(bit 3) Comm Fault 2 (internal communicati ons failed within adapter)(bit 2) Unused (bit 1) Unused (bit 0)(least significant b it) Network output variable nvoZ oneSampling shows which zone is currently being sample[...]

15 of 18 Object 18 – Alarm Control Object The Alarm Control Object provides information about any alarm s which are present in the HGM. It also provides mechanisms fo r acknowledging alarm s, and for viewing and setting the Leak, Spill, and Evacuate alarm thresholds for each zone: Network input variable nviHgmAlarmAck has a single parameter (unsi[...]

16 of 18 Network input variable nviSetZoneThresh allows Leak, Spill, and Eva cuate alarm thresholds (in PPM) to be set for each m onitoring zone. nviSetZoneThresh has four parameters to be set by the user: Zone Specifier: a number 1-16 specifies which zone is having its thresholds changed Leak Alarm Threshold: a number 0–65535 PPM Spill Alarm Thr[...]

17 of 18 Network output variable nvoHgmZoneThresh displays the following in formation for the zone specified by nviGetZoneThresh: 1. Zone (1-16) whose alarm th resholds are being displayed 2. Leak Alarm Threshold in PPM (0-65535) 3. Spill Alarm Threshold in PPM (0-65535) 4. Evacuate Alarm Threshold in PPM (0-65535) To change the Leak, Spill, or Eva[...]

18 of 18 LED 1 and LED 2 will normally show activ ity about every 15 seconds. Since the refrigerant monitoring process is fairly slow and new data is only available every 15 seconds or so, the adapter po lls the HGM at a slow rate to reduce the com munications burden on the HGM main processor. Agai n, commands com ing in from LonWorks might occasio[...]