Rickard MCU 2 User manual

1
RICKARD 2019
MLM INTEGRATION WITH BMS
MLM INTERGRATION
WITH BMS
ISSUE 4

2
RICKARD 2019
MLM INTEGRATION WITH BMS
MLM Integration with BMS...........................................................................................................................................................................................................1
MCU 2 Gateway Overview .........................................................................................................................................................................................................3
Output from BMS ..........................................................................................................................................................................................................................3
Input to BMS .......................................................................................................................................................................................................................................4
Zone/Master/Slave Diffuser concept …………………………………………………………………………………………………………………………...…..4
Channel and Zone designations ...............................................................................................................................................................................5
Identifying, mapping and binding of network variables to other network protocols ...................6
MCU to Lon Mapping ..............................................................................................................................................................................................................6
Discovering the MCU 2 with Lon ……………………………………………………………………………………………………………………………………….7
MCU 2 BACnet to BMS setup ……………………………………………………………………………………………………………………………………………….9
Bacnet/IP setup ……………………………………………………………………………………………………………………………………………………………………………….9
BACnet ms/tp setup …………………………………………………………………………………………………………………………………………………………………….10
MCU BACnet point mapping ………………………………………………………………………………………………………………………………………………...11
Diffuser Mode (status) - multi-state input 0-59 ……………………………………………………………………………………………………...14
Occupancy Mode (status) - multi-state input 60-119 ………………………………………………………………………………………....15
BMS control override - multi-state output 0-59 ……………………………………………………………………………………………………..15
Occupancy override - multi-state output 60-119 …………………………………………………………………………………………………..15
MLM Control Override Handling Procedure ……………………………………………………………………………………………………………….17
Manual control override activation …………………………………………………………………………………………………………………………………..17
RTC control override activation ..................................................................................................................................................................................18
RTC control override operation ..................................................................................................................................................................................19
RTC control override Command Table: ………………………………………………………………………………………………………………………….19
Occupancy sensor description ……………………………………………………………………………………………………………………………………………..19
Occupancy control override operation ………………………………………………………………………………………………………………………….20
System set-up for Occupancy Sense ……………………………………………………………………………………………………………………………….20
MLM Tool occupancy wizard ………………………………………………………………………………………………………………………………………………...22
MLM24 Tool Occupancy display ................................................................................................................................................................................22
Occupancy override ……………………………………………………………………………………………………………………………………………………………………..23
Light Switch operation ……………………………………………………………………………………………………………………………………………………………….23
Airflow sense setup and operation …………………………………………………………………………………………………………………………………...24
Table of Contents

3
RICKARD 2019
MLM INTEGRATION WITH BMS
MCU 2 Gateway Overview
The Master Comms Unit 2 (MCU) serves as a gateway to other BMS protocols such as Lontalk or BacNet.
The MCU features four diffuser data channels with a capacity of 15 diffusers each, i.e. a total of 60 diffusers can
be connected to a single MCU. It also interfaces with the MLM Tool application for setup, diagnostic and moni-
toring functions.
The following physical protocol interfaces are supported:
 MLM Tool application (UDP/IP) – Magnetic Ethernet
 MLM Tool application(ms/tp) – USB
 BacNet/IP – Magnetic Ethernet
 BacNet ms/tp – RS485 bus
 Lontalk - TP/FT-10 bus
The following MCU 2 hardware models are available:
Please note: The Standard and BACnet/IP MCU contains a two port magnetic Ethernet switch.
BACnet ms/tp and the Lon MCU only contains USB user interfaces.
The following network variables of the MLM Proprietary network are visible to other BMS network protocols:
Output from BMS
Temperature Setpoint
 BACnet - 0.1 °C, .5 °F resolution
 Lon - 1°C resolution (°F not supported)
 Control Override command available in BACnet:
 Drive Diffuser Open to pre-set limit position
 Drive Diffuser Close to pre-set limit position
 Emergency Activation (Disable re-heat output)
 Emergency Open to physical limit position
 Emergency Close to physical limit position
 Activate Backoff Band control
 Set heater to maximum output
 Occupancy override occupied/unoccupied
 Occupancy external input occupied/unoccupied
 The following MCU global outputs are available on BACnet:
 Setpoint global
 Control override
 Occupancy override
