CTI MVE User manual

Installation and Operation Manual
MVE VEHICLE EMISSIONS MODBUS CONTROLLER

2MVE
Warning
Use this product only in the manner described in this manual.
If the equipment is used in a manner not specied by CTI, the
protection provided by the equipment may be impaired.
This equipment should be installed by qualied personnel.
For technical support, contact:
CTI
920 N Tradewinds Pkwy
Columbia, MO 65201
phone: [phone]
email: [email protected]
website: ctigas.com

MVE 3
Table of Contents
1. General description ..................... 4
2. Installation ............................. 5
2.1 Installation guidelines ................ 5
2.2 Dimensions ........................ 5
2.3 Wiring ............................. 6
Wiring Guidelines ................. 6
AC Power Wiring .................. 6
Communication Wiring ............. 6
Device Power Wiring ............... 7
Relay Output Wiring ............... 7
Network Layout Example ........... 8
MVE terminals & board layout ...... 10
3. Operation ............................. 12
3.1 Power-up.......................... 12
3.2 Programming the Controller .......... 12
Preparation ..................... 12
Navigating the screens ............ 13
Menu Tree Outline. . . . . . . . . . . . . . . . 13
Quick Start Guide................. 14
Login to Utlilities ................. 14
Discover Mode ................... 15
Sensor Conguration ............. 16
Relay Conguration............... 17
Analog Output Conguration ....... 18
Date & Time Conguration ......... 19
Export/Import Data ............... 20
Update Software ................. 21
Calibration Timer................. 22
Factory Reset .................... 23
3.3 Home Screen ...................... 24
System Status. . . . . . . . . . . . . . . . . . . . 24
Sensor Status Table............... 24
Responding to an Alarm ........... 25
3.4 Status Screens (viewable only) ........ 26
Unit Info ........................ 26
Unit Status ...................... 27
Sensor Info ...................... 28
Relay Info ....................... 29
Relay States ..................... 30
Analog Output Info ............... 31
Event Log ....................... 32
Software Info .................... 33
Service Required Screen ........... 34
3.5 Startup Test........................ 35
4. Maintenance .......................... 36
5. Specications .......................... 37
6. Warranty .............................. 38

4MVE
1. General Description
The MVE is a Modbus gas detection controller specically
designed for use with the DuoSense-M CO/NO2 gas
detectors and MVFD fan controllers. It has four RS-485
Modbus channels and can handle up to 255 devices.
It has an onboard 24Vdc power supplies to provide power
for the controller, gas detectors and audible/visual devices.
The color LCD touchscreen provides an at-a-glance status
of gas concentrations and alarms.
The MVE control panel is assembled into a wall mounted
enclosure designed for indoor locations only. The
DuoSense-M CO/NO2 gas detectors can be installed up to
4,000' from the controller.
The eight programmable onboard relays have on/o time
delays and can be programmed to be silenceable, latching
and normally energized.
Analog outputs of the MVFD devices can be congured on
the MVE controller to control exhaust fans.
All operator functions are performed from the
touchscreen on the front of the panel.

MVE 5
2. Installation
2.1 Installation Guidelines:
Locating the MVE Control Panel
• The important consideration when installing the MVE
control panel is that it must be easily accessible for
operating personnel.
• Mount controller indoors on a solid surface with minimal
vibration. If mounting on a wall with studs, the mounting
• screws should be screwed into the studs.
• Mount controller through the holes in the mounting
anges.
• Mount controller in a general-purpose location only. Do
not install in a hazardous environment.
• Mount controller away from electromagnetic
interference.
• Protect controller from physical damage.
2.2 Dimensions:
6.2" deep
12.125"
19.5"
14.5" 13.125"

