2600 multiprotocol EOBD Interface

clears the DTC stored. • gets the PID supported and. • gets the coolant temperatur in 1.Byte in response. Bytes.
397KB taille 35 téléchargements 501 vues
mOByDiC 2600 plus version 1.00 released 11.11.2004

2600 multiprotocol EOBD Interface • • • • •

Yellow LED Tx/Rx

ıso9141-2 kwp2000 j1850 – pwm j1850 vpwm CAN bus

Green LED ( mobydic connected to ECU )

mOByDic2600/2600i quick reference

1.) To connect the mobydic to a PC please use 1:1 DSUB9/F DSUB9/M cable 2.) For the OBD connection use a standard OBDII/DSUB9 cable as described on the next page. 3.) The yellow LED indicates OBD Bus activity evertime a message exchange occurs between ECU and mobydic . The green LED is ON once a connection is etablished to ECU.

1

mOByDiC 2600 plus version 1.00 released 11.11.2004

4.) At power on an auto search for a valid protocol is running. The mobydic searchs 3 times for each protocol. It takes a few second till all protocols are tried out. During this procedure mobydic doesn’t respond to any request from PC. If no protocol is found blinks the yellow LED with an interval of 3 sec. This means the car is not OBD compliant. 5.) Once the Green LED is ON you can start an of our programs ( MCI , scanmaster or lite ). If no protocol is found , those programs don’t work correctly

2

mOByDiC 2600 plus version 1.00 released 11.11.2004

Schematic VCC VCC D1 U4

16 13 8

P1 1 6 2 7 3 8 4 9 5

11 10

C1 10uF

T1IN T2IN

T1OUT T2OUT

U1

12 9

13 14 10 11

14 7

1 3 4 5 2 6

+

+ C2 10uF

DB9

VC R1IN R1OUT R2INC R2OUT

+ C3 10uF

+

VCC

C1+ C1C2+ C2- GN V+ D VMAX232 15 RXCAN TXCAN C4 10uF

C5 27pF

D2

GREEN

TXD RXD NC NC

LED1 LED2 CLKOUT BAUDIN

1 21 4 5

15

Y1 16M C6 27pF

16 19 3 17 +

C7 1uF

NC NC RXCAN TXCAN

XTAL2

TXPWMTXPWM+ TXK RXK TXL RXPWM TXVPWM RXVPWM DOWNLD GND GND

XTAL1

6 20 28

R2 1k

9 7 8 26 22 23 12 24 25

YELLOW

R1 1k

TXK RXK TXL

TXPWM(-) TXPWM(-)

RXPWM TXVPWM RXVPWM

27 2 18

JP1 DJMP

RST VCC VCC

OE90C2600

VCC

• • • • •

it is recommended to use a brown out device ( e.g TL7705 from TI ). the both LEDs are low current If < 5 mA. close jumper to download a new release. Don’t change the value of crystal. LED yellow indicates everytime a frame exchange occurs. LED green is on if a valid protocol is found.

3

mOByDiC 2600 plus version 1.00 released 11.11.2004 8V

VCC

8V

VBAT

1k1

3k JP2

8 3 +

TXVPWM

LM393 1

2 -

2N3906

4

3k9

4k7

1N4148

2 4 6 8 10 12 14 16

1 3 5 7 9 11 13 15

OBD CONNECTOR LM393 7

-

RXVPWM

6

10k

5

10k

+

VBAT

GND

LM7805C/TO220 3 1 OUT IN

VCC

100nF

2

100nF

1N4001

U6 GND

LM7808/TO220 3 1 OUT IN

8V

2

100nF

typical J1850-VPWM to RS232 interface

4

mOByDiC 2600 plus version 1.00 released 11.11.2004 VCC R3 4K7

VCC Q1 2N3906

TXPWM(+)

VBAT

R7 10K

8 +

1

RXPWM

4

-

2 4 6 8 10 12 14 16

R9 10K

D4

1N4148

JP2

3

1 3 5 7 9 11 13 15

OBD CONNECTOR

2

U2A LM393

R10 10K

R4 4K7

Q2 2N3904

TXPWM(-)

R8 10K

OBD to j1850 PWM interface

VBAT

510

VBAT 2N2222 510

2N2222

2 4 6 8 10 12 14 16

OBD CONNECTOR

VBAT

4K7

1 3 5 7 9 11 13 15

VBAT

8

TXL TXK 4K7

1

4

RXK

+

3

10K

10K

2

LM393

10K

OBD to ISO interface

5

mOByDiC 2600 plus version 1.00 released 11.11.2004 VCC

1 4 5

TXD CAN_H RXD CAN_L REF

PCA82C251

7 6

100 2

TXCAN RXCAN

-VCC GND

3

2 4 6 8 10 12 14 16

470Pf

1 3 5 7 9 11 13 15

OBD CONN. 100 470Pf

OBD to CAN interface

6

mOByDiC 2600 plus version 1.00 released 11.11.2004

PC Serial Port Parameters The Rs232 parameters are : 9600 Baud , 8 bits , no parity. The PC is Master and the Adapter is slave. Software There are 2 types of commands for communication with the interface adapter. High Level Commands When sending to the adapter the service Nr. and the PID a response of 7 data bytes as specified in ISO 15031-5 is received. For exemple: • • • •

