+ Home|+ Guide to DDC|+ Manufacturer Products|+ Contact

Search


Manufacturers




Quick Links

Add Quick Link
 Delete Quick Links
Manufacturers > Invensys Building Systems > Network 8000  >  Product Preview

Print this page. Invensys Building Systems - Network 8000

MN-FLO; MN-FLO3T

Secondary Control Units
MicroNet VAV
Last Saved: Dec 18, 2003 3:34:40 PM

Description

Product Name(s):

  • MN-FLO
  • MN-FLO3T

Product Description:

The MicroNet VAV -Series is an application-specific, pre-programmed (user configurable) VAV terminal box controller with integral damper actuator and flow sensor. These controllers take standard zone sensor inputs as shown below and provide flow control. The two models are identical except the MN-FLO3T model provides 3 triac outputs for controlling reheat. MicroNet controllers reside an a sub-network to the secondary ASD Bus called the 'U' Bus, which is supervised by the MicroNet Integrator supervisory interface.

Product Application(s):

The MicroNet VAV controllers are designed to control common configurations of pressure-independent VAV terminal boxes, with or without fan and/or reheat.
Input/Output Processing
Point Quantity Characteristics
Analog Input (AI) 4*/See below Zone temperature

Duct temperature

Flow sensor (on-board; see below)

Zone setpoint (optional)
Digital Input (DI) 1* /See below Occupant override (optional)
Universal Input (AI or DI)    
Analog Output (AO) 1 Damper output (on-board; see below)
Digital Output (DO) 3** /See below Triac switches (24 VA total combined load at 24 Vac for DO-1 and DO-2; 12 VA for DO-3).
Universal Output (UO)    
Other    

Control Unit Model #:AIDIUIDOAOUOOther

A/D Converter Resolution
- 8 bit
- 10 bit
- 12 bit
- 16 bit
X Other (Information not provided)
D/A Converter Resolution
- 6 bit
- 8 bit
- 10 bit
- No Analog Output
X Other (Information not provided)
HOA switches provided on each output?
Note: These are also available as an add-on from 3rd party vendors.
X No
- Both AO and DO
- DO Only
- Other
Indicating status LED on each output?
X No
- AO and DO
- AO Only
- DO Only
- Other
Additional Features *All inputs are provided from a proprietary zone thermostat over a 2-wire local network port (as opposed to separate terminated inputs)

** Provided with MN-FLO3T model only


VAV Controllers
Integral Flow Sensor? Yes (Range 0.0 - 2.0 inches; Accuracy ± 5% @ 1.00 inch)
Integral Damper Actuator? Yes (Stroke 0-90 degree adjustable Timing 3min. @ 90 deg. 60Hz. Torque 53 lb-in. Visual Position Indicator. Manual Override)
Can controller accept occupant override from thermostat? Yes
Can controller accept occupancy sensor input? Yes
I/O Expansion
Expander Boards None

Expansion Device Model #AIDIUIDOAOUOOther

Network and External Communication Ports

Network Ports, Protocol(s), and Speed(s) Supported

(Note: See 'Architecture' for network details)

 (1) - Proprietary to secondary U Bus (used solely for MicroNet controllers) @ 9.6 kbps (polling)
External Communication Ports, Speeds and Access Devices (1) - Proprietary MicroNet 'U-Link' port which is used for Wall Sensor or a proprietary portable PC port.
Additional Information
(Optional)
 		 
Operator Interfaces (via Controller) *
Network Accessing Capabilities via Controller
no Access controller only
yes Access controller plus additional controllers on network segment / LAN
no Access all controllers on system
no No access available on this controller
no Other
Controller Access Devices
  Laptop/PC
  Local Display Panel (controller-mounted)
  Local Display Panel (zone-mounted)
  Handheld Interface Device (proprietary device)
  PDA (3rd-Party HID)
  Zone-Based port (details below)
  Other
Functions Available Through Field Interface**:View ParamsChange ParamsChange
Programs/Logic		O&M SupportTAB/Cx Support
Laptop/PC XX XX
Zone-Based port (details below)  X  X
Zone-Based Interface Access When Wall Sensor is used, the PC is connected to port at sensor. PC connection is proprietary and allows complete access to other U Bus controllers and interface for editing, monitoring, and air balancing.
Zone Interface Hardware
no Zone-Mounted touchpad (thermostat or stand-alone display)
no HID (proprietary device)
no PDA (3rd party HID, with software)
yes Laptop/PC
no none
no Other
*Note: This section covers the capabilities for accessing the controller or other parts of the network from the controller (i.e. 'bottom-up'). Standard access functionality is covered in the Architecture and Software sections.
**Does NOT include front-end OI functions. See vendor for specific functions available.
Processor, Memory, and Battery
Microprocessor(s) 80C198 @ 7 MHz (16 bit)
Clock Type
no Powered, battery-backed
no Battery powered
no Powered, no battery backing
yes None
no Other
Clock Synchronization Not applicable
Volatile Memory (RAM) Capacity 8kB RAM
Volatile Memory (RAM) Uses
- RAM use unrestricted
- RAM use restricted as shown below
X Information Not Provided
no Program Execution / Calculation storage
no Data / Trends / Alarms storage
no Configuration / Parameter storage
no Control Programming storage
yes Others (Information not provided)
Is Volatile Memory Supported By Battery? No
Battery Type(s) Not applicable
Battery Life Not applicable
Backup Battery Operating Time Not applicable
Non-Volatile Memory Capacity
(EEPROM/Flash) *
 		Information not provided.
