The application is capable of:
- reading the live data
- showing the fault codes and clearing them
- displaying the logged freeze frame data
The application requires the OBD II Bluetooth or WiFi dongle (ELM327 based) to communicate with a car.
All the popular OBD II protocols are supported:
- J1850 VPW and PWM
- ISO 9141-2
- KWP 2000
- CAN (11 and 29 bits - both 250 and 500 kBit/s)
If you have any request, comment or suggestion, please don't hesitate to contact me.
-- We have been receiving many complaints in regard to the app not functioning with the MX Wifi... AND... we now have released our latest version to include WIFI compatibility... Please read further below for more information in regard to requirements for our app to function...
-- If you have questions, issues etc., please e-mail us and we will respond as quickly as practical... We receive a lot of requests, reply to every one of them, and cross our fingers that your SPAM filters don't keep them out of your inbox (please be advised in case you don't get a response). Also, we have a FAQ page on our website at http://obdcanex.com/o/faq Please visit this page first for general inquiries about the app. -- more information below...
The easy way to control your car, truck or van using your smartphone -- WITH NO SUBSCRIPTION FEES!
Support OBDLink MX Wifi!!!
--- We have fixed customer reported bugs from both previous versions of obdCANeX Lite and added additional vehicles...
Voice control functionality is now standard to obdCANeX Lite! We have also continued to decrease overall vehicle response time as well - faster than your OEM Key-fob!
obdCaneX Lite is an Android based application which allows full keyfob control functions of your vehicle. Including unlocking and locking of doors, activation of your panic alarm, remote starting and shutting off of your engine (if OEM equipped remote start capability is activated).
Please read the 3 requirements listed below:
1. This application has been developed for use with and requires ScanTool’s Bluetooth OBDLink MX module (Wifi or Bluetooth). You can purchase the module directly from obdCANeX (http://obdcanex.com/o/hardware/obdlink-mx), or if you purchase obdCANeX, Lite, a link is provided in-App which will give you FREE SHIPPING. This module plugs into your OBDII port and is needed for our app to communicate with your car. If you already own an OBDLink MX Bluetooth or Wifi module, please make sure your has firmware update 3.0 and above installed. http://www.scantool.net/downloads/updates/obdlink_mx/
2. GM vehicle 2007-2012 (some 2007/2012 model vehicles are not currently supported. Please e-mail us with any questions of applicability).
We are currently testing other makes, models, and year groups and will post a list of compatible vehicles as they become verified. We do have a Dodge Journey, 2013 tested and added in for basic key-fob functionality (NO REMOTE START yet on the Dodge...)
3. A Android phone with touch-screen and BlueTooth capability is required.
Future obdCANeX releases will be available soon with more features. Please visit http://www.obdcanex.com for more information. Upgrade options for existing customers of the obdCANeX Lite version will be available.
Please send us an e-mail with any questions and we will be happy to assist you further.
The software connects to Auterra's Bluetooth OBD II adapter included in the A-303 Dyno-Scan for Windows Bluetooth kit. A demonstration mode is built into the software that simulates all vehicle data so you can test the software.
Auterra's Bluetooth OBD II adapter is required to connect to a vehicle. The product supports 1996 and newer US vehicles including American, European, and Asian brands such as Ford, GM, Chrysler, Toyota, Honda, BMW, VW, Volvo, etc… Outside the US many vehicles are supported also (see Auterra website FAQ page for specific details).
Auterra's Bluetooth OBD II adapter supports Auterra’s Windows and Android software. The Android software is optimized for both phone and tablet platforms. Common file formats means you can record on Android and open file on a Windows PC.
Live data is recorded with vehicle position using your Android’s built-in GPS. Open files on your PC using Dyno-Scan for Windows and see the vehicle data and your vehicle position within Google Earth.
Record vehicle power/torque and acceleration and display graphically.
Auterra manufacturers all hardware and software for the Android, Windows PC, and DashDyno SPD platforms so all the products work seamlessly together. This free software was designed for Auterra customers using Auterra's Bluetooth OBD II adapter.
The Android users guide is available on our Downloads page or in the link below:
Dyno-Scan for Android key features:
* Connects to Auterra's Bluetooth OBD II adapter.
* Wirelessly view and record data from your vehicle using Bluetooth.
* Android and Windows PC platforms supported.
* Read/clear vehicle diagnostic trouble codes.
* Integrated DTC database with thousands for trouble code definitions.
* Software supports 264 live vehicle parameters.
* CAN 6x mode for 600% faster data throughput (vehicle dependent feature).
* Record vehicle sensor data and GPS position.
* Measure horsepower and torque.
* Measure acceleration times such as 0-60MPH and 1/8mile times.
* Measure vehicle overall gear ratio.
* Open Android recorded data (live data, power/torque and acceleration) on your PC using Dyno-Scan for Windows.
* Recorded GPS location is displayed within Google Earth on your PC.
* Easily save and load your favorite screen configurations.
* Numerous screen layout options with meter and graph widgets.
* Dynamic portrait and landscape orientation changes.
* Full gesture support including pinch-zoom graphs, drag zoomed graphs, and double-tap zoom.
The application uses the device ELM327 Bluetooth Adapter OBD connector and to communicate with different vehicles.
ELM 327 Bluetooth Adapter is a device for the cars of joining through the 16-pin OBD diagnostic connector.
This application is a simple terminal that supports all device commands ELM327.
- The application includes a ready list of basic commands.
- Possibility clearing the terminal window
- Ability to write the log to a file
- The ability to type your own commands
(ECU) of motorcycles Triumph, KTM, Aprilia and Benelli.
This application requires an USB/OBD2 cable with FTDI chipset or a Bluetooth adapter ELM327 v1.4 or 1.5.
Warning, with bluetooth connection, the reading and reprograming functions are not available.
Models list compatibility :
Triumph Daytona 675, cable & bluetooth, up to VIN # 564947
Triumph Daytona 675, from VIN # 564948, bluetooth connection only
Triumph Street Triple & Street Triple R, cable & bluetooth, up to VIN # 560476
Triumph Street Triple & Street Triple R, from VIN # 560477, bluetooth connection only
Triumph Speed Triple 885, 955, 1050 & 1050 R (including 2014 models)
Triumph Tiger 800/800XC, 885 (900), 955, 1050 & Tiger Sport (including 2014 models)
Triumph Tiger Explorer, bluetooth connection only
Triumph Sprint ST/RS 955 and 1050, Sprint ST/GT (including 2013 models)
Triumph Daytona T595/955i Daytona (all models)
Triumph Rocket III (include 2014 models)
Triumph Daytona 600, 650, Speed Four, TT600 (all models)
Triumph Thunderbird 1600 & 1700 cc, except Commander et LT
Triumph America, Bonneville, Scrambler, Speedmaster, Thruxton (including 2015 models)
KTM 990 LC8 & 1190 RC8 (include 2012 models)
KTM 690 Duke (include 2011 models) (except Duke 4)
KTM 690 SMC & Enduro/690 Supermoto (including 2013 models)
Aprilia Caponord and Futura RST
Benelli Tornado (Sagem ECU)
Ducati* 749, 848, 999, 1098, 1198
Ducati StreetFighter 848 & 1098
Ducati* Monster S2R 800 & 1000, S4R
Ducati* Hypermotard 1100 (not EVO)
Ducati* Multistrada 1000 & 1100
* ECU 5AMHW610
It is highly recommended to visit the site www.tuneecu.com before using this application.
It's quite simple. Select The vehicle manufacturer or Global, enter the Diagnostic Trouble Code DTC, then press search and in case it appears within the 100,000 Trouble Codes, the description will be displayed!!
In addition, by pressing the "Search Web" button, it will search within Google for the relevant Fault Code.
This app is an excellent tool, for those who obtain only the OBD-II Trouble Code, but do not know what it means.
Please note that using this app does not require connecting to ELM / ELM327 device, or any other scanner. this is a standalone application!
In order to access over 100,000 Trouble Codes, you must have an active internet connection!
This App supports the following:
1. More than 100,000 Extended DTCs !!! (Specific Manufacturer Fault Codes).
2. Powertrain, Body, Chassis and Communication DTCs.
3. Global Trouble Codes for all vehicle manufacturers in the world!!
3. Specific Trouble Codes for all vehicles belonging to these manufacturers:
* Chrysler + Dodge + Jeep (Select Chrysler in app)
* Ford + Ford Truck + Lincoln (Select Ford in app)
* Honda + Acura
* Nissan + Infiniti. (Select Nissan in app)
* Toyota + Lexus. (Select Toyota in app)
Please try the free app version before buying the pro app!
DTC, Trouble code, fault code, obd, obd2, obd-ii, obdii, on-board diagnostics, vehicle, automotive, elm327, scanner, automotive diagnostic tool, error code, cars, onboard, check-engine, check engine. warning code, warning light, ECU, Oxygen Sensor, Throttle, PCM, TCM, Ottotest, Blue Streak Electronics, Ototest, Maf, ECM, error code, obdi, obd1, coolant temperature, vehicle speed, Actuator, Cylinder, Injector, Exhaust, Fuel, Gear, Ignition, Immobilizer, Motor, Passenger, RPM, mph, kmh, pedal, Yaw Rate.
After the installation, launch Torque Pro and click on the RacingMeter icon.
This is a highly customizable Racing digital dash including live telemetry, power meter, accelerations measurements, shift lights, gear estimation, HUD and much more... This plugin requires the app Torque Pro in order to communicate with your car's ECU via OBD 2.
Support: Should you experience issues, contact me at email@example.com before adding a comment, the solution might be easy or a fix ready.
• Digital widgets for RPM, Speed, Engine coolant temperature, Intake Air temperature, Catalysts temperature, Engine Load, Turbo boost, Fuel Consumption, Clock, Fuel pump, Rail pressures (gauge and relative pressure) and Air/Fuel ratio, Mass Air Flow, Intake Manifold Air Pressure, Fuel Used, Fuel Cost, Voltage and others described below.
• Dials with auto scale, customizable style, scale, angle, size and warning thresholds. RPM, Engine Load, Turbo boost, Engine coolant temperature, Intake Air temperature, Speed, Catalyst temperatures, Fuel pump, Rail pressures, Mass Air Flow, Intake Manifold Air Pressure.
• RPM LEDs Bar
Custom colors, four styles and three animations available. Automatic or manual threshold settings. Two additional LEDs Bar are available to display Turbo, RPM or Load data.
• Acceleration Measurements
Configure and display six independent stopwatches with specific speed thresholds for your current and best acceleration. Display 1/4 mile, km DA times.
• Engine Power and Torque estimations
Based on speed, RPM, weight, wheel radius, SCx and G-forces.
• Gear Estimate
Based on speed and RPM values.
• Braking Statistics
Distance, time, speed in/out, G-force avg/max.
• Make your own dashboard
Move, rescale, add or remove any parameters, three different presets containing up to five screens each can be saved. All colors fully customizable.
• Shift Light
Flash on screen, Automatic or manual threshold, customize color. Ability to define different RPM thresholds depending on your gear.
• Telemetry Viewer
Display Telemetry in real-time and save up to one hour of data. Two cursors can be placed on the graph to measure the time between two points.
The following data are recorded:
Speed, RPM, Gear, Engine load, Turbo boost, Lateral forces, Longitudinal forces.
• Import/Export the telemetry data as a CSV file on your sdcard for further calculations. Export to RaceRender format supported with the following data: Time, GPS Latitude, GPS Longitude, Speed, G-Forces, RPM, Throttle position, Gear, Turbo.
• Heads up display / HUD mode for night time driving.
• G-Force Meter (plotted 5s)
Mph/Kmh ; °C/°F ; psi/kPa/bar ; LPK/KPL/MPG ; HP/CV/Kw ; Nm/mKg ; L/gal
OBD2 Fahrzeugdiagnose mit Ihrem Smartphone: Kfz-Fehlerspeicher auslesen, Kraftstoffverbrauch, Kühlmitteltemperatur und weitere Live-Messwerte anzeigen.
Via Bluetooth erhält Ihr Smartphone direkten Zugriff auf die OBD2 Schnittstelle des Fahrzeugs und wird somit zum erweiterten Bordcomputer. Neben der Überwachung der wesentlichen Motor-Parameter liefert die Diagnose- Schnittstelle auch Informationen zur einfachen Bestimmung fehlerhafter Aggregate und Sensoren.
Hinweise zur Installation:
- Stecken Sie den OBD2 Bluetooth-Adapter in den Steckplatz an Ihrem Fahrzeug und starten den Anlasser
- Schalten Sie Bluetooth an Ihrem Smartphone / Tablet ein
- Starten Sie die App
- Gehen Sie in das Menü „Einstellungen“
- Drücken Sie auf den Pfeil rechts im Bereich „Pairing“
- Suchen Sie nach „dnt OBD2“ und geben den Code 1234 ein um das Pairing zu starten
- Starten Sie jetzt in den App-Einstellungen die Verbindung mit dem Smartphone
- Bei korrekter Verbindung leuchten jetzt alle 3 Sysmbole im Hauptmenü blau auf (Adapter, Handy, Auto)
Android system: 2.1 or above 2.1
Get the description and the possible cause of the check engine code by searching for the code for all of the major manufacturers and now with quick access to your search history and save results to for use at a later date.
Acura, Audi, BMW, Buick, Cadillac, Chevrolet, Chrysler, Dodge, Ford, GMC, Honda, Hummer, Hyundai, Infiniti, Isuzu, Jaguar, Jeep, KIA, Land Rover, Lexus, Lincoln, Mazda, Mercedes-Benz, Mercury, MINI, Mitsubishi, Nissan, Oldsmobile, Pontiac, Saab, Saturn, Scion, Subaru, Suzuki, Toyota, Volkswagen and Volvo all on the go.
Don't get cheated by your mechanic. Have the facts with you.
We have apparently not been sufficient clear about supported cars:
As this is an OBD adapter, only EOBD/OBDII compatible cars are supported.
In EU, all cars sold since 2001(gasoline)/2004(diesel) are required to be EOBD/OBDII compatible.
As far as we can tell, most brands comply, but if you have a French car, you may want to check its compatibility.
You may have luck with older cars, too.
Read more at www.mobilscan.dk!
** 2.6 **
More workarounds for the phones' different ways of handling BT pairing and connection.
** 2.5 **
Some phones (XPeria GO, and others using Android 4.X) have seen problems connecting to the adapter. Release 2.5 contains a workaround that seems to have fixed this.
The font size now respects the general font scaling setting on the phone.
** 2.4 **
HUD mode for Instrument page (1 or two instruments only, 3/4 would be too cluttered).
Select HUD from the menu. Tap the HUD display to select color.
For Android 3.0 and newer.
*** New in 2.3 ***
Workaround for the apparent Bluetooth problems introduced in Android 4.2 and 4.3. Tested on Nexus4, HTC One, and Samsung Galaxy S4 mini.
*** New in 2.2 ***
View your previous reports as 'My reports' (report page).
*** New in version 2.1.4 ***
* Sharing of snapshot report now also possible to facebook and similar services. Requires that you have the Facebook app installed.
* 'Real' fuel consumption calculation added - FOR GASOLINE/PETROL VEHICLES. This will only be visible on vehicles having MAF (Mass AirFlow), otherwise we simply don't have the necessary information. Note that the value may be visible also on diesel vehicles, but that calculated value is most likely completely wrong, then. We have no (sure) way of detecting a diesel, so in that case, you'll have to use the 'Energy burn' calculation instead.
* Take a screenshot and share it with your friends. Available from the menu (or in the action bar if there's room).
Now you do not need to drive on with the MIL light on.
Now you do not need to wait to go to the garage with your car to know what is wrong.
Now you can prepare the garage by knowing what is wrong.
Now you can see what is wrong with your car on your holiday so that you know if you can drive on.
And all this for less than what most garages take for doing the same test once.
The system comprises an this app and an OBD Bluetooth adapter you either buy at the local dealer or online.
MobilScan gives access to car information as defined by the ISO standards about OBD, this means that you can read out fault codes, continuously receive and display a full list of engine parameters like oxygen sensor readings, air mass, temperature sensors and other parameters used by the engine control computer (ECU).
When you want to capture the current state of the car, you may send a 'snapshot report'. MobilScan compiles information about the current state of the car, and allows you to send this as a HTML report to a receiver of your choice (e-mail, Bluetooth, ...)
NB! The MobilScan software is free, but we're trying to make a living from this, and you'll have to buy the corresponding MobilScan OBD adapter from us. Please contact firstname.lastname@example.org for pricing and availability in your region. If you are already a MobilScan customer, you may use your existing OBD adapter.
If you are just looking for a fault code lookup tool, try http://market.android.com/details?id=com.care2wear.dtclookup_full
Version 2.0 uses the ActionBarSherlock framework to implement action bar support on early Android versions. If you're a developer: try it!
OBD Dashboard connects to the OBD2 port of cars using ELM327 compatible bluetooth or Wi-Fi adapters, showing real-time data on an dashboard like screen.
Data can be logged to sdcard.
Application is optimized to have lower CPU usage, and reduce the delay of information being shown on screen.
Please check http://obddashboard.blogspot.com for more information.
Follow me on Twitter @ObdDashboard for development updates.
If you do have a gyroscope, be aware that the quality of the drift compensations on the gyroscope sensor vary considerably among devices. In the case that your device has a gyroscope that doesn't work well, there is the option to fuse the gyroscope with the acceleration and magnetic sensors. This option, which uses a fusion of the acceleration, magnetic and gyroscope sensors via complementary filter to determine the rotation of the device, is far more reliable that the gyroscope sensor alone.
Gyroscopes measure the rotation of a device with a pair of vibrating arms that take advantage of what is known as the Coriolis effect, which is caused by the Earth's rotation. By measuring changes in the direction of the vibrating arms caused by a rotation and the Coriolis effect, an estimation of the rotation can be produced. The gyroscope is one of three sensors that are always hardware based (the other two are the magnetic and the acceleration sensors) on Android devices. In conjunction with the acceleration sensor, the gyroscope can be used to create other sensors like gravity, linear acceleration or rotation sensors.
If your device is equipped with Android 4.4 or higher, you *might* have the uncalibrated version of the gyroscope so you can see how drift affects the gyroscope sensor relative to the calibrated gyroscope.
The linear acceleration of an object is calculated as the acceleration of the device minus the force of the earth's gravitational field ( the tilt of the device). Gyro Linear Acceleration uses a complimentary filter to fuse the acceleration sensor and gyroscope sensor together to provide a measurement of the devices linear acceleration. The acceleration sensor alone is not capable of distinguishing true linear acceleration from tilt, or gravity. The gyroscope sensor is used to find the tilt of the device. The tilt angle of the device can then be used to calculate the gravity component of the acceleration that can then be subtracted from the acceleration to find the linear acceleration.
Most people will find that the end-result of this implementation is that, while linear acceleration can be measured while the device is static (not accelerating), linear acceleration cannot be accurately measured while the device is actually under linear acceleration. This is because the complementary filter, which is used to compensate for the drift of the gyroscope, begins to assume the acceleration of the device is actually tilt, skewing the rotation measurements from the gyroscope.
Related to the linear acceleration problem is that the gyroscope sensor can easily drift out of rotation with the device when it is experiencing vibrations or rapid rotations, even with the help of an acceleration sensor. If you modify the complementary filter to quickly compensate for gyroscope drift with the acceleration sensor, you increase the problem of the complimentary filter confusing linear acceleration for tilt when the device is actually accelerating.
Gyro Linear Acceleration may work well for determining linear acceleration for a static device, for instance, that moves a character or vehicle in a game by tilting the device. Gyro Linear Acceleration will not work well for determining the linear acceleration of a vehicle or other object that actually accelerates the device.
Gyro Linear Acceleration will plot the output of the sensor fusion in real-time and will also log the data to an external .CSV file that can be viewed at a later time on any spreadsheet application.
• Plot data in real-time
• Analog gauges to visualize the outputs
• Log the output to an external .CSV file
Linear Acceleration Sensor is intended to provide developers with code examples and an application to quickly test devices for an implementation of Sensor.TYPE_LINEAR_ACCELERATION. Some Android devices provide an implementation of linear acceleration with Sensor.TYPE_LINEAR_ACCELERATION, others do not. The implementation and performance of Sensor.TYPE_LINEAR_ACCELERATION varies from device to device. Some devices rely on low-pass filters, some fuse the magnetic and acceleration sensors, some fuse the gyroscope and acceleration sensors and others do not implement linear acceleration at all.
Almost all implementations of Sensor.TYPE_LINEAR_ACCELERATION are poor. The implementations succesfully isolate gravity from the acceleration under static conditions. However, while the device is actually under linear acceleration, the gravity compensation tends to be overestimated skewing the linear acceleration measurement. Linear Acceleration Sensor is ideal for discovering the limitations and performance of Sensor.TYPE_LINEAR_ACCELERATION.
• Log all of your data in real-time
• Analog gauges to display the outputs
• Real time sensor plots to visualize performance
Discover how low-pass filters work on acceleration sensors by viewing the outputs in real-time. Acceleration Filter runs multiple low-pass filters at once so you can compare the results from a single input quickly and easily. The output from the filters is plotted with a line graph while the noise is plotted with a bar graph. There is also the option to view the acceleration as a two-dimensional vector. The user can select the sample period in units of seconds to apply to the different filters. This allows user to explore a large number of filter settings to quickly determine what is best for their application. Perfect for visualizing the effect of low-pass filters on digital signals. You can even log the output to an external .csv file.
• Graph acceleration in real-time
• View signal noise in real-time
• Compare multiple low-pass filter configurations simultaneously
• Define how the low-pass filter calculates alpha, or, set alpha to a static value
• Define windows for moving average filters
• Log filter outputs to an external .csv file
• Complementary IIR Low-Pass
• FIR Moving Average
An accelerometer can measure the static gravitation field of earth (like a tilt sensor) or it can measure measure linear acceleration (like accelerating in a vehicle), but it cannot measure both at the same time. When talking about linear acceleration in reference to an acceleration sensor, what we really mean is Linear Acceleration = Measured Acceleration - Gravity. The tricky part is determining what part of the signal is gravity.
It is difficult to sequester the gravity component of the signal from the linear acceleration. Some Android devices implement Sensor.TYPE_LINEAR_ACCELERATION and Sensor.TYPE_GRAVITY which perform the calculations for you. Most of these devices are new and equipped with a gyroscope. If you have and older device and do not have a gyroscope, you are going to face some limitations with Sensor.TYPE_ACCELERATION. Note that the implementations of Sensor.TYPE_LINEAR_ACCELERATION and Sensor.TYPE_GRAVITY tend to be poor and are skewed while the device is under periods of true linear acceleration.
A low-pass filter is a filter that passes low-frequency signals and attenuates (reduces the amplitude of) signals with frequencies higher than the cutoff frequency. The actual amount of attenuation for each frequency varies depending on specific filter design. To find the gravity component of an acceleration signal, a low-pass filter is used to pass the long term portion of the signal (which is assumed to be gravity) through the filter and to attenuate everything else. The gravity component of the signal can then be subtracted from the original acceleration signal to find the linear acceleration.
• Log all sensor data to a .CSV file
• Analog gauges display the tilt and acceleration of both the acceleration and linear acceleration sensors
• Plot sensor output to visualize data in real-time
• Visualize acceleration in two-dimensions with a vector view
• Adjust the time-constant of the low-pass filter to your needs
• Adjust the acceleration sensors output frequency to your needs
Smarter than your average compass! Compass Geek can be calibrated to work in places most compass applications will not, like in a car, boat or plane. There are a number of compass applications available, but Compass Geek exists because I needed a compass that could be calibrated to work in a car and I couldn't find one. Compass Geek is capable of correcting for the hard and soft iron distortions in the local magnetic field caused by metals and electronics.
Compass Geek attempts to produce the most accurate compass possible by optimizing sensor fusions for your Android devices specific hardware. Compass Geek provides both hand-held and vehicle modes for vehicle-docks and can even compensate for hard-iron offsets produced by a vehicles metal frame and electronics. Compass Geek can be calibrated to work in most cars, planes or boats and works where many compasses will not.
In addition to a compass, Compass Geek supports Google Maps so you can see your location in Google Maps anywhere in the world!
Choose from up to eight unique gauge skins to get the look and feel you want. You can even graph the bearing in real time to see just how awesome your compass is working.
• Tilt compensation from the gyroscopes and acceleration sensors are used to compensate for the tilt of the device
• Magnetic declination compensation for earth’s magnetic field with the GPS sensor
• Hard-iron offset calibrations for vehicles like cars, planes and boats
• View the bearing from the magnetic field and GPS as well as the location
• Measure the rotation of the device and the magnitude of local magnetic field
• Alerts when the magnetic field is out of the expected range
• Select from 8 unique, super awesome hardware accelerated gauge skins
• View the bearing, magnetic field, rotation of the device, the location of the device and more
Acceleration Explorer allows the user to investigate the noise, offset and skew associated with the accelerometer sensor on Android devices. After a quick calibration process, Acceleration Explorer will calculate the magnitude of each axis and the noise associated with it. Acceleration Explorer also determines the minimum and maximum amplitudes of each axis along with the update frequency of the acceleration sensor.
Why would you want to know about noise, offset and skew?
We want to know about noise, offset and skew because they are aspects that make the sensor less accurate that we can partially compensate for. For example, you may want to implement a low-pass filter or mean filter to smooth the acceleration sensors output and knowing how much noise the sensor has is very useful. Or you may want to know how accurately your device measures gravity, tilt or acceleration.
Acceleration Explorer makes it easy to compare the performance of the acceleration sensors of multiple devices. Not every Android device is the same and knowing the range of how acceleration sensors perform can be very helpful.
Write better code!
Acceleration Explorer can help fine tune your acceleration sensor algorithms.
The magnitude and sensitivity of these dangerous driving events can be defined by the user. Once a dangerous driving event is detected, the data occurring a short period before the event and the entire event are logged to a .csv formatted file and saved to a folder on the device. The data log can also be emailed to a Gmail account. Note that we do not collect any of the trip information, but the application can be set up to share trip information with yourself or other parties. This makes Acceleration Alert ideal for monitoring your own driving behavior or the driving behavior of many people.
Acceleration Alert supports linear acceleration optimized for vehicle use on all devices. This means that the application can operate in any orientation, there is no need to "level" the device or mount the device (although the device should always be secured while in a vehicle).
- Record your route and any dangerous events during the trip
- Define the magnitude and sensitivity of the dangerous events
- View acceleration data from dangerous events in real time
- Mount the device at any angle, no need for leveling
- Log the vehicle acceleration, speed, location and time during a dangerous event
- Email log files to a Gmail account
- Support multiple drivers
Continued use of GPS running in the background can dramatically decrease battery life.