[Flightgear-devel] External sim hardware to properties a policy or guide line,

[Harry C. <har...@gm...>]

Some years ago i wrote my own driver that interfaces my sim hardware (a
network of Microchip pics) to FG. It reads incoming messages and writes the
values direct to the tree.

However, Nasal scripts controlling properties are becoming ever more
prevelant in FG. There can be a fight going on in software 10 times a second
as to a particular switch being on or off. Either the Nasal does not work or
the physical switch does not work!

So for those of us who build sims, no one solution or custom IO module suits
all, (but if any one wants to copy my picF18 can bus setup they are most
welcome, just mail me)

Is there a guide line for this kind of interfacing?

If not and assuming nasal is the way to go,  I would propose we specify a
dedicated sub branch and format on the propriety tree where sim hardware
values can be written. That branch would only occur when such a driver is in
use.

Then those who need too, can modify model and system nasal scripts
accordingly, 2 people can have 2 different sim set ups with different
interface drivers, But the tweaks we would make to Nasal would in fact be
the same because we would both present our sim hardware settings to the same
properties tree branch.




Comments, been done before or other options to consider?








-- 
Regards Harry