DDC Online direct digital controls
Invensys - Network 8000  

MicroFlow II Controller

Secondary Control Units
MicroFlow II Controller
Date Last Saved: 6/1/2007 2:47:19 PM

Product Name(s): MicroFlow II Controller
Product Description: The MicroFlow II controller 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 MicroFlowII VAV controllers are designed to control common configurations of pressure-independent VAV terminal boxes, with or without fan and/or reheat.
Point Quantity Characteristics
Analog Input (AI): 4*/See below Zone temperatureDuct temperatureFlow 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:
A/D Converter Resolution
8 bit
10 bit
12 bit
16 bit
Other Information not provided
D/A Converter Resolution
6 bit
8 bit
10 bit
No Analog Output
Other Information not provided
HOA switches provided on each output?
Note: These are also available as an add-on from 3rd party vendors.
No
Both AO and DO
DO Only
Other
Indicating status LED on each output?
No
AO and DO
AO Only
DO Only
Other
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
Expander Boards None
Network Ports, Protocol(s), and Speed(s) Supported
(Note: See 'Architecture' for network details)
(1) - Proprietary to secondary ASD Bus @ 19.2 kbps (peer-to-peer)
External Communication Ports, Speeds and Access Devices (1) - Proprietary port for Personal System Interface (PSI) hand held device. (1)

(1) - Serial port
Additional Information (Optional)
Network Accessing Capabilities via Controller
Access controller only
Access controller plus additional controllers on network segment / LAN
Access all controllers on system
No access available on this controller
Other Information not provided
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
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
Zone-Mounted touchpad (thermostat or stand-alone display)
HID (proprietary device)
PDA (3rd party HID, with software)
Laptop/PC
none
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.
Functions Available Through Field Interface**:View ParamsChange ParamsChange
Programs/Logic
O&M SupportTAB/Cx Support
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
Microprocessor(s) 80C198 @ 7 MHz (16 bit)
Clock Type
Powered, battery-backed
Battery powered
Powered, no battery backing
None
Other
Clock Synchronization Not applicable
Volatile Memory (RAM) Capacity 8 kB RAM
Volatile Memory (RAM) Uses
RAM use unrestricted
RAM use restricted as shown below
Information Not Provided
Program Execution / Calculation storage
Data / Trends / Alarms storage
Configuration / Parameter storage
Control Programming storage
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)* 2 kB EEPROM
Non-Volatile Memory Uses
Data / Trends / Alarms / Calculation Storage
Configuration / Parameter Storage
Control Programming Storage
Controller Operating System
Other
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.
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? None - trend points are called by and stored at the GCM
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 Method(s) 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
Resident/Supervisory. This controller supervises the scheduling of other controllers.
Resident/Stand Alone. This controller contains its own schedule.
Non-Resident. This controller is dependent upon another controller for its schedule.
None. This controller has no scheduling features.
Other
Resident Energy Management
Energy management algorithms for this controller can be custom programmed
Pre-programmed/built-in algorithms available, and are fully editable using custom programming
Pre-Programmed/built-in with limited editing via template-based programming
Controller is not typically used for energy management functions
Others
Specific Pre-Programmed Algorithms Available
None (custom programming only)
None (not applicable)
Optimal Start/Optimal Stop
Peak Demand Limiting/Load Shedding
Economizer (enthalpy, dry-bulb, CO2, modulating/2-position, etc.)
Other
Additional Energy Management functions are resident at SI
Additional Programming Functions
DDC Loops (P, PI, PID) PI
Automatic PID Tuning Feature No
Automatical-Dial Alarm Support No
Does controller perform multiple retries 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
Outputs fail to last position
Other
Volatile memory functions?
Lost
Retained for life of backup battery
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 (no battery)
Upon network or communications failure does controller:
Continue to operate standalone? Yes
Operate with last global settings or user-specified value? N.A.
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
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?
 
Control Enclosure Optional NEMA 1 enclosure available
Power Supply Required
Voltage 24 Vac
VA 5 VA, plus power for DO's (if used). 41 VA max
Surge Protection Provided
Underwriters Laboratories UL 916 PAZX (Energy Management)

CSA LR-3728
FCC Part 15, Sub-Part B, Class A
CE
LonMark Certified
Yes
No
No - but LonWorks compatible
Information not provided
BACnet (BTL) Certified
Yes
No
Not submitted for testing
Information not provided
Other