Force OBD2 and Performance is now Force OBD2: Tuner Edition!
Force OBD2: Tuner Edition v2.15 features significant improvements to the OBD2 engine.
- The threading and i/o model has been revisited and improved in an attempt to maximize transfer speeds between the OBD2 module and the application
- A bug with certain OBD2 modules (including iSaddle OBD2) has been resolved. The iSaddle was sending illegal ‘>’ characters preceded by a ‘?\r’ randomly within AT response frames. The ‘>’ character delimits the end of the frame, so the character set ‘?\r>’ found in random responses was causing chaos for the application when it was trying to connect.
- A bug with certain OBD2 modules (including MyOBD2) has been resolved. The MyOBD2 was sending illegal CAN frame delimiters resulting in CAN frames with extra characters. For example, MyOBD2 would send ’01:06′ as a frame delimiter when “1:’ was expected.
- A bug was fixed with occasional garbage characters being received an causing illegal character exceptions when trying to decode illegal hexadecimal characters into their numerical representations. Responses are now sanitized for illegal characters and the exceptions are caught instead of crashing the application.
- Various bug fixes/improvements for Android’s sketchy bluetooth stack have been implemented. On some Android devices, the Bluetooth sockets can randomly stop responding when trying to connect to a device. The application can now perform a full tear down and retry a connection when appropriate without the user having to intervene.
Force OBD2: Tuner Edition has been tested with the following protocols:
- J1850 PWM
- J1850 VPW
- ISO 9141-2
- ISO 14230-4
- ISO 15765-4 (11-bit, 250/500 baud)
- ISO 15765-4 (29-bit, 250/500 baud)