WiFi ENGINE ECU 3.0.8

WiFi Engine ECU - Version 3.0.8

WiFi Network Platform is used for connection

Key parameters:
* IP address: the host address of device emulates ECU (as server).This address can NOT be changed because it is assigned be the Network. So the tester (as client) must set it IP address to this address to connect to
* Port : the port to make connection, this port number can be changed via settings(also can be changed on tester app side)

How to use:
Run "WiFi engin ECU" first to get the Host IP Address and Port number
Modify IP address and port on "app tester" to these IP and port.

Press button "Start" to start the ECU simulating process, the data like DTCs and VIN that are visible only on a dialog screen (menu Edit) can be modified
All other invisible data will be returned with fixed values.

Wait some seconds (ECU gets stable) then start launching tester on other device.

When completing stop the tester first and then the ECU server

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

Hardware
Use 2 android devices, the one runs this app (as wifi server - SIM ECU) and the other runs an android OBDII app for testing (as client - tester)

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

The apps have been tested :
* OBD-II Code Reader Pro
* Torque Pro
* DashCommand
* Hobdrive

The ECU Engine Simulation can also work well with command line on android WiFi 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 3 OBD-II standards:
1 - ISO 15765-4 CAN 11/500Kb
2 - ISO 9141-2 (5 Baud init)
3 - SAE J1850 PWM (41.6 Kbaud)

The OBD standard for work can be selected in Setting Menu
The app can process most AT commands, but the following AT commands are usually used:
* 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 request other freeze frame data

AT commands can use by tester or wifi terminal as following :
ATZ - reset OBD-II adapter
ATSP6 - set protocol ISO 15765-4 CAN 11/500Kb (maybe use ATSP0 or ATTP6)
ATSP3 - set protocol ISO 9141-2 (5 Baud init) (maybe use ATSP0 or ATTP3)
ATSP1 - set protocol SAE J1850 PWM (maybe use ATSP0 or ATTP1)
ATH1 - if you want to view the header 7E8 in the response and ATH0 if not
ATCAF1 - if you want the adapter to format data for you
ATCAF0 - you have to format the request data yourself. in this case remember to add PCI byte (equal to number of data bytes in the request) 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

After 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