MCU 2 model Part No Mlm Tool User Hardware Interface BMS Protocol
Standard BW2011‐2T Magnec Ethernet or USB B standard None
BACnet/IP BW2011‐2B Magnec Ethernet or USB B standard BACnet/IP
BACnet ms/tp BW2011‐2M USB B standard device BACnet ms/tp
LON BW2011‐2L USB B standard device LonTalk

4
RICKARD 2019
MLM INTEGRATION WITH BMS
Input to BMS
 Space temperature, °C or °F
 Re-heater output, 0 to 100%
 Diffuser plate position, 0 to 100%
 Supply air temperature, °C or °F
 BacNet Mode
 System Idle (in control temperature band)
 Initializing
 Heating mode
 Cooling mode
 Motor in manual drive mode
 Occupancy state occupied/unoccupied
 Zone air pressure
 Zone air flow
 Averaged MCU inputs available on BACnet:
 Average disk position
 Average space temperature
 Lon Mode specific:
 Data from the MCU active
 Busy initializing
 Heating mode
 Cooling mode
Zone/Master/Slave Diffuser concept
The MLM Proprietary network can consist of up to 60 diffusers installed on 4 separate channels per MCU. Each
channel is connected to a maximum of 15 diffusers. They can be arranged into temperature control areas, with
each such area being populated with the number of diffusers required to satisfy the comfort control in that ar-
ea.
Areas of control are designated ‘zones’ and comprise a demarked space such as a room, hallway or office area.
Each such ‘zone’ will contain a single or multiple diffusers.
One diffuser in such a zone will be designated a ‘master’ diffuser and will ‘host’ the space temperature measure-
ment and setpoint facility.
Other diffusers in the same control zone will be designated ‘slave’ or ‘drone’ diffusers and will follow the
‘master’ control outputs.

5
RICKARD 2019
MLM INTEGRATION WITH BMS
Channel and Zone designations
The Channel number corresponds to the physical (hardware) connection of the field diffusers to the MCU. From
each Power Supply Unit (PSU) a RJ9 data cable connects to a numbered channel on the MCU. During commis-
sioning, diffusers for each control area are linked (zoned) together utilising the MLM Tool application (see MLM
Tool/Help/Getting Started). The number of zones could be from 1 to a maximum of 15 per channel, sequentially
allocated to each master diffuser, with a maximum then of 60 zones per MCU. In practice there will be less than
60 zones as not all diffusers will be designated as master diffusers.
Information between channels can be routed across channels, with a master diffuser on one channel linked to a
slave diffuser(s) on a different channel(s).
For example, the above layout is designated Zone 16:
Diffuser with serial number 14010022 is connected to channel 2, designated as zone 16 and is set as a master
(temperature reading and setpoint enabled). This diffuser controls the slave diffusers with serial numbers
12120347, 14010028 and 14010024, physically connected to channels 1 and 2.
Note:
 It is important to mark the cables from a specific PSU to a specific channel. Swopping cables after com-
missioning will rearrange the data points on the BMS.
 The edit and save feature on the application MLM Tool is used to bind the diffusers to their respective
control zones.
 Please consult the ‘Making changes to a diffuser network’ section in the MLM Tool rev 8.xx Help file.
During commissioning in edit mode, the user is prompted to allocate zone numbers to diffuser control groups.
These numbers can be arbitrarily allocated to each control zone by the user. Once the save button is pressed,
the application will automatically allocate sequential zone numbers to the project. Zone numbers will be allocat-
ed 15 per channel, with channel 1 starting with Zone 1 up to a maximum of Zone 15. Channel 2 will start with
Zone 16, irrespective of channel 1 taking up 15 control zones or not. By the same token the channel 3 zone
numbers will start at 31 and channel 4 starts at zone number 46.
The 3 zone numbers marked in bold in the table below corresponds to the physical connection to channel 1
(Zone 1) and channel 2 (Zones 16, 17 & 18) as depicted in the logical diffuser layout (below) in the MLM Tool.
Channel 1 Z1 Z2 Z3 Z4 Z5 Z6 Z7 Z8 Z9 Z10 Z11 Z12 Z13 Z14 Z15
Channel 2 Z16 Z17 Z18 Z19 Z20 Z21 Z22 Z23 Z24 Z25 Z26 Z27 Z28 Z29 Z30
Channel 3 Z31 Z32 Z33 Z34 Z35 Z36 Z37 Z38 Z39 Z40 Z41 Z42 Z43 Z44 Z45
Channel 4 Z46 Z47 Z48 Z49 Z50 Z51 Z52 Z53 Z54 Z55 Z56 Z57 Z58 Z59 Z60

