Is there anyway to connect to the car like a datlogger system or using a snapon scanner? I heard of some people making code checkers would definetly want to find out more about it

 

Anything for the FC will be completely custom. There's no ODB-compliant system in a car this old, so there's nothing to connect to for engine data.

 

Wait a minute. So I can't take my 1988 to a shop and have them check and see if the O2 sensor is reading on the ECU?

Mazda said they wanted 90 bucks to do just that... I told them to screw off I was gonna go to an independent shop.

 

mazda has a code checker and yes it is very expensive last i checked roughly 1500 cdn ,,, however using some led lights and some wire u can make yuour own decoder ... but u just have to know how to read it .... when i bought my fc it came with a printed writeup on how to make one and how to read the codes ..... if it wasnt like 10 pages long id post it but yeah it can be done

 

Doesn't the rtek ecu upgrade have diagnostic capabilities

 

well is anyone has any diagnostics instruction on how to make a device let me know or any other methods

 

actually a mechanic had a code reader and it read my old 91 NA coupe. I came with a code that talked about the thermopellet or something.

 

Mazda have a switchable ECU voltage reader that connects inline with the ECU to read all the input and output voltages (see FSM pages 4A-29 or 4B-30). The same thing can be achieved with a little less convenience using a conventional voltmeter or DMM.

There's also a diagnostic plug in the engine bay that can be used to read ECU error codes and also get a general indication of the O2 sensor reading (rich or lean). Mazda have a box they connect to that plug to read the codes (see FSM pages 4A-21 or 4B-22), but you can do the same thing yourself for just a few dollars:

http://www.teamfc3s.org/info/article...odes/main.html

If you don't have the FSM (Factory Service Manual), go here:

http://www.teamfc3s.org/main/factory_service_manual

 

You can data log with the RTEK 2.0.

You can buy the code checkeer from Mazdatrix for big $.

Buying two LED's from Radio Shack for less than three bucks and following the instructions from the FC3S site in NZs above post is a lot cheaper for looking for codes.

Even cheaper, if you own a meter, is to go to the CONTROL UNIT of the FSM and do it yourself using your meter and the values in the FSM.

Seeing if a 02 sensor works or not ust takes a meter and knowing that pin 2D on a series four is the O2 input from the O2. Actually that CAN be tricky if you don't know that the value will be close to zero if you have a factory car with everything working because the acvv will be dumping air into the exaust ports at idle making he 02 read near zip. IF you pull the switching signal to the acv off then the value will rise to its *real* value.

Also if you go to that FC3S site you can make a one light LED that will flash when the car goes into Closed Loop mode and will not flash when NOT in closed loop.

I've a code checker I'll sell you for ????????? Cash on the barrel head before I part with it. Been robbed too much on this forum.

 

I built the LED based one suggested above and it was easy enough (and inexpensive). Our ECU is being upgraded today to include the Rtek 2.0 ($400) which connects to a Palm PDA through a serial cable. Diagnostic reporting is part of the Pocketlogger software package for the Palm PDA that is included in the upgrade. Hailers got it already, isn't that right Hailer?