J1939 ECU Engine Pro

This app converts an Android device simultaneously become a truck ECUs and an EML327 bluetooth adapter connected to the truck Data Link Connector Port via J1939 CAN BUS
This is convenient and cost-effective solution for android J1939 software developing & testing

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

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

This app has been tested with following apps:
J1939 Code Reader Pro
Bluetooth Terminal

The J1939 ECU Engine Pro can work in command line mode with android terminal apps:
Bluetooth Terminal
alOBD Terminal

The J1939 ECU Engine Pro works like a data server, so it waits (listens) for data request (AT, J1939 commands) from external tester, then processing and responds to the tester

Protocol: SAE J1939 CAN (29 bit/250 KBaud)

Features:
1. ECU may accept SA of F9, FA, FE on request for address claimed, but all CA must claim their address on power up.
2. Simulates 3 ECUs:
Engine #1-Address 00
Engine #2-Address 01
Management Computer-Address 27

3. AT commands

Mandatory AT commands:
The tester (your developing app) must use at least the following AT commands to configure the real ELM327 adapter properly to J1939 protocol:
ATWS, ATE0, ATL0, ATS0, ATSPA, ATAL, ATCAF0, ATR1, ATSTFF, ATAT0, ATJE, ATH1, ATCPnn, ATSHEAFFF9

For convenient when testing,here we assume that the simulation ELM327 adapter has been configured properly before, so we don't have to enter too many AT commands, in fact when testing we only need to use some AT commands like ATSPA, ATSHnnnnnn.

example
1. The order to request component identification (when use the bluetooth terminal) as below:
ATSPA: protocol A-J1939
ATJE: (ATJS depends on the order to enter PGN)
00EE00: request for Address Claimed
ATSHEA00F9: set header to EA00F9
00FEEB: request for Component identifier
2. CA claims its address
set header: ATSHEEFFxx: (xx claim address)
enter 8 bytes of CA's name and wait for contention (250 mS)

Optional AT commands:
ATMA, ATDP, ATDPn, AT@1, ATI, ATTPn, ATCAF1, ATJS

AT command in situation, depends on ECU's address and CAN priority of J1939 message:
ATCPnn(nn-priority), ATSHEAxxyy (xx- ECU address, yy - tester address (F9 or FA))

4. J1939 Commands (PGNs - Parameter Group Number)

a PGN includes several SPNs (Suspect Parameter Number)

The J1939 ECU Engine Pro works with the following PGNs

A. PGNs to send at global address (FF)

00EE00 Address Claimed
00FEEC VIN number (Live Changed Option)
00E800 Acknowledgment PGN

B. PGNs to send to specific addresses (ECU)

Auto tramsmission PGNs on CAN BUS Stream with transmission repetition time

00FECA Active Fault codes (1 s)
00FEE3 Engine Configuration 1 (5 s)
00FEF3 Vehicle Position (5 s)
00FEEE Engine Temperature 1 (1 s)
00FEF5 Ambient Condition (1 s)
00FEE9 Fuel Consumption (1 s)
00F004 EEC1 - The Engine RPM (Live Changed Option) (100 ms)
00F003 EEC2 (Electronic Engine Controller) (50 ms)
00FEF6 Inlet/Exhaust Condition (500 ms)
00FE6C Tachograph - The Vehicle SPEED (Live Changed Option) (50 ms)
00FEF2 Fuel Economy (100ms)
00FEEF Engine Fluid Level/Pressure (500 ms)

PGNs response On Request

00FECB Previously (inactive) fault codes
00FEEB Component Identification
00FEE0 Vehicle Distance
00FEFC Dash Display
00FEC1 High Resolution Vehicle Distance
00FEBC Compression/Service Brake Information
00FEB7 Speed/Load Factor Information
00FEDA Software Identification
00FEE5 Engine Hours/Rpm
00FEDC Idle Operation
00FED3 Clear Active Faults
00FECC Clear Inactive Faults

C. Other PGNs

00EA00 Request
00EF00 Proprietary Manufacturer specific PGN
00EC00 BAM (Broadcast Announce Message)
00EB00 Data Packets message on transport protocol

5.To View live CAN BUS Stream use a bluetooth terminal and send ATMA command