6MVE
2.3 Wiring:
Wiring Guidelines:
• Electrical wiring must comply with all applicable
codes
• Use stranded, copper wire/cable with a minimum of
167°F rating (75°C rating).
• Always use insulated, stranded, shielded copper cable
for all communication cables. Refer to individual device
manuals for wiring instructions.
• Do not pull communication wiring with AC power cables.
This can cause electrical interference.
• Use only the existing conduit hole for connections to
each device.
• Bonding between metallic conduit connections is not
automatic with the non-conductive enclosure. Separate
bonding must be provided.
• During installation, cover conduit holes and close the
enclosure cover to prevent debris from falling into the
equipment.
AC Power Wiring:
• Power should be provided by a dedicated 15A circuit
breaker. It is recommended that the circuit breaker be
located near the equipment, and clearly marked as the
disconnect for the MVE gas detection control panel.
• See Specication on page 37 for requirements.
L N
Line
Neutral
Earth Ground
• For 200-240Vac input voltage, the input voltage selector
switch must be switched. The factory setting is 100-
120Vac. It is located on the side of the right power
supply. See illustration on page 11. Red circle shows
location of switch. The switch is located behind the
protective cage of the power supply, but is accessible by
using a small screwdriver or pointy object.
Communication Wiring:
The MVE controller has four Modbus communication
channels. Up to 255 devices can be installed on the MVE,
distributed among the four channels.
It is recommended to pull 24Vdc power cable with the
communication cables. These cables can share the same
conduit.
• RS-485 communication cable, 22-24 AWG, 2 conductor,
twisted pair, shielded, stranded, with drain wire (Alpha
Wire 6460 or Quabbin 8302 or equivalent)
• 4,000 ft max per channel.
• For optimum performance, it is recommended that no
more than 128 devices are connected on any of the four
channels.
• For optimum performance, CTI recommends that the
MVE controller is always at the end of the line. When the
MVE controller is at the end of the line, the EOL switches
should always be set to the ON position.
• Avoid splices and T-taps. All terminations should be
made at network device wire terminals
• Wire shields must be connected at all shield terminals,
creating a continuous shield run from the controller to
the device at the end of the line.
B A GND SHLD
To rst device
SHIELD
not used
A
B
COM 1
Terminal Block Plug (Field Wiring):
SHLD: To shield terminal of rst network device.
GND: Not used
A: To RS-485-A terminals of rst network device.
B: To RS-485-B terminals of rst network device.
See DuoSense-M and MVFD installation manuals for more
details on communication wiring.
Each device has a communication port with two terminals,
A and B. In these two terminals, the communication
cable is connected so that all the devices that take part in
the communication are connected in parallel. All of the
‘A’ terminals must be connected together and all the ‘B’
terminals must be connected together, respectively.

MVE 7
Device Power Wiring:
24Vdc power is provided by the onboard 24Vdc power
supply in the MVE controller. Additional power supplies
can be added on the Modbus channels distributed
throughout the network as needed.
• Use 18 AWG, 2 conductor, shielded, stranded cable with
a drain wire (General Cable C2534A or Belden 8760 or
equivalent)
See DuoSense-M and MVFD installation manuals for more
details on device power wiring.
Caution:
To prevent excessive voltage drops and/or power supply
overloads, careful consideration should be taken to take
into account all 24Vdc devices on the power supplies.
This includes gas detectors, audio/visual devices, etc.
See Specications on for maximum current draw for all
devices.
If the supply voltage drops below a devices minimum
supply voltage at any device on the network, a power
supply should be added at that point on the power cable.
When utilizing the 24Vdc supply for any connected MVFD
relays for external devices (horn-strobes, fan controllers,
etc.), make sure all device's minimum supply voltage is
maintained under full load (all devices active).”
24V GND SHLD
To rst device
PWR
SHIELD
GND
24VDC
Terminal Block Plug (Field Wiring):
SHLD: To shield terminal of rst network device.
GND: To ground terminal of rst network device.
24V: To 24Vdc terminal of rst network device.
Relay Output Wiring:
There are nine relay outputs local to the MVE. One is
designated as the Fault Relay, while the other eight are
general purpose, user congurable relays.
• AC wiring must be run in separate conduit from the
sensor cables.
• All relays have Form C dry contacts, and are rated 5A
@ 24Vdc or 8A @ 240Vac (dry contacts require external
power).
• The fault relay is normally energized. It will trip upon loss
of power or hardware failure of the MVE controller.
• Each relay has a status LED to show the state of the
relay.
• When utilizing the onboard power supply of the MVE
controller for power of external devices such as horn/
strobes, make sure the total current draw of all powered
devices does not exceed the current limits on page 37.
• There are two courtesy 24Vdc and ground terminal
blocks amongst the relays. These can be used to provide
power for external devices such as audio/visual devices,
exhaust fan control, etc.
• See Relay Output section in the Setup menu for more
details on relay conguration.
NO C NC
To relay output device
R5
24V 24V GND GND
COURTESY
R5-NC
R5-C
R5-NO
GND
GND
24VDC
24VDC

8MVE
Network Layout Example

MVE 9

10 MVE
MVE Terminals, Ports, Components, and Board Layout
Display
Board
HORN ETHERNET REMOTE
DISP PWR
REMOTE
DISP COM
DISP COMUSB

MVE 11
Cooling
Fan
Fuse
Main
Board
L N G

