AFM Hz not displayed for FL5 or DE5

[jeffx]

AFM Hz channel is not available for display on the sensors list or graph templates for FL5 and DE5 logfiles. If you define a graph template to include AFM Hz nothing is displayed with FL5 or DE5 logfiles.

Is this a bug with the FlashPro Manager software or the FlashPro logging function?

It has been like this for awhile. It still appears to be the case with FlashPro Manager 4.3.2.0.

[Hondata]

The ECU does not provide that channel for the FL5/DE5.

[jeffx]

ok thanks for clearing that up.

So I assume this would make it pretty difficult to tune AFM on an FL5 or DE5 then?

[Hondata]

Not particularly. You can datalog AFM flow in g/s. The AFM table values are in g/s.

If you look at a datalog and your fuel trims are -10% for 10 g/s to 40 g/s then you go into the AFM table and change that range by -10%.

It just requires an adjustment for the values that you might change because the table values are g/s not the index, so in the above example you might end your changes at 44 g/s rather than 40 g/s. It's not that big an issue since you'll be blending any changes into the table anyhow.

[DomGSR-T]

Hi,

I have a suggestion for that table that would be great for FL5 and DE5. The frequency of that table is from 1240hz to 12000hz... but we will only use about 2000hz to 9000hz for tuning. Could you give more resolutions of this table by creating 100hz increments table using the 2000hz to 9000hz range? That would mean one g/s entry for 2000hz then one g/s for 2100hz etc... Because when we get to +5000hz the gap in g/s makes is hard to fine tune...

Thanks and have a nice day!

[Hondata]

It uses a calculated index.

[DomGSR-T]

Could you add more resolutions from 5000hz+ ?

[Hondata]

It's a calculated index, not a table lookup.

[DomGSR-T]

What I meant is if we look at the AFM table at 6009hz the g/s value is 64.67, the next one is 6250hz and the g/s value is 73.81. I'm pretty sure that a " in between '' value can be calculated easily and added to the table... should be something like 6130hz and the g/s value would be around 69.24...

If it's not possible could you unlock the frequency field so we could edit it?

thanks for the time

[Hondata]

I understand what you are asking. It is not possible because the index is not a lookup table but calculated arithmetically. Can we move on?