Cynan

Friend pointed this out to me, since I work with CAN some, and he owns an RX-8. I think he wants free work from me or something!

Anyway, here are what the chips are:

MC 331 (CPU?)
____________
Motorola Part, but Incomplete Number
Could be a MC68331CFC16B1-ND, which is a microprocessor, but unlikely since there is the hitachi chip on there.
Best guess is that it is a MC33199, commonly used in interfacing with diagnostic equipment doc sheet even has a schematic of it in a car electronic control unit http://rocky.digikey.com/WebLib/Moto...ta/MC33199.pdf
**********************************************

(3E19) SE555
__________
This is probably a Texas Instruments part. Can be used as a Timer, or a Clock output. Will have to convince friend to let me see his board, unless someone can post a clearer picture of the board for me.
************************************************

SE585
_____
Also appears to be a TI part, but seaching for it didn't bring anything up. Searching for 585 gave me parts, but nothing that looked obvious
**************************************************

SK3206
______

Nothing on this part on digikey, or google. Will try other places later
*************************************************

D151821-1280
____________
Can't find anything useful on this number either. Will try other places later
************************************************** **

64F7055F40
__________
See Above
************************************************** **

D151815-8550
____________
Can't Find anything on this either. Will try other places later
************************************************** **

For the ones I couldn't find anything on, the numbers might not be the actual part number.

rpm_pwr

Cynan,

Best ways to search for chips via part # would be to use chipdir:
http://www.xs4all.nl/~ganswijk/chipdir/
And if that fails use something like this:
http://www.broker1.tv/index1.html?chipdir_t0

Regardless, you dont really need to know the other chips. Maybe knowing the CAN transciever might be useful for some but the rest will be FET packs etc for output switching and stuff for input scaling.

-pete

Sparky

HIgh speed CAN chipsets are running around $120 in quantity on the projects I'm working. Hence my previous skeptisism that someone can produce a device that retails less than 300 dollars that can produce the speed. I've been doing some research myself and the gist that I'm getting is that most of the low dollar diagnostic folks are in over their head on this one. The real time PC dataloggers via PC card seam to be the most viable but they're around $600 for the hardware plus whatever the resaler wants to charge for his S/W front end.

OverLOAD

I've heard a few developers as my place of work say that they doubt some of these cheap boards too, however that said, for the price they seem to be worth exploring.. As long as they support the right CAN bus spec..

I also found a super cheap CAN bus site, which will sell a harness interface to convert the OBDII connector to RS-232 with a CAN interface board protocol analyzer:

under $100 for the module, and the cable:

http://www.multiplex-engineering.com/products.htm

forgive my transgressions, but this is in no way an endorsement on my part, just another picture of what's out there.

I'm going to be seeing if I can pick up the interface cable, and running some info with either the CARDAQ boxes, or the Saint boxes, which are both $1500+ analyzer modules.. plus there's tons of extra analyzer software... all of which I have free access to.

OverLOAD

Blue87Sport

I, for one, welcome our new ECU scanning OVERLOADs. :D

You have our gratitude and best wishes for success. Keep us posted.

astrlsrfr

I can add a little more info on the chips:

there are three (3) D151821-1280 chips. Rmember that 5s could be Ss, so it may be D1S1821-1280?

the Moto part MC331 has an additional # - 86DH

There are three (3) SK3206 & they have an addition #, too: SPF0001.

Mazda Monkey

Hate to burst everyone's bubble, the Japan spec RX8 HP is the same as the US version.

OverLOAD

M Monkey: How is 247 JDM = 238 US?

From every source on this forum, and many off of it, Mazda is still saying 247 in japan for the JDM RX-8 and the dyno's proove it. do you think we'd all be trying to go through this much effort if there wasn't some power to be gained? (oh, and the US 238 HP number is still an overstatement).

No offence, but please do a little bit of research before you make unfounded comments.


official numbers from http://www.rx-8.mazda.co.jp/spec07.html state: 184 KW for the 6MT. (~247 hp, 250 ps). They state 154 KW for the 5MT and the automatic (~207 hp, 209 ps)).

Official numbers from www.mazdausa.com, and the letter that everyone who purchased an RX-8 before August 27 indicate that the North American model has revised power in the 6MT from the 247 to 238 hp.

OverLOAD

syntrix

Hello monkey!!


Would also like to state that 238 is not equal to 247. Hate to burst your bubble

LTAGFERN

