Hi guys,
I'm still trying to improve my knowledge on MLV.
Anyone knows the meaning of Flags 0 to 5 values?
Regards
Hi guys,
I'm still trying to improve my knowledge on MLV.
Anyone knows the meaning of Flags 0 to 5 values?
Regards
Last edited by osvaldo; 09-10-2019 at 05:51 AM.
😍😁
I'm upset John answered before I could. I was going to say the same.
So... same answerI'm upset John answered before I could. I was going to say the same.
😍😁
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.
Last edited by ReadyXB; 09-10-2019 at 05:38 PM.
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.
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.
So, after 8 year just reading this forum, and wanting now to fully understand ECM stuff I decided to get in and post somewhat.
During this years I have seen a few guys with a lot of this knowledge, a few more willing to do what I'm doing, and among all the other, as anywhere, a few of unpleasant people.
Definitely, I think I am in the right place and as far as some 'ECM' guys are still here I will still post.
This not to say I am not interested in the rest of my Bike, but in this case I will have probably much more answers than questions
My regards
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?
I have a currently unmanageable amount of logs, spreadsheets, notes, emails, etc. growing over time for ddfi. My gifting is not in making nice presentations of said data, which ecmspy.com has done very nicely.
Hi Ready,
I like a lot your way to answer, much, much more helpful than other; thank you.
I did not know at all this way; it look a bit overwhelming, but I will do my best to get out infos.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.
BUE2D-V5.jpg
Yes, off course, and excuse me to have not been clearer.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?
It can be just because I'm not able to understand it, but if I look at this and the others:
Flags.jpg
I'm not able to correlate them with what is changing in engine management when the showed below flags values change.
MLV.jpg
That was the meaning of my original question.
Honestly there are more values, let say 30% of the total, that are not yet fully clear to me, but I thought flags were enough for the moment.
It must be very clear that everybody that can't or don't want take care of what I often talk about, have my full respect.
Off course as far as they do not send unmotivated unpleasant answers.
Thanks again
Osvaldo
Last edited by osvaldo; 09-12-2019 at 07:21 AM.
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.
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.