6
RICKARD 2019
MLM INTEGRATION WITH BMS
Identifying, mapping and binding of network variables to other network protocols
MCU to Lon Mapping
To connect with the MLM Tool to a Lon configured MCU, the USB type B hardware port on the MCU 2 is used.
Either ‘Basic View’ or ‘Project View’ can be selected in the MLM Tool application.
For Basic View access press the connect button and select the MSTP tab. The diffuser network will be displayed.
The MLM Tool can now be used to set up and commission the diffuser network.
By using the File/Export Setup command, a list can now be exported to a tab delimited text file of all the master
diffusers in the MLM proprietary network. Note that although it is not essential to extract a ‘master’ list, it is a
handy tool to link the zone, serial number and DeviceName (location) fields.
Be sure to select the ‘Master Only’ box to identify the point reference for the BMS.The table is exported in the
following text format:
Description:
Connection Address: MSTP-USB
Exporting only masters
Channel Type ID HID Loop ChLpMap LonStr Zone Code Serial Nr Firmw DevName
1 Diff 6 6 1 17 [1] 1 1 BT20 14010027 0608 Boardroom
2 Diff 2 2 1 33 [2] 1 1 BT20 14010022 0608 Recepon
2 Diff 6 6 2 34 [2] 2 17 BT20 14010029 0608 Admin
2 Diff 4 4 3 35 [2] 3 18 BT20 14010025 0608 Sales
The fields of interest are:
 Type – ‘Diff’ indicates the diffuser controller hardware and in conjuncon with the ‘Serial Nr’ field idenfies
the actual diffuser selected as master for that control zone.
 LonStr – Indicates the [channel][loop number] of the physical hardware point. This is legacy informaon and
can be ignored.
 ChLpMap – Decimal presentaon of the LonStr indicator. Legacy informaon.
 Devicename – Physical locaon in the building of the control zone. It is strongly recommended that this 12
character (Device name + Device name ext) identy string is implemented during commissioning.

7
RICKARD 2019
MLM INTEGRATION WITH BMS
For BMS mapping of the data points, the zone number of the master diffusers is used as the reference point. In
our example Zone 1 will be the identifier surfaced to the BMS to indicate control data for Zone 1. Channel 1 has
a single master controller connected, whereas channel 2 contains 3 master zone controllers.
Discovering the MCU 2 with Lon
Some concepts about the MCU Lon gateway implementation:
 The Lon configuration file (.xif) should preferably be downloaded from the MCU device during commis-
sioning utilizing the service button. If not, the .xif program revision files 3 (standard command set) and 4
(extended command set) is available on the Rickard Trac download site http://trac.lhar.co.za/
 Pressing the service button will broadcast the Neuron ID and the program ID to the BMS system.
 Each MCU is labelled with the unique Neuron ID number for that device.
 Should the user wish to utilize the heartbeat (nciSndHrtBt) functionality, the MCU will propagate all the
remaining network variables that were not propagated during the previous heartbeat period.
It is assumed the user is familiar with the standard LNS (Lon Network Service) tools and their implementation.
Reference will only be made to these software tools.
The Lon MCU device is easily discovered by the Lonmaker tool by entering a Neuron ID or using the service
button.
Note the SCC functional blocks starting at SCC VAV(0) through SCC VAV(59) corresponds with Zone 1 through
Zone 60 on the MCU.

