I have some bugs to report as follow:

1. Can not chage value in the "Max Knock Retard" , "Knock Retard Increment" and "Closed Loop Cruise AFR" tables (These are all I can find right now...)

2. For a logging activation method, I have to choose Logging => Trigger Log file on Defog Swithch everytime I open the Logger. This is very annoying because it's easy to forget to select and at the end of the log run, I have zero data to analyze.

3. Many times that Logger program stop running on its own. The screen would freeze up without any responses to commands. When I tried to close the Logger, an error window would popped as "Purge Comm*&%#$#%^!#@#@$%#$ ...Error". And I lost my COM Port from that. I have to shutdown and boot up the computer again. This is very clumsy during the precious tuning time. What is wrong with the program or my laptop??

Kindly find the solution to the above bugs please.

Thank you so much in advance for your help.

Nik.

Spec C Wannabe wrote:1. Can not chage value in the "Max Knock Retard" , "Knock Retard Increment" and "Closed Loop Cruise AFR" tables (These are all I can find right now...)

Why you can't change? What kind of map descriptions do you use? XMLWrite or converted from EcuFlash, Enginuity?

Spec C Wannabe wrote:2. For a logging activation method, I have to choose Logging => Trigger Log file on Defog Swithch everytime I open the Logger. This is very annoying because it's easy to forget to select and at the end of the log run, I have zero data to analyze.

Set it one time to "Trigger -> None" if you don't want to use trigger.

Spec C Wannabe wrote:3. Many times that Logger program stop running on its own. The screen would freeze up without any responses to commands. When I tried to close the Logger, an error window would popped as "Purge Comm*&%#$#%^!#@#@$%#$ ...Error". And I lost my COM Port from that. I have to shutdown and boot up the computer again. This is very clumsy during the precious tuning time. What is wrong with the program or my laptop??

Upgrade your version to 3.0, I fix freeze problems.

epifan wrote:

Spec C Wannabe wrote:2. For a logging activation method, I have to choose Logging => Trigger Log file on Defog Swithch everytime I open the Logger. This is very annoying because it's easy to forget to select and at the end of the log run, I have zero data to analyze.

Set it one time to "Trigger -> None" if you don't want to use trigger.

I experience the same problem since a long time ago. Epifan, the problem is not to not use the trigger, the problem is that every time you open the logger or disconnect/reconnect, you have to select "Logging => Trigger Log file on Defog Switch" despit the fact it is already selected by default. if you don't do that, nothing will be recorded something

XNWRX wrote:

epifan wrote:

Spec C Wannabe wrote:2. For a logging activation method, I have to choose Logging => Trigger Log file on Defog Swithch everytime I open the Logger. This is very annoying because it's easy to forget to select and at the end of the log run, I have zero data to analyze.

Set it one time to "Trigger -> None" if you don't want to use trigger.

I experience the same problem since a long time ago. Epifan, the problem is not to not use the trigger, the problem is that every time you open the logger or disconnect/reconnect, you have to select "Logging => Trigger Log file on Defog Switch" despit the fact it is already selected by default. if you don't do that, nothing will be recorded something

That is it.... Same for me...

For those tables that I said I cant change, I have already hit "+" and "-" buttons on the keyboard repeatedly to change the value in those tables but the value on the program display did not change/response according to my key stroke.

I will try upgrading to Ver3.0 to see if my logger freezing will be cured.

Epifan, Thanks anyway for your quick supports.

XNWRX wrote:I experience the same problem since a long time ago. Epifan, the problem is not to not use the trigger, the problem is that every time you open the logger or disconnect/reconnect, you have to select "Logging => Trigger Log file on Defog Switch" despit the fact it is already selected by default. if you don't do that, nothing will be recorded something

I made a solution: then you manually press "Log to file" trigger never happens until you stop log to file.

Spec C Wannabe wrote:For those tables that I said I cant change, I have already hit "+" and "-" buttons on the keyboard repeatedly to change the value in those tables but the value on the program display did not change/response according to my key stroke.

I think this is description problems. But, you can change values by set value directly. BTW, send to me this ECU description - I check it.

When you press + or - what your F9 screen says for data or increment/decrement. I think the default is to do a data increment if there is nothing defined in the XML.

So, if the data is 16bit UINT, you're only moving the data value by 1 out of 65536 (2^16). So if it shows a value of 1.00, changing it by 1 out 65536 won't do much. You might want to change it from "data" to "value" increment and put in how much you want it to jump.

It's really bad on stuff like the MAF scaling table, which is full floating point precise. You could press + a hundred times and it won't change the data by even 0.01 g/s. You need to tweak the F9 screen as above. Move the radio button down and put in a small and large increment that you want.

If the data is only 8bit, pressing + or - a few times should cause a change even if it is set default to data increment. That's only 1 out of 256 points, so pressing it a few times causes a larger change. Make sense?

Epifan once again thanks for one great application!

i have encountered an issue with the read/flash...the kernel files referenced in the FLASH.XML are missing from the installation!

Freon wrote:When you press + or - what your F9 screen says for data or increment/decrement. I think the default is to do a data increment if there is nothing defined in the XML.

So, if the data is 16bit UINT, you're only moving the data value by 1 out of 65536 (2^16). So if it shows a value of 1.00, changing it by 1 out 65536 won't do much. You might want to change it from "data" to "value" increment and put in how much you want it to jump.

It's really bad on stuff like the MAF scaling table, which is full floating point precise. You could press + a hundred times and it won't change the data by even 0.01 g/s. You need to tweak the F9 screen as above. Move the radio button down and put in a small and large increment that you want.

If the data is only 8bit, pressing + or - a few times should cause a change even if it is set default to data increment. That's only 1 out of 256 points, so pressing it a few times causes a larger change. Make sense?

Hmmm.....I think I understand what you trying to explain. The resolution from 16 bit is so high it has very little effect when changing value by just only one very small increment at a time(1 out of 65536 steps per key stroke) on the small value in the table (like max knock retard)......

In a nutshell, how could I go about and tweak the F9 screen that you explain? Just hit the F9 button??

Epifan: I found one strange thing yesterday while trying to tune my friend car. I open his rom and was able to change the values on those said tables. But I couldn't change mine when I opened my rom at the same sessin????? Why?????

My observation is I have been using my ROM image for a long time and there may be some errornous descriptions inhibited in my ROM that carried over from previous generation. Is this possible?? and most importantly, How can I correct it????



Where is the description in the EcUEdit that you need me to send to you?

Sorry that I sound like computer idiot. I know very well about tuning but less about computer programming. Sorry

Press F9 when you have a map selected. It shows you what is in the XML, but in an easier to use editor.

About 3/4 down there are two radio buttons, one for "Value In" and one for "Data Increment". Value Inc notches the raw value in the ECU by the finest possible increment allowed by the precision of that particular map. You can move the radio button to Data Increment and just to the right of that type in how much you want the + button to do in the Increment.

tinywrex wrote:Epifan once again thanks for one great application!

Thanks

tinywrex wrote:i have encountered an issue with the read/flash...the kernel files referenced in the FLASH.XML are missing from the installation!

kernels link
Extract it to ecuEdit\kernels folder

Freon wrote:Press F9 when you have a map selected. It shows you what is in the XML, but in an easier to use editor.

About 3/4 down there are two radio buttons, one for "Value In" and one for "Data Increment". Value Inc notches the raw value in the ECU by the finest possible increment allowed by the precision of that particular map. You can move the radio button to Data Increment and just to the right of that type in how much you want the + button to do in the Increment.

^^^^^^^^^
I did it and the problem solved

Thank you Freon

Trigger issue fixed version here