I've been monitoring this thread for some time. I moderate the ECU Tuning forum at newcelica.org and the Power FC is pretty much the best way to go for that family of engines. I'm earerly awaiting a version of this software to support our Power FC version.

I was looking at the Honda DAT file with the 053 version of the software and noticed that the entire Advanced menu is not active. Why? I have some serious questions about how the PFC calculates load (based on an MAFS setup...what other variables are involved?), what the hysteris function is, and what "mystery" parameters are hidden either in FC Edit or or FC Pro. For one, I see ignition advance jump all over the place at idle, not seeming to reference the map at all. I will also see ignition advanced around two degrees over the map very often. All the correction values would seem to retard ignition timing, not advance. I would think that the PFC would read the crank position sensor for ignition timing, but it isn't available as one of the sensors to monitor.

 

The problem with the advanced settings is that they can only be written to the PFC, but not read from. That means you can't just change a value, you have to enter them all from scratch.


Idle ignition control advances the timing if current RPM falls below the target RPM or retards if it's above. That's why you see the timing at idle bouncing.

 

Fasthatch
Have you looked into making a knock/ignition retard table? It would have to be completely adjustable on the knock side as every knock sensor seems to be different. But it would be a great feature not offered with the standard PFC. Not sure if you would want the knock to retard timing at different levels based on rpm.

 

Grand That pretty much explains my problem. Now to understand why my car refuses to sit at the idle I have it set at. I thought the idle ignition control also controls cold startp...no? So if idle ignition control can only be written to the PFC, how would you find out what its current setting is so that you can make an educated guess at changing it?

 

Forgot to ask one more question...

Have you figured out what the value in the O2 sensor feedback control means? It seems to typically be above 1.000 Is it a gain setting of some sort or is it more like an INJ value?

 

Well I can answer those...

If you want to set your idle ignition, you can turn off idle ignition control. I'm not aware of it doing anythign for cold startup, but I could definitely be wrong about that. Also, if you're going to try to set your timing for very low RPMs, you have to temporarily set your idle down to a value lower than the timing that you want to set. Write the maps, and then set your idle back up. Otherwise the PFC seems to ignore your values.

The O2 sensor feedback value determines where the ECU switches to closed loop and monitors the O2 sensor. When the value in your correction map is lower than the value for the O2 feedback, then the ECU attempts closed loop. Otherwise it's in open loop mode. This caused problems for the FC Edit crowd since after they would do a recalc, the O2 feedback wouldn't work right anymore.

As far as getting a good idle, at least on RX7s you may have to fiddle with a mechanical air bleed screw on the intake. The PFC seems to only handle idle well when everything's set just right...

 

It is possible to read the NVRAM/EEPROM inside the PFC. So all i have to do is to make a copy of the EEPROM, change a setting and compare the new copy with the old one

The PFC has a idle ignition timing setting. If idle ignition control is enabled and current RPM is equal target RPM the current timing is the value from idle ignition timing, regardless what is set in the ignition map. The PFC then advances or retards the timing if the RPM is above or below the target RPM.

 

Good news about the Idle ignition control. I'll just turn that off, as the values it uses are beyond ridiculous for what its trying to do.

As far as the O2 sensor feedback control...that is indeed bad. Out of practice, I always run with the INJ map set all to 1.000 and due my tuning in Excel and copy the values directly back into the base map. In that case, I would be running closed loop all the time with the default value. If say I wanted only idle and cruising affected by the O2 feedback, I would have to set it below 1.000 and then set the INJ in the cells I wanted below that...corrrect?

 

As far as I understand it, the idle ignition timing cannot be changed using FC-Edit. Correct? Will you be able to alter the idle ignition timing settings with FC-Tune?

-Rob

 

That's the way I understand it. So, for example, set O2 feedback to 0.85, and then change your few cruise cells to 0.80 (and fix them on the base map). That should work... Most of us RX7 guys just run with O2 feedback turned off. You can still get good cruise AFRs.

 

That will work, but he will have to change his base fuel map because otherwise he leans out the mixture.

 

All "advanced" settings can be altered with FC Tune. But as already mentioned the problem is that the settings can not be read from the PFC.

Auto update will also not work with the advanced settings. Let's have a look at the "Idle RPM vs. Water temp" table. Initially FC Tune has to set all values to 0 because it doesn't know the values. They are not stored in any file format and can not be read from the PFC. If you now change the value for 30C to +500 RPM and Auto update is enabled, for all other temperature breakpoints 0 would be written to the PFC.

I can also not write the advanced settings with "Upload calibration" to the PFC because they are invalid in most cases.

I have to make a "Upload advanced settings" dialog where you can select and confirm which setting should be written.

I'm not even sure if it is useful to alter these settings. They can't even be changed with by Power Excel dealers. I guess the packets are just there to preprogramm the PFC or for development reasons.

 

AH! I'm with you now. Sorry, I'm a bit slow at times.

 

or ?

 

two tumbs up!!

 

How soon it will be available including the box?

 

I've been following your thread as a lurker for a little while. You project has evolved!

So do I have this correct: currently, FC Tune won't have switchable maps for on-the-fly octane changes? Hardware-switchable mapping capabilities could also be used to provide separate ignition timing for nitrous oxide applications and/or fuel enrichment for dry N2O systems. Is this beyond the scope of the Power FC's capabilities?

 

I don't think hardware switchable maps are a good idea. Only one set of maps can be stored in the Power FC. That means the second maps have to be stored in the box. If you now want to switch the maps the box would have to make a copy of the maps in the Power FC and then write the other maps to the Power FC. That means the box must have the capability to store 2 set of maps. It would have to be possible to read and write the maps in the box and the box must have some kind of buttons and a LED.

Instead you should use a Pocket PC and FC Tune CE if you don't want to have a laptop in your car all the time. I think that's the better solution.

 

Are you an engineering god...?? Let me guess you won a latto and now you feel you need to give back to a community of some sort right? I mean come on seriously? What you've shown here is absolutely amazing all this programming and hacking I am absolutely amazed!

 

Any updates on this fasthatch?
Thanks

 

+1, I just bought an LC-1 and XD-1 and I cant wait to do some logging This wideband will be able to interface with the FC Tune box correct?

 

The brown santa (UPS) just brought my XD-1, so i guess this answers your question

 

FastHatch,

Awesome work. Speachless.

 

I would like to know how soon this may be available as well, and if you have an idea on a price yet. I assume from the reading the thread it will have all the hardware and software?

 

I think this would be cool. Just like many of the other default settings, I feel that some of these are way off base.