I have just checked-in the new XPlane_HLAPlugin.

You may browse the to-be-improved installation doc
http://cvs.savannah.gnu.org/viewvc/*checkout*/applications/XPlaneHLAPlugin/XPlane_Doc/XPlaneHLAPlugin.chm?root=certi

I do not have time [yet] to test it with aviationsimnet FOM.
But if you want to give it a try you'll have to
edit the

initFile/XPlaneOut.txt
initFile/XPlaneCmd.txt

files in order to replace XPlane.fed with aviationsimnet...

and
initFile/initXPlane.txt
initFile/initPhyDget.txt
with appropriate values in order
to map updated FOM name to XPlane names.

XPlaneOut.txt / initXPlane.txt is for getting information
FROM XPlane

whereas

XPlaneCmd.txt / initPhyDget.txt is for command to XPlane.

The initPhyDget.txt is ill-named but it comes from the fact
that we did use Phidgets (www.phidgets.com) as a way
to enter command into XPlane.

This is a "toy" but easy to do experiment where we have:

- 1 federate XPlaneOut (observation publisher of XPlane data)
- 1 federate XPlaneCde (sending command to XPlane comming from an HLA subscription)
- 1 federate XPlanePhiDget (bound to phidget sensor publishing command to HLA)

- 1 purely observer federate XPlaneTrace

XPlaneCde and XPlanePhiDget are optional.

Hi Petr,

I agree with that.
We have a new version (not released yet)
of the XPlaneHLAPlugin which includes many changes.

I'll try to make it work with AviationSimNet.
In fact the next release should work with almost
any FOM since we use a text configuration file
for the plugin which is used to
map XPlane object names
onto HLA object classname/attributes.