Bug found .98 when updating many cells simultaneously

[dre99gsx]

I have to find the error log, but when I try to increment or decrement (using + or - key) a matrix of 6x6 fuel cells, it throws up an error and will sometimes freeze.  If I change all the values slowly, it doesn't complain.  If I hit them very quickly, it will complain.

[dre99gsx]

Error Received at: Tuesday, November 24, 2009 3:23:24 PM

AEM.Shared.Exceptions.CUnhandledException: An Unhandled exception was found. It will be logged and execution will continue. ---> System.InvalidOperationException: Stack empty.
   at System.Collections.Stack.Peek()
   at AEM.Shared.Calibration.CCalibrationEquationParser.CCalibrationFunction.PopCalibration()
   at AEM.Shared.Calibration.CCalibrationEquationExecuter.0(IEquation , Double , Int32 , Int32 , Int32 , String , CalItemType , CCalibration )
   at AEM.Shared.Calibration.CCalibrationEquationExecuter.Evaluate(IEquation pEquation, Double dCurValue, Int32 iCurRawValue, Int32 iXAxisIndex, Int32 iYAxisIndex, String strCalItemName, CalItemType eCalItemType, CCalibration pCalibration)
   at AEM.Shared.Calibration.CUserScalarDef.RawToReal(Double dRawValue, Int32 iXAxisIndex, Int32 iYAxisIndex, String strCalItemName, CalItemType eCalItemType, CCalibration pCalibration)
   at AEM.Shared.Calibration.CCalibrationItemDef.RawToReal(Int32 iRawValue, Int32 iXAxisIndex, Int32 iYAxisIndex, CCalibration pCalibration)
   at AEM.Shared.Calibration.C3DTableDef.RawToReal(Int32 iRawValue, Int32 iXAxisIndex, Int32 iYAxisIndex, CCalibration pCalibration)
   at AEM.Shared.Calibration.CCalibration.Increment3DTableItem(String strTableName, Int32 iXTableIndex, Int32 iYTableIndex, Int32 iIncrement)
   at AEM.Shared.Calibration.CCalibrationEditor.IncrementValuesTable(Point ptFirstPoint, Point ptSecondPoint, Int32 iSteps, String strTableName, Boolean b2DTable)
   at 0.1v.IncrementValues(Int32 iSteps)
   at 0.1V.SelectedCellsIncremented(Int32 iIncrement)
   at 0.1t.TableCellsIncremented(Int32 iIncrement)
   at 0.1W.8(Int32 )
   at 0.1W.OnKeyDown(KeyEventArgs e)
   at System.Windows.Forms.Control.ProcessKeyEventArgs(Message& m)
   at System.Windows.Forms.Control.ProcessKeyMessage(Message& m)
   at System.Windows.Forms.Control.WmKeyChar(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at NineRays.Windows.Forms.FlyGrid.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   --- End of inner exception stack trace ---

[AZ]

I need more info:
Is EMS connected while you're adjusting the fuel map?
Is Auto-Rescale turned on? (Go to Tools->Preference, it's under Misc category).
If yes, is the adjusting causing a auto-rescale? ( you can tell by looking the MicroSec/bit option)
What's your OS?

Thanks.

[dre99gsx]

No problem:

Happens when connected and tuning the vehicle
Windows XP SP3
Auto Scale is on (come to think of it, I could turn it off...)
-  I haven't been watching the Microsec/bit.  I'll keep my eye on it.

It happens consistently.  I can turn off Microsec/bit and see if it disapears.

Thanks.

[jonbar87]

I've been having this problem as well. If i highlight a bunch of cells and try to + or -, sometimes it'll freeze up completely. Other times, it changes right away. But, the times it does freeze and I have to ctrl+alt+del out of the program, when I open it up again and download the map, half the cells are changed...so it's like it is changing them, just very very slowly. Doesn't make sense though because it's not always like this, other times it changes almost instantly (maybe 1 - 2 seconds).

[AZ]

The reason wh

I've been having this problem as well. If i highlight a bunch of cells and try to + or -, sometimes it'll freeze up completely. Other times, it changes right away. But, the times it does freeze and I have to ctrl+alt+del out of the program, when I open it up again and download the map, half the cells are changed...so it's like it is changing them, just very very slowly. Doesn't make sense though because it's not always like this, other times it changes almost instantly (maybe 1 - 2 seconds).

The reason it looks like "freeze up" and "half the cells are changed" is because you have "AutoRescale" turned ON, and AEMTuner is rescaling the WHOLE fuel map. And while the ECU is connected, the process is slow because of the communication. You can test it by entering a very large number in one cell of fuel map and you'll see the whole map is changed. If you exit the program during the rescaling, half of you cells are changed.

I do find there is a issue and it'll be fixed in the next version. Thanks for your posts!

[jonbar87]

I see. I will turn off autorescale and see if that helps. Thanks!