osvaldo, much of what you ask is already conveniently documented:
http://ecmspy.com/cgi-bin/runtime.cgi
Also, if you haven't already, you should look over the Buell Tuning Guide and other info from Gunter Baumann/Nick Pashley.
I'm upset John answered before I could. I was going to say the same.
But it's much easier for him to just facebook questions on here one at a time, starting a whole new thread, over and over.
Why would he look up the directions when he can have us look up the answer and get spoon fed one at a time? It's much easier that way. For him anyway lol.
A different way for you to learn about the various config settings and live data is to look at the Tunerpro RT v5 .xdf and .adx files for Buell:Hi Ready,
thanks for the answer.
Before to post any question or observation here you can be sure I have done all of my best to find myself the answers on the net as well as here with search tool
Sorry, I don't quite follow the wording here. The same flags parameters that you can add to an MLV log view are shown on the ecmspy link I shared. Could you rephrase?I could not find what I was looking for, as you will not will find what is in this topic in the link you post that off course I know as well as the other stuff you mention and much much more.
s Cooter,
you are wrong.
A different way for you to learn about the various config settings and live data is to look at the Tunerpro RT v5 .xdf and .adx files for Buell:
http://tunerpro.net/downloadBinDefs.htm#Buell
Just open with a text editor. Within a short time you can become familiar with the file format and then see how the ECM settings/runtime data are broken down.
Sorry, I don't quite follow the wording here. The same flags parameters that you can add to an MLV log view are shown on the ecmspy link I shared. Could you rephrase?
That particular ADX file uses Linux end-of-line markers. Windows and Linux use different markers to indicate new lines (EOL). Windows = CR/LF, Linux = LF. Windows notepad doesn't properly interpret Linux EOL markers, so it just shows the text in one long string. Look for Notepad++; the formatting should be better.I did not know at all this way; it look a bit overwhelming, but I will do my best to get out infos.
Each flag holds eight different logic state settings in bitfields. If you try to examine an entire flag byte in MLV, it would be confusing.I'm not able to correlate them with what is changing in engine management when the showed below flags values change.
That particular ADX file uses Linux end-of-line markers. Windows and Linux use different markers to indicate new lines (EOL). Windows = CR/LF, Linux = LF. Windows notepad doesn't properly interpret Linux EOL markers, so it just shows the text in one long string. Look for Notepad++; the formatting should be better.
Each flag holds eight different logic state settings in bitfields. If you try to examine an entire flag byte in MLV, it would be confusing.
MLV supports creating custom fields from existing data fields. Do this for any flag bits you are interested in.
For example, I have a custom field called "ClosedLoopLearn" with formula "[Flags2]&16", another named "ClosedLoop" with formula "[Flags2]&128", etc. Then add them to your graph view.
I have a currently unmanageable amount of logs, spreadsheets, notes, emails, etc. growing over time for ddfi.