Page 1 Controller Unit 301C Controller User Manual M‐510324 Revision 04 December 2015 ...
Page 2 ...
Page 3: Table Of Contents
Table of Contents Notices and Trademarks ................5 Symbol Definitions ..................7 Introduction ....................9 Installation Instructions ................10 Surface Mount Installation ............... 11 Wiring Details ................... 12 Power Connections .................. 13 Communication Connections ..............13 Settings for Specific Transmitters ............14 Relay Output ....................
Page 4 Action Menu ..................41 Delays Menu ..................42 Latch Mode ..................43 Conditions ..................44 Status ....................49 4. Acqui Menu ..................50 Starting and Stopping Tx Logging ............51 Starting and Stopping Event Logging ..........53 5. Copy Menu ..................54 Configuration ..................
Page 5: Notices And Trademarks
In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice.
Page 6 6 ...
Page 7: Symbol Definitions
Symbol Definitions The following table lists the symbols used in this document to denote certain conditions: Symbol Definition ATTENTION: Identifies information that requires special consideration TIP: Identifies advice or hints for the user, often in terms of performing a task REFERENCE _ INTERNAL: Identifies an additional source of information within the bookset.
Page 8 8 ...
Page 9: Introduction
Introduction The 301C controller acts as a nerve center for a gas detection net‐ work, providing continuous monitoring for up to 96 connected units (plus 1 301ADI). Once installed and connected, the controllers allow the user to monitor, adjust, or reconfigure an entire network of units. Intended Use The controller is intended to monitor an entire gas detection network around the clock. The unit offers logging capabilities, creating log files of all transmitter concentrations and alarms for analysis. The unit is also equipped with grouping or zoning capabilities that allow users to query and monitor specific groups of transmitters or specific transmit‐ ter zones. Receiving and Unpacking Upon receiving the controller unit: Check that the package is undamaged • Carefully open the package. • Locate the packing slip or purchase order and verify that all items on • the order are present and undamaged Note: If the package or any of its contents are damaged, please refer to the Warranty section at the back of the manual for instructions.
Page 10: Installation Instructions
Installation Instructions Basic Guidelines For proper operation of the controller, follow the instructions in this manual carefully.  Locate all units in areas easily accessible for service.  Avoid locations where instruments are subject to vibrations  Avoid locating units near sources of electromagnetic interference  Avoid locating units in areas subject to significant temperature swings Verify local requirements and existing codes that may impact choice of location. 10 ...
Page 11: Surface Mount Installation
Surface Mount Installation It is recommended that controllers be installed 5 feet (1.5 m) above the floor, at approximate eye level. Mark the holes as shown:  Height markers 6 13/32” (16.3 cm) apart  Width markers 10 9/16” (26.8 cm) apart  Pre‐drill 1/4” mounting holes as needed  Securely mount the 301C controller using the appropriate screws Wiring for the unit must be passed through the knock‐outs provided at the bottom of the unit. 11 ...
Page 12: Wiring Details
Wiring Details The diagram below provides the details required to connect the 301C controller with power, transmitters, external relay loads, and BACnet. Details concerning power supply, cables, capacities, etc., are provided in the Specifications section at the back of this manual. RELAY STATUS Relay # 3 Optional datalogger RELAY STATUS Relay # 4 ALA R M_ A SILE N C E Buzzer ALA R M _B LCD screen End-of-the-line ALA RM_ C jumper position...
Page 13: Power Connections
Topic Description Connect the power supply to the controller (see J22 Power Input Wiring Details for cabling diagrams) J23, J24 Communi‐ Connect communication cables to channels 1 cation inputs through 3. Depending on the desired configuration, con‐ nect the relay cables to either N.O. or N.C. Re‐ Relay Outputs 1‐4 lays 1 and 2 are commandable by either inter‐ nal events or by BACnet; relays 3 and 4 are driven only by internal events. Place the jumper over the Shutdown header SHDN jumper pins to reset or restart the system. Place the jumper over the header pins to in‐ EOL Resistors 1‐4 clude resistors to attenuate communication echoes. Power Connections The 301C controller requires a power range of 17‐27 Vac, 50/60 Hz (8.64 VA), 18‐36 Vdc, 350 mA @24 Vdc (8.4 VA). Polarization is not important in either AC or DC mode. The system must be grounded on the transformer and a dedicated circuit breaker must be used. Communication Connections Communication cables must be grounded using the shield terminal, using twisted and shielded pair Belden 2‐24 AWG #9841 cable (or equivalent). The network cabling can extend up to 2000 feet (609 m) per channel. Daisy‐chain the network cable with no T‐taps. 13 ...
Page 14: Settings For Specific Transmitters
The 301C controller communicates with gas sensors over a Modbus RS‐485 network. This transmission line requires that 120Ω termina‐ tion resistors be fitted at both ends of each network segment to ab‐ sorb the signal and thus prevent reflections. Fortunately, the control‐ ler makes network termination simple as resistors are included on the board. These can be switched in and out of network by moving the “EOL” jumpers as shown in the figure on page 12. More information on RS‐485 wiring is published by Maxim Integrated in the TUTORIAL 763 Guidelines for Proper Wiring of an RS‐485 (TIA/EIA‐485‐A) Net‐ work . Settings for Specific Transmitters Honeywell Sensepoint XCD Transmitters must be configured for 9600 baud, no parity, and a unique address. Honeywell XNX Universal Transmitters must be configured for 9600 baud and a unique address. Information on configuring each transmitter is in the associated tech‐ nical manual. Some sensors consume multiple addresses on the 301C controller. Specifically, the 301EM consumes 4 addresses regardless of the num‐ ber of sensors connected. Additionally, the IAQPoint2 consumes 3 addresses if fitted with the optional temperature / humidity sensor. Please allocate proper address spacing for applications utilizing a mix‐ ture of sensors on a single system. Relay Output The relay output can withstand up to 5A at 30Vdc or 250Vac resistive load. Relays can be used to activate horns and strobes. Although each relay is programmed with a default setting (below), they can be con‐ figured using the controller programming menu. 14 ...
Page 15 By default, the relays are normally de‐energized and will go energized when events occur. However the relays can be configured for “fail‐ safe” or normally‐energized. If so, events will drive them to de‐ energized. If relays are set to normally closed, the relay is powered up with the controller and the device linked to the relay is functioning. The relay will shut down when the associated event is activated. If the relay is set to normally open, the relay will remain off when the controller is powered up and the device connected to the relay will only be activated when the associated event is activated. 15 ...
Page 16: Jumper Use Instructions
Jumper Use Instructions The jumpers on the controller PCB allow a variety of operations to be performed manually: Topic Description Enables the user to add End‐Of‐Line jumpers that improve communication signals. Put the jumper in R position (as shown on wiring diagram) to ac‐ EOL 1‐4 tivate the End‐of‐Line termination. (R provides a resistance termination and RC provides resistance and condensator termination.) Enables the microcontroller to be reset or tempo‐ rarily shut down. This function is used mainly when system wiring adjustments are needed (power off for safety). SHDN Power may still be present on the relay CAUTION terminals even after powering off. These jumpers allow the relay to be tested by Relays J29‐J32 activating it without having any effect on Events.
Page 17: Initial Startup
Initial Startup Make sure that all wiring has been completed according to specifica‐ tions in the wiring details before powering up the unit. When all is secure, remove the SHDN jumper to power‐up the unit. Within sixty seconds the controller will be fully operational. Datalogger (SD card) The DLC (Data Logger Card) option for the controller collects data and stores it on a digital Flash memory card (SDCard). In the event that the card memory becomes full:  Information logging is stopped  No SDcard flag is displayed on‐screen  The SDcard LED blinks See the Acquisition section for more details on starting and stopping the datalogging function. SDHC cards are not supported; use only SD cards. Always deactivate datalogging function before removing the CAUTION SDcard. Never remove the card when its LED is on. ...
Page 18: Programming Interface
Programming Interface The front panel of the 301C provides a programming keypad (buttons) and LEDs. 301C controller front panel keypad: Keypad Functions Each unit has 7 keypad keys. The display contrast can be adjusted by pressing the Up and Down keys when the main screen is displayed. Keys Description Used to move the cursor through the various programming fields (Up, Down, Left and Right), or to adjust the display Arrows contrast (press and hold the up or down arrow until desired contrast is reached and release). Used to exit the programming menu or to cancel a change or ESC input. Used to access the programming menu and to modify pro‐ Enter gramming fields. Silence Turns off the controller’s buzzer. 18 ...
Page 19: Led Definitions
LED Definitions The controller is equipped with 7 LEDs that provide a status for each function related to that indicator: LED Description A blinking red light indicates that an event has been acti‐ Alarm A vated. A constant red light indicates that one or more transmitters have reached Alarm A or Alarm 1. When the red indicator is on, one or more transmitters have Alarm B reached Alarm B or Alarm 2. When the red indicator is on, one or more transmitters Alarm C have reached Alarm C. Green indicates that the unit is powered up and functional Power ...
Page 20: System Operation
System Operation The system operates in four different modes that allow it to use, ana‐ lyze, debug, and simulate the actions that the system can perform. These modes are: Normal, Single Tx, Debug and Simulate. The default system operation mode is Normal. The other modes are available through the Tests menu (option 8 from the Main Menu). Note: Systems services may be disrupted by some menu operations. Specifically, viewing the “events” dialogue may inhibit event operation. 20 ...
Page 21: System Programming
System Programming The system’s Normal programming mode offers several menu options that are accessible from the main menu screen: Mode Description 1. Tx Info Allows transmitter parameters to be programmed 2. Groups Allows sets of multiple transmitters to be aggregated for simpler programming of a common response. 3. Events Facilitates creation of logical terms which respond to transmitters or events. These Boolean outputs can respond to concentration, alarm, or fault status. The‐ se events facilitate voting within a group and can drive relay outputs. 4. Acqui Allows the datalogging feature to be activated or de‐ activated 5. Copy Allows data or parameters to be copied from the (controller) configuration to parameters 6. Config Allows system parameters and password to be set 7. Network Allows actions on the network to be performed, communication statistics to be consulted, and remote calibrations to be performed 8. Tests Allows each device to be tested sequentially (inputs, outputs, communications, events, etc.) and operation of various parameters to be validated 9. BACNet Allows a device’s BACNet parameters to be set 10. Wireless Not supported. Note: Access to the programming functions is password protected. The default password is 2967.
Page 22 If one or more of the connected devices is in an alarm mode, the con‐ troller will only scroll between the main information screen and the screens for device(s) in alarm mode. In this case, you must scroll man‐ ually to view screens for other devices. 22 ...
Page 23 The information screen also displays icons representing certain sys‐ tem functions. Here is a list of possible icons and their meaning: Icon Description BACNet: Indicates that there is a BACNet module present and that it is communicating with the controller. BACNet error: Indicates that a BACNet module is present but communication with the controller has failed (error) Debug: Indicates whether the controller is in debug mode (Single TX, Debug or Simulation modes).
Page 24 Since the controller’s programming functions are password protected, it is necessary to access the login screen:  Press Enter to access the programming options. The password screen appears:  Use the keypad Up or Down arrows to increase or decrease the value, one digit at a time, starting with the first digit  When all the digits of the password are correct, press Enter to access the programming functions. The first MENU options screen appears. Use the keypad arrows to navigate through multiple screens to the desired function and press Enter to access it. 24 ...
Page 25: Tx Info Menu
1. Tx Info Menu Tx Info is the menu option dedicated to transmitter information and several sub‐menu options. They are summarized here and detailed on the following pages. Exact screens will vary with transmitter types. Menu Option Description Screen Allows the network component’s identification information to be Ident viewed. Allows the communication proto‐ col to be viewed or changed COM Allows the detection range and the unit of measurement parameters to be viewed and changed Detection or Scale (1) and Scale (2) Allows the label (or name) of a specific component to be Display changed Allow alarm thresholds to be viewed and sometimes changed. There can be significant varia‐ Alarms tions in this screen depending on transmitter type. Transmitter and node status (in hexadecimal values) Status Displays Erases or changes the Erase or ...
Page 26: Ident Menu
Ident Menu The Ident, or identification menu allows a component’s network ID to be consulted: The upper right corner of the screen shows the component’s address. If the address of the device whose information must be viewed is known:  Use the arrows to move the cursor arrow to the on‐screen ad‐ dress  Press Enter (the value can be edited while the number is flashing)  Use the up or down arrows to increase or decrease the value  Press Enter again to validate the entry and display the information for the desired device. The bottom left corner of the display shows the transmitter name (ex.: 301D2 ‐ product name) and the sensor type (ex.: CH4 ‐ methane sensor). These values can also be changed for Group or Vulbus prod‐ uct types. The procedure is identical for both fields: Programming or changing a product or sensor type  Use the arrows to move the cursor to the product type field.  Press Enter to select the field (the value can be modified when flashing)  Use the arrows to scroll through the list of product types and press Enter when the desired product or sensor appears 26 ...
Page 27: Product And Sensor Types
Product and Sensor Types This is a list of all the (preprogrammed) product types available from the Identification option in the Tx Info menu. 1. Tx Info -Ident- E3Point Compatible products: E3Point 420MDBS ECFX 301R 301EM SQN8X XCD XNX IAQPoint2 Legacy Vulcain products Note: When Group is selected as a product type, the remaining Tx INFO screens are not accessible (because each product in the group has already been individually programmed).
Page 28: Com Menu
COM Menu This screen displays the selected communication protocol for device addresses from 1 to 96. Each transmitter’s protocol is defined by the controller (see Network Auto‐configuration section) If a transmitter is compatible with several different protocols, it can be modified using to one of the following options:  Vulbus  Mdbs ASCII 7D 2S NP 9600 bauds  Mdbs RTU 8D 2S NP 9600 bauds  Mdbs RTU 8D 1S NP 9600 bauds  Mdbs RTU 8D 1S OP 9600 bauds When a transmitter is configured with the Modbus communication protocol, the transmitters automatically sends the programmable pa‐ rameters to the controller. Note: Vulbus transmitter parameters must be programmed manually. 28 ...
Page 29: Scale Menus (1 And 2)
Scale Menus (1 and 2) These menus appear only for certain devices. Scale(1) allows the de‐ tection range, minimum and maximum, to be defined for the selected device. Whatever value is specified is the value that will appear at the device display (if applicable). The Minimum value is generally left at 0. Parameters for the XNX and XCD gas detectors can be viewed here but can be changed only at the transmitter. Scale(2) allows the factor by which to divide the scale (between 0 and 65535) and the unit of measurement for the selected scale to be de‐ termined. The factor allows precise scale limits for detection to be set. By divid‐ ing the maximum scale value in the first Scale screen (250 in this ex‐ ample) by 10, a scale value of 25.0 can then be displayed. The “Units” allow the device’s unit of measurement to be selected: °F: Sets degree Farenheit as the unit of measurement °C Sets degree Centigrade as the unit of measurement Sets Relative Humidity as the unit of measurement Sets millivolts as the unit of measurement Sets volts as the unit of measurement...
Page 30: Detection Menu
Detection Menu The detection menu (available only for devices with addresses be‐ tween 1 and 96) displays the detection range (scale: 0‐100.0) and the unit of measurement (unit: %) for the selected component. If a transmitter uses the Modbus protocol, the detection parameters are automatically defined during network configuration and are not ed‐ itable. Vulbus protocols must be manually defined by the program‐ mer. The detection scale is between 0 and the maximum value (0.00) and the unit of measurement is either ppm or percent (% for oxygen and % LEL for combustibles). The detection menu is not available for the VA301R or VA301AP. Programming or modifying the scale range or unit:  Use the arrows to move the cursor to the scale or unit option  Press Enter and use the arrow to increase or decrease the value  Press Enter when the desired value is obtained 30 ...
Page 31: Display Menu
Display Menu This option allows a specific label or name to be assigned to the se‐ lected component (transmitters, relay modules, annunciators). Up to 20 characters, including spaces, can be used in the label (example: BOILER ROOM). The default Modbus transmitter labels are composed of the component (or transmitter) name, sensor type and address. Vulbus transmitter labels contain 20 blank characters (spaces). 31 ...
Page 32: Alarm A, B, And C Menus
Alarm A, B, and C Menus The screens for viewing alarm thresholds are combined in this manu‐ al. There will be either two or three levels, depending on transmitter type. If present, separate “MIN” and “MAX”levels permit manual control of the hysteresis of each alarm. Normally, the “MAX” level is set greater than “MIN.” However, alarms can be made to trigger on falling con‐ centration (as with oxygen) by setting the “MAX” threshold smaller than the “MIN” threshold. With certain transmitters, only one threshold will be displayed. Additionally, with certain transmitters, the alarm thresholds are read‐ only at the controller. These thresholds can be set only at the trans‐ mitter. These are typical screens: Typical screen for viewing alarms A or B on XCD and XNX transmitters Typical screen for viewing or changing alarm A, B, or C thresholds on other transmitters. 32 ...
Page 33: Servicing And Operating Menus
Servicing and Operating Menus These functions vary depending on the transmitter type. These dis‐ plays show the total time the device has been in service and the amount of time remaining until the next required calibration or re‐ placement. 33 ...
Page 34: Status Code
Status Code These screens display transmission or node status and sensor status for the selected transmitter. This read‐only information can assist ser‐ vice personnel in troubleshooting. The XNX and XCD gas detectors will report the warning or fault num‐ ber (iFaultWarnNumber) in hexidecimal on the third line. These transmitters will also report the monitoring state (iMonitoringState) in the fourth line. See the transmitter documentation for interpretation of fault numbers and monitoring states. Typical display for XNX or XCD Typical display for other transmitters 34 ...
Page 35: Erase Current Tx
Erase Current Tx This function allows the configuration to be erased or the Tx address for the displayed component to be changed. Note: Selecting erase current Tx only erases the current device entry Tx Info configuration. No other data is erased. 35 ...
Page 36: Change Tx Address
Change Tx Address Selecting Change Tx Address allows users to move a device from one TX address to another:  Use the arrows to scroll to Change Tx Address and press Enter to select  In the next screen, scroll to the address number and press Enter to select  Use the up or down arrows to increase or decrease the address value and press Enter to validate the new address. The Change Tx address option is only available (active) for device ad‐ dress 1 to 96 and if there is a Modbus device connected. If the address is valid, the screen will display “Processing”. If the ad‐ dress is invalid, the screen will display “Invalid Tx” and return to the Change Tx Address screen (the address for GasPoint devices cannot be changed). A final screen will display either “Error” or “Success” (re‐ start procedure if Error is displayed). Note: If a device address is changed to one already associated with another device, the existing data will be overwritten. Customers should know their network’s address assignments and be careful when changing a Tx address.
Page 37: Groups Menu
2. Groups Menu Programming groups of transmitters allows several units to be com‐ bined which then enables actions (events) to be taken based on a se‐ ries of units rather than each unit, individually. A group is a stack containing the addresses from each of the transmit‐ ters included in the group. Groups are displayed in a single line; if a group contains more than four components, the arrows must be used to scroll left and right of the display window to view all members of a group. The cursor in the Group screen is represented by the blinking brackets (<end>). Any information between the brackets can be edited. 37 ...
Page 38: Creating Groups
Creating Groups The 301C controller accepts a variety of transmitter models with a variety of gas sensors. It can organize the data conveniently using groups and events. However, the group logic requires that all of the members of the group be from the same transmitter models and the same sensor type. Mixing dissimilar sensors or transmitters in a group can cause incorrect results.  Use the arrows to move the cursor to a group line and press Enter  The field can be edited when the brackets stop blinking and the word “end” blinks  Use the up or down arrows to scroll through the list of all units connected to the 301C controller, until the desired address is dis‐ played.  Press Enter again to validate the address.  The address is added to the group and the <end> bracket is shift‐ ed one position to the right.  Do not add duplicate copies of a transmitter. The process can be repeated until all the desired transmitters in the group (up to 126) have been added. The address for each transmitter added in the Tx Info menu is available when creating groups. Note: Groups created in the Groups menu will appear in the product type list (Tx Info - Ident screen) as “Group xx”...
Page 39: Deleting Groups
Deleting Groups Use the empty all groups command to delete all groups previously programmed in the controller. Single groups can be deleted with a simple procedure:  Scroll to the first transmitter in the group list,  Select the transmitter (its address blinks) and scroll to <del> (<del> erases the entry and <end> marks the end of the stack)  Press enter and the group is emptied. This procedure makes it possible to delete one, several or all entries previously included in a group. Note: Up to 126 groups, with a maximum of 128 members each, can be created. 39 ...
Page 40: Events Menu
3. Events Menu The Events menu is programmable. Event programming lets specific actions to be defined: Menu Description Screen Topic What will be done if programmed criteria are reached Action Defines the length of time to wait before taking an action on Delays an event and time to wait after an event has returned to normal before the action out- put is returned to normal state.
Page 41: Action Menu
Action Menu Actions are comprised of two parameters: Parameter Description Indicates which component is responsible for the action to be taken; Tx (transmitter) Target Re (Relay/Annunciator) Ctrl (Controller) Indicates which of three possible outputs will be activated when the event is true; #XX (activates the component’s #xx relay), Relay Buzzer (activates the component’s audible alarm) ALL (activates the relays and audible alarms) ...
Page 42: Delays Menu
Delays Menu This option allows Before and After settings that will delay the activa‐ tion or deactivation of an action to be programmed. Before Delays the action for the specified length of time. If the condition persists beyond this delay, the defined action is executed. After The time to wait after an event has returned to normal before returning action output to normal state. The after delay also offers a Latch option, described below.
Page 43: Latch Mode
Latch Mode  The Latch function is executed on an Event state  It is possible to select the Latch mode by changing the after delay to “latch”  The Event stays active until the Silence keypad button is pressed  The Silence keypad button has two functions: Silence the buzzer and unlatch the event.  When the Silence keypad button is pressed, events in Latch mode are unlatched and reevaluated. If the Event condition per‐ sists, the Event remains active and returns to Latch mode. If the condition does not persist, the event is deactivated. Note: If the Event has a Before delay and the Silence button is pressed while the Event conditions are still true, the buzzer will be silenced only for the length of the programmed delay.
Page 44: Conditions
Conditions Conditions are the parameters that define what makes an Event true. Each condition is defined by four elements and can be combined with other conditions to provide greater flexibility. A condition, as in the example provided below, defines: IF at least 1/3 of group 36 detects concentrations greater than 2.01% of specified gas AND all of group 03 detects a concentration greater than 2.99% of gas, then the specified action (Actions were set at the first Event screen) for that Event will be triggered. Since the display screens offer limited space, scroll left and right to view and edit further information. Condition programming screens The portion of the Events condition screen that is within the brackets is divided into four editable list fields: 44 ...
Page 45 The top left portion contains the statistic quantifier (available only for Groups) that take only the specified part of the group into the equa‐ tion. Options available in this field are: Option Description all includes all transmitters in the group includes the average concentration for the group’s trans‐ mean mitters max includes the group’s maximum concentration min includes the group’s minimum concentration includes at least a quarter of the group’s transmitters that 1/4 meets set conditions includes at least a third of the group’s transmitters that 1/3 meets set conditions includes at least half of the group’s transmitters that meets 1/2 set conditions includes at least two thirds of the group’s transmitters that 2/3 meets set conditions includes at least three quarters of the group’s transmitters 3/4 that meets set conditions at least one or more than one of the group’s transmitters 1 or + that meets set conditions The transmitter that deviates the most from the average concentration reading of a group of transmitters is known as an outlier. This quantifier is only available in 301C24 models. Further dialog facilitates specifying the deviation ...
Page 46 The bottom left portion contains the logic, or operator, quantifier that determines how conditions are calculated. Options available in this field are: Operator Meaning Symbol No operator Equal to Equal to or smaller than <= Smaller than < Equal to or larger than >= Larger than > Not equal to When the maximum value is reached, an action is max triggered. It will not be deactivated until levels fall below minimum value When concentrations fall below minimum value, an min action is triggered. It will not be deactivated until concentrations rise above set maximum value The time since calibration reported by the sensor is evaluated. This number is also listed in the “1. TxInfo / Operating Times / Since Calib” menu. Further dialog TSC allows the time limit to be set from 0 minutes to 98 months. This logic function is supported only with E³Point transmitters. 46 ...
Page 47 The top right portion contains the source, which defines what device or group of devices the Event will be based on. The list provides the following options: Option Description GrAll Includes all transmitters (see note) GR _ _ _ Includes only the devices in the specified group (see note) Includes only the specified transmitter (connected to the Tx000 controller) Includes only information gathered between the specified times. Selecting clock sets a condition that is applied only between the start and end time frame. It is possible to set Clock one condition screen to specific parameters and the se‐ cond to clock, which means that the specified condition will trigger an event only if it occurs during the set time period. Note: Clicking on the magnifying glass to the right of a Group number on the display opens a view of the Group for consultation or editing.
Page 48 The bottom right portion contains the operand, which defines what device or group of devices on which the Event will be based. The list provides the following options: Option Description OFF Used for status on binary inputs (ex.: used with 301ADI) ON Used for status on binary inputs (ex.: used with 301ADI) Bases trigger on maintenance alarm, communication fail‐ Fault ure or device failure If the chosen device or group has an Alarm A or Alarm 1, Alrm A an event will be triggered. If the chosen device or group has an Alarm B or Alarm 2, Alrm B an event will be triggered If the chosen device or group has an Alarm C, an event will Alrm C be triggered. The Coverage Period screen allows the period that will be covered by the Event to be defined. (The time frames for each of these periods can be defined in the controller Config menu.) This option provides two further selection fields: Day definition field: allows All day, Daytime, or Nighttime to be se‐ lected Week definition field: Weekend, Working Days, All week 1. Use the keypad up or down arrows to scroll to either All day or All week 2.
Page 49: Status
Status This screen displays the current event status and allows it to be either enabled or disabled, depending on the current status. Enable event: Toggles between Enable and Disable. After going through all the steps and programming an event, this screen will display “Enable event”. Press Enter to activate all the pa‐ rameters and enable the Event. If an existing Event is being consulted, this screen would display “Dis‐ able event”. Press Enter to disable an Event (it will not be deleted but will not function). The programming of this Event is always present, which means that it easily can be reactivated by scrolling to this screen and pressing Enter. 49 ...
Page 50: Acqui Menu
Acqui Menu The Acquisition mode is accessible only when there is an SD card pre‐ sent (controllers with the Data Logging, or DLC function). It is used to enable or disable the logging of system Events or transmitter infor‐ mation. The information is logged (or recorded) on an SD card. Inter‐ vals or conditions must be defined before using this option. The first line of the Acquisition screen offers either: First Line Description Delay Allows for delay intervals of 10 to 59 seconds or 1 to 60 mode minutes. Allows log values to be set according to set variation Threshold thresholds (based on last reading) of 3% or more, 5% or mode more or 10% or more of last detected concentration. If a 3% threshold is selected, the system will not log a value at 3% but will log a value of 3.1%. Remember that the sampling rate (system refresh rate) may have an impact on logging. Here is an example of threshold logging. The logs a semi‐colon delin‐ eated text files. 2005-04-27 11:05:20;1_CO2_ppm;574;-normal-: 2005-04-27 11:06:02;1_CO2_ppm;503;-normal-: 2005-04-27 11:06:15;1_CO2_ppm;562;-normal-: 2005-04-27 11:06:28;1_CO2_ppm;645;-normal-: 2005-04-27 11:06:39;1_CO2_ppm;557;-normal-: 2005-04-27 11:30:45;1_CO2_ppm;715;-normal-: ...
Page 51: Starting And Stopping Tx Logging
Starting and Stopping Tx Logging In the previous step, “Acquisition”, the frequency at which Tx logs would be recorded can be configured. To start the logging function: When “Start Tx logging” appears on the display, it indicates that the acquisition, or logging, mode is inactive. When “Stop Tx logging” ap‐ pears, it indicates that Tx data is being logged. The log message is displayed on the screen according to the chosen mode and LED 1 will light up. Press the Enter keypad button to stop or start Tx logging. When Tx data is logged, the system creates files named tayymmdd.log, tbyymmdd.log and tcyymmdd.log, each representing one third of the network. The record includes the transmitter’s date, time and address, the sensor type, the concentration read, as well as the alarm status. Here is a sample of what a Tx log looks like: 2004-01-23 17;54;25; 001_CO_ppm;0;-normal-;002_NO2_ppm;1.5;-normal-;003_CO_ppm;0;-normal- 2004-01-23 17;55;25; 001_CO_ppm;0;-normal-;002_NO2_ppm;0.5;-normal-;003_CO_ppm;0;-normal- 2004-01-23 17;56;25; 001_CO_ppm;0;-normal-;002_NO2_ppm;0.5;-normal-;003_CO_ppm;0;-normal- 2004-01-23 17;57;25; 001_CO_ppm;0;-normal-;002_NO2_ppm;1.0;-normal-;003_CO_ppm;0;-normal- 2004-01-23 17;58;25; 001_CO_ppm;0;-normal-;002_NO2_ppm;1.5;-normal-;003_CO_ppm;0;-normal- These log files are delimited by semicolons and are thus easily read by popular spreadsheet programs such as Microsoft Excel. The first col‐ umn of the Tx log displays the date (yyyy‐mm‐dd) and the time (hh:mm:ss) of the log. In this example, the “Delay mode” was set to one minute intervals. The third column of the Tx log displays the transmitter address and ...
Page 52 The display then lists the next transmitter address with its gas type, concentration and unit of measurement, and so on until all the trans‐ mitters have been listed. 52 ...
Page 53: Starting And Stopping Event Logging
Starting and Stopping Event Logging The Acquisition menu offers an event logging option. Event Logging records controller transactions, events, Tx and alarm flags and relay status. When “Start Event logging” appears on the display, it indicates that the acquisition, or logging, mode is inactive. When “Stop Event log‐ ging” appears, it indicates that Event data is being logged. Press the Enter keypad button to stop or start Event logging. When Event data is logged, the system creates a file named evyymmdd.log. The record includes the date, time and the event. Here is a sample of what an Event log looks like: 2004-01-23 17:54:25: Event logging enable 2004-01-23 17:55:25: Event logging enabled 2004-01-23 19:05:47; Simulation sequence activated 2004-01-23 19:05:48; Tx 6 communication no more in fault 2004-01-23 19:05:48;...
Page 54: Copy Menu
. Note: The second option is SDcard to 301C controller allows the configuration and parameters of the “config.ini” file on an SDcard to be copied to the controller. Power must be cycled to fully implement the SD card’s configuration by stowing the jumper on the SHDN pin (see the illustration on page 12.) The “config.ini”...
Page 55: Parameters
Parameters The “parameters” function allows one transmitter’s configuration to be copied to another or one event’s parameters to be copied to an‐ other event. This allows several devices that share identical or similar parameters to be quickly configured. The options within this screen are: Tx Info to Tx Info copies transmitter parameters from one device to another. Event to Event copies parameters from Event to Event. The process is identical for both options:  Select source, (the data to be copied) using the up/down keypad arrows and press Enter.  When the transmitter address is flashing, use the up/down key‐ pad buttons to search for the desired device address.  Press Enter to select the new address  Select the target address (where the data is to be copied to) in exactly the same way as source  Select COPY and press Enter. The parameters have been copied. 55 ...
Page 56: System Log Menu
System Log Menu The controller will record log information to its internal memory. If the controller is equipped with an SD card, the system log function allows users to save system log information to the memory card in text format. When this option is selected, a log of all the last actions performed on the controller is copied to the SDcard, with the filename slyymmdd.log. This file can contain up to a maximum of 64Kb of in‐ formation in text format. Once the memory card is full, the oldest log entries are erased and replaced by new entries. Here is an example of a system log: --- STAR T of system log dump : 2007-04-18 13:19:05 --- 2007-04-04 18:42:06;Accessing menu; 2007-04-04 18:43:47;Event 1 definition modified; 2007-04-04 18:48:12;Exiting menu; 2007-04-04 18:54:49;System power-down; 2007-04-04 18:56:40;System power-up;...
Page 57: Config Menu
6. Config Menu The Config menu contains several main configuration screens and is used to program the controller display mode, adjust the date and time, select the display language, change the controller access pass‐ word, set the Relay Configuration, and select the AP Broadcast mode. Each main screen offers further programming options, as shown. 57 ...
Page 58 Selecting the first line of the first screen allows selection from three display modes: Manual scroll, 3‐second scroll, 5‐second scroll. If Manual scroll mode is chosen, the screen will only advance if you press on the arrow keypad buttons. If either 3 or 5 second scroll mode is chosen, the screens will automatically scroll display readings for all devices connected to the controller after 3 or 5 seconds. 3 or 5 second scroll modes do not prevent the keypad arrows to be used to return to a previous screen or move ahead through the screens manually. Selecting the second line allows the date and time in a new screen to be adjusted; Date and Time. When a number is flashing, the value can be changed using the up/down keypad arrows. The year, month, day and the hour, minute and second values can be changed. The controller does not manage Daylight Savings Time, therefore, us‐ ers must manually adjust any time changes. Selecting the third line allows the display language to be changed. If the display is already in English, it will then display the Menu français option (and vice‐versa). Simply scroll to the line and press Enter to change the language. 58 ...
Page 59 The default password is 2967. Select Set User Password to change the password: When the first digit blinks, change the value by using the • up/down keypad arrows to increase or decrease the number Use the left/right keypad arrows to move from one digit to the • next. When the desired e has been set, press Enter to validate it and • exit the editing mode. Note: Contact Honeywell technical support for help with lost passwords at 1-800-563-2967. The slave port is not used. 59 ...
Page 60 Scroll through the main Config menu screens using the left (previous) or right (next) keypad arrows. The third main screen in the Config menu allows the relay configura‐ tion to be set, the AP broadcast mode and to select from four sepa‐ rate manufacturers for the given controller. When Relay Configuration is selected, two further options to config‐ ure the relays are available: The first screen, Failsafe, appears allow‐ ing the failsafe to be activated for all relays using the Enter keypad button. This function inverts relay operation to be normally ener‐ gized. If power is cut, the relay will activate the connected device. (ex. a light.) Scrolling to the right displays the “Silence” screen that enables or dis‐ ables the silence option for each relay, using the Enter keypad button. 60 ...
Page 61 The fourth screen in the Config menu allows a definition of a day and a week to be programmed. Day and Week definition allows hours (time frames) to be defined for either Daytime and Working Days respectively. Note: Remember, the controller uses a 24 hour clock (0:00 to 23:59). Any time changes (e.g., for Daylight Savings Time) must be made manually or through BACNet time synchronization (BACNet module required).
Page 62: Network Menu
7. Network Menu The Modbus network menu allows network device information to be either scanned or reset. This menu offers four options, divided into two screens; the first screen contains three options: Option Description Resets all network device Tx information in the database. Reset This only resets the Tx infomation for the network device. Database It does not affect programmed Groups or Events. Begins an auto‐detect of all network devices that allows the system to configure the Tx database for network de‐ Network vices (i.e. it will scan and add new devices but will not Scan overwrite or erase the old database). This process takes approximately one minute. Reset Performs both previous functions simultaneously. and Scan Note: Once one of these options has been set, wait until the controller completes the process.
Page 63 The second Network screen offers the Statistics and Calibration op‐ tions. Selecting Statistics from the Network menu displays a screen contain‐ ing the statistics for the selected device address. Term Description Indicates the number of valid responses for the last 16 Valid requests Indicates the number of errors in the response for the last Errors 16 requests Indicates the number of timeouts (no response) for the Timeouts last 16 requests 63 ...
Page 64: Remote Calibration
Remote Calibration The network menu also offers a Calibration option for use with devic‐ es that support network calibration. The Calibration screen contains four lines of information: Term Description Indicates the mode (Calib, meaning calibration), the Line 1 (Modbus) address of the device to calibrate (001) and the type of device to calibrate (301D2 Indicates the status (Normal or In calib…) of the specified Line 2 device Line 3 Displays the function to perform (Set Zero) Displays the function to perform (Set Span) and the span Line 4 gas concentration value (246 ppm) 64 ...
Page 65 4. Scroll to select the desired function, Set Zero to set the device's zero, and press Enter to select. 5. Upon pressing Set Zero, the controller requests confirmation. *The device must be configured in the 301C controller’s database in order to be included in the device addresses displayed on screen. 6. Press Enter to confirm or Esc to cancel. If confirmed, the controller calibrates the sensor’s Zero.
Page 66 7. To calibrate the device, scroll to Set Span** and change the span gas calibration value using this procedure; Using the right arrow, move the cursor to xxx PPM (span value field). Press Enter to select the field (it is editable when flashing). Use the up or down arrows to increase or decrease the val‐ ue, press Enter to validate the new value. Move the cursor back to Set Span and press Enter to start the calibration. The device Span is being calibrated. The screen will display the de‐ vice’s status as “In calib...” until the calibration is complete. **When selecting Set Span, make sure that the device has been sup‐ plied with the appropriate calibration gas before and during the cali‐ bration process. 66 ...
Page 67: Tests Menu
8. Tests Menu The Tests menu allows a variety of tests to be performed on compo‐ nents and on the network communications. It also allows the system to be operated in four different modes which, in turn, provide differ‐ ent functionalities. 67 ...
Page 68 The Tests menu provides four main options, divided between two screens. Each of these options offers different capabilities. The first screen presents three options: Option Description Enables each output to be activated and validates Test sequence operation of each controller keypad buttons, dis‐ play pixels, and various communication protocols. This options starts or stops the Simulation mode, which allows a simulation of a gas concentration over an associated scale range on all transmitters. Start Sim The simulated gas concentration values are local Sequence (on the controller) and do not affect logging func‐ tions. (Events will be activated for the simulation but detection devices are not affected.) Maximum load Activates all controller components The second screen option is “Oprt Mode”, which offers three separate operation settings: Normal, Single Tx or Debug. Setting Description Normal Normal controller operation mode Single Tx Activates the polling mode on a single transmitter.
Page 69: Test Sequence
Test Sequence When test sequence is selected from the main Tests menu, the con‐ troller will display the Test sequence screen. If Esc is pressed on the keypad, the main Tests menu screen will be displayed. However, to perform system tests, press any key to pro‐ ceed to the first test screen. This screen tests each component individually and will advance only to the next component when a key is pressed. This option will display 13 screens. Screens 1, 2, and 3 test Relays, BUZZER and LEDs. The following six screens prompt the user to press the keypad but‐ tons, in turn: left, right, up, down, Silence, Enter and Esc. The system will not advance until a key is pressed. The system then moves to the Display test. When the blank screen is displayed, it is testing for display pixels. Press any key to proceed to the next step. 69 ...
Page 70 The final test that the system performs is a network communication test: Once these tests have begun, do not interrupt or stop them. When the system has completed the test, it displays the final Tests screen. Press any key to return to the main Tests menu. 70 ...
Page 71: Normal Mode
Normal Mode This is the system’s normal (default) operation mode. When the sys‐ tem is in normal mode, some values can be changed without inter‐ rupting services. When a value has been changed in any of the menu fields, the change will take effect upon returning to the main menu screen. Single Tx Mode This mode allows transmitters to be analyzed one at a time. The con‐ troller polls only the selected device, which subsequently has its in‐ formation updated. This mode does not interfere with Event Evalua‐ tion functions. Debug Mode This mode allows complete system operation to be evaluated and tested without affecting operations (outside of debug mode). Events are evaluated and displayed as necessary but no action is triggered. 71 ...
Page 72: Simulation Mode
Simulation Mode This mode deactivates network communication Information Updates. It can be combined with any of the three previous modes (example: using the Simulation mode when in Debug mode allows the user to test the entire system [groups, events, etc] without triggering any ac‐ tions or using any additional material such as gases). It allows gas concentrations to be simulated over an associated scale for each transmitter, sequentially: Alarm levels A, B and C are evaluated according to the simulated gas concentration and events are evaluated and actions are taken. This type of alarm simulation at the controller does not work with cer‐ tain transmitters with falling alarms. In these cases, an alarm can be simulated at the transmitter. While in simulation mode, the controller is unaware of the device’s actual network status. This mode can be stopped at any time in the Test menu (see Normal System Operation). If one of these modes has been activated, the system will automatical‐ ly return to Normal Mode after 12 hours of inactivity. (No changes will be lost.) 72 ...
Page 73: Bacnet Menu
9. BACnet Menu The BACNet menu on the following page offers several main menu screens to configure the BACNET IP connection, DHCP, server, time zone information and more. Communications parameter changes to the BACnet interface may not be implemented for up to 30 seconds after modification. These parameters include the device ID, the IP ad‐ dress, and the subnet mask. BACnet/IP Module (BIP option) This section configures the optional BACnet interface (included with models with “BIP” in the part number). The 301C BACnet/IP interface has been listed by BACnet Testing Labs as complying with the BACnet protocol version 7. BACnet is a registered trademark of ASHRAE. ASHRAE does not en‐ dorse, approve or test products for compliance with ASHRAE stand‐ ards. Compliance of listed products to the requirements of ASHRAE Standard 135 is the responsibility of BACnet International (BI). BTL is a registered trademark of BI. 73 ...
Page 74 74 ...
Page 75 The first of these screens allows the identification and address to be configured: BACnet ID: (Building Automation and Control Networks) is the device ID number assigned to this particular controller on a network. Static IP address: This is an address that is used when DHCP is disabled. Changing BACNet values  Use the keypad arrows to scroll down to select the desired line ...
Page 76 The next screen allows the device DHCP (Dynamic Host Configuration Protocol) to be enabled or disabled.  Press Enter to change the field value. The Device Name screen allows a specific name to be assigned to the BACNet device. For more information on this subject, please consult the ASHRAE standard number 135‐2001, Annex J, section J5. The BACnet port number is fixed at hexidecimal 0xBAC0 or decimal 47808. It will not function with other port numbers. 76 ...
Page 77: Device Object
The tables on pages 77‐90 are also available on the Honeywell Analyt‐ ics’ Commercial Products CD that accomfpanied the 301C controller and from the Honeywell Analytics technical library (www.honeywellanalytics.com > Products > Commercial Solutions > 301C > Technical Library). Device Object 77 ...
Page 78: Base Objects
Base Objects 78 ...
Page 79: Iaqpoint2
IAQPoint2 79 ...
Page 80 IAQPoint2 continued 80 ...
Page 81 IAQPoint2 continued 81 ...
Page 82: E³Point
E³Point 82 ...
Page 83 E³Point continued 83 ...
Page 84: Xnx And Xcd
XNX and XCD 84 ...
Page 85: Objects For 301Em
Objects for 301EM 85 ...
Page 86 Objects for 301EM continued 86 ...
Page 87: Ec-Fx
EC‐FX 87 ...
Page 88: 420Mdbs_Ir-F9
420MDBS_IR‐F9 88 ...
Page 89: 301Adi
301ADI 89 ...
Page 90 301R 90 ...
Page 91: Bacnet Protocol Implementation Conformance Statement
ANNEX A ‐ PROTOCOL IMPLEMENTATION CONFORMANCE STATE‐ MENT (NORMATIVE) (This annex is part of this Standard and is required for its use.) BACnet Protocol Implementation Conformance Statement Date: __________________2015May07__________________________ Vendor Name: Honeywell International Product Name: 301C Controller Product Model Number: 301C‐DLC‐BIP, AA96D‐DLC‐BIP Application Software Version: __1.1____ Firmware Revision: _1.4.9_____ BACnet Protocol Revision: ___7______ Product Description: Gas Detection controller offering unique zoning capabilities which permit the averaging and comparison of multiple sensor readings. Up to 96 sensors including the E3Point and the Senspoint XCD may be connected. Includes 4 relays. Available in a heavy duty industrial housing and with a datalogging option. BACnet Standardized Device Profile (Annex L):  BACnet Operator Workstation (B‐OWS)  BACnet Advanced Operator Workstation (B‐AWS)  ...
Page 92  Data Sharing‐ReadPropertyMultiple‐B (DS‐RPM‐B)  Data Sharing‐WriteProperty‐B (DS‐WP‐B)  Device Management‐Dynamic Object Binding‐B (DM‐DOB‐B)  Device Management‐Dynamic Device Binding‐B (DM‐DDB‐B)  Device Management‐TimeSynchronization‐B (DM‐TS‐B) Segmentation Capability:  Able to transmit segmented messages Window Size  Able to receive segmented messages Window Size 92 ...
Page 93 Standard Object Types Supported: Optional Writable Dynamically Dynamically Range Object Properties Beyond Creatable? Deletable? Restrictions Supported Standard local_date local_time UTC_offset device N N N none Day‐ light_Savings_St atus ana‐ log_in N N reliability N none put bina‐ ry_inp N N reliability N ...
Page 94   ISO 10646 (UTF‐8) IBM /Microsoft DBCS ISO 8859‐1    ISO 10646 (UCS‐2) ISO 10646 (UCS‐4) JIS X 0208 If this product is a communication gateway, describe the types of non- BACnet equipment/networks(s) that the gateway supports: This supports translating data from Honeywell Analytics proprietary Modbus‐RTU gas detectors to BACnet/IP. Supported detectors in‐ clude the E3Point and the SensePoint XCD. 94 ...
Page 95: Wireless Network
10. Wireless network Not supported. 95 ...
Page 96: How To Build A Title 24 Compliant System
How to Build a Title 24 Compliant System California Title 24 Part 6 specifies mandatory requirements for en‐ closed parking garages. A compliant gas detection system can be con‐ structed from the Honeywell Analytics 301C24 and E³Point Network gas sensor. This section describes how to configure the 301C control‐ ler to accomplish this. Glossary The terminology for a couple of technical concepts differs between Honeywell and California. California’s Honeywell’s Description Term Term A region of a garage containing several proximity sensors. Gas readings in the region are group zone presumed to be similar because of free air circulation. A notification from the gas detection alarm fault system that the system is not working correctly. Requirement: Section 120.6(c)4 “CO concentration at all sensors is maintained at 25 ppm or less at all times.” Solution: Create an event for each group such that if one or more sensors report a concentration greater than 25 ppm the event is acti‐ vated. ...
Page 97 Requirement: Section 120.6(c)7 A‐D “CO sensor shall be: A. Certified by the manufacturer to be accurate within plus or minus 5 percent of measurement. B. Factory calibrated. C. Certified by the manufacturer to drift no more than 5 percent per year. D. Certified by the manufacturer to require calibration no more fre‐ quently than once a year. Solution: Use Honeywell Analytics E3Point Network Gas Monitor with carbon monoxide cartridges. Requirement: Section 120.6(c)7Ei “The CO sensor shall be monitored by a control system. If any sensor has not been calibrated according to the manufacturer’s recommendations within the specified calibration period, the sensor has failed.” Solution: Use E3Point carbon monoxide sensors, which require cali‐ bration every 12 months. Create a event to activate if time since cali‐ bration (TSC) is 12 months. Configure this event to activate fans and the alarm device. 97 ...
Page 98 Requirement: Section 120.6(c)7Eiii “The CO sensor shall be moni‐ tored by a control system. During occupied periods the system com‐ pares the readings of sensors in the same proximity zone, e.g. if the 30 minute rolling average for any sensor in a proximity zone is more than 15 ppm above or below the 30 minute rolling average for other sensor(s) in that proximity zone, the sensor has failed.” Solution: Create an event to activate if the concentration reading of any sensor in a group is an outlier deviating by 15 ppm for longer than 30 minutes. Requirement: Section 120.6(c)7Eii “The CO sensor shall be monitored by a control system. During unoccupied periods the system compares the readings of all sensors, e.g. if any sensor is more than 15 ppm above or below the average of all sensors for longer than 4 hours, the sensor has failed.” Solution: Configure an event to activate if the concentration reading of any sensor in a group is an outlier deviating by 15 ppm for longer than 4 hours. Note that this requirement is less strict that Section 120.6(c)7Eiii above because the aberrant reading is allowed to persist longer. Thus this requirement is only meaningful for garages that are rarely occu‐ 98 ...
Page 99 pied. And the only rationale for implementing this looser require‐ ment would be to avoid superfluous faults. The 301C controller can discriminate between occupied and unoccu‐ pied duration limits this by making two outlier events (for 30 minutes and 4 hours) and making the 30 minute event coverage period only “Daytime”. The hours of “Daytime” can be set under menu function 6. If occupancy is based on some other criterion than the time of day, this binary condition can be accepted into the 301C controller system by a digital input channel of a 301ADI. The event can be made condi‐ tional on the outlier and the digital input. Note: The following requirements are from the The 2013 Nonresiden‐ tial Compliance Manual Appendix A form NRCA‐PRC‐03‐F “Enclosed Parking Garage Exhaust System Acceptance” Requirement: Step A 3 instructs “Temporarily override the pro‐ grammed sensor calibration/ replacement period to 5 minutes.” Solution: Reconfigure the time since calibration (TSC) event time limit to 0 minutes. Alternatively, a stale cartridge can be temporarily plugged into the E³Point. Note that the 301C controller/E³Point system reports time since cali‐ bration in days. Therefore, setting the time limit to 5 minutes would cause an event to activate 1140 minutes (1 day) after calibration. 99 ...
Page 100 Requirement: Form NRCA‐PRC‐03‐F step A 4 instructs “Temporarily place the system in unoccupied mode and override the programmed unoccupied sensor alarm differential from 30% for 4 hours to 1% for 5 minutes.” Solution: Note that the 301C controller measures deviation in ppm, not percent. Change the event screen to outlier deviation 0 ppm du‐ ration 5 minutes. Note that Honeywell Analytics E3Point CO sensors have a resolution of 1 ppm. Requirement: Form NRCA‐PRC‐03‐F step A 5 instructs “Temporarily override the programmed occupied sensor proximity zone alarm dif‐ ferential from 30% for 4 hours to 1% for 5 minutes.” Solution: Like step A 4, Set the event screen to deviation 0 ppm and duration 5 minutes. 100 ...
Page 101: Specifications
Specifications Topic Description 17-27 Vac, 50/60 Hz, 8.64 VA Power requirements 18-36 Vdc, 350mA @ 24 Vdc (8.4 VA) Operating temperature range -20°C to 50°C (-4°F to 122°F) Operating humidity range 0 to 95% RH (non-condensing) Operating altitude Up to 3000 m (9843 ft) Up to 96 transmitters, 32 per channel Network capacity Channels 1, 2 = Modbus and Vulbus...
Page 102: Limited Warranty
Limited Warranty Limited Warranty Honeywell Analytics, Inc. warrants to the original purchaser and/or ultimate customer ("Purchaser") of Vulcain products ("Product") that if any part thereof proves to be defective in material or workmanship within twelve (12) months, such defective part will be repaired or re‐ placed, free of charge, at Honeywell Analytics' discretion if shipped prepaid to Honeywell Analytics at 405 Barclay Blvd., Lincolnshire IL 60069 USA, or 3580 Rue Isabelle Unit 100 Brossard, Quebec, Canada J4Y 2R3, in a package equal to or in the original container. The Product will be returned freight prepaid and repaired or replaced if it is de‐ termined by Honeywell Analytics that the part failed due to defective materials or workmanship. The repair or replacement of any such de‐ fective part shall be Honeywell Analytics' sole and exclusive responsi‐ bility and liability under this limited warranty. Re‐Stocking Policy The following restocking fees will apply when customers return prod‐ ucts for credit: • 15% restocking fee will be applied if the product is returned within 1 month following the shipping date •...
Page 103 (12) month limited warranty of the manufacturer. B. If gas sensors are covered by this limited warranty, the gas sensor is subject to inspection by Honeywell Analytics for extended exposure to excessive gas concentrations if a claim by the Purchaser is made under this limited warranty.
Page 104 Disclaimer of Unstated Warranties The warranty printed above is the only warranty applicable to this purchase. All other warranties, express or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose are hereby disclaimed. Limitation of Liability It is understood and agreed that Honeywell Analytics’ liability, wheth‐ er in contract, in tort, under any warranty, in negligence or otherwise shall not exceed the amount of the purchase price paid by the pur‐ chaser for the product and under no circumstances shall Honeywell Analytics be liable for special, indirect, or consequential damages. The price stated for the product is a consideration limiting Honeywell Ana‐ lytics' liability. No action, regardless of form, arising out of the trans‐ actions under this warranty may be brought by the purchaser more than one year after the cause of actions has occurred. 104 ...
Page 105 Contrôleur 301C Manuel de l’utilisateur M-510324 Révision 04 decémbre 2015...
Page 107 Table des matières Notes et marques de commerce ............109 Définition des symboles ................. 111 Introduction .................... 113 Instructions d’installation ................ 114 Installation murale .................. 115 Détails de connexion................116 Connexions d’alimentation ..............117 Connexions de communication .............. 117 Paramètres d’émetteurs spécifiques ............118 Sortie relais ....................
Page 108 4. Menu Acquisition ................153 Debuter et arreter log Tx ..............154 Débuter et arrêter log événement ............155 5. Menu de copie ................... 156 Configuration ..................157 Paramètres ..................158 Journal système ................. 159 6. Menu de config .................. 160 7.
Page 109: Notes Et Marques De Commerce
à l’exception du contenu des accords écrits avec et pour ses clients. Honeywell ne peut, en aucun cas, être tenue responsable envers quiconque de tout dommage indirect, spécial ou consécutif. Les renseignements et les spécifications figurant dans le présent document sont modifiables sans préavis.
Page 111: Définition Des Symboles
Définition des symboles Le tableau suivant répertorie les symboles utilisés dans ce document pour désigner certaines conditions : Symbole Définition MISE EN GARDE : Identifie les renseignements qui exigent une attention particulière CONSEIL : Identifie les conseils ou astuces, généralement relatifs à l’exécution d’une tâche, à l’intention de l’utilisateur RÉFÉRENCE _ INTERNE : Identifie une source supplémentaire de renseignements dans le...
Page 113: Introduction
Introduction La centrale 301C agit de centrale pour réseaux de détection de gaz, offrant une surveillance continue sur un maximum de 96 unités (avec un 301ADI) connectées. Puisque la centrale est configuré selon vos besoins, l’installation demande simplement le montage et la connexion.
Page 114: Instructions D'installation
Instructions d’installation Directives de base Suivre les instructions minutieusement pour assurer le bon fonctionnement de l’équippement. À défaut de respecter les directives, Honeywell Analytics sera libéré de toute responsabilité : • Installer les unités dans des endroits facilement accessible pour l’entretien • Éviter les endroits où les unités pourraient être exposées aux vibra‐ tions ...
Page 115: Installation Murale
Installation murale Nous recommandons d’installer les centrales à 1.5m (5 pi.) du sol. Mesurer les distances tel qu’indiqué: • Distance en hauteur 16.3 cm (6 13/32”) entre les trous • Distance en largeur entre les trous 26.8 cm (10 9/16”) • Perçer les trous 1/4 po • Fixer la centrale avec les vis appropriées Le câblage de l’unité doit être enfiler dans les trous des pastilles poinçonnées (knock‐out) situées en dessous de l’unité. Passez les câbles de l’unité à travers les orifices à défoncer au bas de l’unité.
Page 116: Détails De Connexion
Détails de connexion Le dessin ci-dessous démontre la connexion pour la centrale. Les descriptions de connecteurs et de connexions se trouvent dans les pages suivantes. Les détails de câblage, alimentation, capacités, etc. se trouvent à la section Spéci_cations de ce guide.
Page 117: Connexions D'alimentation
Le câblage réseau peut être prolongé jusqu'à 2000 pieds (609 mètres) par canal comme un bus sans connecteurs type T-tap. Le contrôleur de 301C communique avec des capteurs de gaz sur un réseau RS-485 Modbus. Cette ligne de transmission exige que les...
Page 118: Paramètres D'émetteurs Spécifiques
à quatre capteurs sont reliés au 301EM celui-ci réserve automatiquement quatre adresses sur le 301C. Au-delà de quatre capteurs, le 301EM réservera sur le 301C, le nombre exact d’adresses correspondants au nombre de capteurs qui y sont reliés et ce jusqu’au maximum permis de 20 capteurs sur le 301EM.
Page 119: Sortie Relais
Sortie relais La sortie relais supporte jusqu’à 5A à 30 Vcc ou 250 Vca (charge résistive seulement). Les relais peuvent activer les alarmes sonores et les lampes stroboscopiques. Consulter le dessin pour instructions de connexion. Chaque relais est configuré avec des valeurs par défaut, cependant, la configuration des relais peut être modifiée depuis le menu de programmation de la centrale.
Page 120: Instructions Pour Cavaliers
Instructions pour cavaliers Les divers cavaliers de la carte (PCB) permettent d’effectuer certaines opérations manuellement: Sujet Description Permet l’ajout de cavaliers de fin de ligne pour améliorer les signaux de communication. Mettre le cavalier en position R pour activer la terminaison EOL 1-4 : fin-de-ligne.
Page 121: Démarrage
Démarrage Assurer que tout le câblage est terminé et effectué selon les spécifications et les détails de connexion avant de mettre la centrale sous tension. Lorsque tout est sécuritaire, enlever le connecteur du cavalier SHDN pour alimenter l’unité (il y aura un délai de quelques secondes).
Page 122: Interface De Programmation
Interface de programmation Le panneau avant du 301C comporte un clavier de boutons poussoirs puis des indicateurs DEL. Panneau 301C Fonctions du clavier La centrale comporte 7 touches de clavier, soit. Le contraste de l'affichage peut être réglé en appuyant sur les touches Haut et Bas lorsque l'écran principal est affiché.
Page 123: Définition Des Del
Définitions des DEL La centrale comporte 7 DEL indiquant le statut de chaque fonction : Description Le DEL rouge clignotant indique qu’un événement est activé. Le DEL rouge continu indique qu’un ou Alarm A: plusieurs transmetteurs ont atteint un niveau d’alarme programmé.
Page 124: Programmation Du Système
Programmation du système Le mode Normal de programmation du système propose plusieurs options de menu accessibles depuis l’écran du menu principal : Mode Description Permet de configurer les paramètres des 1 Info Tx: transmetteurs 2. Groupes : Permet de configurer des groupes de transmetteurs Permet de configurer des événement et les actions 3.
Page 125 Lorsqu’en opération normale, le système affiche l’écran ci-dessous et déroule des écrans d’informations pour chaque dispositif connecté à la centrale: Si un ou plusieurs appareils connectés à la centrale sont en mode d’alarme, la centrale affichera seulement l’écran principal et les écrans pour les appareils en mode d’alarme.
Page 126 L’écran d’information affiche également des icônes représentant certaines fonctions. Voici la liste des icônes et leurs descriptions: Icône Description BACNet : Indique la présence d’un module BACNet en communication avec la centrale. Erreur BACNet : Indique la présence d’un module BACNet, mais que la communication avec la centrale est en faute (erreur) Débogage : Indique que la centrale est en mode débogage (modes de TX unique, Débogage ou Simulation).
Page 127 Puisque les fonctions de programmation de la centrale sont protégées par mot de passe, il est nécessaire d’accéder à l’écran de mot de passe :  Appuyer sur Enter pour afficher l’écran « Mot de passe »  Utiliser les flèches haut ou bas pour augmenter ou diminuer la valeur du premier chiffre  Utiliser la flèche de droite pour passer au prochain chiffre  Lorsque tous les chiffres sont exactes, appuyer sur Enter pour valider le mot de passe et accéder aux fonctions de programmation.
Page 128: Menu Info Tx
1. Menu Info Tx INFO Tx est l’option de menu dédiée aux informations de transmetteurs et contient plusieurs autres options qui peuvent varier selon l’adresse (ou le type) d’appareil. Certains appareils afficheront les options Tx INFO suivantes : Option Description Écran Permet de consulter ou modifier Ident : ...
Page 129: Menu Ident
Menu Ident Le menu Ident, ou identification, permet de consulter ou de modifier l’identification de réseau de la composante sélectionnée : La partie supérieure droit de l’écran affiche l’adresse de réseau de la composante. Sélectionner le champs pour inscrire l’adresse à consulter (si elle est connue) : • Utiliser les flèches pour déplacer le curseur à la gauche de ...
Page 130: Type De Produit Et Types De Sondes
ype de pr roduit et t types de sondes ici une liste d de tous les typ pes de produi ts (préprogra ammés) dispo nibles ns l’option d’id dentification d du menu de r renseignemen nts sur l’émett teur. oduits compa tibles : E3Point 420MDBS...
Page 131: Com
Cet écran affiche le protocole de communication de la composante sélectionnée pour les adresses de 1 à 96. Le protocole de chaque transmetteur est défini par la centrale (voir la section Auto-configuration du réseau). Si un transmetteur est compatible avec plusieurs protocoles, il est possible de sélectionner un autre protocole parmi les options suivantes : Vulbus...
Page 132: Echelle (1 Et 2)
chelle (1 et 2) es menus app paraîssent uni iquement pou ur certains dis spositifs. Eche elle permet de m modifier la plag ge de détectio on, minimum et maximum, ur l’appareil s sélectionné. Q Quelle que so it la valeur sp pécifiée, elle paraîtra sur l’...
Page 133: Détection
Dé étection menu Détect tion (disponib ble uniquemen nt pour les ad dresses de 1 à à ) affiche la pla age de détect tion (plage: 0 à 0.00) ainsi que l’unité de esure (unité : %) pour le tra ansmetteur sé...
Page 134: Affichage
ffichage ette option per rmet de donn er une étique ette ou un nom m à la mposante sél ectionnée (tra ansmetteur, r relais et anno nciateurs). L’é étiquette peut contenir jusq qu’à 20 caract tères, incluan nt les espaces x.
Page 135: Alarme A, B Et C
larme A, B et C isque les écra ans d’affichag ge sont identi ques pour ch hacun des armes, ils ont été regroupé s aux fins de ce manuel. C Cependant, aque alarme d doit être conf iguré séparém ment selon vo os besoins.
Page 136: Entretien Et Exploitation Des Menus
ntretien e et Exploit tation des s Menus es fonctions va arient selon le e type d'émet tteur. Ces écr rans montrent t le mps total du d dispositif a été é mis en serv ice et le temp ps restant jusq qu'à...
Page 137: Code De'etat
ode d’Eta et écran affich e l’état de la transmission (Tx) ou du no oeud (seulem ment ur les appare ils sans-fil) et t l’état de la s onde pour l’a adresse du spositif sélecti onné, en vale eurs hexadéc cimales.
Page 138: Effacer Tx Courant
ffacer Tx x couran ette fonction p permet de sup pprimer la con nfiguration (In nfoTx seuleme ent) la composan nte sélectionn ée. ote: Cette fonc ction efface se seulement les données Info oTx. Aucune tre informatio on n’est effacé ée.
Page 139: Modification De L'adresse De L'émetteur
odificatio on de l’ad dresse de e l’émette L’o option Change er l’adresse p permet de mo difier l’adress se d’un dispot tif : L’o option Change er l’adresse e est seulement t disponible po our les adres 1 à 96 et s’il y a un appare eil Modbus co onnecté.
Page 140: Menu Groupes
. Menu g groupes programmati on de groupe es de transme etteurs perme et de regroupe s unités, ce q qui permet d’a agir (événeme ents) en répon nse à un grou d’u unités plutôt q que sur chaqu ue unité, indiv viduellement.
Page 141: Créer Des Groupes
Créer des groupes Le contrôleur 301C accepte différents modèles d'émetteurs avec une variété de capteurs de gaz. Il peut organiser les données de façon pra- tique en utilisant des groupes et événements. Cependant, la logique du groupe exige que tous les membres du groupe appartiennent aux mêmes modèles d'émetteurs et au même type de capteur.
Page 142: Supprimer Des Groupes
Supprimer des groupes La commande vider les groupes permet de supprimer tous les groupes configurés dans la centrale. Pour supprimer des groupes individuellement : • Afficher le premier transmetteur du groupe • Sélectionner le transmetteur (l’adresse clignote) et utiliser les flèches pour dérouler les options et sélectionner <del> (l’option <del> supprime l’entrée et l’option <fin> indique la fin du bloc. • Appuyer sur Enter et le groupe est vidé. Cette procédure permet de supprimer un, plusieurs ou tous les transmetteurs du groupe. Note: Vous pouvez créer jusqu’à...
Page 143: Menu Événement
3. Menu événement Quoique la centrale est expédiée avec des configurations d’événement par défaut (exemple ci-dessous), le menu Évenement offre la flexibilité de modifier les paramètres. La programmation d’événement permet de définir des actions précises : Option Description Écran Quelle action sera activée si les Action: critères configures sont atteints Définition du délais à...
Page 144: Action
Action Les actions comprennent deux paramètres : 3. EVE NE ME NT -Acti on- Cible: Ctrl Relais: Paramètre Description Indique le composant responsable de l’action à exécuter; Tx (transmetteur) Cible Re (relais/indicateur) Ctrl (centrale) Indique quelle des trois sorties activé lorsque l’événement est vrai : #XX (active le relais #xx de la composante), Relais...
Page 145: Délais
Délais Cette option permet de configurer les paramètres Avant et Après qui retardent l’activation ou la désactivation d’une action. Avant Retarde une action pour la durée de temps précisée. Si la condition persiste après le délai précisé, un alarme est activé et l’action précisée est effectuée.
Page 146: Délais Mode Latch
Délais mode latch  La fonction Latch, disponible depuis le menu déroulant du délais.  Après, est exécuté sur un état d’événement. Essentiellement, c’est un circuit de verrouillage, c’est à dire qu’une intervention humaine est nécessaire pour déverrouiller l’action de l’événement.  L’événement demeure actif jusqu’au moment de pression sur la touché Silence.  Cette touche arrête l’alarme sonore et relâche l’événement. Lors de l’appui sur la touche Silence, les événements sont relâchés et réévalués.  Si la condition de l’événement est toujours vrai,l’événement demeure actif et revient en mode Latch. Si la condition ne persiste pas, l’événement est désactivé. Note: Si un événement est configuré avec un délais Avant et que la touche Silence est enfoncée lorsque les conditions de l’événement sont toujours vraies, l’alarme sonore sera fermé...
Page 147: Conditions
onditions s Conditions s sont les para mètres de dé éfinition (de ca alculs) qui déc cident si un é événement es st vrai ou non. . Chaque con ndition est déf finie r quatres élém ments. Il est é également po ssible de lier deux conditio...
Page 148 La partie supérieur de gauche contient le quantificateur de statistique (disponible seulement pour les groupes). Cette option permet de choisir quelle partie du groupe à inclure dans l’équation. Les optionsde ce champs sont : Option Description tous comprend tous les émetteurs du groupe comprend la concentration moyenne des émetteurs du groupe comprend la concentration maximale du groupe comprend la concentration minimale du groupe...
Page 149 La partie inférieure à gauche de l’écran contient le quantificateur de logique, ou l’opérateur, qui détermine comment les conditions sont calculées. Les options disponibles dans ce champs sont : Symbole Signification opérateur Aucun opérateur Égal à Égal à ou inférieur à <= <...
Page 150 La partie supérieure droite de l’écran contient la source, ce qui défini sur quel unité ou groupe d’unités l’événement sera basé. Les options disponibles dans ce champs sont : Option Description Inclus tous les transmetteurs (voir note) GrTous Gr000 Inclus seulement les unités dans le groupe précisé (voir note) Inclus seulement le transmetteur précisé...
Page 151 La partie supérieure droite de l’écran contient la source, ce qui défini sur quel unité ou groupe d’unités l’événement sera basé. Les options disponibles dans ce champs sont : Option Description Utilisé pour le statut des entrées binaires (ex. : utilisé avec le 301ADI) Utilisé...
Page 152: Statut
Statut Cet écran affiche l’état actuel des événements et permet de les activer ou de les désactiver, selon l’état actuel. Active événement : Appuyer sur Enter pour sélectionner Active evenement ou Desactive evenement 3. EVENEMENT -Statut : desacti ve- Acti ve evenemen t Lorsque tous les détails d’un événement sont inscrits, le dernier écran de configuration affiche «...
Page 153: Menu Acquisition
Menu Acquisition Le mode Acquisition est seulement disponible lorsque la centrale est munie d’une carte SD (option d’enregistrement de données). Cette fonction permet d’activer ou de désactiver l’enregistrement des événements du système ou les informations des transmetteurs. L’information est enregistrée sur une carte de mémoire « SD ». L’utilisateur doit configurer les intervales et les conditions d’enregistrement nécessaires à...
Page 154: Debuter Et Arreter Log Tx
Debuter et arreter log Tx L’étape précédente traitait la fréquence d’enregistrement de données. Maintenant, il faut débuter le processus : Lorsque « Debuter log Tx » est affiché, le mode acquisition (enregistrement) est inactif. Lorsque « Arreter log Tx » est affiché, les données sont en cours d’enregistrement.
Page 155: Débuter Et Arrêter Log Événement
Débuter et arrêter log événement Le menu Acquisition offre l’option d’enregistrement d’événements. L’enregistrement d’événements enregistre les transactions de la centrale, les événements, les avertisseurs de Tx et d’alarmes et le statut de relais. Lorsque « Debuter log even. » est affiché, le mode acquisition (enregistrement) est inactif.
Page 156: Menu De Copie
5. Menu de copie L’option Copie du menu Info TX permet de copier ou de transférer les paramètres programmés. Il est possible de transférer des données d’une carte SD de la centrale à un ordinateur et vice versa ou de copier des paramètres d’un transmetteur à...
Page 157: Configuration
Configuration Si la centrale est munie d’une carte mémoire, la fonction Configuration permet de transférer les données soit du 301C à la carte SD ou vice versa. Ceci permet de transférer la programmation de la centrale sur un ordinateur ou d’un ordinateur à la centrale.
Page 158: Paramètres
Paramètres La fonction paramètres permet de copier la configuration d’un transmetteur à un autre ou de copier les paramètres d’un événement à un autre. Ceci permet une configuration plus rapide pour les unités partageant des paramètres identiques ou similaires 5. Copie -para me tres- InfoTx vers InfoTx Evene.
Page 159: Journal Système
Journal système La centrale enregistre les données du journal dans sa mémoire interne. Si la centrale est munie d’une carte mémoire, la fonction Journal Sys permet d’enregistrer les informations de journal du système en format texte sur la carte de mémoire flash (SD card). 5.
Page 160: Menu De Config
Cnfg po rt esclave Adr esse: 001 384 00 bau ds Mdbs RTU 8D 2S NP 6. Config Configurat. rela is Emissio n A P: auto Honeywell Configuration rela is Configuration rela is -Failsafe- -Sile nce- Tous le s relai s Inactif 6.
Page 161 La sélection de la première ligne (du premier écran) offre le choix de trois modes d’affichage : Defilement manuel, Defilement 3 sec, Defilement 5 sec. Ces réglages contrôlent la présence et la fréquence d’affichage des données à l’écran de la centrale. Le mode de défilement manuel signifie que l’utilisateur doit appuyer sur les flèches pour visionner le statut de chaque unité...
Page 162  Lorsque le mot de passe désiré est afficher, appuyer sur Enter pour le valider et quitter le mode d’édition. Note: Communiquer avec le soutien technique de Honeywell pour assistance concernant les mots de passe perdus au 1-800-563- 2967.
Page 163 6. Config Configurat. rela is Emissio n A P: auto Honeywell La sélection Configurat. relais offre deux options supplémentaires pour la configuration des relais : La première option, Failsafe, permet d’activer (ou désactiver) tous les relais en appuyant sur la touche Enter. Cette fonction est utilisée en cas de panne d’électricité: en cas de panne, le relais déclenche le dispositif...
Page 164 Le quatrième écran de configuration permet de programmer une définition d’un jour et d’une semaine. 6. Config Definiti on jour Definiti on semain e Les définitions de jour ou de semaine permettent de définir les plages d’heures représentées par Jour et les plages de journées représentées par Semaine.
Page 165: Menu De Réseau
7. Menu de Réseau Le menu Reseau permet soit de réinitialiser ou de balayer les informations de dispositifs de réseau. Ce menu offre plusieurs options supplémentaires, en deux écrans. Le premier écran contient trois options : Option Description Réinitialise toutes les informations de dispositifs de réseau dans la base de données.
Page 166 Le deuxième écran de Reseau présente les options Statistiques et Etalonnage. 7. Reseau Statistique s Etalonn age La sélection de statistiques affichent les statistiques pour l’adresse précisée. Statistique s Vali de 100% Erre urs San s rep Terme Description Indique le nombre de réponses valides pour les 16 Valide dernières requêtes.
Page 167: Étalonnage À Distance
Étalonnage à distance Le menu Reseau offre également l’option Etalonnage permettant d’effectuer un étalonnage à distance pour les dispositifs qui supportent l’étalonnage en réseau. 7. Reseau Statistique s Etalonn age L'écran d'étalonnage contient quatre (4) lignes d'information : Calib 001 : 301D2 Statut : Normal Etal Ze ro Etal plage...
Page 168 Etalonn er Zer o? Etal Ze ro Etal plage *L'unité doit être configurée dans la base de donnée du 301C pour figurer dans la liste d'adresses d'unités affichée à l'écran. 6. Appuyer sur Enter pour confirmer ou Esc pour annuler. Si confirmé, la centrale procède à...
Page 169 7. Pour étalonner l’appareil, sélectionnez Régler intervalle de mesure** et modifiez la valeur d’étalonnage du gaz de réglage en procédant comme suit : Calib 001 : 301D2 Statut : Normal Etal Ze ro Etal plage a. Utiliser la flèche droite pour déplacer le curseur à la gauche de xxx ppm (champ de valeur d'étalonnage).
Page 170: Menu Tests
8. Menu tests Le menu Tests permet d’effectuer une gamme de vérifications sur les composantes et sur les communications de réseau. Ce menu permet également d’opérer le système dans quatre modes différents, chacun offrant des fonctionalités particulières. MENU 5. Copie 7.
Page 171 Le menu Tests offre quatre options principales, disponibles sur deux écrans. Chacune de ces options offres des fonctionnalités supplémentaires. Le premier écran présente trois options : 8. Tests Sequ ence de test Debuter sequ. Sim. Charge maximum Option Description Permet d’activer chaque sortie et de valider l’opération de chaque touche de clavier, des pix- Sequence de test els d’affichage et les divers protocoles de...
Page 172: Séquence De Tests
Séquence de tests Lors de la sélection de cette option, la centrale affiche l’écran de Séquence de test. Appuyer sur ESC à n’importe quelle étape pour revenir à l’écran principale du menu Tests. Seq uence de test Relais actives App uye z une touche ESC pour qui ttter Appuyer sur n’importe quelle touche pour procéder aux tests du système.
Page 173 Le dernier test est l’essais de communication de réseau : Seq uence de test Test co mm. reseau 960 0 bau ds Chann el 1 SUCCE S Assitôt ces essais commencés, il n’est pas possible de les interrompre ou de les arrêter. Le système essaye chacun des cinq bauds (vitesse de communication : 9600, 19200, 38400, 57600, 115200) et chacun des quatre canaux par baud.
Page 174: Mode Normal
Mode Normal Ceci est le mode d’opération normal (par défaut) du système. Lorsque le système est en mode normal, certaines valeurs peuvent être modifiées sans interruption de services. Toute modification est validée et effectuée lors du retour à l’écran principale. Mode Émetteur unique Ce mode permet d’effectuer l’analyse de transmetteurs, un à...
Page 175: Mode Simulation
Mode Simulation Ce mode désactive les mises à jour d’information de communication de réseau. Ce mode peut être employé, peu importe quel est le mode d’opération actuel du système (exemple: l’emploi du mode Silumlation simultanément avec le mode Débogage permet d’évaluer le système au complet [groupes, événements, etc.] sans déclencher des actions ou sans utilisation de matériel supplémentaire).
Page 176: Menu Bacnet
Cette section permet de configurer l'interface BACnet en option (incluse dans les modèles avec «BIP» figurant dans le numéro de pièce). L'interface 301C BACnet/IP a été homologuée par BACnet Testing Labs comme étant conforme à la version 7 du protocole BACnet.
Page 178 Le premier écran permet de configurer l’identification et l’adresse : 9. BACNet -App areil- BACne t ID Adr esse statique IP BACnet ID : (Building Automation and Control Networks) est le numéro assigné à une centrale sur le réseau. Adresse IP statique : Ceci est une adresse qui est toujours assignée à...
Page 179 Le deuxième écran permet d’activer ou de désactiver le protocole DHCP (Dynamic Host Configuration Protocol). 9. BACNet -DHCP : desacti ve- Acti ve DHCP Appuyer sur la touche Enter pour basculer le champs Activer ou Desactiver DHCP. Consulter votre service de TI pour de plus amples informations sur le DHCP.
Page 180: Device Object
Les tableaux des pages 181 à 203 sont également disponibles sur le CD des produits commerciaux de Honeywell Analytics livré avec le contrôleur 301C et dans la bibliothèque technique de Honeywell Analytics (www.honeywellanalytics.com > Products > Commercial Solutions > 301C > Technical Library).
Page 181: Objets De Base
Objets de base...
Page 182: Iaqpoint2
IAQPoint2...
Page 183 IAQPoint2 (suite)
Page 184 IAQPoint2 (suite)
Page 185: E³Point
E³Point...
Page 186 E³Point (suite)
Page 187: Xnx Et Xcd
XNX et XCD...
Page 188: Objets Du 301Em
Objets du 301EM...
Page 189 Objets du 301EM (suite)
Page 190: Ec-Fx
EC-FX...
Page 191: 420Mdbs_Ir-F9
420MDBS_IR-F9...
Page 192: 301Adi
301 ADI...
Page 193: 193
301R...
Page 194: Protocol Implementation Conformance Statement (Normative)
BACnet Protocol Implementation Conformance Statement Date: __________________2015May07__________________________ Vendor Name: Honeywell International Product Name: 301C Controller Product Model Number: 301C-DLC-BIP, AA96D-DLC-BIP Application Software Version: __1.1____ Firmware Revision: _1.4.9_____ BACnet Protocol Revision: ___7______ Product Description: Gas Detection controller offering unique zoning capabilities which permit the averaging and comparison of multiple sensor readings.
Page 195  Data Sharing-ReadPropertyMultiple-B (DS-RPM-B)  Data Sharing-WriteProperty-B (DS-WP-B)  Device Management-Dynamic Object Binding-B (DM-DOB-B)  Device Management-Dynamic Device Binding-B (DM-DDB-B)  Device Management-TimeSynchronization-B (DM-TS-B) Segmentation Capability:  Able to transmit segmented messages Window Size  Able to receive segmented messages Window Size...
Page 196 Standard Object Types Supported: Writabl Dynamicall Dynamicall Optional Range Objec Properties Beyond Restriction Creatable? Deletable? Supported Standar local_date local_time devic UTC_offset none Daylight_Savin gs_Status analo g_inp reliability none binary reliability none _input Data Link Layer Options:  BACnet IP, (Annex J) ...
Page 197 JIS X 0208 If this product is a communication gateway, describe the types of non-BACnet equipment/networks(s) that the gateway supports: This supports translating data from Honeywell Analytics proprietary Modbus-RTU gas detectors to BACnet/IP. Supported detectors include the E3Point and the SensePoint XCD.
Page 198: Reseau Sans-Fil
10. Reseau sans-fil Non pris en charge.
Page 199: Spécifications
Spécifications Sujet Description 17-27 VCA, 50/60 Hz, 8,64 VA Alimentation requise pour le 301C 18-36 VCC, 350 mA à 24 VCC (8,4 VA) Plage de température de -20 °C à 50 °C (-4 °F à 122 F) fonctionnement Plage d’humidité en 0 à...
Page 200: Garantie Limitée
équivalent. Le Produit sera renvoyé en fret prépayé et réparé ou remplacé s’il est déterminé par Honeywell Analytics que la défaillance de la pièce est due à un vice de matériau ou de fabrication. La réparation ou le remplacement de cette pièce défectueuse constitue la seule responsabilité...
Page 201 éléments de filtre. Limitation et exclusion de la garantie Dans le cadre de cette garantie limitée, Honeywell Analytics n’a aucune autre obligation. Toutes les obligations de garantie de Honeywell Analytics sont annulées si le produit a fait l’objet d’usage abusif, de mauvaises utilisations, de négligence ou d’un accident ou si l’acheteur...
Page 202 Limitation de responsabilité Il est entendu et accepté que la responsabilité de Honeywell Analytics, que la cause invoquée soit le contrat, le délit civil, n’importe quelle garantie de responsabilité, la négligence ou autre, n’excédera pas le prix d’achat payé...

Honeywell 301C User Manual

Quick Links

3 English

107 Français

Chapters

3 English

107 Français

Also See for Honeywell 301C

Related Manuals for Honeywell 301C

Summary of Contents for Honeywell 301C

3
English

107
Français

3
English

107
Français