vnNVUloadNextLeg: "Virtual Navigator": Tune the Tu-154B NVU to the next leg of...
In thlytras/rfgfs: Flight planner and companion package for FlightGear
Description
Through the FlightGear props (telnet) interface, load the NVU parameters for the
next (i.e. upcoming) leg of a flight plan to the inactive NVU device of the Tu-154B.
Usage
1
vnNVUloadNextLeg(con, plan, leg, 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 next (i.e. upcoming) leg of the flight plan. Specified as waypoint name.
If ZPY and S for that leg are NA, nothing happens.
cols
An optional vector of column names, if these are named differently in plan
thlytras/rfgfs documentation built on May 31, 2019, 10:44 a.m.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Description
Through the FlightGear props (telnet) interface, load the NVU parameters for the next (i.e. upcoming) leg of a flight plan to the inactive NVU device of the Tu-154B.
Usage
1 | vnNVUloadNextLeg(con, plan, leg, cols = c("fix", "ZPY", "S"))
|
Arguments
con |
A socket connection object created with |
plan |
A flight plan, as a data.frame. Plans created with |
leg |
The next (i.e. upcoming) leg of the flight plan. Specified as waypoint name.
If ZPY and S for that leg are |
cols |
An optional vector of column names, if these are named differently in |
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Embedding an R snippet on your website
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.