Non Volatile Memory Uses
no Data / Trends / Alarms / Calculation Storage
no Configuration / Parameter Storage
no Control Programming Storage
no Controller Operating System
yes Other (Information not provided)
Additional Information  
* Items in NV memory are not lost upon power or battery failure. Other types of NV memory such as EPROM, NOVROM, etc. do not directly impact system performance.
Trend Data Storage
Can trend data be stored in this controller? No
How many total trend values can be stored? Not applicable
What is the controllers role in trending? Information not provided
Can controller be programmed to 'push' data to archive or are trends 'pulled' from controller?  
When full, does controller automatically send up trend data; overwrite data, or stop logging data? Not applicable
Programming

Programming Method(s)

(See Also 'Software' Form)

 Uses Network 8000 Object Block programming. 'Object Blocks' are available for many common DDC control routines, and custom Object Blocks can be written and used in programming when required. Block parameters and values are left as template-based inputs by the user.
Resident vs. Non-Resident Program Execution Local control loop logic is resident at the controller. Schedules, trending, data control, and global point sharing requires GCM supervisory interface.

Scheduling

(See Also 'Software' Form)
no Resident/Supervisory. This controller supervises the scheduling of other controllers.
no Resident/Stand Alone. This controller contains its own schedule.
yes Non-Resident. This controller is dependent upon another controller for its schedule.
no None. This controller has no scheduling features.
no Other

Resident Energy Management

(Controller-resident energy management functions/algorithms calculated and performed by this controller. These typically require point-sharing and can involve calculations and multiple-loop functions. One or more of these choices may be selected.)
no Energy management algorithms for this controller can be custom programmed
no Pre-programmed/built-in algorithms available, and are fully editable using custom programming
no Pre-Programmed/built-in with limited editing via template-based programming
yes Controller is not typically used for energy management functions
no Others
Specific Pre-Programmed Algorithms Available
yes None (custom programming only)
no None (not applicable)
no Optimal Start/Optimal Stop
no Peak Demand Limiting/Load Shedding
no Economizer (enthalpy, dry-bulb, CO2, modulating/2-position, etc.)
no Other
yes Additional Energy Management functions are resident at SI
Additional Programming Functions  
Controller Features
DDC Loops (P, PI, PID) PI
Automatic PID Tuning Feature No

Automatic-Dial Alarm Support

(See 'Software' for further information)

 No
Does controller perform multiple retires and buffer/store alarm until connection is made? No
Are multiple destinations possible? No
Upon controller power loss or hardware failure:
Are network communications affected? No
Is loss recognized on/by the network and alarm reported? Yes
DO and AO response?
- Outputs fail to a user pre-specified position
- Outputs fail to a normal (unpowered) position
X Outputs fail to last position
- Other

Volatile memory functions?


(See 'Memory' section)
- Lost
- Retained for life of backup battery
X Other (Information not provided)
Upon restoration of power does the controller:
Auto-reboot without operator intervention? Yes. Special reboot control functions can be programmed to accommodate component sequencing.
Automatically reset/synchronize the clock? Not applicable
Update all monitored functions? Yes
Generate an alarm if backup battery is dead? Not applicable
Upon network or communications failure:
Does controller:  

Continue to operate standalone?

 Yes

Operate with last global settings or user-specified value?

 Global values default to last value or a programmed pre-assigned value.
Do broken network segments continue to communicate within the remaining segment?
(Note: may depend on proper termination of segments for higher speed networks.)
 		No
Does network automatically reconfigure upon restoration? Yes - Communications between controllers is automatically restored upon network reconnection.
Does network store 'loss of communications' alarm with time of event? Yes
Additional Information (optional) Special reboot control functions can be programmed to accommodate component sequencing
Self Test Diagnostics

Does controller have internal self-test diagnostics to check:
Processor failure? Information not provided
Internal hardware failure? Information not provided
Open/shortened sensor? Information not provided
Others? Information not provided
 
Control Enclosure Optional NEMA 1 enclosure available
Power Supply
Power Supply Required  
Voltage 24 Vac
VA 5 VA, plus power for DO's (if used). 41 VA max.
Surge Protection Provided
Listing, Labeling, and Compliance
Underwriters Laboratories UL 916 PAZX (Energy Management)
CSA LR-3728
FCC Part 15, Sub-Part B, Class A
CE  
LonMark Certified
- Yes
X No
- No - but LonWorks compatible
- Information not provided
BACnet (BTL) Certified
- Yes
X No
- Not submitted for testing
- Information not provided
Other  
Supported by the Iowa Energy Center.
http://energy.iastate.edu/
Copyright Iowa Energy Center.