When exporting the VE or Spark tables, Megatune rounds the MAP or MAF digits to the closet whole number. This is a problem for MAF, obviously. Can this be fixed? I've seen it mentioned on the forums a few times over the last year, but no solution has been posted. Are the megatune developers active? Is it open source?
Justin
Bug in VE/Spark Table Export (MAF)
-
- Helpful MS/Extra'er
- Posts: 105
- Joined: Sun Nov 25, 2007 7:14 pm
- Location: Hillsborough, NC
- Contact:
-
- Super MS/Extra'er
- Posts: 12731
- Joined: Sat Jul 16, 2005 8:07 am
- Location: Moorseville, NC
- Contact:
Re: Bug in VE/Spark Table Export (MAF)
That isn't really a bug as much as a limitation to the VEX format. VEX only caries 2 digits for the x & y array's. I am implementing a new XML based format for table import and export in TunerStudio and MegaLogViewer that takes care of this. Expect it in releases within the next 2 months.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html