Connect2Car MFC (V Series) Installation Manual - page 7
MFC INSTALLATION MANUAL
Page 6 of 22
CONNECT
2
CAR.COM
2.
SYSTEM OVERVIEW
The MFC accessory customizable functionality is presented as vehicle data called RECIPES.
In the recipe you make a series of steps, and say what happens or gets activated through
each step. You set these based on timing (e.g. max time, min time etc) or tachometer
reading (e.g. if below certain RPM’s, if above certain RPM’s e.g.)
One can create recipes for practically almost any purpose since the hardware interface to
the vehicle is a universal blank multi-functional control device that has standard input and
output interfaces to most vehicles. The hardware unit performs remote functional
instructions contained in the Recipes. These Recipes are sent over the wireless or wired
link at runtime command by the user. These Recipes are also saved locally as XML
(Extensible Markup Language) formatted data files on the device, which describe the
functionality of the accessory.
The user interface to the vehicle is on the smart phone device. The mobile device or PC
acts as a tool to hold, configure and deploy the recipes which are actually run in real time
on the hardware controller while reporting status of activities back to the smart phone
device. Recipes can be made, shared or customized on the mobile device, and are created
to fit the interface of the accessory to be managed and also the functionality based on
user interaction.
Sample recipes include Car Alarms, Keyless Entry; Tachometer Shift light, Turbo timers,
Strobe/Emergency flashers, Engine cut-off, Window rollup/down, Remote Starter,
Fuel/Ignition Cut-off etc.
Administrators can setup package of Recipes for users/installers. E.g. Recipe packages
with Recipes specifically setup for a Ford Mustang security system installation, a custom
Turbo timer Recipe, hydraulics control recipe, or even a custom combo.