Baton free at KLAM

 

Text / Tracking

On 2/1/2019 at 12:03 AM, somiller said:

Baton is free at KHCS

I didn't post docs for two reasons:

1.) didn't have "flight tracking" enabled, so I got nothing I could link to for a post on the forum; 2.) see below

Flight Errors:
Date / Time(UTC);       Latitude;               Longitude;               Altitude;   GS;     ERROR / WARNING
2019-02-01 03:38:33; N35° 39' 13.584"; W079° 53' 42.616";    678.5;   146.8; (No Error) Aircraft flying state changed [ON GROUND: False, STALL: False, G-FORCE: 1.01, VS: 5.4]
2019-02-01 03:58:56; N33° 12' 43.627"; W080° 03' 03.406"; 16,955.4;   498.0; 90 Second Overspeed Limit Exceeded
2019-02-01 04:02:36; N32° 54' 36.097"; W080° 02' 45.115";     50.4;   109.0; (No Error) Aircraft flying state changed [ON GROUND: True, STALL: False, G-FORCE: 1.97, VS: -254.5]

Error is reported as a ground speed limit? Hardly seems a realistic metric, as GS has no direct effect on aircraft physics. I see in the log that airspeed hit M.842, and on a reflight it peaked at M.84 with no error, so maybe it's M# that's critical?

1. You dont NEED to have flight tracking to post an output, you will just need to upload the files somewhere yourself and link them unless avsim lets you upload files again? (but DO have it on for the race)

2. Your error isn't a ground speed limit its a SIM Overspeed limit.  Within flightsim there is an overspeed flag, a simple yes / no flag, when the red overspeed prompt appears on your sim (unless you have that turned off) the overspeed flag is tripped and Duenna starts recording it, once you have accumulated 90 seconds of overspeed (not all at once, its cumulative) it will throw an error, ground speed and mach are meaningless to the Duenna other than its monitored.  Do note however that the overspeed flag is tripped even if you have the notification on your sim turned off.

OK Quick test of old FSX installation.

I have the baton KLAM-KFMN in the A2A P-51H.

 

Text / Tracking

(And a second consecutive flight, this time around the circuit, was initiated by "RESETing" the Duenna and arming the Auto-Baton. The Duenna worked perfectly.)

 

Insomnia strikes again 😞 
A quick flight around the pattern at KTUL to give a test to the revised duenna then a leg of practice I never got to - KTUL to KASE to start last Saturday's practice.
Baton, if successful, will return to KFMN.
A follow up test to Mike's confirms the reset working properly - Thanks Eamonn! 👍👌 ( validation below )
I have the baton KTUL --> KASE in the non-whitelisted Shupe / SOH / Madison A-26C, FSRealWXPro

Text / Tracking

Well, that was a "waker upper" - need to sleep! Landed safely at KASE.
Baton is back at KFMN.


Text / Tracking

KASE 050828Z AUTO 00000KT 3/4SM -SN BR VV008 00/M01 A2968 RMK AO2 P0003 T00001006
LOC only - not DME equipped, a clock, altimeter and VSI were my best buddies.
A good thing a pack of Camels was onboard, needed a smoke after this.

First sign of the runway - quite a bit high, "Rocky Mountain High"..


Getting back in line..

12 hours ago, MM said:

(And a second consecutive flight, this time around the circuit, was initiated by "RESETing" the Duenna and arming the Auto-Baton. The Duenna worked perfectly.)

👍

5 hours ago, Eamonn Watson said:

👍

I can confirm that the reset worked for me too on the latest download.  I tested it last night.

I have the baton KFMN - KBCE in Alpha F-80C

Baton free at KBCE

 

Text / Tracking

Well wasn't that interesting...should've checked the weather at KBCE BEFORE selecting it as destination:

OC @ 500ft; 0.3SM in heavy snow

Does make for an interesting approach with no ILS.

Did a lap to test Duenna reset, and it worked perfectly.

I have the baton, KBCE --> KOTH in the Alpha P/F-80C, RealWXPro 

Baton free at KOTH, could've shortened up the approach a bit but down safe is #1.
Made it longer due to the initial metar & ceiling, ( KOTH 061256Z AUTO 13006KT 10SM OVC003 03/03 A3016 RMK AO2 RAB13E28 SLP212 P0000 T00280028 ) was much better than that when arrived - broken @ 003 Overcast @ 050. 

Text / Tracking