General information

ECU Engine Pro - Version 1.4.2

This app converts an Android device (phone or tablet) become a car (virtual) with an OBDII bluetooth adapter connected
This is convenient and cost-effective solution for android OBDII software developing and testing

Hardware:
Use 2 android devices (they are bluetooth paired), the one runs this app (in ECU simulation role) and the other runs an android OBDII app for testing (OBDII scanner)

Using this app you don't need a real car, stay indoor and do all testing before doing with a real car
The ECU Engine Simulation can affirm is running stable and reliable

This application has been tested with following android OBD-II apps:
* Code Reader Pro
* Torque Pro
* DashCommand
* ELMScanToyota
The testing result is very good

Note: some android OBD-II apps used the bluetooth threshold detection can not connect to the simulation device, because the threshold of a real ELM adapter is different from the threshold of BLE on android device

The ECU Engine Simulation can also work well with command line on android terminal apps

The ECU Engine Simulation works like a data server, so it waits (listen) for data request (AT or OBD-II commands) from external tester, then processing and responds to the request

The ECU Engine Simulation emulates OBD-II standard: ISO 15765-4 CAN 11/500Kb
The app can process most AT commands, but the following AT commands are usually used with the ISO 15765-4 CAN standard:
* ATZ, ATWS, ATSP0, AT@1, ATI, ATH0, ATH1, ATE0, ATE1, ATDP, ATRV, ATDPn, ATSPn, ATTPn, ATCAF0, ATCAF1, ATSP6, ATAT0

OBD-II commands supported by this app
1. Supported PIDs requests:
01 00 : pid 0x01 to pid 0x20
01 20 : pid 0x21 to pid 0x3F
2. Live data PIDs:
01 01, 01 04, 01 05, 01 0A, 01 0C, 01 0D, 01 0E, 01 10, 01 11, 01 03, 01 04, 01 05, 01 21,
01 33, 01 46, 01 5C, 01 5E, 01 6A, 01 67
3. Vehile information:
09 00 - request supported PIDs
09 02 - request VIN number
09 04 - request calibration number
4. DTC trouble codes:
03 - request stored codes
07 - request pending codes
0A - request permanent codes
04 - request clearing trouble codes and relevant stored data
5. Freeze frame data - frame #0
02 00 00 - request supported PIDs
02 02 00 - request DTC that cause freeze frame data to store
02 XX 00 - where XX are PIDs to ask other freeze frame data

Usage:
Button "Start simulating the ECU" : the data screen appears
On the data screen you can live change some data that are visible on the data screen for the testing purpose
All other invisible data will be returned with fixed values

On the starting screen there are 2 information about the simulation bluetooth OBD-II adapter
* Adapter name: the name of built-in bluetooth device of the phone. this bluetooth device emulates the ELM327 bluetooth adapter
* Adapter address : the max address of built-in bluetooth device

If you do testing on command line terminal, there is an order to put AT commands as following :
ATZ - reset OBD-II adapter
ATSP6 - set protocol ISO 15765-4 CAN 11/500Kb (may use ATSP0 or ATTP6)
ATH1 - View the header 7E8 in the response or ATH0 if not
ATCAF1 -The adapter to format data for you
ATCAF0 - Do format the request data yourself. in this case remember to add PCI byte (number of data bytes) at the first place in the request
for example 02 01 0D : where 01 0D is request vehicle speed (2 data bytes) and PCI byte is 02

Init the OBD-II adapter with the above AT commands you can send what OBD-II request (or other AT commands) you want as usual

Support extra PIDs for testing with ISO 15765-4 CAN 11/500Kb protocol
Header: PID (Ford)
7E0: 221E1C/2209D4
760: 223A51
Prius
Gen2
7E2: 21C3/21C4
7E3: 21CE
Gen3 & PHV
7E0: 21C1
7E2: 21C2/217D/2181/2192
7B0: 2103
7C0: 2113
Privacy policy :
https://www.freeprivacypolicy.com/live/94233689-4b2c-4217-aa1e-91a4ab0572ef