Save previous datalog bug after update FPM

[myuser]

After connect the FP on the pc with the new version o FPM, the following
steps were followed (this was done with the FPM 1550 Beta):

• Upgrade procedure was done, with every thing correct.
• Message confirming the success of flashing the new firmware.
• Choose Flashpro/Datalogging
• Select one datalog from the Datalogs
• Save As... (Save one datalog from previous version, done - Not compressing)
• Select another datalog and try to perform "Save As..." (nothing FPM ignores)
• Unplug FP from the pc and the previous values remain and the list of datalogs is cleared (should the values be cleared? or should the list remain filled?)
  The same happend if we press "Delete All" and confirm, in this case it must refresh the "Datalogging capacity" details.
• Close and Re-open FPM.
• Now it's possible to save one more datalog.

JPS

[Spunkster]

Can you please go to Help at the top of the FlashPro manager screen and click on send information to Hondata support. Include a detailed description of the problem you are having.

[Spunkster]

How long is the recording you are making once all the datalogs are erased?

[myuser]

Some datalogs are 15m to 25/30m.
There is no error message in FPM. The button just don't bring the save dialog window.

To reproduce some datalogs from previous version should be in the FP;
Next upgrade the firmware;
Then try to save two datalog's... one at the time.
The second only could be saved if FPM is restarted.

[Spunkster]

I have tried this and am unable to reproduce.

Once you have deleted all previous datalogs does it work as it is supposed to?

[myuser]

I deleted all the previous datalogs.
I will do some more data logs and check if the issue persists.

Thanks! :)

[myuser]

This are the steps that I have done to check some more scenarios and try to discover a workaround:

• Open FPM
• Message That the previous Calibration should be updated.
• Ok
• Saving one datalog out of three.
• First was done with success.
• Button "Save As..." was unable to open dialog.
• Tab Calibrations
• Delete Primary Calibration (Download button - still active)
• Pressed :) Msg (The FlashPro does not contain a calibration)
• ReOpen FPM - No message
• Save second datalog
• Unable to save the third datalog
• Calibrations (Delete button active with no calibration) :)
• Upload a calibration to Primary slot.
• Unable to save the third datalog
• ReOpen FPM - No message
• Save third datalog
• The saved datalogs are bigger - FPM not compressing
• The FP is protected with security and upload.
• Removed protection
• Try to rename one datalog
• Unplug FP
• Wait for removal symbol in FPM
• Connect FP
• The datalog list is loaded - No rename was done
• Save Settings,Sensors,Graphs and Display
• Uninstall
• ReInstall
• Test again saving more than two datalogs - fail
• Use "Download" button - OK

Probably the compression process fail and leaving the button in a unwanted state.

[Spunkster]

What version of Windows are you using and what vehicle is your FlashPro for.

Can you post a screenshot of the on-board FlashPro datalogging window.

[myuser]

The OS is Windows 7 Ultimate 32bits and the FP is for Civic FN2.

Here is the video: http://goo.gl/KkJSk

[Spunkster]

Try this on a different computer or laptop and see if the problem persists.

[myuser]

I tested in a i7 2.8Ghz machine with Windows 7 Ultimate SP1 64bits a same thing happend.
The next test was made in a P4 3.4Ghz Windows XP SP3 and some interesting things happend.
In this last machine, Hondata Flash Pro Manager 1.2.8.0b was installed.
The save process work fine and de default name to appear in the save dialog box is the name present on the datalog list.
I saved all the datalogs that I have in FP and then I installed the FPM 1.5.5.0b.
Now the default name in the save dialog box is "datalo" and the next name is "dataloument" if we try to save again.
The save process worked only in XP. :)

In the Windows 7 UAC was disable and still the same. What could it be?

[Spunkster]

I will try this again on my own laptop with windows 7 64 bit tomorrow and see if it works properly. So far we have tested this with windows 7, windows 8, XP and none of them have had any problems.

This may have somethign to do with regional settings within windows, or comma vs. period usage.