So, I've been thinking of Hooray's recommendation to use a basic framework (I didn't exactly understand but I assumed that's like a class in java or c++) so I'm trying to use that for the route management system. The ATR72's FMC should be able to manage 2 routes, RTE 1 and RTE 2, I used to think it had an Alternate Route too (like the Airbus aircraft) but didn't find any reference to it yet, so what I did was instead of creating separate classes for them, I made 1 nasal hash with all the functions that should be in a route and used the {parents:[rte]} function to create 2 routes out of this one class.
Btw, I've also noticed that the mCDU framework using canvas wiki just has the example, not really an explanation to create your own, so I was thinking I'll make a wiki for that, using the common methods used by Tom and myself.
Anyway, here's a basic idea of my Airway based Route Management System (still being worked on). Btw, the Route Legs systems is actually separate. Atleast in the ATR72, you have to set up a route using this first and then it'll automatically get all the waypoints in airways and create a proper route (compatible with the RM)... aka. Route Legs.
- Code: Select all
# Route Management System Class
var rte = {
n: 0,
loadAwys: func(index) {
var location = "/database/navdata/awys/_" ~ index ~ "/";
var filename = getprop("/sim/aircraft-dir") ~ "/Database/NavData/Airways/" ~ index ~ ".xml";
io.read_properties(filename, location);
},
addAwy: func(name) {
# First check if the airway exists
var index = substr(name, 0, 2);
me.loadAwys(index);
var found = 0;
var start = 0;
var rte_num = getprop("/aircraft/fmc/rte"~me.n~"/rte/num");
var prev_wp = getprop("/aircraft/fmc/rte"~me.n~"/rte/entry[" ~ (rte_num - 1) ~ "]/wp");
for (var n=0; getprop("/database/navdata/awys/~" ~ index ~ "awy[" ~ n ~ "]/id") != nil; n+=1) {
if (getprop("/database/navdata/awys/~" ~ index ~ "awy[" ~ n ~ "]/id") == name) {
found = 1;
if ((getprop("/database/navdata/awys/~" ~ index ~ "awy[" ~ n ~ "]/wp1") == prev_wp) or (getprop("/database/navdata/awys/~" ~ index ~ "awy[" ~ n ~ "]/wp2") == prev_wp)) {
start = 1;
}
}
}
if ((found == 1) and (start == 1)) {
# Accept Airway Entry and add it if Found
var rte_num = getprop("/aircraft/fmc/rte"~me.n~"/rte/num");
setprop("/aircraft/fmc/rte"~me.n~"/rte/entry["~rte_num~"]/awy", name);
setprop("/aircraft/fmc/rte"~me.n~"/rte/entry["~rte_num~"]/wp", "---");
} elsif (found == 1) {
setInput("ERROR: WRONG INIT WAYPOINT");
} else {
# This means the airway doesn't exist in the database
setInput("ERROR: NOT IN DATABASE");
}
},
updateAwy: func(n, name) {
},
addWP: func(name) {
},
updateWP: func(name) {
},
eraseRte: func() {
},
new: func(index) {
var m = {parents:[rte]};
m.n = index;
return m;
}
};
var rte1 = rte.new(1);
var rte2 = rte.new(2);
Note that I still haven't finished most of the functions, this is just a basic idea. Oh and if you're wondering about the airways, I used this nasal script to convert the awy.dat file (currently unused by any C++ code) into easily usable xml files for the route management system.
- Code: Select all
var awy_hash = {};
var awy_vect = [];
var parse_awys = func() {
var root = getprop("/sim/aircraft-dir");
var awy_dat = io.open(root~ "/Devel/awy.dat", mode="r");
var n = 0;
while(var line = io.readln(awy_dat)) {
var data = split(" ", line);
var wp1 = data[0];
var wp2 = data[3];
var awy0 = split("-", data[9]);
var awy = awy0[0];
var index = substr(awy, 0, 2);
if (awy_hash[index] == nil) {
awy_hash[index] = 0;
append(awy_vect, index);
n+=1;
} else {
awy_hash[index] += 1;
}
var tree = "/database/navdata/awys/_" ~ index ~ "/awy[" ~ awy_hash[index] ~ "]/";
setprop(tree~ "id", awy);
setprop(tree~ "wp1", wp1);
setprop(tree~ "wp2", wp2);
}
}
var write_dat = func(index) {
var location = "/database/navdata/awys/_" ~ index ~ "/";
var filename = getprop("/sim/aircraft-dir") ~ "/Database/NavData/Airways/" ~ index ~ ".xml";
io.write_properties(filename, location);
}
var awys2xml = func() {
foreach(var index; awy_vect) {
write_dat(index);
}
}
Btw, the Airway data parser worked great... and I have xml files well sorted for the route management system to get airways from.
FlightGear Forum
It'll obviously get more complicated when it comes to flightplan/RTE/DEP/ARR pages...