service 3 and no pid to get the stored error codes. gets the freeze frame stored in ECU. clears the DTC stored. gets the PID supported and gets the coolant temperatur in 1.Byte in response Bytes.

Low Level Commands In this mode the adapter can speak to ECU directly. We must first request the found protocol. For J1850-VPWM to speak to ECU for exemple we send to mobydic . thE CRC is calculated by adapter. As a response we obtain ( for service 1)

7

mOByDiC 2600 plus version 1.00 released 11.11.2004

Software driver The Host software must wait at power on until a valid protocol is found. It is normally max 6 sec. The protocol can be requested with Command. 0x05. Is this number zero than is no protocol found. The host can search a valid protocol itself too. The Host must set a time out of 6 sec. for a response. The Fonction numbers are all decimal. But 0x30 means hexadecimal. The Mobydic has a timeout of 1000mS for a incoming Message.The unused commands return • • •

first let the mOByDic search a valid protocol with default parameters use set header command to set the different ECU address generic command is only used when the mOByDic finds a valid protocol at power on.

8

mOByDiC 2600 plus version 1.00 released 11.11.2004

Commande Fonction Request Pos. Response Neg. Response

00 Reserved for system N/A N/A

Commande Fonction Request Pos. Response

02 OBDII/EOBD generic commands 02 THEN SEND

MODE MODE MODE MODE MODE MODE MODE MODE MODE

1 2 3 4 5 6 7 8 9

Pos response









Neg. Response

N/A

Commande Fonction Request Pos. Response

03 Read serial number of mOByDic 03 03 HB LB HB = high byte of serial number LB = low byte of serial number N/A

Neg. Response

9

mOByDiC 2600 plus version 1.00 released 11.11.2004

Commande Fonction Request Pos. Response Neg. Response

Commande Fonction Request Pos. Response

04 Read version of mOByDic 04 04 HB LB HB = high byte version LB = low byte of version N/A

05 Read found protocol 05 05 HB LB HB = high byte of protocol LB = low byte of protocol 0x0000 0x0001 0x0002 0x0004 0x0008 0x0010 0x0020 0x0040 0x0080 0x0100 0x0200 0x0400 0x0800 0x1000

: : : : : : : : : : : : : :

no protocol ISO9141-2 keywords 08 08 ISO9141-2 keywords 94 94 KWP2000 slow init KWP2000 fast init J1850 PWM J1850 VPWM CAN 11 ident 250 KB CAN 11 ident 500 KB CAN 29 ident 250 KB CAN 29 ident 500 KB Reserved SAE J1939 Reserved KW1281 / KW71 Reserved KW82

Neg. Response

N/A

Commande Fonction Request Pos. Response

06 Read chip ident of mOByDic 06 06 HB LB HB = high byte of chip ident LB = low byte of chip ident 2600 = OE90C2600

Neg. Response

10

N/A

mOByDiC 2600 plus version 1.00 released 11.11.2004

Commande Fonction Request Pos. Response

07 Connect to ECU 07 07 HB LB HB = high byte of found protocol LB = low byte of found protocol

Neg. Response

N/A

Commande Fonction Request Pos. Response

08 Disconnect 08 08 HB LB HB = high byte of the disconnected protocol LB = low byte of the disconnected protocol ISO and KWP2000 needs yet 5 sec to disconnect

Neg. Response

N/A

Commande Fonction Request Pos. Response

09 Get found keywords 09 09 KW1 KW2 this command returns the ISO/KWP read keywords

Neg. Response

N/A

Commande Fonction Request Pos. Response

10 K-Line monitoring 10 mOByDic send continous data This command is inactive once after Reset

Neg. Response

11

N/A

mOByDiC 2600 plus version 1.00 released 11.11.2004

Commande Fonction Request Pos. Response

12 Send direct data to ECU 12

ISO9141-2

send receive

Neg. Response

N/A

Commande Fonction Request

13 Send direct data to ECU 13

Pos. Response

KWP2000

send receive

Neg. Response

N/A

Commande Fonction Request

18 KWP2000 fast user init 18

Pos. Response

send receive

Neg. Response

12

N/A

mOByDiC 2600 plus version 1.00 released 11.11.2004

Commande Fonction Request Pos. Response

19 Stop auto keep alive 19 send

,

keepISO = 0 keepISO = 1 keepKWP = 0 keepKWP = 1

stop iso keep alive start ISO keep alive stop KWP keep alive start KWP keep alive

receive Neg. Response

N/A

Commande Fonction Request

24 Send direct data to ECU 24

Pos. Response

J1850 PWM

send receive

Neg. Response

N/A

Commande Fonction Request

25 Send direct data to ECU 25

Pos. Response

J1850 VPWM

send receive

Neg. Response

13

N/A

mOByDiC 2600 plus version 1.00 released 11.11.2004

Commande Fonction Request Pos. Response

33 Send direct data to ECU 33

CAN 11/250

send receive

Neg. Response

N/A

Commande Fonction Request

34 Send direct data to ECU 34

Pos. Response

CAN 11/500

send receive

Neg. Response

N/A

Commande Fonction Request

35 Send direct data to ECU 35

Pos. Response

CAN 29/250

send receive

Neg. Response

14

N/A

mOByDiC 2600 plus version 1.00 released 11.11.2004

Commande Fonction Request Pos. Response

36 Send direct data to ECU 36

CAN 29/500

send receive

Neg. Response

15

N/A