For whatever this is worth . . . today I visited my local Vehicle Inspection 'diagnostic' Station (Nashville, TN) in preparation for purchase of my next years auto tags for my '8'. The glitch I experienced today was the inspection station was not CAN-compatible. The under-dash connection was made (to 'read' from the cars' computer), but the 'information' couldn't be read by their computer. The CAN system, I was told, is "too new", and the necessary 'air quality' diagnostic was completed using a 'sniff-probe' stuck into one of the exhaust pipes. (BTW, "RX-8" was not one of the vehicle options listed under "Mazda". I'm now listed as driving a 2004 Mazda "Other".)

The inspection guy (very courteous) said "all cars will be going to CAN in the future, but Mazda was cutting edge by using CAN on the Mazda 6 and the RX-8 now."

As I began to slowly drive out of the inspection bay (with windows open), inspection guy, critically appraising my '8', said "I sure do love your car." I said "thanks" and thought to myself . . me too. I love this car!

OverLOAD

Ok, here's the deal. The RX-8 does not support PWM or VPW ODB..

It does support ISO ODB... however not the older standard ISO9141.. Here's the output from the j1699.c ODB complaince test procedure document when connected to to the RX-8 with a CarDAQ box:

51924ms Checking for OBD on J1850PWM protocol
59065ms REQ MSG: J1850PWM 61 6A F1 01 00
59075ms TX MSG: 95184usec J1850PWM 61 6A F1 01 00
60356ms Checking for OBD on J1850VPW protocol
69019ms REQ MSG: J1850VPW 68 6A F1 01 00
69029ms TX MSG: 105011usec J1850VPW 68 6A F1 01 00
69560ms Checking for OBD on ISO9141 protocol
80676ms Checking for OBD on ISO14230 Fast Init protocol
87856ms REQ MSG: ISO14230 C2 33 F1 01 00
87876ms TX MSG: 123609usec ISO14230 C2 33 F1 01 00
88697ms Checking for OBD on ISO14230 protocol
99743ms Checking for OBD on ISO15765 protocol
105932ms REQ MSG: ISO15765 00 00 07 DF 01 00
105942ms TX MSG: 141451usec ISO15765 00 00 07 DF 01 00
105962ms RX MSG: 141452usec ISO15765 00 00 07 E8 41 00 BE 1F E8 13
106142ms 1 OBD ECU(s) found
106142ms OBD on ISO15765 protocol detected


So, basically, in order to communicate with the RX-8, you must use the newer ISO spec.. meaning just about all the older, cheap tools just plain won't work.. if you've got $ to spare, buy a cardaq or a JPOD...

I've heard about a new tool coming out soon fo USB that'll support the newer tool, whih is much cheaper.. Check the spec first..

OverLOAD

Mazda Family

I think this link might be what you talking about : http://www.mecel.se/products/cantool...an/default.htm
and this web site also may help some : http://www.mecel.se/services/loc3t/default.htm

I don't own an Rx-8 and porbally wont for a few years, but I wanna see this thang get hacked and see people be able to talk to there cars.

Digisan

syntrix

Here's one response from a vendor. Even another one is baffled about the missing +12 line.


Hello Lee,

It is very odd that your diagnostic connector is missing pin 16. Any car that has OBD-II has to have +12V according to the J1962 document. The pins in the DLC go as shown on this diagram: http://www.scantool.net/faq/which_protocol.htm

Try asking our German distrubutor, www.obd-2.de. He is selling a scan tool called AutoMex, and it supports all known OBD-II protocols.

Best regards,

Vitaliy Maksimov
General Partner, ScanTool.net
vitaliy@scantool.net


----- Original Message -----
From: "It's Lee" <lee@lasvegastech.com>
To: <info@scantool.net>
Sent: Sunday, September 21, 2003 4:58 PM
Subject: Hybrid OBDii's?


> This info request was submitted
> by lee@lasvegastech.com (It's Lee)
> on Sunday, September 21, 2003 at 19:58:59
> ----------------------------------------------------------------------
>
> Ok,
>
> Im' trying to connect a 2004 Mazda RX8. Fully registered vag-com
(bi-com) won't connect nor will alex peper's tool.
>
> I did some research and 60%-CAN 40%-ISO 9141 is what the car is.
> Can
you help me with a tool that will actually communicate with this car?
>
> Also on the pinout:
http://www.ross-tech.com/vag-com/images/DLC_Pinout.gif
>
> There are only pins at 2,3,4,5,9 & 11. Maybe I read that backwards,
> but
that's how it shows on the connector on the car. So instantly, we are missing a +12v.
>
> If you have any ideas, let me know. If you have something that will
work, then I'll buy something right away.
>
> Thanks,
> Lee
>
>
> ----------------------------------------------------------------------
> IP address: 65.40.151.137
> User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b)
Gecko/20030611 Mozilla Firebird/0.6
>

1Il

Hello, I live in Albuquerque, NM and have access to a OTC Genisys and several other scan tools. The Genisys chip is supposed to be able to handle all of the CAN protocols but the cable and software is to be released at the end of the year, in a few months when it comes out I'll be more than happy to "demo" it on a RX8 and get some numbers for you guys.

PM me if any one is interested.

syntrix

As soon as someone is able to read the ecu and the sensors successfully, let us all know.

On another note, I just got this wideband O2 setup:

http://www.innovatemotorsports.com/

OverLOAD

I've already read a few of the sensors, as I submitted a partial log previously, let me include the whole thing:

j1699.c source file output, using CarDAQ:

0ms Mon Sep 22 13:07:02 2003
0ms **** LOG FILENAME 2004-Mazda-RX8-1.log ****
0ms **** SAE J1699-3 Revision 10.2.2 (Buid Date: Aug 7 2003) ****

0ms **** NOTE: Timestamp on left is from the PC ****
0ms **** NOTE: Timestamp with messages is from the J2534 interface ****

0ms Windows NT/2K (08930005)
8432ms Enter your name and/or contact information (optional) (Press Enter): XXXxxx
16333ms How many OBD-II ECUs are on this vehicle (1 to 8)? (Press Enter): 1
20038ms Does the vehicle use compression ignition (i.e. diesel)? (Enter Yes or No): n
21601ms Is this a hybrid vehicle? (Enter Yes or No): n
24565ms Is this an engineering test (i.e. ignore protocol errors)? (Enter Yes or No): y
24565ms Device = CarDAQ
24565ms ProtocolsSupported = CAN,ISO9141,KWP2000,CAN,ISO15765,J1850VPW,J1850PWM
24565ms Device = JPod
24565ms ProtocolsSupported = CAN,ISO9141,KWP2000,CAN,ISO15765,J1850VPW,J1850PWM ,SCI,ISO14230
24565ms Select tool from following list:

24565ms 1 CarDAQ (CARDAQ32.DLL)
24565ms 2 JPod (JPOD32.DLL)
24565ms Enter device number (1-2): 28280ms 1
28280ms Loading CARDAQ32.DLL library
31515ms Would you like to run the optional tests first? (Enter Yes or No): n
31515ms **** Test 1.1 (No DTC set) ****
36192ms Turn key OFF for at least thirty (30) seconds (Press Enter):
36192ms Turn key ON with engine OFF.
36192ms Do not crank engine.
51924ms Was the MIL ON for at least fifteen (15) seconds? (Enter Yes or No): y
51924ms **** Test 1.1 PASSED ****
51924ms **** Test 1.2 ****
51924ms Checking for OBD on J1850PWM protocol
59065ms REQ MSG: J1850PWM 61 6A F1 01 00
59075ms TX MSG: 95184usec J1850PWM 61 6A F1 01 00
60356ms Checking for OBD on J1850VPW protocol
69019ms REQ MSG: J1850VPW 68 6A F1 01 00
69029ms TX MSG: 105011usec J1850VPW 68 6A F1 01 00
69560ms Checking for OBD on ISO9141 protocol
80676ms Checking for OBD on ISO14230 Fast Init protocol
87856ms REQ MSG: ISO14230 C2 33 F1 01 00
87876ms TX MSG: 123609usec ISO14230 C2 33 F1 01 00
88697ms Checking for OBD on ISO14230 protocol
99743ms Checking for OBD on ISO15765 protocol
105932ms REQ MSG: ISO15765 00 00 07 DF 01 00
105942ms TX MSG: 141451usec ISO15765 00 00 07 DF 01 00
105962ms RX MSG: 141452usec ISO15765 00 00 07 E8 41 00 BE 1F E8 13
106142ms 1 OBD ECU(s) found
106142ms OBD on ISO15765 protocol detected
106673ms Checking for OBD on ISO15765 29 Bit protocol
109006ms REQ MSG: ISO15765 18 DB 33 F1 01 00
109016ms TX MSG: 144492usec ISO15765 18 DB 33 F1 01 00
112091ms Firmware Version: 04.52
112091ms DLL Version: 05.01
112091ms API Version: 02.02
112111ms Battery = 11.910V
112111ms **** Test 1.2 PASSED ****
112121ms **** Test 1.3 ****
112201ms REQ MSG: ISO15765 00 00 07 DF 04
112211ms TX MSG: 147640usec ISO15765 00 00 07 DF 04
112251ms RX MSG: 147681usec ISO15765 00 00 07 E8 7F 04 78
115135ms RX MSG: 150519usec ISO15765 00 00 07 E8 44
122326ms **** Test 1.3 PASSED ****
122336ms **** Test 1.4 ****
122426ms REQ MSG: ISO15765 00 00 07 DF 01 01
122436ms TX MSG: 157734usec ISO15765 00 00 07 DF 01 01
122446ms RX MSG: 157735usec ISO15765 00 00 07 E8 41 01 00 07 6D 6D
122626ms **** Test 1.4 PASSED ****
122636ms **** Test 1.5 ****
122716ms REQ MSG: ISO15765 00 00 07 DF 06 00
122736ms TX MSG: 158029usec ISO15765 00 00 07 DF 06 00
122746ms RX MSG: 158030usec ISO15765 00 00 07 E8 46 00 C0 00 00 01
123007ms REQ MSG: ISO15765 00 00 07 DF 06 20
123027ms TX MSG: 158313usec ISO15765 00 00 07 DF 06 20
123037ms RX MSG: 158314usec ISO15765 00 00 07 E8 46 20 80 00 00 79
123297ms REQ MSG: ISO15765 00 00 07 DF 06 40
123317ms TX MSG: 158601usec ISO15765 00 00 07 DF 06 40
123327ms RX MSG: 158602usec ISO15765 00 00 07 E8 46 40 00 00 00 01
123567ms REQ MSG: ISO15765 00 00 07 DF 06 60
123577ms TX MSG: 158864usec ISO15765 00 00 07 DF 06 60
123587ms RX MSG: 158865usec ISO15765 00 00 07 E8 46 60 00 00 80 01
123818ms REQ MSG: ISO15765 00 00 07 DF 06 80
123828ms TX MSG: 159110usec ISO15765 00 00 07 DF 06 80
123848ms RX MSG: 159110usec ISO15765 00 00 07 E8 46 80 00 00 00 01
124108ms REQ MSG: ISO15765 00 00 07 DF 06 A0
124118ms TX MSG: 159398usec ISO15765 00 00 07 DF 06 A0
124138ms RX MSG: 159400usec ISO15765 00 00 07 E8 46 A0 00 00 00 01
124419ms REQ MSG: ISO15765 00 00 07 DF 06 C0
124429ms TX MSG: 159702usec ISO15765 00 00 07 DF 06 C0
124449ms RX MSG: 159703usec ISO15765 00 00 07 E8 46 C0 00 00 00 01
124709ms REQ MSG: ISO15765 00 00 07 DF 06 E0
124719ms TX MSG: 159991usec ISO15765 00 00 07 DF 06 E0
124739ms RX MSG: 159991usec ISO15765 00 00 07 E8 46 E0 80 00 00 00
125019ms REQ MSG: ISO15765 00 00 07 DF 06 03
125029ms TX MSG: 160295usec ISO15765 00 00 07 DF 06 03
125290ms REQ MSG: ISO15765 00 00 07 DF 06 01
125310ms TX MSG: 160569usec ISO15765 00 00 07 DF 06 01
125320ms RX MSG: 160570usec ISO15765 FirstFrame Indication
125360ms RX MSG: 160572usec ISO15765 00 00 07 E8 46 01 80 20 00 00 00 00 00 00 01 81 20 00 00 00 00 00 00
125630ms REQ MSG: ISO15765 00 00 07 DF 06 02
125640ms TX MSG: 160897usec ISO15765 00 00 07 DF 06 02
125650ms RX MSG: 160898usec ISO15765 FirstFrame Indication
125771ms RX MSG: 160903usec ISO15765 00 00 07 E8 46 02 01 0A 00 00 00 00 00 00 02 03 0A 00 00 00 00 00 00 02 04 0A 00 00 00 00 00 00 02 05 10 00 00 00 00 00 00
126031ms REQ MSG: ISO15765 00 00 07 DF 06 21
126041ms TX MSG: 161296usec ISO15765 00 00 07 DF 06 21
126061ms RX MSG: 161298usec ISO15765 FirstFrame Indication
126071ms RX MSG: 161299usec ISO15765 00 00 07 E8 46 21 80 20 00 00 00 00 00 00
126331ms REQ MSG: ISO15765 00 00 07 DF 06 3A
126351ms TX MSG: 161596usec ISO15765 00 00 07 DF 06 3A
126361ms RX MSG: 161597usec ISO15765 FirstFrame Indication
126381ms RX MSG: 161598usec ISO15765 00 00 07 E8 46 3A 80 0D 00 00 00 00 00 00
126642ms REQ MSG: ISO15765 00 00 07 DF 06 3B
126652ms TX MSG: 161900usec ISO15765 00 00 07 DF 06 3B
126672ms RX MSG: 161901usec ISO15765 FirstFrame Indication
126682ms RX MSG: 161903usec ISO15765 00 00 07 E8 46 3B 80 0D 00 00 00 00 00 00
126952ms REQ MSG: ISO15765 00 00 07 DF 06 3C
126962ms TX MSG: 162204usec ISO15765 00 00 07 DF 06 3C
126982ms RX MSG: 162205usec ISO15765 FirstFrame Indication
126992ms RX MSG: 162206usec ISO15765 00 00 07 E8 46 3C 80 05 00 00 00 00 00 00
127253ms REQ MSG: ISO15765 00 00 07 DF 06 3D
127263ms TX MSG: 162502usec ISO15765 00 00 07 DF 06 3D
127283ms RX MSG: 162502usec ISO15765 FirstFrame Indication
127293ms RX MSG: 162504usec ISO15765 00 00 07 E8 46 3D 80 0D 00 00 00 00 00 00
127563ms REQ MSG: ISO15765 00 00 07 DF 06 71
127573ms TX MSG: 162805usec ISO15765 00 00 07 DF 06 71
127583ms RX MSG: 162807usec ISO15765 FirstFrame Indication
127603ms RX MSG: 162808usec ISO15765 00 00 07 E8 46 71 80 10 00 00 00 00 00 00
127874ms REQ MSG: ISO15765 00 00 07 DF 06 E1
127894ms TX MSG: 163117usec ISO15765 00 00 07 DF 06 E1
127904ms RX MSG: 163118usec ISO15765 FirstFrame Indication
127954ms RX MSG: 163120usec ISO15765 00 00 07 E8 46 E1 80 20 00 00 00 00 00 00 E1 81 16 00 00 00 00 00 00
128234ms REQ MSG: ISO15765 00 00 07 DF 06 00 20 40 60 80 A0
128254ms TX MSG: 163475usec ISO15765 00 00 07 DF 06 00 20 40 60 80 A0
128274ms RX MSG: 163476usec ISO15765 FirstFrame Indication
128344ms RX MSG: 163480usec ISO15765 00 00 07 E8 46 00 C0 00 00 01 20 80 00 00 79 40 00 00 00 01 60 00 00 80 01 80 00 00 00 01 A0 00 00 00 01
128524ms **** Test 1.5 PASSED ****
128524ms **** Test 1.6 ****
128595ms REQ MSG: ISO15765 00 00 07 DF 01 00
128605ms TX MSG: 163828usec ISO15765 00 00 07 DF 01 00
128615ms RX MSG: 163829usec ISO15765 00 00 07 E8 41 00 BE 1F E8 13
128885ms REQ MSG: ISO15765 00 00 07 DF 01 20
128895ms TX MSG: 164111usec ISO15765 00 00 07 DF 01 20
128905ms RX MSG: 164112usec ISO15765 00 00 07 E8 41 20 80 07 B0 11
129165ms REQ MSG: ISO15765 00 00 07 DF 01 40
129185ms TX MSG: 164395usec ISO15765 00 00 07 DF 01 40
129195ms RX MSG: 164396usec ISO15765 00 00 07 E8 41 40 7A D0 00 00
129456ms REQ MSG: ISO15765 00 00 07 DF 01 01
129466ms TX MSG: 164679usec ISO15765 00 00 07 DF 01 01
129486ms RX MSG: 164679usec ISO15765 00 00 07 E8 41 01 00 07 6D 6D
129746ms REQ MSG: ISO15765 00 00 07 DF 01 03
129766ms TX MSG: 164967usec ISO15765 00 00 07 DF 01 03
129776ms RX MSG: 164967usec ISO15765 00 00 07 E8 41 03 04 00
130037ms REQ MSG: ISO15765 00 00 07 DF 01 04
130057ms TX MSG: 165254usec ISO15765 00 00 07 DF 01 04
130077ms RX MSG: 165256usec ISO15765 00 00 07 E8 41 04 DC
130267ms LOAD_PCT = 86%
130267ms WARNING: LOAD_PCT > 0%
130347ms REQ MSG: ISO15765 00 00 07 DF 01 05
130357ms TX MSG: 165555usec ISO15765 00 00 07 DF 01 05
130367ms RX MSG: 165556usec ISO15765 00 00 07 E8 41 05 52
130537ms ECT = 42 C
130607ms REQ MSG: ISO15765 00 00 07 DF 01 06
130617ms TX MSG: 165817usec ISO15765 00 00 07 DF 01 06
130628ms RX MSG: 165818usec ISO15765 00 00 07 E8 41 06 80
130898ms REQ MSG: ISO15765 00 00 07 DF 01 07
130918ms TX MSG: 166104usec ISO15765 00 00 07 DF 01 07
130928ms RX MSG: 166104usec ISO15765 00 00 07 E8 41 07 80
131188ms REQ MSG: ISO15765 00 00 07 DF 01 0C
131198ms TX MSG: 166387usec ISO15765 00 00 07 DF 01 0C
131218ms RX MSG: 166388usec ISO15765 00 00 07 E8 41 0C 00 00
131399ms RPM = 0 rpm
131479ms REQ MSG: ISO15765 00 00 07 DF 01 0D
131499ms TX MSG: 166677usec ISO15765 00 00 07 DF 01 0D
131509ms RX MSG: 166678usec ISO15765 00 00 07 E8 41 0D 00
131689ms VSS = 0 km/h
131769ms REQ MSG: ISO15765 00 00 07 DF 01 0E
131789ms TX MSG: 166966usec ISO15765 00 00 07 DF 01 0E
131799ms RX MSG: 166967usec ISO15765 00 00 07 E8 41 0E 80
132090ms REQ MSG: ISO15765 00 00 07 DF 01 0F
132110ms TX MSG: 167279usec ISO15765 00 00 07 DF 01 0F
132120ms RX MSG: 167280usec ISO15765 00 00 07 E8 41 0F 41
132310ms IAT = 25 C
132370ms REQ MSG: ISO15765 00 00 07 DF 01 10
132380ms TX MSG: 167558usec ISO15765 00 00 07 DF 01 10
132390ms RX MSG: 167559usec ISO15765 00 00 07 E8 41 10 00 00
132570ms MAF = 0.000000 gm/s
132640ms REQ MSG: ISO15765 00 00 07 DF 01 11
132650ms TX MSG: 167820usec ISO15765 00 00 07 DF 01 11
132660ms RX MSG: 167821usec ISO15765 00 00 07 E8 41 11 2B
132831ms TP = 16%
132921ms REQ MSG: ISO15765 00 00 07 DF 01 12
132931ms TX MSG: 168096usec ISO15765 00 00 07 DF 01 12
132941ms RX MSG: 168097usec ISO15765 00 00 07 E8 41 12 04
133201ms REQ MSG: ISO15765 00 00 07 DF 01 13
133221ms TX MSG: 168380usec ISO15765 00 00 07 DF 01 13
133231ms RX MSG: 168380usec ISO15765 00 00 07 E8 41 13 02
133492ms REQ MSG: ISO15765 00 00 07 DF 01 15
133512ms TX MSG: 168667usec ISO15765 00 00 07 DF 01 15
133522ms RX MSG: 168668usec ISO15765 00 00 07 E8 41 15 A1 FF
133782ms REQ MSG: ISO15765 00 00 07 DF 01 1C
133802ms TX MSG: 168954usec ISO15765 00 00 07 DF 01 1C
133812ms RX MSG: 168955usec ISO15765 00 00 07 E8 41 1C 01
133992ms OBD_TYPE = OBD II
134072ms REQ MSG: ISO15765 00 00 07 DF 01 1F
134082ms TX MSG: 169233usec ISO15765 00 00 07 DF 01 1F
134092ms RX MSG: 169234usec ISO15765 00 00 07 E8 41 1F 00 00
134253ms RUNTM = 0 sec
134323ms REQ MSG: ISO15765 00 00 07 DF 01 21
134333ms TX MSG: 169480usec ISO15765 00 00 07 DF 01 21
134343ms RX MSG: 169480usec ISO15765 00 00 07 E8 41 21 00 00
134513ms MIL_DIST = 0 km
134593ms REQ MSG: ISO15765 00 00 07 DF 01 2E
134613ms TX MSG: 169751usec ISO15765 00 00 07 DF 01 2E
134623ms RX MSG: 169752usec ISO15765 00 00 07 E8 41 2E 00
134884ms REQ MSG: ISO15765 00 00 07 DF 01 2F
134904ms TX MSG: 170039usec ISO15765 00 00 07 DF 01 2F
134914ms RX MSG: 170040usec ISO15765 00 00 07 E8 41 2F 98
135174ms REQ MSG: ISO15765 00 00 07 DF 01 30
135194ms TX MSG: 170328usec ISO15765 00 00 07 DF 01 30
135204ms RX MSG: 170330usec ISO15765 00 00 07 E8 41 30 00
135384ms WARM_UPS = 0
135474ms REQ MSG: ISO15765 00 00 07 DF 01 31
135484ms TX MSG: 170617usec ISO15765 00 00 07 DF 01 31
135495ms RX MSG: 170618usec ISO15765 00 00 07 E8 41 31 00 00
135675ms CLR_DIST = 0 km
135765ms REQ MSG: ISO15765 00 00 07 DF 01 33
135775ms TX MSG: 170906usec ISO15765 00 00 07 DF 01 33
135795ms RX MSG: 170907usec ISO15765 00 00 07 E8 41 33 61
135975ms BARO = 97 kPa
136055ms REQ MSG: ISO15765 00 00 07 DF 01 34
136075ms TX MSG: 171195usec ISO15765 00 00 07 DF 01 34
136085ms RX MSG: 171196usec ISO15765 00 00 07 E8 41 34 80 00 80 02
136346ms REQ MSG: ISO15765 00 00 07 DF 01 3C
136366ms TX MSG: 171484usec ISO15765 00 00 07 DF 01 3C
136376ms RX MSG: 171484usec ISO15765 00 00 07 E8 41 3C 0B 70
136636ms REQ MSG: ISO15765 00 00 07 DF 01 42
136656ms TX MSG: 171772usec ISO15765 00 00 07 DF 01 42
136666ms RX MSG: 171773usec ISO15765 00 00 07 E8 41 42 2F 3A
136937ms REQ MSG: ISO15765 00 00 07 DF 01 43
136947ms TX MSG: 172059usec ISO15765 00 00 07 DF 01 43
136957ms RX MSG: 172060usec ISO15765 00 00 07 E8 41 43 00 86
137137ms LOAD_ABS = 52%
137137ms LOAD_ABS > 0
137227ms REQ MSG: ISO15765 00 00 07 DF 01 44
137237ms TX MSG: 172350usec ISO15765 00 00 07 DF 01 44
137257ms RX MSG: 172352usec ISO15765 00 00 07 E8 41 44 00 00
137517ms REQ MSG: ISO15765 00 00 07 DF 01 45
137537ms TX MSG: 172638usec ISO15765 00 00 07 DF 01 45
137547ms RX MSG: 172639usec ISO15765 00 00 07 E8 41 45 13
137728ms TP_R = 7%
137818ms REQ MSG: ISO15765 00 00 07 DF 01 47
137838ms TX MSG: 172932usec ISO15765 00 00 07 DF 01 47
137848ms RX MSG: 172933usec ISO15765 00 00 07 E8 41 47 55
138038ms TP_B = 33%
138038ms TP_B exceeded normal range
138138ms REQ MSG: ISO15765 00 00 07 DF 01 49
138148ms TX MSG: 173247usec ISO15765 00 00 07 DF 01 49
138168ms RX MSG: 173248usec ISO15765 00 00 07 E8 41 49 51
138349ms APP_D = 31%
138439ms REQ MSG: ISO15765 00 00 07 DF 01 4A
138449ms TX MSG: 173545usec ISO15765 00 00 07 DF 01 4A
138469ms RX MSG: 173545usec ISO15765 00 00 07 E8 41 4A 34
138639ms APP_E = 20%
138729ms REQ MSG: ISO15765 00 00 07 DF 01 4C
138739ms TX MSG: 173834usec ISO15765 00 00 07 DF 01 4C
138759ms RX MSG: 173835usec ISO15765 00 00 07 E8 41 4C 14
139020ms REQ MSG: ISO15765 00 00 07 DF 01 00 20 40 60 80 A0
139040ms TX MSG: 174121usec ISO15765 00 00 07 DF 01 00 20 40 60 80 A0
139050ms RX MSG: 174122usec ISO15765 FirstFrame Indication
139090ms RX MSG: 174124usec ISO15765 00 00 07 E8 41 00 BE 1F E8 13 20 80 07 B0 11 40 7A D0 00 00
139370ms REQ MSG: ISO15765 00 00 07 DF 01 01 03 04 05 06 07
139380ms TX MSG: 174463usec ISO15765 00 00 07 DF 01 01 03 04 05 06 07
139390ms RX MSG: 174464usec ISO15765 FirstFrame Indication
139430ms RX MSG: 174465usec ISO15765 00 00 07 E8 41 01 00 07 6D 6D 03 04 00 04 DC 05 52 06 80 07 80
139620ms **** Test 1.7 ****
139701ms REQ MSG: ISO15765 00 00 07 DF 08 00
139721ms TX MSG: 174795usec ISO15765 00 00 07 DF 08 00
139731ms RX MSG: 174796usec ISO15765 00 00 07 E8 48 00 80 00 00 00
139991ms REQ MSG: ISO15765 00 00 07 DF 08 01
140011ms TX MSG: 175084usec ISO15765 00 00 07 DF 08 01
140021ms RX MSG: 175085usec ISO15765 00 00 07 E8 48 01
140281ms REQ MSG: ISO15765 00 00 07 DF 08 00 20 40 60 80 A0
140301ms TX MSG: 175369usec ISO15765 00 00 07 DF 08 00 20 40 60 80 A0
140311ms RX MSG: 175370usec ISO15765 00 00 07 E8 48 00 80 00 00 00
140492ms **** Test 1.8 ****
140502ms Start engine and let idle for one (1) minute.
164496ms USER TIP: Set A/C to defrost on hybrid vehicles to keep engine running (Press Enter): Start engine and let idle for one (1) minute.




As you can clearly see, I get RPM's, Speed, Engine coolant Temp (ECT), Mass Airflow readings, etc etc... This is a pretty well supported applicaiton, but I don't OWN any hardware, I can only borrow it, so any solution I could make with it would be temporary at best...


OverLOAD

JPatrick_ATAP

A microchip CAN capable PIC is under $10.
A phillips CAN transceiver is under $2.

Both can support up to 1Mbps. Automotive CAN only runs at 500kbps.

Jeff

U. N. O.

how is this going?!?!

SpacerX

I've traded emails with a couple of current OBD-2 scan solution providers (apart from the intrepid efforts of our resident RX-8 researchers here in the forum). Affordable commercial solutions should become available about 6 months from now (Spring 04), if not a little sooner.

I plan on getting a solution for either a PDA or a laptop -- probably about 8-10 months from now.

OverLOAD

I agree with that.. I'm aware of a couple of developers who are working on new, small CAN tranciver modules.. One of particular interest to me, in development is supposedly going to be less than $500 (~$300?) and will be a compact device that comes complete with cables, and an API to make function calls.

In between full time work, school, and tons of other stuff, I'm trying to work on a DirectX 3D program which will be extensible and modifiable, and will work with a variety of units..

I'm quite a ways away, but the initial concept is done, and the process to implement it is complete. It's just a matter of bringing the concept completely into the code..

I probably won't really be able to get too far until spring time.. But that suits me fine, since my RX-8 is going in mothballs over the winter.

OverLOAD

blizz81

Keep us posted! By developing interpretive software for the CAN on the RX-8, will you end up with a product that works universally for all cars that support CAN, or are you only keying in on things specific to the RX-8 (ie, leaving out codes and responses only found on piston engines?)

OverLOAD

for the most part, it doesn't look like it has the capability of being completely comprehensive without the help of a Mazda insider to find out what the specific requests are to get the majority of the information, but it looks like if could very well all be there..

It should work with not only CAN protocol, but any other type of OBD-II bus protocol... potentially, depending on the message structure and how extensible I can make the application in the time I have.. I can always go back and add more later..

OverLOAD

VividRacing.com

I saw your discussion on CAN and the RX-8. We have finished our CAN electrical interface and are working towards completing the protocol layer for our software now. (www.autoenginuity.com). CAN is a lot more difficult than KPW2000 or ISO9141-2. You can get the specs. for the protocol from SAE only. They are the keepers of the knowledge as far as this goes. Also, keep in mind that CAN is used for several things so don't confuse any CAN article with the CAN-bus you require.

Our CAN support will be finished in Dec.

OverLOAD

Vivid,

Thanks for your reply. I've got some good contacts already, and the "Team" is working on a custom hardware interface for CAN, with a few IO's for extra processing capability, and a Serial port connection. We'll probably be making the basic softwaer to display a neat on-screen gauge cluster soon. The concept software is just about done, and the software interface is next.

I do have some access to SAE documents, as another contact is a member.

Thanks for the info, the AutoEnginuity site looks pretty neat.

OverLOAD