8
RICKARD 2019
MLM INTEGRATION WITH BMS
There are 62 functional blocks supported in the functional profile of the MCU Lon module. The node and virtual
blocks are standard Lon implementations. The balance all utilizes the Lon 8502 Space Comfort Controller tem-
plate. This in effect means each MCU serves as a gateway for a maximum of 60 master diffuser zones. Zones
not populated on the MCU will reflect as null data in the corresponding functional block.
The table below shows the basic functional profile supported for each control zone:
Note: More manufacturer defined network variables are available on request.
The same functional block as depicted in Lonmaker. Note the nvoHeatPrimary variable is not activated in the
basic functional profile.

9
RICKARD 2019
MLM INTEGRATION WITH BMS
MCU 2 BACnet to BMS setup
The MCU 2 supports both BACnet/IP or BACnet ms/tp. Note MLM Tool V8.xx is required to bind the MCU 2 to
other devices in a BACnet installation.
The BACnet ms/tp MCU connects via a RS485 transceiver port to the ms/tp network, whereas BACnet /IP inter-
face to the Ethernet IP port on the MCU.
Please note the MCU ms/tp conforms electrically to the RS485 network specification as recommended by
ASHRAE. The RS485 port on MCU 2 is optically isolated. For the interconnection and shielding instructions, refer
to Addendum y of ANSI/ASHRAE Standard 135-2008.
A major advantage of BACnet/IP implementation is that the MLM Tool application can run simultaneously with
the BMS BACnet client on the same (PC) hardware platform. This greatly simplifies system commissioning and
diagnostics.
Bacnet/IP setup
To configure a MCU 2 into a BACnet/IP network, connect to the MCU web page by entering the MCU 2 IP ad-
dress into an Internet browser. The default IP address is 192.168.0.251. The following information will be dis-
played on the web page:
 The Serial number and Software Version number - cannot be changed.
 The Device Name can be changed by the user and usually identify the physical location of the MCU.
 BACnet State indicates if the BACnet key has been activated, i.e. the BACnet/IP protocol is active on the
MCU.
 The default unique BACnet device ID (instance) is derived from the Ethernet mac address. This parameter
can be changed by the user (edit and press save) to comply with the BMS requirements.
 BACnet key entered to activate the BACnet protocol. This is a once-of setting normally activated during
manufacture. To convert a MCU 2 Standard device to BACnet a key value can be procured from the man-
ufacturer and entered into this field.
Note:
 The BACnet ID and Device Name fields indicated are contained in the Object Identifier and Object Name
properties of the BACnet Device Object.
 To change MCU IP addresses consult the Hardware/Master Comms Unit section in the MLM Tool Help
menu.
 To revert to the default IP address (192.168.0.251) press and hold the BOOT button on the MCU until the
ST1 LED flashes. Release BOOT, press and release the DEF button. After a few seconds the CH1…4 LED’s
will flash to indicate a reset condition. The IP address is now set to default.

10
RICKARD 2019
MLM INTEGRATION WITH BMS
BACnet ms/tp setup
For an MCU to be configured into a BACnet ms/tp network the following setup is required:
Please note: To connect the MLM Tool to a ms/tp configured MCU, the USB type B hardware port is used. Either
‘Basic View’ or ‘Project View’ can be selected in the MLM Tool application.
For Basic View access press the connect button and select the MSTP tab. The diffuser network will be displayed.
Select the View/Open New Terminal/USB (MSTP) tabs. Press Connect and then ‘Show config’ to verify the BAC-
net ID, MAC address and baud rate fields.
 The ms/tp mac address is a crucial setting and each MCU must contain an individual mac address for cor-
rect operation. The default mac address is 25.
 Please note the ms/tp standard limit for mac addresses are 0 to 127.
 For optimum data throughput on ms/tp it is recommended that the mac addresses be allocated sequen-
tially from zero. Also the MaxMaster parameter in the BACnet Device Object should be set to the highest
mac address for all the devices on the network.
 The default baud rate for ms/tp on the MCU is set at 76800 bps.
Once the diffuser network has been set up with the MLM Tool, it is recommended that the same Master List as
described in the MCU to Lon mapping section, now be extracted to map the diffuser network to BMS.