Thanks to all the devs and contributors here! I have been having a blast flying the improved Bonanza.
Thanks for the file ; however there is a sentence I donāt understand (Iām neither a pilot or a native english speaker) :
Then lean mixture until you are 70 degrees LOP if below 6,000. If at 7,000 to 9,000 you will want to be about 40 degrees LOP
I donāt get ā70 degrees LOPā / ā40 degrees LOPā : I expected to read ā70 degrees over temperature at LOPā or ā70 degrees under temperature at LOPā ; does it mean either, or is it something else altogether ? ![]()
Btw thanks to everyone involved in the mod, please keep up this great work !
LOP stands for lean of peak. Peak is the hottest temperature you can get from the engine. Lean of peak means that you are running the engine at lower fuel mixture than the peak temperature.
Usually it goes the following: move the mixture and watch the EGT rise. if it caps at a certain temp and then starts to fall again, you found your PEAK. Then you just pull a bit more mixture until EGT shows 70° or 40° below the peak.
Now you have a perfectly leaned engine.
I get it now, thanks !
Will stop by the hangar today and can get some photos / video. Anything else you can think of?
That would be great! From the top of my head:
Engine off, buses tied:
- only BAT1 on
- BAT2 on, then BAT1 off
- BAT1 + 2 on, then ALT1 + ALT2 on (is there an actual ALT1 load indicated at this point, since the alternators are not active with the engine turned off, the current is drawn from the battery? This is potentially wrong in the sim?)
Engine on, buses tied (do not suppose you can easily do this without actually going for a flight)
- ALT1 on, ALT2 off (should make no difference at all?)
- ALT1 off, ALT2 on (Bus volt back to battery voltage indication?)
And finally engine on, buses untied (ALT2 active).
For current draw per active circuit, I think itās best to get my hands on a maintenance manual. But if you can identify clear errors (e.g. load while engaging starter way too high/low) I can make an arbitrary adjustment.
Thanks again! Donāt suppose you can do all these 
know of any good tutorials on systems for this game (i guess old fsx ones too). I wanna redo the DA40 systems, as its also wrong.
Made some small engine and flight model changes which are on my fork of the dev-version, if anybody wants to test them. A few observations:
-
Using auto mixture is useful for climb testing, but I have confirmed that it flows about 5% more fuel and puts out about 3% more power than is possible with manual mixture, even when you use the āset best mixtureā hotkey. So if the plane climbs a bit too well with AM on I think thatās fine; most of us wonāt be using it for actual flying.
-
Additional changes may be necessary to get both ROP and LOP operation accurate. Itās also possible that the engine modeling simply wonāt allow us to get both just right. As @Matchrocket has obvserved, LOP operations are basically right on for TAS but use a bit too much gas. In my tests today using ROP, fuel consumption was about 95-96% of book, while TAS was about 98%. So using the basic scalars to fix one will hurt the other; no immediate solution jumps out at me but maybe we can work on it? Itās really close though and I donāt know if we want to make ourselves crazy over it.

-
Iāve got low altitude speeds nearly correct, I think. A couple things help bring speed under control at 2,000ft: setting mixture to 100% (best mixture is about 90% in the sim, so this costs a few knots) and opening the cowl flaps (slows you about 5 knots).
-
I ran out of time to fly approaches today so Iāll do that tomorrow, I think the flap drag is about right now.
Side question: will an EGT be coming to the Bonanza via this project or via the Working Title G1000?
@FrettFS, I wasnāt able to pull the plane out and start the engine, but hope to have a trip here soon where I can do some more with then engine running (current draw, etc). So maybe not too useful, but can get some more data if you need. The only Bonanzas I have access to all have the NXi version of the G1000. In case you notice any minor display differences. Numbers are below.
Video 1: https://youtu.be/NHZ1UEnVTEU (sorry for the odd angle, lighting was bad)
Video 2: https://youtu.be/1gE9EYOr9j0
Both BAT 1&2 ON
Bus 1: 24.6
Bus 2: 23.8
BAT1 only
Bus 1: 24.3
Bus 2: 22.5
(Bus 2 typically 1.5v less than when both batteries on)
BAT2 only
Bus 1: 0.0
Bus 2: 23.8
(Bus 1 zero even with though buses are tied - diode prevents bus 2 from powering bus 1)
Turning on the alternator switches will cause about a .5v drop
Thanks a lot!
Important thing I noticed: on BAT1 the PFD turns on in reversionary mode, whereas it is connected to BUS2. I assume due to the bus tie. This means I will have to connect the PFD to bus 1 to work around the problem of not having an actual bus tieā¦
Some work to be done. I didnāt realize voltage would drop when the alternators are turned on. I donāt think I will be able to model it all correctly, but I will see what I can do and keep this as a reference (for when someone joins in who can do a better job than me).
Itās cool that youāre going to this much effort on the buses and the voltage, but I think itās something that most people wonāt even notice, other than a real G36 owner. You sir are dedicated.
Itās not for them, itās for the people who would notice and care.

yupā¦not complaining, just saying that close enough might be good enough is all. Like I said. Amazing dedication.
Partially agree. In the new checklists there are some indications that need to be checked. With the basic implementation in the current dev-version you can do these checks.
Other than that I have to agree, but there will always be people who enjoy the attention to detail. And then I, and I assume also the other contributors, just like to work on little things like this because it is rewarding and educational.
Oh yeah, I totally understand. Iām not above getting knee deep in stuff, that when I take a step back, ask myself what was I thinkingā¦LOL.
After the bus and voltage stuff, what do you think youāll look at next?
Thanks for the amazing work. Actully just flying the Bonanza and found a bug, when pressing hdg to sync it syncs to a course 45° west of my current course. Could as well be a hickup in the garmin modā¦
Sure, no problem!
Actually, Reversionary mode was active because the avionics master was off. So, turning the avionics master switch on will allow power to the avionics bus (part of bus 2) and bring up the MFD. And once you hit ENT on the MFD, it will exit reversionary mode.
Little tidbit of unique, āin the weedsā systems knowledge, you could also pull the Avionics circuit breaker out and it would actually turn the avionics master on. This is a failsafe for the switch (it is powered off, and de-powered on).
But I think like you eluded to, with Bat 1 on, Bat 2 off, and Avionics master on, the avionics would still be powered even though they are on bus 2 (due to the bus tie).
Yeah, probably not a big deal if that isnāt modeled. There are some shunts / resistors, and diodes and current limiters throughout the system that rob a volt or two here and there. For a small airplane, it has a pretty solid design. If you really want to see a cool electrical system, the King Air 350 has what is called a Triple Fed Bus. Pretty smart system. Maybe you can tweak that one next! ![]()
One thing I donāt think I mentioned, in the G1000/GFC700 combo I fly, there is also a YD (yaw damper) function to the autopilot. This is standard. There are multiple planes with this issue though and it may be better fixed by the G1000 working title folks. (DA62 / C208 / G58 as well)

edit: this isnāt the one I fly, this is a 2013 model. They both have YD function in the same place, and it looks exactly the same though (except it has a nicer environmental - air conditioner - system)
Yaw damper is disabled on all planes I believe. Functionaly , I am not sure its working in the core game currently.
YD seems to work ok (or at least display) on the king air 350. Its disabled incorrectly on the DA62 / C208 / G58 as well as the G36. It is pretty important, and the G1000 panel is labelled incorrectly in its absence.