12 MVE
3.1 Power-up
Before applying power, make a nal check of all wiring
for continuity, shorts, grounds, etc. It is usually best to
disconnect external alarms and other equipment from
the control panel until the initial start-up procedures are
completed.
Initial Startup
The CTI logo will be displayed while the system initializes
the hardware and software components. The Initial
Startup sequence will be initialized by simply powering up
the unit from an OFF state.
Home Screen (shown below)
The initial System Status screen won't show any connected
devices until they are discovered.
3.2 Programming the Controller
Note:
If Importing a previously saved Conguration le, skip to
Import/Export section of this manual.
Preparation
The key to accurate and timely programming is dening
the conguration parameters ahead of time.
Included with the control panel are blank worksheets to
ll out prior to programming. Make sure to notate the
Modbus ID along with sensor name and location as this
will be needed for sensor conguration later.
Note:
For MVE controller programming, the only way to tie
inputs to outputs is through Groups, not sensors.
Dening the conguration parameters in the following
order will usually make programming easier to assimilate.
1. Sensors
2. Groups
3. Relays
4. Analog Outputs
3. Operation

MVE 13
Connected Devices (DuoSense-M and MVFD)
Once powered, make sure all connected devices are
programmed with unique Modbus ID's (1-255). See device
manuals for details.
Naming
Keep in mind character length when naming.
Abbreviations may need to be used.
Sensors: Typically, using the sensor location for the name
provides the best information. For example: Column 22,
Loading Area 1A, etc.
Relays: The relay output function typically works best for
the name of the relay. For example: Vent fan North, etc.
Navigating the screens
Swiping
Swipe up or down to view more table rows when
applicable.Where side scroll bars are present, they can be
used for fasting scrolling.
Page Activity
The controller display will default to screensaver mode
after 60 minutes of inactivity. Press the screen to activate.
Tables
When the user selects a box/eld on a page with a table,
a pop-up keyboard will allow edits to the eld. Tables can
scroll beyond the page.
Unless otherwise specied, if the user presses any of
the column headers in a table, the data will be sorted in
descending order by that columns data. If the user presses
the column header again, the data will toggle between
descending and ascending sort order.
Pop-up keyboard
Any pop-up keyboard will:
• Have a cursor to show the location of the next typed
character and allow the user to touch the data entry
screen and select the location of the next typed
character.
• Have a Cancel key that will exit the keyboard without
changing the eld.
• Have an Enter key that will exit the keyboard and save
the entered value.
• Have a backspace (BKSP) key that will delete the
character to the left of the cursor.
Numeric Keyboard
Whenever a eld is selected that needs a numeric value, a
numeric keyboard will pop-up with the numbers 0-9, “.”, “-”
and a space.
Alpha-numeric Keyboard
Whenever a eld is selected that needs an alpha-numeric
value, a full QWERTY alpha-numeric keyboard will pop-up.
Menu tree outline
The Menu Tree can be used to quickly nd screens. It also
shows which screens are congurable and which are view
only.
Home Screen
Info / Status
(view)
Utilities / Settings
(congure)
Unit Info (Login Screen)
Unit Status Calibration Mode
Sensor Info Discover Units
Relay Info Sensor Conguration
Relay States Relay Conguration
Analog Out Info Analog Out
Conguration
Event Log Export/Import To USB
Update Software
Date & Time
Conguration
Factory Reset

14 MVE
Quick Start Guide
1. Check Wiring: Make sure all connected devices are
terminated and wire terminals are tightened.
2. Apply Power: Turn on AC power breaker to apply
power to the system.
3. Setup: Congure all connected devices with proper
Modbus ID's.
4. Discover: Discover all connected devices
5. Utilities: Congure all settings.
6. Programming: Complete MVE programming, tying
sensor Groups to intended Relay Outputs or Analog
Outputs.
7. Test System: Perform extensive startup test to verify
all alarm functions perform as intended.
8. Export: Save new conguration and system settings to
USB drive for backup.
Login to Utilities
To login to Utilities, press the Utilities button on the
bottom right of the Home page.
A Login screen will pop-up.
The User name will be pre-populated with: CTI Admin
Press the Password eld. A numeric keyboard will pop-up
and allow a 4-digit password. This password is provided
with the MVE controller, inside of the shipping box with
the manual. Enter the 4-digit password and press the
Enter key. Then press the Login key.
Once logged in successfully, the Utilities screen is now
accessible for all congurable settings.

MVE 15
Discover Mode
Discover Mode attempts to communicate with all Modbus
addresses 1 thru 255 on each of the four channels to
establish communications with all connected devices.
Prior to using Discover Mode, make sure all devices are
installed, powered, and are programmed with unique
Modbus ID's. See individual device instruction manuals for
Modbus ID setup.
When ready, select Start on the Discovery Process screen.
This may take a couple of minutes depending on the
number of connected devices.
There will be no duplicates, only unique discovered
devices will be added to the lists. If two devices have the
same Modbus address on the same Modbus channel,
they will not be discovered. If two devices have the same
Modbus address on dierent Modbus channels, only one
will be discovered.
If it appears that one or more devices were not detected,
for example if the Modbus addresses were not set, the
Sensor Conguration page should be useful to nd the
devices that were not discovered.

