auto-tune

[secco]

Hi Phil
i use the LC1 and if the LED blinks the contoller has a failure.
i found that fault with your MLV. Log4 the failure is between 1182s and 1399s
in log 3 between 701s and 731s and to 761 another problem occues.
the controller shows afr 10 and i cant belive this value.
If i stop the engine and start again it works good!!
the failure comes out of the Lamda controller and i have no idea how to solve this problem.
normally we must connect the led with our laptop so we can filter itt

In MLV i use following Filter AFR < 11 II AFR > 16.5 II PW<1 II TPS<2 this works not so bad
i hope you recive my attachments. if not i send you a email
you have a idea to get my idle rpm smother?

ciao Frank

[LT401Vette]

I am a little unclear of your request. I see where your lambda controller failure is occuring and that filter you are using looks like it would filter those sections out , it is probably filtering more than you need to. But are you requesting MLV to filter those automatically?

My first guess on the lambda failures would be proper grounds.

[secco]

Hi,
this was no question. i could not imagine how you filter those problems in your AUTO-TUNE funktion.
if it is not filtert the VE-tabele went totally wrong. in a bad case the engine get destroyed.

thx
Frank

[LT401Vette]

Ah. I get you now... Yes for live VE Analyze I think you would want a few more stop gaps and safety measures.
Limits to the amount a cell can be changed before the user must approve.
It would probably be good to filter all records with AFR readings near the limits.

[gurov]

with LC1 (using the lm programmer) you can tell it to output a certain voltage if there is an error condition, as well as a voltage when the sensor is warming up.

[ausloki]

And of course with something like this live analysis built into TS we are no longer limited by 8x8 maps` for our afr.

bring it on, i've been willing to start donating funds for what you have already done as long as i get the upgrades when they are available.
This way it helps you out and maybe you don't have to spend as much time at the other job

[65looter]

Phil,

Will the "live VE Analyze" feature act like a self-tune? The kind of feature you find on other after-market EFI system.

[LT401Vette]

It is similar to the VE Analyze in MegaLogViewer but runs real-time instead of on historical data. What systems are you thinking of? Just to get an idea of what you have in mind and how they work?

[65looter]

Phil,

I'm thinking of the FAST™ EZ-EFI™ Self Tuning Fuel Injection for example
http://www.fuelairspark.com/WhatsNew/Fi ... lebody.pdf

Many of the new EFI kits are focusing on this "self-tune" feature.
If seems to be a selling point.

[Matt Cramer]

I really don't envy the EZ-EFI user who ends up with unexpected noise in his sensor readings and can't connect any real tuning tools to it...

[PSIG]

Ah. I get you now... Yes for live VE Analyze I think you would want a few more stop gaps and safety measures.
Limits to the amount a cell can be changed before the user must approve.
It would probably be good to filter all records with AFR readings near the limits.

Absolutely, Phil. Example is a few rich misfires and your sensor goes lean. Other limits would be good. Speaking of that - can MLS/TS come with reasonable pre-defined field limits so data output is relative on any log - i.e., preset TPadc at 0-255 so it's obvious that your throttle is at X position even if the log has no higher/lower values to compare against? I'm trying to get traces that are relative so I don't have to constantly read the little numbers, especially from others. I can do this myself in my configuration, but to have the basic ones pre-set would be a real time saver as I move from laptop to laptop and between mine and others I'm helping. Screen shots on the forums would also be more consistent and relative and a big help to others assisting. Whatcha think?

To others - I can tell you from watching Phil over the years, he is not a ripoff artist. Whatever the charge is, it will be fair, or worse - it will be too low to allow him to afford the time and effort to bring these goodies to you. Consider, you can learn all the skills of tuning and use the cheap or free programs and a lot of time to do it, or if you don't/can't lean the skills you can bang your head against the wall long enough you pay someone else BIG money to tune or dyno your setup and walk away with nothing in your hands but a hopefully good tune and no reasonable way to modify it, or you can pay someone like Phil for his efforts to give you a cheaper and easier option. Just because your other options are either difficult or very expensive does not mean he will charge unfairly for it as others in the market often do. After all you've invested and desire for results, are you really going to cheap-out and be less than fair with the guy giving the easiest and most effective option? Please.

David

[65looter]

I don't think that anybody here doubt the skills of Phil.

[62f100]

i started alittle after tuner came out & couldnt under stand mega,so i loaded tuner & been happy with it eversince. when it out of beta or even if phil puts a prebuy option id pay now. ive got some friends to switch & they prefer tuner over others. id just like to say thankyou to phil for all his hard work.

[LT401Vette]

Thanks guys.

PSIG,

can MLS/TS come with reasonable pre-defined field limits so data output is relative on any log - i.e., preset TPadc at 0-255 so it's obvious that your throttle is at X position even if the log has no higher/lower values to compare against? I'm trying to get traces that are relative so I don't have to constantly read the little numbers, especially from others.

TS pretty well gets the limits from the ini file, but yes, MLV is almost entirely auto-scale. It would be nice to have more default limits, but it is difficult with many of them. Things like the tpADC in your example is 0-255 on an MS1, but 0-1023 in MS2...

What seems like it would make sense to do.. Is put the default limits in a separate file that is read on start up and just creates a default like I do for the HP and TQ fields. I did that there because spikes really mess up auto-scaling, but the same thing could be said for others. And it would likely be nice to have AFR read a more standard range so you know that 14.7:1 is always the middle line.. I'll look at doing this to the MLV 3.0 code, then we can sort through what fields make sense to have a preset limit.

[PSIG]

Thanks, Phil. Yeah, I thought it read the limits on all the variables so it would know that you were using MS1 or MS2 or at least the (example) tpADC would automatically set the range if optioned to do so. Since most codes of each family are similar in their data ranges, hopefully only 4 or 5 limit files would be necessary to handle most of them. Perhaps it could detect which limit file to load automatically? In any case, thanks for the thought.

David