Features Compatible with EOBD/OBDII standard Communication at 900 Baud OBDII / EOBD Modes..9 ISO9 KWP000 J0 VPWM and PWM CAN Bus Multiple response from multiple ECU Physical and fonctional addressing EOBD/OBDII to RS gateway Description OBDII is an international standard for communication between automobiles and diagnostic testers.it specifies a serial data communication bus between ECUs and diagnostic test SAE OBDII Scan Tool ( SAE j9 ). The OE90C00 provides an inteligent interface between a Host and the vehicle s Electronic control units. Both LEDs display the current communication status and connected information. OE90C00 is developed to meet the ISO 0- standard with ISO9,KWP000,SAE j0 and CAN Bus protocols in Service..9 OE90C00 LED TXVPWM BAUDIN 9 0 0 9 TXD GND CLKOUT TXK OE90C00 XTAL RxCAN DOWNL RXVPWM TXL RXK LED RESET RXD TxCAN XTAL PLCC- RxPWM GND TXPWM- TXPWM+
Pin description Pin Pin Name Type Description GND Ground Supply voltage RXCAN I CAN BUS input TXCAN O CAN BUS output LED O OK LED max ma for low current LED TXPWM- O Transmit (-) output for PWM signal TXPWM+ O Transmit (+) output for PWM signal 9 BAUDIN RS Baudrate input clock 0 RXPWM I PWM input TXD O RS output RXD I RS input XTAL I Mhz crystal input XTAL I MHz crystal input Supply voltage GND I Ground 9 RESET I/O A high level on this pin during machine cycles while the oscillator is running resets the device. 0 LED O LED output to indicate the frames exchange RXK I ISO K-line input TXL O ISO L-Line output TXVPWM O VPWM transmit output RXVPWM I VPWM receive input TxK O ISO K-Line output DOWNLD I A low on this pin puts the device in download mode CLKOUT O Clock output for RS baud rate in
Application notes P DB9 9 + C 0uF + C 0uF C 0uF + 0 + C 0uF VC RIN ROUT RIN C ROUT TIN TIN C+ C- C+ C- V+ D V- GN C pf TOUT TOUT MAX U 9 RXCAN TXCAN Y M C pf 0 9 + C uf U TXD RXD RXCAN TXCAN XTAL XTAL RST LED LED CLKOUT BAUDIN GND GND OE90C00 0 9 TXPWM- TXPWM+ TXK RXK TXL RXPWM TXVPWM RXVPWM DOWNLD R k TXK RXK TXL D TXPWM(-) TXPWM(-) RXPWM TXVPWM RXVPWM GREEN R k JP DJMP D YELLOW it is recommended to use a brown out device ( e.g TL0 from TI ). the both LEDs are low current If < 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.
V V k VBAT k TXVPWM k9 + - LM9 k N90 N JP 0 9 OBD CONNECTOR LM9 RXVPWM - + 0k 0k VBAT LM0C/TO0 OUT IN GND 00nF 00nF N00 U V LM0/TO0 OUT IN GND 00nF typical J0-VPWM to RS interface
TXPWM(+) RXPWM R K VBAT + - N R 0K Q N90 D R9 0K JP 0 9 OBD CONNECTOR UA LM9 R0 0K TXPWM(-) R K Q N90 R 0K OBD to j0 PWM interface VBAT 0 VBAT N TXL TXK RXK K K VBAT + - 0K VBAT 0K 0 N 9 0 OBD CONNECTOR LM9 0K OBD to ISO interface
TXCAN RXCAN PCAC TXD RXD REF CAN_H CAN_L - GND 00 00 0 9 OBD CONN. 0Pf 0Pf OBD to CAN interface
PC Serial Port Parameters The Rs parameters are : 900 Baud, bits, no parity. The PC is Master and the Adapter is slave. Software There are 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 data bytes as specified in ISO 0- is received. For exemple: <STX> <0> service and no pid to get the stored error codes. <STX> <0><frame> gets the freeze frame stored in ECU. <STX> <0> clears the DTC stored. <STX> <0><00> gets the PID supported and <STX><0><0> gets the coolant temperatur in.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 J0-VPWM to speak to ECU for exemple we send <length> <0x><0xa><0xf><service Nr><PID> to mobydic. the CRC is calculated by adapter. As a response we obtain <length> <0x><0XB><ECU_adr><0x0+Service><PID> ( for service )
Software driver The Host software must wait at power on until a valid protocol is found. It is normally max sec. The protocol can be requested with Command. 0x0. 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 sec. for a response. The numbers are all decimal. But 0x0 means hexadecimal. The Mobydic has a timeout of 000mS for a incoming Message.The unused commands return <Command-Nr> <00> 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.
Commande 00 Reserved for system Request - Commande 0 OBDII/EOBD generic commands Request 0 <0> THEN SEND MODE <0> <PID> MODE <0> <PID> MODE <0> MODE <0> MODE <0> <TID> <OSNO> MODE <0> <TID> MODE <0> MODE <0> <TID> <DataA><DataB><DataC><DataD><DataE> MODE 9 <09> <INFO_Type> Commande 0 Read serial number of mobydic Request 0 0 HB LB HB = high byte of serial number LB = low byte of serial number 9
Commande 0 Read version of mobydic Request 0 0 HB LB HB = high byte version LB = low byte of version Commande 0 Read found protocol Request 0 0 HB LB HB = high byte of protocol LB = low byte of protocol 0x0000 : no protocol 0x000 : ISO9- keywords 0 0 0x000 : ISO9- keywords 9 9 0x000 : KWP000 slow init 0x000 : KWP000 fast init 0x000 : J0 PWM 0x000 : J0 VPWM 0x000 : CAN ident 0 KB 0x000 : CAN ident 00 KB 0x000 : CAN 9 ident 0 KB 0x000 : CAN 9 ident 00 KB 0x000 : Reserved SAE J99 0x000 : Reserved KW / KW 0x000 : Reserved KW Commande 0 Read chip ident of mobydic Request 0 0 HB LB HB = high byte of chip ident LB = low byte of chip ident 00 = OE90C00 0
Commande 0 Connect to ECU Request 0 0 HB LB HB = high byte of found protocol LB = low byte of found protocol Commande 0 Disconnect Request 0 0 HB LB HB = high byte of the disconnected protocol LB = low byte of the disconnected protocol ISO and KWP000 needs yet sec to disconnect Commande 09 Get found keywords Request 09 09 KW KW this command returns the ISO/KWP read keywords Commande 0 K-Line monitoring Request 0 mobydic send continous data This command is inactive once after Reset
Commande Send direct data to ECU ISO9- Request send <length><iso message without checksum> receive <><length><response data> Commande Send direct data to ECU KWP000 Request send <length><iso message without checksum> receive <><length><response data> Commande KWP000 fast user init Request send <length><kwp message without checksum> receive <><length><response data>
Commande 9 Stop auto keep alive Request 9 send <KeepISO>, <KeepKWP> keepiso = 0 keepiso = keepkwp = 0 keepkwp = stop iso keep alive start ISO keep alive stop KWP keep alive start KWP keep alive receive <9> Commande Send direct data to ECU J0 PWM Request send <length><pwm message without crc> receive <><length><response data> Commande Send direct data to ECU J0 VPWM Request send <length><vpwm message without crc> receive <><length><response data>
Commande Send direct data to ECU CAN /0 Request send <0><CAN message without crc> receive <><0><response data> Commande Send direct data to ECU CAN /00 Request send <0><CAN message without crc> receive <><0><response data> Commande Send direct data to ECU CAN 9/0 Request send <><CAN message without crc> receive <><><response data>
Commande Send direct data to ECU CAN 9/00 Request send <><CAN message without crc> receive <><><response data>