Force OBD2: Diagnostic Edition on Windows Pc

Force OBD2: Diagnostic Edition offers full OBD2 diagnostic and logging functionality. It works with almost all vehicles built after 1996 supporting OBD2. The app can be paired with almost any ELM327 based OBD2 Bluetooth or WiFi (infrastructure only) module to read and clear DTC's (diagnostic trouble codes) from your vehicle. Force OBD2: Diagnostic Edition supports over 2000 SAE diagnostic trouble code definitions allowing you to quickly diagnose the problem without additional searching.

Force OBD2: Diagnostic Edition will also read the Engine Readiness status of that vehicle. Engine Readiness tests the status of the vehicles emissions system which is required to pass emissions for many vehicles. You will know that your vehicle can pass an emissions test before paying for the test and failing. Reading engine DTC's can help diagnose failing Engine Readiness tests. After resolving the issue, Force OBD2: Diagnostic Edition can reset the Drive Cycle by clearing the engine codes and driving the car will cause the Engine Readiness tests to be run.

If additional information is required to diagnose an issue, Force OBD2: Diagnostic Edition can log data from the OBD2 system providing detailed insight into how the engine is performing. In addition to live charting of the data, these additional parameters are logged to an external .CSV file that can be opened with any spreadsheet software for further analysis. Force OBD2: Diagnostic Edition can log all standard defined PID's (parameter identification) including engine RPM, mass-airflow, vehicle speed, coolant temperature and boost among many others.

Force OBD2: Diagnostic Edition supports the following protocols:

* J1850 PWM/VPW
* ISO 9141-2
* ISO 14230-4
* ISO CAN 15765-4 (11/29-bit, 250/500baud)

Please note that most vehicle manufacturers only implement enough PID's to pass legal requirements and do not implement *all* PID's. This means that even though Force OBD2: Diagnostic Edition supports the PID, your vehicle may not. This is especially common when trying to log boost from a turbo. For example, there are two PID's reserved for Intake Manifold Absolute Pressure and, especially among VAG (Volkswagen Auto Group) and Japanese automakers, neither of the boost PID's are commonly implemented.

Another limitation to keep in mind is the sample rate. An ISO 15765-4 (CAN) vehicle with a quality OBD2 module can produce sample rates upwards of 15Hz (15 samples/second). Older vehicles without CAN might only see 5Hz or less and cheap OBD2 modules from China can make it worse. It would not be advisable to use *any* OBD2 based application to tune boost, timing or air fuel ratio.

To tune your vehicle safely, you would need specialized software and hardware for your vehicle that implements the manufacturers proprietary protocols that are design for very high data transfer rates, not an OBD2 system primarily intended for emissions diagnostics.

Be aware that a number of the cheap OBD2 modules I have tested only support ISO 1941-2 and ISO CAN 15765-4 despite claiming support for J1850 and ISO 14230-4. In addition, many of these OBD2 modules send frames that are incorrectly formed or contain garbage characters. While I have made a great effort to get Force OBD2: Diagnostic Edition to work with the more popular violators, I don't have fixes for all of them. I would encourage users to spend more and purchase genuine ELM327 or STN devices from reputable companies.