Page 2 of 25

Re: FlashPro Requests

Posted: Wed Apr 09, 2014 2:18 pm
by Hondata
romeochris wrote:Any add on bluetooth module for older FP?
The original FlashPro was not designed to have Bluetooth and there is no way to add a Bluetooth module. The newer FlashPro is a different board - not the same as the original.

Re: FlashPro Requests

Posted: Wed Apr 09, 2014 4:49 pm
by DomGSR-T
thatguyinms wrote:Instantaneous mpg and Avg MPG for datalog please!
Oh yes! good one :)

Re: FlashPro Requests

Posted: Fri Apr 11, 2014 5:10 pm
by bigbadspoon
I wouldn't mind seeing a calibration compare tool similar to what TunerCat does. You load in your two calibrations, then the software highlights every cell that is different and can be switched to show what the difference is. The current comparison tool only seems to tell you that there *are* differences, but not what they are.

Also, as previously stated, instant mpg in datalogs would be a fantastic feature. Or, if it were implemented as a feature in FlashPro Manager instead of on the FP itself. This way it would not waste clock cycles on the logger and could be calculated after-the-fact on the user's computer if chosen. Same for calculated engine load.

I would also like to see the ability to stitch together datalogs or the ability to load .csv files as datalogs (so I can stitch them manually if I need to).

I'd like finer control of the air-fuel ratio in closed loop on AFM tunes, as well. The current situation relies on some very inaccurate switches (for example, I can set a high ratio in the WOT table (like 14.5) and set the switch to WOT at 61kPa, but it actually switches to WOT at 50kPa). Using throttle pedal isn't really a great option as load and throttle opening are not necessarily as well-correlated as load and MAP reading.

Lastly, if there's any constant that can be edited so that we can fix the mpg display in the i-mid, that would be awesome! I'm tired of being disappointed at the pump because the i-mid reads 3 mpg high all the time.

And not to sound like a whiny demanding prick, I think FlashPro is an awesome piece of equipment and I appreciate you guys working to constantly improve it by adding new features and fine-tuning the little things in the background that most of us don't notice.

Re: FlashPro Requests

Posted: Sat Apr 12, 2014 5:14 am
by maximus_pan
Add Honda CU2 K24Z5 for Chinese users PLEASE! Foolishly bought a FlashPro for U.S. TSX CU2...
PS: I'm not a spammer :-)

Re: FlashPro Requests

Posted: Sat Apr 12, 2014 7:04 am
by civicRSA
Some urgent requests for FN2 Euro CTR AFM calibrations. These already exists in Civic Si AFM calibrations so I guess it shouldn't be a major trouble.

1. Ability to control radiator fan On/Off temps
2. MAP to high or to low error enable (I've had faulty 4 bar map sensors spike to 40bar)
3. Extended knock sensitivity and knock retard tables for boost.
4. TPS WOT determination
5. VTEC activation conditions ie. coolant temp, minimum speed

6. And then a boost control function. We don't have the EGR pin in our ecu's so we have had to use USDM ecu's. Thus we cannot then use AFM calibrations.
Maybe you could use another output for boost control.

As I mentioned these functions already exist in the Civic Si AFM calibrations but the Euro CTR is not getting much updating at all.
Please points 1,2,3 and 6 are important.

Re: FlashPro Requests

Posted: Tue Apr 15, 2014 5:28 pm
by DomGSR-T
I would like to have the L/100km fuel reading instead of MPG on the new mobile apps!

Re: FlashPro Requests

Posted: Sat Apr 19, 2014 10:31 am
by Gernby
A couple of really great features IMHO would be:

* the ability to cut out a section in the middle of a datalog. For example, if you select a section in the middle with the mouse, instead of always zooming in on that section, have a mode where it asks if you want to delete the selected part of the datalog.
* when saving datalogs that were recorded on the flashpro, eliminate the "filler" rows to reduce the file size, similar to the way the datalogs are saved when recorded in FlashPro Manager. This would reduce file size by about 80% without reducing the data resolution.
* add the ability to use hot keys to switch between cam angles on the tables.
* change the source for VSS to be the average of the 4 wheels from the VSA data stream (like 65.47 mph) instead of the low resolution integer value that is currently used. You probably already have the CANBUS packet info for it, but I'll provide it if you don't.
* add the option to NOT datalog all parameters, so that sample rate can be improved by eliminating things we don't care about (like Traction control values when we don't have the TC unit). The ability to eliminate some columns in the datalog file to reduce file size would be great too.

Re: FlashPro Requests

