bugCERTI - Bugs: bug #24736, XPlane plug-in should use a...

 
 

bug #24736: XPlane plug-in should use a standard FOM

Submitter:  Petr Gotthard <gotthardp>
Submitted:  Mon 03 Nov 2008 12:13:31 PM UTC
   
 
Category:  XPlaneHLA_Plugin Severity:  * 3 - Normal
Item Group:  Feature request Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Release:  * CVS
Reproducibility:  Every Time Fixed Release:  * NextRelease
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 06 Nov 2008 02:55:15 PM UTC, comment #3: 

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.




Eric NOULARD <erk>
Group administrator
Mon 03 Nov 2008 01:21:45 PM UTC, comment #2: 

Thanks, Eric. I'll stay tuned then. :-)

Petr Gotthard <gotthardp>
Group Member
Mon 03 Nov 2008 01:14:14 PM UTC, comment #1: 

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.

Eric NOULARD <erk>
Group administrator
Mon 03 Nov 2008 12:13:31 PM UTC, original submission:  

I propose the XPlane plug-in should use a standartized FOM. The AviationSimNet seems to be very close to what you have already implemented. What do you think?

Attached patch is 50% of required effort. As a next step, the right types/endianess need to be used.

Petr Gotthard <gotthardp>
Group Member

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #16781:  ASN.diff added by gotthardp (5KiB - text/x-patch - Proposed change.)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by erk (Posted a comment)
  • -email is unavailable- added by gotthardp (Submitted the item)
  •  

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-11-03 gotthardp Attached File- Added ASN.diff, #16781

    Back to the top

    Powered by Savane 3.13-b921.
    Corresponding source code