March 9, 20188 yr I read the other postings and since I have almost all the Alabeo and Carenado aircraft I figured I would look up one that uses the warning sound and how it is set up. I only tested this once at KFHR and was to excited to wait and post. IF I made a mistake I will repost with a fix. [gear_warning_system] THIS IS THE CHANGE I MADE TO THE SARATOGA AND SEEMS TO WORK gear_warning_available=1 //pct_throttle_limit=0.35 original pct_throttle_limit=0.15 //Percent throttle that activates warning flap_limit_power=41 //Flap angle that activates warning at idle flap_limit_idle=0 //Flap angle that activates warning at above idle reference used from alabeo M20 mooney //Percent... //Flap....and //Flap were written on the M20 mooney WHICH explains WHAT it does. The flap_limit power was one number past the last flap setting. I raised the landing gear with flaps at first setting and the warning came back on coming into KFHR. I put the landing gear down and it went off. When landed there was no warning again. I powered to idle on taxi and no warning sound. This is the Saratoga flap settings note: last setting is position 3 @ 40 so I put down 41. I will post the M20 mooney setttings so if you do not own it you can see it. [Flaps.0] type = 1 THIS IS TO THE SARATOGA span-outboard = 0.45 extending-time = 6 system_type = 0 flaps-position.0 = 0 flaps-position.1 = 10 flaps-position.2 = 25 flaps-position.3 = 40 damaging-speed = 115 blowout-speed = 120 lift_scalar = 1.0 drag_scalar = 1.0 pitch_scalar = 1.0 [Flaps.0] THIS IS TO THE ALABEO M20 MOONEY type=1 span-outboard=0.7 // Percent span for flap position extending-time=5 // Seconds, time to fully extend system_type=0 // 0 = electrical damaging-speed = 204 // KIAS blowout-speed = 209 // KIAS flaps-position.0= 0 flaps-position.1=10 flaps-position.2=33 [gear_warning_system] gear_warning_available=1 pct_throttle_limit=0.15 flap_limit_power= 34 flap_limit_idle= 0
March 9, 20188 yr Author pct_throttle_limit=0.15 //Percent throttle that activates warning I had change this from 0.35 I remember just to see IF it was the problem. This lowers the manifold pressure to 7.4 BEFORE the warning comes on. I set it back to the normal 0.35 which makes it 13.9 inches manifold pressure before the warning comes on. I believe in non turbo charged normal aspirated engines keeping the manifold at 15 inches on descent is about the lowest for cooling purposes etc... I tested with and without flaps and the warning comes on at 13.9 either way. If the flaps SHOULD be set FIRST before warning???? more tinkering needs to be done. Thanks and hope this makes it better. The phone company is putting optic lines in and keeps cutting my copper cable to the internet.
March 10, 20188 yr Author I was just flying the Carenado PA46 Malibu Mirage it is similar to the Saratoga I think they both have the Large Turbo Charged engine. It has the gear warning and the flaps are NOT part of the process. The warning comes on at 11.9 inches of manifold pressure when decending without gears extended. [gear_warning_system] gear_warning_available=1 pct_throttle_limit=0.25 flap_limit_power=13.22 flap_limit_idle=0.0 [Flaps.0] type=1 span-outboard=0.7 // Percent span for flap position extending-time=5 // Seconds, time to fully extend system_type=0 // 0 = electrical damaging-speed = 175 // KIAS blowout-speed = 195 // KIAS flaps-position.0= 0 flaps-position.1=10 flaps-position.2=20 flaps-position.3=36 flap limit position is 13.22 with the position 3 @ 36 degrees ??? So the thought of the M20 being 33 degrees with limit power at 34 must have NOTHING to do with being one number past 33 as a rule. Well anyway........the Saratoga I use the GNS430 GNS530 combo which I got the 430 sized just right in another listing on this forum. I have the GTN750 but am NOT like most people who SEEM to prefer it. Too much like flying a computer monitor. I was thinking as a humorous moment today about Alabeo, Carenado self fix program. I wonder if all this is on purpose cause they think we are having more fun fixing and tinkering with the airplanes then NOT needing to. I do like it a good fix when it works!! Edited March 10, 20188 yr by troybilt sentence did not complete
March 12, 20188 yr Author New observation is....tried some new settings and they worked perfect flying around KFHR yesterday. I would fly KFHR to KORS and then to S31 making takeoffs and landings frequent. All worked fine. Today is the next day after and I took off from KSBA to go to KMRY about an hour flight. DERN!!! today no go! Warning came on at 12.9 mp and DID NOT shutoff??? My new experimental settings that worked last night but DID NOT today are... [gear_warning_system] gear_warning_available=1 //pct_throttle_limit=0.35 original pct_throttle_limit=0.25 //Percent throttle that activates warning flap_limit_power=25 //Flap angle that activates warning at idle flap_limit_idle=0 //Flap angle that activates warning at above idle reference used from alabeo M20 mooney
March 12, 20188 yr Author This is 2 days after first post. Just back from V.A. oncology have a bit of a headache from Chemo but I went back to these settings which work perfect for me. At 13.9 inches manifold pressure the alarm comes on and shuts off with landing gear extended. The flaps seem to have no affect. [gear_warning_system] gear_warning_available=1 //pct_throttle_limit=0.35 original pct_throttle_limit=0.35 //Percent throttle that activates warning flap_limit_power=41 //Flap angle that activates warning at idle flap_limit_idle=0 //Flap angle that activates warning at above idle reference used from alabeo M20 mooney I am going to leave mine at this setting as it is GOOD ENOUGH. Also I think the original radio panel only worked with one radio on. Either 1 or 2 but not the 1/2 or 3 settings which allow com 1 to remain on while listening to ATIS. You can replace with any Alabeo or Carenado radio panel that works. Vcockpit03] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=513,513 texture=$Panel_3 //gauge00=Radio_PA32TC!RadioAudio, 0, 0, 512, 99 gauge00=Radio_PA31350!RadioAudio, 0, 0, 512, 99 ******sorry I do not remember WHICH aircraft this is gauge01=DIGTTRANS_PA32TC!transponder, 0,101, 512,130 gauge02=GAUGEPA32TC!Gauge_ENGINE_DIGVC, 0,232, 349,139 gauge03=GAUGEPA32TC!Gauge_Clock, 350,232, 160,162 gauge04=GAUGEPA32TC!Gauge_Anum_TOP, 0, 391, 512, 57 And a quick alter I did to install the GNS430 from reality WITH the GNS530. [Window Titles] Window00=GNS530 XP Window01=GNS430 XP Window02=Toggle_Control Window03=INFO Window04=ENGINE SETUP Window05=START [VIEWS] VIEW_FORWARD_DIR=10.000, 0.000, 0.000 VIEW_FORWARD_ZOOM=0.5000 //-------------------------------------------------------- [Window00] window_pos=0.739583,0.000000 window_size=0.260417,0.300000 visible=0 ident=15531 zorder=99 gauge00=rxpGNS!GNS530,0,0,100,100 //-------------------------------------------------------- [Window01] window_pos=0.739583,0.300000 window_size=0.260417,0.175000 visible=0 ident=15431 zorder=99 gauge00=rxpGNS!GNS430,0,0,100,100 //-------------------------------------------------------- ***************************************************************************and then skip down to the VC's [Vcockpit01] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=512,512 texture=$Panel_1 gauge00=rxpGNS!GNS530, 0, 0, 512, 372 gauge01=PA32TC!ToggleCAR530, 64,0, 256, 32 //-------------------------------------------------------- [Vcockpit02] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=512,512 texture=$Panel_2 gauge00=rxpGNS!GNS430, -10,-10,512,258 gauge01=PA32TC!ToggleCAR430, 0,0,512,30 gauge02=ALSound_PA32TC!CarSound, 0,0, 1, 1 gauge03=PA32TC!SYS_SMOKE, 0,0,1,1 //-------------------------------------------------------- Thanks hope this has been helpful. My intension is to reveal the makings of the WARNING SOUND so that anyone can see them to experiment on there own. Keith
November 30, 20187 yr Author Just found the real fix from another member which I will post here, IT WORKS!! Wing 32 Member Members 32 152 posts Donor Posted March 5, 2016 I figured out the cause of this particular problem. The issue is that the max gear extension speed is supposed to be 132 KIAS but Carenado has it set so that the nose gear will get damaged if you extend the gear at anything above 115 KIAS. Typical lack of quality control and unwillingness to fix bugs that we've come to expect from Carenado. Fortunately this particular issue can be fixed. Open the aircraft.cfg and find the [contact_points] section. There are three lines in that section that look like this: point.0 = 1, -2.2, 0.0, -2.9, 1500, 0, 0.6, 38, 0.20, 2.3, 0.5, 2.5, 3.5, 0, 135, 115 point.1 = 1, -10.5, -4.8, -2.9, 1500, 1, 0.8, 0, 0.20, 1.6, 0.5, 5.0, 7.0, 2, 195, 125 point.2 = 1, -10.5, 4.8, -2.9, 1500, 2, 0.8, 0, 0.20, 1.6, 0.5, 5.2, 7.2, 3, 155, 135 The first line is for the nose gear, the second for the left main, and the third for the right main. The last two numbers in each of the above lines specify the speed at which landing gear extension becomes inhibited, and the speed at which the landing gear accrues damage. As you can see, Carenado has this set so that the gear will become damaged at a slower speed than it becomes inhibited, which is backwards. To fix, I changed the gear inhibited setting to 135 (since the max extension speed is 132), and the damage speed to 155. I have no idea if these numbers are accurate, I just picked them because they seem reasonable based on the 132 KIAS max gear extension specification. After doing that the three lines look like this: point.0 = 1, -2.2, 0.0, -2.9, 1500, 0, 0.6, 38, 0.20, 2.3, 0.5, 2.5, 3.5, 0, 135, 155 point.1 = 1, -10.5, -4.8, -2.9, 1500, 1, 0.8, 0, 0.20, 1.6, 0.5, 5.0, 7.0, 2, 135, 155 point.2 = 1, -10.5, 4.8, -2.9, 1500, 2, 0.8, 0, 0.20, 1.6, 0.5, 5.2, 7.2, 3, 135, 155 After making these changes, as long as you extend the gear below 132 KIAS as specified you won't have the stuck gear warning siren or the lack of nose wheel steering after touching down.
December 1, 20187 yr Thank you for sharing this information! Cheers, Scott "...now let's get this thing on the hump - we've got some flyin' to do!" ~ Major Kong from "Dr. Stranglove" Scott Cebula
January 28, 20197 yr I did this also, but why doesn’t Carenado fix the problem. . That’s what bugs me. You shouldn’t have to search all over for a fix. It would be very easy for Carenado to fix.
Archived
This topic is now archived and is closed to further replies.