Suggestion, when opening the edit window for a map that may have the data incorrectly set to Float when it should be something else, often Ecuedit will pop up a huge stream of floating point errors. Sometimes it is hard or impossible to recover.

It would be nice if the map display would just cancel out on the first floating point error and just pop up a single error saying there is bad floating point data. Maybe something like "Floating point error. Error in XML. Data location or data type incorrectly set to Float."

Many maps data in the DBW subarus do not tell you if they are 8bit, 16bit, or float, so you sometimes have to guess. It's just a pain when trying to write XML data from scratch.

Current work around is to hold down the enter button on the keyboard and frantically click the "X" on the top right of the map display and hope the click "counts" in between the errors.

Try fixed version 2.4.0.94
http://www.epifansoft.com/download/ecuEdit.exe
This is executable file, just copy it to ecuEdit folder.

I'm still having this issue. If I check a log item and the data that comes back is not a valid floating point, it pops up the "invalid floating point value" error and I have to end Ecuedit with task manager. Then it forgets what I changed up to that point.

Same here. So I have to save everytime I make a change in parameter

Freon wrote:I'm still having this issue. If I check a log item and the data that comes back is not a valid floating point, it pops up the "invalid floating point value" error and I have to end Ecuedit with task manager.

In Logger?

^^ i got a few times today.... kind of anoying

Well, both. I get it in the logger or editor. If the datatype is FLOAT and the data that is retrieved (either a map in the editor, or a RAM query from the ECU in the logger) is not a valid floating point number it gives bad float errors.

In the editor, if you click OK for every bad float item in the map that is opened it eventually goes away. I can hold down spacebar and let it "ok" for every item in the map that gets the error then it stops. The map can be closed, or changed with F9 to fix the problem.

But in the logger, once you check the box for that log item it will not go away. I have to kill ecuedit.exe from the task manager.

I think you just need to have an exception handler for this. It would be nice if it would give just one "bad float" error, then automatically turn off that log item.

At least in the logger, because it really causes problems. In particular, if there is a long list of possible memory locations for a parameter (like Engine Load, there may be 20 possible items). It can take 20 tries of killing ecuedit.exe to find the right one in the list.

I think that I fix float error in logger. Try with new version.
I try to catch other errors...

Freon wrote:Well, both. I get it in the logger or editor. If the datatype is FLOAT and the data that is retrieved (either a map in the editor, or a RAM query from the ECU in the logger) is not a valid floating point number it gives bad float errors.

In the editor, if you click OK for every bad float item in the map that is opened it eventually goes away. I can hold down spacebar and let it "ok" for every item in the map that gets the error then it stops. The map can be closed, or changed with F9 to fix the problem.

But in the logger, once you check the box for that log item it will not go away. I have to kill ecuedit.exe from the task manager.

I think you just need to have an exception handler for this. It would be nice if it would give just one "bad float" error, then automatically turn off that log item.

At least in the logger, because it really causes problems. In particular, if there is a long list of possible memory locations for a parameter (like Engine Load, there may be 20 possible items). It can take 20 tries of killing ecuedit.exe to find the right one in the list.

I hope that this version can fix errors in editor also:
Download

Hi Epifan
it seems to be much better. The problem with this revision is that ECU flasher doesn't work any more with my EUDM MY02STi (i didn't test with other cars). Popup window raised "access violation at address 0x00000020...". I Changed Ecuedit.exe file with rev 3.0 one and it worked fine again.

The new version only seems to pop one error per data string. Once for the column if it is set wrong, one for the entire data if it is set wrong, and if it is 3D, once for the row. This is better than before, where it would do it once for every data item (so on a 10x10 maps it would give the error 100 times). I think this is good behavior.

I haven't tested the bad float on the logger yet.

did you check flashing with this rev Freon ? does it work ?

Freon, the logger still craps out, still does the same thing.... you need to kill the process to get out. had it happen 3 times today.

Dweeb wrote:Freon, the logger still craps out, still does the same thing.... you need to kill the process to get out. had it happen 3 times today.

program version?

Yeah, I tested it today. The floating point error keeps popping up every time I click ok. It is because it keeps trying to log it, so as soon as you click ok the logger tries to query the ECU again without removing the bad item. Error pops right back up. When the error occurs it should either pause the logger automatically or uncheck that log item.

This is the version I downloaded about 2 days ago while working on the baud rate issue.