No idea for which RX-7 series (6/7/8), but for some reason it does not have a fuel temperature sensor and brake pedal switch.

 

Looks from the shop manual that the output to the MOP is a duty cycle, then it outputs a 0-5v signal. So, I would say you're looking at the output.

One easy way would be to cut the wire that's the output from the MOP to the ECU and see what you get reading-wise.

Dale

 

Ja. hier. Habe eins in der Version 3.11. Diese ist jedoch eine von AP.

Grüße

 

I can't remember if you mentioned it or not but will your box have Aux inputs...To make this easier can you just mention what the box is going to come with?

thanks

 

is the fc turer software still for sale?? is it any good??? or should i spend the cach on datalogit???

 

I do. mine is a AP engineering for FC3S

 

Thanks, so 13B1 3.11 = 4E14Z02Z FC3S

If you go to the "etc. > Sensor/SW check" Commander screen there is no FUEL sensor and STP switch right? There should be a **** and ***.

 

yes

４Ｅ１４Ｚ０２Ｚ FC3S ECU
４１５－Ｚ００１ FC3S / FD3S commander
４Ｅ１５Ａ０４Ｚ Apexi map sensor with harness

 

Have you checked the Sensor/SW screen?

 

yes I have 2 that are **** and *** I got a picture I will upload it shortly

 

here is the pics

 

Thanks, I've splitted the RX-7 into FD3S and FC3S now.

Should FC Tune allow to upload FD3S files to a FC3S? Unfortunately I don't have the factory settings for the FC3S to compare them. Are they almost identical?

At least one difference is between both generations, the FC3S does not have a fuel temperature sensor and therefore all Fuel Temperature Correction values are set to 1.000 (No correction) while the FD3S has a correction of 1.020 for a fuel temperature of 60C.

 

Ah! That makes sense on the sensors not being there - the FC doesn't have the fuel thermosensor, and the stoplight switch isn't an ECU input. Very interesting!

I think you're right - you should not be able to upload an FD map into an FC PowerFC or vice versa. The motors are different enough that that could be a problem. Also, the FC version is quite rare - I'd say only a handful are running them.

Dale

 

The PFC seems to have pull-up resistors for the sensor inputs to detect not connected/faulty sensors. That's the reason why the Commander displays 4.98V and not 0V for the not present fuel temp. sensor.

The question is if the PFC ignores corrections based on faulty sensors or if the voltage is still converted into the temperature and then the corrections applied. That might be the reason why all correction values are 1.000 for the FC3S because the PFC always uses the last cell.

 

you can "upload" FD maps into FC PFC and you can "upload" the FC maps into FD.
The FC fuel rail has no option for the fuel temp-sensor.

REgards
Iwan

 

I'm sure you *could* upload maps, but *should* is another matter. It's splitting hairs a bit, as again there are VERY few FC guys running the PowerFC, and the ones that do most likely know what they're doing to some extent.

Dale

 

So when is the available date for this again? Seems like its been going on for a while now.

 

sure.... it das not change anything about the option to "upload" both maps mate. We dont need to talk about the values, we are just talking about the option in the communication between FC-Tune and both versions of PFC.

this is the output of my FC3S running Apexi PFC and tuned with Datalogit making 435hp....



REgards
Iwan

 

A little info about the channel settings, Minimum and Maximum is used for scaling on the graphs, while the Limit is used for warning. If a value is above the the set limit the cell background is set to red and then fades out within 3 seconds. The countdown starts as soon as the values is below the limit again. So in case of a faulty sensor the cell would be red all the time.

So far there is only an upper limit because a lower limit doesn't make sense in my eyes. Let me know if you have other ideas for warning, audible, or whatever.

 

The only spot I could think of where a low value would help would be battery voltage. But, that's not typically something I worry about - I know I have a healthy charging system, and if it acts up, I can tell in other ways (dim headlights, hard to start, etc.).

That's looking GREAT!

Any news on the hardware interface? I've got money burnin' a hole in my pocket for it!

Thanks,
Dale

 

Just a quick comment. Coolat temp,battery voltage,ISCV voltage, tps voltage and ATF voltage to name a few should be displayed with below minimum warning, as it would not be advisable to tune with these and other sensors out of range. ( ie cold or below specs etc.)Also can these warnings be user defined as in colour , min and max value, on or off etc.

Ashley.

 

How about a way to add our own sounds/alerts to warn us of problems...I like to have sounds to back up the visuals as sometimes I don't always see something right away...I think low value warnings should be available for things like batt voltage, MOP, and maybe for something else I can think of....Also with the alarm/warning, what about an option for enabling/disabling just the alarm/warning for reasons such as (No MOP--like in my case)??

And as for the box is it going to have input and switched connections like the Datalogit?
Also, are you going to release a later version of the software with some of these new feature for test purposes?

Thanks
Marshall

 

Sounds would be cool..

For the knock warning...
I am able to get a nice clean wav of a motor pinging like nothing else on earth.

 

@Cubes: The RB26DETT has two air flow meters (AF-1, AF-2) and two oxygen sensors (O2-1, O2-2), are each of them for 3 cylinders?

 

I know the airflow meters are one for each turbo. Not sure on the O2 sensor.

Dale