16 MVE
Sensor Conguration
The Sensor Conguration page allows the user to
congure and activate the detector settings.
Default settings will be pre-populated for the Vent and
Alarm setpoints for both the CO and NO2 detectors.
Note: All sensors are made Active by default during
Discovery.
Using your provided worksheet and notes:
1. Assign sensor name and/or location. Use abbreviations
for long names
2. Adjust Vent and Alarm setpoints if desired.
3. Select sensor Group. Keep in mind that the Group will
be tied to a specic relay output or analog output (see
Relay Conguration section).
Swipe up on the screen to access more table rows.

MVE 17
Relay Conguration
The Relay Conguration page allows the user to congure
the relay settings onboard the MVE controller, along with
any connected MVFD fan controller relays.
The MVE controller has one dedicated fault relay that
is not programmable or part of any sensor group. This
relay is normally energized, and will trip upon loss of
power, hardware failure of the MVE controller, or device
communication error.
All of the other eight MVE onboard relays are listed in
the Relay Conguration table, along with any connected
MVFD fan controller relays. Below is an explanation of
the relay conguration settings.
Most vehicle emissions applications utilize the relays
for exhaust fan VFDs, audio/visual devices, louvers and
general alarm notication.
Active: Any listed relay set to Active will trip when all of
the following conditions are met:
• Sensor is within the selected Group
• Gas concentration exceeds the set level (Vent or
Alarm)
• Time exceeds the On Delay time setting
Name: Press within the name eld and use the pop-up
keyboard to enter relay name. Assigning a relay name
during installation/start-up provides an at-a-glance relay
assignment in the status menu, without the need for
electrical drawings lookup.
Level: Select Fault, Vent or Alarm gas concentration
at which the relay trips. (see Sensor Conguration on
previous page). Note: Selecting Fault will only trip the relay
upon a device communication error, not to be confused
with the dedicated MVE fault relay which will trip upon
power loss or hardware failure of the MVE.
Group: Select which sensor group (1 through 4) the relay
is associated with. Selecting "None" will make this relay
inactive. (see Sensor Conguration on previous page)
Normally Energized: Selecting normally energized keeps
the relay energized in the normal state. This may not
be ideal for most applications, as a relay set to normally
energized will trip during power loss.
Latching: Setting the relay to latch (typically recommended
for equipment shutdown) will require a manual reset
from the MVE operator interface. A latching relay will only
reset after the gas concentration has dropped below the
alarm setpoints. A non-latching relay automatically resets
after the gas concentration has dropped below the alarm
setpoints.
Silenceable: Setting the relay to be silenceable (typically
used for buzzers/horns) allows the relay to be reset by
pressing SILENCE from the MVE operator interface.
On Delay: Set relay on-time delay
O Delay: Set relay o-time delay

18 MVE
Analog Output Conguration
The Analog Output Conguration page allows the user to
congure the 4-20 mA analog output settings onboard
any connected MVFD fan controller.
Using your provided worksheet and notes:
1. Make MVFD analog output active (if desired).
2. Assign name and/or location. For example, Exhaust
Fan 3. Use abbreviations for long names
3. Select sensor group Source. (Groups 1 through 4).
Selecting "None" will disable the analog output.
Each Active sensor has a 4-20 mA value, equivalent to it's
gas concentration, calculated based on the range of the
sensor. Each Group has a 4 to 20 mA value calculated,
based on the largest 4-20 mA value in that group. If a
Group is selected as the Source, the MVFD's Analog
Output will be commanded to output the calculated 4-20
mA for that Group.
Refer to your specic VFD manual for details and
requirements for analog and digital inputs for fan
activation and speed control.

MVE 19
Date & Time Conguration
Set current date and time. Having the correct date and
time is important for accuracy of the Event Log.
Note: Time does not adjust automatically for daylight
savings time.

20 MVE
Import/Export Data
To import or export les,
1. Use a USB ash drive >1Gb.
2. Insert the ash drive into the USB port on the main
display unit on the inside of the enclosure door.
3. Select Click to select USB, and select the USB.
4. Use the drop-down menu to select les to be
imported or exported.
Import
The Import feature allows users to import a system
conguration le (xxx.MVE) from the ash drive.
This le can be Imported to restore corrupt software, or
uploaded into another MVE controller to duplicate the
conguration.
Export
The Export feature lets the user to export the following
controller les to the ash drive:
System Conguration: Creates a backup .MVE le of the
user programmed data tables in the event of a system
crash or software corruption.
Event Log: Creates a CSV le of all events with a date/
time stamp.
Data Log:
For CTI personnel diagnostics
Diagnostics Log:
For CTI personnel diagnostics