With Munic.Box you get all you need, and at a very low price, to deploy vehicle centric applications: Munic.Box combines in a OBD dongle form factor the most advanced technology available today.:
Everything you need to build your solution.
Munic.Box is so powerful and flexible, there’s almost no limit to design new business models and create new applications.
Here are some examples of applications that have already been developed using Munic.Box
Munic.Box has been designed to give you great controls with the minimum efforts
And you are all set!
Munic.Box is available in every country, the dataplan is available in:
Austria, Baltic countries (Baltic States), Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Finland, Germany, Greece, Hungary, Ireland, Italy, Luxembourg, Malta, Netherlands (Holland), Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, United Kingdom,
United States (Contact us for Canada & Mexico)
Munix.Box will soon be available in many more countries. For any location not listed above please contact us.Request for country availability
Munic.Box relies on a powerful hardware platform, deployed in more than 250k units over the world. eOBD / OBD II dongle specifications:
|Extended Connectivity||3G||On demand|
|GPS receiver||Sirf Atlas V (assisted GPS enabled)
Sensitivity : -161dBm, 64 channels
|RAM memory||64 Mbytes|
|Flash memory||256 Mbytes|
|3D Accelerometer||Full scale output range: ±2g; ±4g; ±8g
12 bits - low temperature drift – good linearity
|3D Gyro||±250°/s, ±500°/s, ±1000°/s, ±2000°/s||on demand|
|OBD||SAE J1850 PWM, SAE J1850 VPW, ISO 9141-2, ISO 14230 KWP2000, ISO 15765 CAN|
|Mini USB (2.0 Host/Device) (not powered on internal battery)||Powered (limited to 500 mA on 5V) when connected to external power|
|Internal battery||360 mAh||On demand|
|Built in bluetooth||2.1 & 4 LE||On demand|
|Dimensions (cm)||27 x 48 x 49.5|
Built from the ground-up to enable developers to create compelling Telematics applications, MorpheusOS allows to create richer and more reliable applications through a library of more than 3000 APIs and 2000 events.
More info here
The connection between the in-vehicle device (Munic.box) and CloudConnect is done through an advanced protocol :
CloudConnect is a communication infrastructure made out of flexible and OPTIONAL elements:
The auto calibration feature is an intelligent embedded application that analyzes the movements of the vehicle in order to determine the calibration. Everything works automatically. While the vehicle is moving, it automatically computes a 3 dimensional matrix in order to figure out where the front of the vehicle, its back, left and right are.
Algorithms, using GPS and accelerometer, periodically compute several matrices and assign to each of them a confidence index. This confidence index finally determines which matrix seems to be the best one to choose.
This process is mandatory so that Munic.Box can then provide accurate data regarding drivers behavior.
Nowadays vehicle communication networks built inside every car are complex, but they can provide tons of information. Indeed, through them, you can retrieve almost any information that you can dream about (Airbag impact detection, seat belt, tyre pressure, exact mileage, instantaneous consumption etc...).
Munic.Box is unique in that it enables you to go beyond the standard OBD which you will find on the market and gives you access to much more than what the government's agencies have standardized to control pollution.
Any modern car has to be seen as a network of computers controlling every piece of the vehicle. Each of these computers is called a Electronic Control Unit: ECU.
Most common vehicle ECUs include
Although OEM specific and confidential, every ECU is accessible through a set of protocols integrated into Munic.Box such as (several protocols below are out of the “standard” OBD definition):
In an initiative to reduce the levels of pollution, the American Environmental Protection Agency and the European parliament have requested every Automotive manufacturer to integrate in every commercial and passenger car an On-Board Diagnostic system which monitors the integrity and effectiveness of all emission related components and which is accessible through a standard connector (SAE J1962).
This standard is known as EOBD (European On-Board Diagnostics) and OBD-II, and is generally linked with the Powertrain Control Module (PCM) and helps you to get information such as:
For more information, you can go to OBD-II PIDs wiki: http://en.wikipedia.org/wiki/OBD-II_PIDs
OBD-II and eOBD protocols are:
Usually installed in a cumbersome position, Munic.Box has to accommodate with an often poor GPS signal.
Munic.Box includes a powerful assisted GPS mechanism based on the download of the extended ephemeris that are feeded into the GPS module to accelerate the fix.
GPS performance is measured by its fix speed. Below are some performances measured in ideal conditions (open space, no urban-canyon, blue sky ...):
|Cold start||At first start or after a non-use period of many weeks or far away (300km) from the last fix||14 seconds|
|Warm start||At restart after a non-use period of more than 4 hours||16 seconds|
|Hot start||At restart after a non-use period of less than 4 hours||2 seconds|
|Hot start||After a signal loss (under a tunnel for example)||2 seconds|
Munic.Box comes with a Web Tool for the configuration and the administration called Device. Features of the Device Manager includes:
With Munic.Box you can define your own configuration:
To display your Munic.Box in a map and to get the recorded in vehicle data, you can connect to WebDemo (accesible as soon as Munic.Box is shipped).
With WebDemo, you can: