vnNVUautoload: "Virtual Navigator": Autoload next flight plan leg to the...

In thlytras/rfgfs: Flight planner and companion package for FlightGear

Description

Through the FlightGear props (telnet) interface and on the Tu-154B, this function monitors the NVU and with every waypoint change, it loads the next flight plan leg to the inactive NVU device.

Usage

vnNVUautoload(con, plan, leg, init = FALSE, poll = 10, cols = c("fix",
  "ZPY", "S"))

Arguments

con	A socket connection object created with fgfsConnect
plan	A flight plan, as a data.frame. Plans created with planRoute are accepted as input. At a minimum, the data frame.should have three columns: waypoint names, orthodromic course headings (ZPY) and leg distances (S).
leg	The current leg of the flight plan. Specified as waypoint name.
init	If TRUE, also tune the active NVU device to the start of the current leg. You will only want to use this on the ground, before you takeoff.
poll	Time (in seconds) between successive checks of whether a waypoint change happened. In between, the function Sys.sleeps to conserve CPU cycles.
cols	An optional vector of column names, if these are named differently in plan

Details

This function loads each leg of your journey to the NVU, as your navigator would do, so you can focus on other things. It stops if there's no other leg to be loaded, or if you press Ctrl-C. For example you can stop it to correct your position with vnCorrNVU_VOR, and then run it again from the current leg.

Value

None

thlytras/rfgfs documentation built on May 31, 2019, 10:44 a.m.