Posted: Wed Apr 23, 2014 11:57 am
by VitViper
Gernby wrote: * when saving datalogs that were recorded on the flashpro, eliminate the "filler" rows to reduce the file size, similar to the way the datalogs are saved when recorded in FlashPro Manager. This would reduce file size by about 80% without reducing the data resolution.
No. Absolutely not. Those are not "filler" rows. They absolutely add a ton of resolution to a lot of very important datalogged parameters -- and one of FlashPro's major advantages over KPro/S300 logging.

Re: FlashPro Requests

Posted: Thu Apr 24, 2014 10:35 am
by Gernby
VitViper wrote:
Gernby wrote: * when saving datalogs that were recorded on the flashpro, eliminate the "filler" rows to reduce the file size, similar to the way the datalogs are saved when recorded in FlashPro Manager. This would reduce file size by about 80% without reducing the data resolution.
No. Absolutely not. Those are not "filler" rows. They absolutely add a ton of resolution to a lot of very important datalogged parameters -- and one of FlashPro's major advantages over KPro/S300 logging.
It's been a couple years since I studied the data stream on the CANBUS, but the resolution probably isn't what you think. I don't know about the contents of the data in the FPDL files, but the exported CSV datalogs definitely have a ton of filler values that provide no improvement in resolution.

The CSV files show about 135 records per second, but only some of the parameters are updated in each record. The FlashPro requests the parameters from the ECU in groups, and there are 6 groups. It makes a query to the ECU for just 1 group about every 7.5 milliseconds, so it takes about 45 milliseconds between updates within each group. That's about 22 updates per second for each parameter. Since no parameter is being updated more than 22 samples per second, there really isn't any value in storing each parameter 135 times per second.

However, for the purpose of a software dyno, I agree it's important to "trigger" the timestamp off of the right group, since the time gap between queries does vary between 4-10 milliseconds. Thankfully, the most important parameters for a software dyno are all contained in the same group (VSS, RPM, MAP, AFM, INJ, etc.), and the very next group after that contains the next most important (AF, Trims, etc.). The resolution on the values after that are way less important, especiially since you can simply add .007, .014, or .021 milliseconds logically if you really care. So if the datalogs contained only 22 rows per second, and the timestamp on each of those rows came from that 1 big group with RPM, the resolution would be just as good as it is now.

Re: FlashPro Requests

Posted: Sun Apr 27, 2014 4:27 pm
by bigbadspoon
VitViper wrote:
IcEMoCHa wrote:Some suggestions..

1. Option of using CEL to indicate knocking.

2. Change cam angle preset value for fuel and ign map. (have 5, 10, 15, 20, 25 cam angle)
Both options already exist and work well.

I would definitely like to see option 1 applied to 9th generation Civics. Currently, this looks to only be available for 8th?

Re: FlashPro Requests

Posted: Tue May 06, 2014 2:31 pm
by VitViper
@Derek

Remember when we got the gear selector and such working on the Race calibrations long while ago? I've tested the Civic calibration on my now and the gear selector works properly (all 6 speeds), however there is a small, yet somewhat annoying discrepancy still.

On Race cals:
- Gear selector works, odometer is accurate, trip meter is accurate. I only need to do a % correction against the ECU VSS, I don't have to correct the dash speed -- it is accurate.

On Civic cals:
- Gear selector works, odometer is NOT accurate (it's picking up about .55 miles for every 1 mile traveled), trip meter is not accurate (same as odo). I have to do a % correction against both the ECU VSS and dash speed.


I mean I don't mind keeping the mileage off my car... :)

Re: FlashPro Requests

Posted: Fri May 09, 2014 10:27 pm
by Slip_Angle
Alternator Control for the ILX

Re: FlashPro Requests

Posted: Tue May 13, 2014 8:51 am
by Gernby
After stumbling across the box containing my CAN dongle, which has been missing ever since we moved last year, I went out to do some data logging in my '13 Civic Si. I was very disappointed to find that Honda changed the data definitions on the CANBUS from the '06+ S2000, but was glad to see that the data rates for high resolution speed and RPM more than doubled! Both are now streaming across the CANBUS at 100 frames per second with a 16 bit resolution!

Is there any chance you could have the FlashPro record those values in the datalogs with the higher update rate and resolution? I'm referring to ID 344 bytes 1 and 2 for speed and ID 380 bytes 3 and 4 for RPM. For the S2000 it would be ID 300 bytes 5 and 6 for RPM and ID 448 bytes 5 and 6 for speed.

Re: FlashPro Requests

Posted: Fri May 16, 2014 1:47 pm
by Gernby
I know that this might be one of those "when pigs fly" requests, but it would be uber-awesome if there was a way to import / export calibrations to / from XML files, so it would be easier to use external software to create or modify calibrations.

Re: FlashPro Requests

Posted: Wed May 28, 2014 1:43 pm
by VitViper
Anti-lag for the quasi-launch-control.

My 8th gen will thank you, being able to launch from 7k rpm with more than 1psi of boost.