Jcrotts wrote: ↑Wed Jan 20, 2021 2:55 pm
The way I tuned it with the carburetor was to put it in 4th gear at idle and let the clutch out , and add fuel until it didn't stall.
That is not best performance; that is enough power to not stall.
Conversely, adjusting fuel until rpm is maximum at a stable throttle setting and load (or other indicator, e.g., minimum/lowest MAP under the same conditions) would be best performance. At that point you would follow your plan and use the indicated Lambda/AFR for that AFR Table target cell. The AFR found best will change across the speed and load of the engine, and even more-so if you use advanced tuning for things like sufficient power while saving fuel at certain operational points.
Jcrotts wrote: ↑Wed Jan 20, 2021 2:55 pmAlso is autotune in tunerstudio any good? I have seen some people say it wasnt. If I can use it I'll just stick a plow behind the tractor, go through the field, and let it tune itself.
"Auto-tune" is VE Analyze, or VEAL for live (real-time). Yes, if operated properly, with all of the optional settings configured for your application. You tell it when, where, and how much to change the tune in options and filters, along with important settings like how much delay is on the WBO2 at different rpm, so you are correcting the
right table cells.
Also and at least initially, I suggest you do not allow live (real-time) corrections, as something like a rich misfire will read lean on O2, and auto-tune will
add fuel for the lean spot without asking, making it worse.
Many have wrecked their tune by 1) not saving the tune separately so you can go back to a known point with a click, and 2) letting the VE Analyze Live run wild without supervision. VEA is designed to
help you do the work, not do it all for you, and not without specific instructions (settings).
I have saved a
lot of extra work by just driving for a good log, then taking a few moments to review the VEA suggested changes before accepting them. Yes, TS stores tune changes in a special file folder, but it is much simpler to keep a "last-best" tune, updated with any improvements, as a fallback and the one you drive on. Tune with a copy, and if you get into trouble, just reload the old "last-best" tune and try again. If tuning is better, then save the copy as the new "last-best" tune. This way you can experiment with crazy ideas, or just see what some function does without losing your place, and enables a lot of tuning freedom.
I use TunerStudio for setup and adjustments, but the majority of tuning and analysis I use the much more powerful analytics of MegaLogViewer. This allows me to monitor running and change basic settings on TS, but analyze the live or log data on MLV, and make adjustments through either as-appropriate. It's also much safer to log and analyze, than try to follow what's happening while operating the engine or vehicle simultaneously. You will miss something, perhaps important. That's how I do it for easiest tuning diagnostics (what to change and why) and best and quickest results, but every tuner is different, and you should use whatever proven methods you can wrap your head around and that work for you.