How To Configure WPAN Gateway to work with an E-VDT
With the default setting, the E-VDT will search for a valid protocol and connect to it. However, this auto search feature may not work on some vehicles; in this case, the user will need to change the protocol setting of the E-VDT. Protocols 1 to 9 are for OBDII compliant vehicles.
0 – Automatic
1 – SAE J1850 PWM
2 – SAE J1850 VPW
3 – ISO 9141-2
4 – ISO 14230-4 KWP (slow)
5 – ISO 14230-4 KWP (fast)
6 – ISO 15765-4 CAN (11-bit ID, 500k baud)
7 – ISO 15765-4 CAN (29-bit ID, 500k baud)
8 – ISO 15765-4 CAN (11-bit ID, 250k baud)
9 – ISO 15765-4 CAN (29-bit ID, 250k baud)
10 – SAE J1939 CAN (29-bit ID, 250k baud)
11 – USER1 CAN (11-bit ID, 125k baud)
12 – USER2 CAN (11-bit ID, 50k baud)
| AT^OBDSP=n | configure protocol setting n=0 – 12 |
| AT^OBDSP? | show protocol setting |
Examples:
To change the protocol setting, for example, you want to change to ISO 9141-2:
| at^obdsp=3 | set protocol to ISO 9141-2 |
| at^&w | save changes |
To show the protocol setting, type in the following:
| at^obdsp? | display protocol setting |
| Returned string: | 3 |
A message can hold up to 4 parameters. Users can define up to 4 messages named POBDA to POBDD.
| AT^POBDA=n1[,n2][,n3][,n4] | configures report A |
| AT^POBDB=n1[,n2][,n3][,n4] | configures report B |
| AT^POBDC=n1[,n2][,n3][,n4] | configures report C |
| AT^POBDD=n1[,n2][,n3][,n4] | configures report D |
Where:
n1..n4 are parameters to be displayed, n2..n4 are optional.
These commands and their associated parameters are not case sensitive.
The valid values for n1 – n4 are parameters from the E-VDT table.
Example:
at^pobda=p2,p8,p25 configure POBDA message to report parameters P2,P8 and P25
| AT^POBDA? | view the configuration of report A |
| AT^POBDB? | view the configuration of report B |
| AT^POBDC? | view the configuration of report C |
| AT^POBDD? | view the configuration of report D |
WPAN Gateway to DCE message:
n1[,n2][,n3][,n4] <CR><LF>
Where:
n1..n4 are parameters to be displayed, n2..n4 are optional.
These commands and their associated parameters are not case sensitive.
The valid values for n1 – n4 are parameters from the E-VDT table.
Example:
AT^POBDA =P1,P2,P3,P5
Returned String:
P1,P2,P3,P5
| AT^SHOWPOBDA | display E-VDT report A |
| AT^SHOWPOBDB | display E-VDT report B |
| AT^SHOWPOBDC | display E-VDT report C |
| AT^SHOWPOBDD | display E-VDT report D |
Example:
AT^POBDA=P1,P2,P3,P5
Returned String:
$POBDA,A,p1=85,p2=1544,p3=50,0*74
If a parameter is not supported by the engine or vehicle, only commas will be displayed
Available parameters are listed in the Appendix.
$POBDA,A,,,p2=1544*19
AT^OBDPARAM? pn
Where:
pn is the engine parameter
If the parameter is available and valid, the response should be in the following format:
pn=value
AT^OBDPARAM? ALL
Will query all available engine/vehicle parameters
If no engine diagnostic device is connected the command will return ERROR.
Example:
AT^OBDPARAM?P1
$POBDA,A,p1=125*53