Steam Gauge Overhaul

Are you using the default GNS 530? That GPS, enhanced by Working Title, should automatically generate the plan into the unit.

Thanks for the tip. All is well.
:)

@Black-Square
Thanks for the tips. I will check them out.

Thank you so much for another way of seeing these variables. As it turns out it is SPAD v9.15.54 that is not seeing the variable change.

Thanks again
m

Great! Glad to hear it! That file should be overwritten when you download Sim Update 15, but if you have any issues after that, just delete the file altogether. This will force the launcher to download a new version.

I've learned more about the temperature control system in specifically the Baron, and I need to improve it with an update. As it is, you shouldn't need to turn the heater on and off, though. The cabin heat pull-knob on the bottom left of the panel is used to control the admittance of heated air into the cabin. Here's the relevant section of the manual:

The cabin is heated via a combustion heater in the aircraft’s nose, and funneled to the cabin via
the “CABIN HEAT” pull knob under the pilot’s subpanel. The combustion heater is ignited with
the “HTR” switch, and will consume fuel from the left main tank only at a rate of about one-half
gallon per hour. The exchanged air can be very hot, so operators should take caution when
applying the cabin heat to reduce pilot workload during critical phases of flight, and also to limit
the possibility of a cabin fire. The rate of heating is controlled via the cabin vents and heater
blower, as with equalization and air conditioning.

Do not confuse "rate of heating/cooling" (rate of change) with the target temperature. Turn on the combustion heater to enable heating, and then pull the cabin heat pull-handle until the cabin is at your desired temperature. If it's too hot, push the knob back in.

The easiest solution is to look at the L:Vars "L:var_radio1Mode", and "L:var_radio2Mode"; however the meaning of those variables can change across my aircraft. I would recommend using the variables for each specific GPS (as I've been doing more myself, as my aircraft become more complicated). Those are...

WT GNS 530:
L:XMLVAR_GPS_DISABLED_AS530_1
L:XMLVAR_GPS_DISABLED_AS530_2

WT GNS 430:
L:XMLVAR_GPS_DISABLED_AS430_1
L:XMLVAR_GPS_DISABLED_AS430_2 (does not exist in any of my aircraft yet)

TDS GTNxi 750:
TDSGTNXI_Inactive750U1
TDSGTNXI_Inactive750U2 (does not exist in any of my aircraft yet)

TDS GTNxi 650:
TDSGTNXI_Inactive650U1
TDSGTNXI_Inactive650U2 (does not exist in any of my aircraft yet)

PMS50 GTN 750:
L:XMLVAR_GPS_DISABLED_GTN750_1
L:XMLVAR_GPS_DISABLED_GTN750_2 (does not exist in any of my aircraft yet)

PMS50 GTN 650:
L:XMLVAR_GPS_DISABLED_GTN650_1
L:XMLVAR_GPS_DISABLED_GTN650_2 (does not exist in any of my aircraft yet)

KLN90B:
L:KLN90B_Disabled

Oh and the Bonanza Overhaul addon or the Bonanza and Baron Bundle. 👍

@kityatyi, the MSFS/FSX/P3D version will be adequate to get you started. There is a 14 day free trial so you can try it out before spending the money for a license.

There is no built-in method to do this, but I can offer you an easy solution to implement in the code yourself. First, you must locate the appropriate behaviors XML file for the aircraft you're interested in, such as "AnalogBaron.XML". Search for for "Gma340Location" and "Kma24Location" within the file.

If you want the GMA340 to always be visible, and never show the KMA24, then replace the two blocks of code you found above with the following:

<Component ID="Gma340Location" Node="Gma340Location"> <UseTemplate Name="ASOBO_GT_Visibility_Code"> <VISIBILITY_CODE> 1 </VISIBILITY_CODE> </UseTemplate> </Component> <Component ID="Kma24Location" Node="Kma24Location"> <UseTemplate Name="ASOBO_GT_Visibility_Code"> <VISIBILITY_CODE> 0 </VISIBILITY_CODE> </UseTemplate> </Component>

That worked like a charm, thanks!

Oh, my bad, thought it was an error that had stayed over from my mapping effort. Probably decimals I sat while reading that tutorial, and forgot about it, as I never mapped that function to the Radio Control Panel. Thanks for the insight.

@meh195, knowing this is an older topic, were ever able to find this: [SWITCH_ENGINE (Device)] in spad? I am trying to get the avionics switch assigned to my Honeycomb Alpha and not having success so far.

Works perfectly in both the Baron and Bonanza. Did not touch the code I posted above.

I came to the conclusion I was advancing my throttle too fast. when I slowly advance it, the engine starts as it should

Did you make the change to the GNS530 javascript file that is described above? I did finally receive confirmation from Working Title that this will be fixed permanently in Sim Update 15. If you made that change, and you are still having difficulties, it's like the result of a GPS addon incompatibility or outdated file in your community folder. The good news is that JF tech support has not encountered any GPS or Autopilot issue in my aircraft that they have not been able to solve. The first step is usually just trying the aircraft with a completely clean community folder to rule out as many potential conflicts as possible.

As for the Go-Around button, it's up to Working Title to implement this correctly, and I do not believe that have yet. I will add this to my list for them to consider in a reply today.

Please let me know how this goes for you, because there is no reason that we cannot get you a perfectly functioning Baron and Bonanza to enjoy, asap.

@Black-Square said in Bonanza Autopilot - occasional issues:

Some of the switches will just "spam" their command 10 times per second, which tends to break things. It sounds like something similar was happening with the autopilot disconnect.

That certainly is the one and only thing I don’t care for about the otherwise excellent Honeycomb controllers. Perhaps at some point I’ll look into SPAD or FSUIPC to make my own filtering for those controls, but I’m not of a mind to tackle that task just yet.

The comments in the manual only speak to the virtual buttons inside the cockpit, not to physical hardware controls.

Oh! That’s a thought which had not occurred to me - I always assumed the manual was referring to sim control bindings, and hence hardware controllers. Now I’ll reread the manuals with a fresh insight.

Thanks again for describing your problem so thoroughly!

No problem at all! My biggest problem is usually going into too much detail, rather than the inverse. And thanks again for your help.

@RoughLandings said in Baron Engine Start:

Running them for 2-3 seconds

I don't know why but I always keep the pump(s) on for 5 sec and I never had an issue starting. I see that 2-3 is on the checklist so I will try that.