63
edits
Stand Alone ATC Control Development: Difference between revisions
Jump to navigation
Jump to search
Stand Alone ATC Control Development (view source)
Revision as of 10:26, 22 September 2010
, 22 September 2010no edit summary
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
=Other features and ideas = | =Other features and ideas = | ||
* [[FGCom]] integration | * [[FGCom]] integration | ||
==Beginning of an idea from zakharov== | |||
A project has been started some years ago, named [http://seb.marque.free.fr/fichiers/scripts/perl/auto-atc/ AutoATC]. Indeed it is in a really alpha 0.0.0.1 version :-D. | |||
Here are the great lines: the idea was/is to create an lightweight application which fakes its position on Multiplayer Network. This would allow the application to receive/send messages to others connected players, as well knowing their position/bearing/speed/xpdr. | |||
The automated ATC would manage all airports in its area, should have defaults configuration for quite all airports, and can be configured for some specifics airports using XML. | |||
The imagined protocol is this one: | |||
# the player send a specific formated message over the multiplayer network (nasal or xml should format the message): it contains multiplayer's callsign and her/his intentions. | |||
# the automated ATC grab the message, create an internal instance for this player and gives her/him a transponder code to use | |||
# both communicate in a formatted protocol. | |||
The appli was initially written in [http://www.perl.org/ Perl]. Each instance of a multiplayer was a hash table entry (using callsign/transponder couple for authentification), each runway of all managed airports should be hash instances containing the sorted list of users queriing on it. AutoATC could determine a way to enter the final approach of a runway, take care of other players queriing approach or departure, asking them for enter in a waiting-circuit, manage emergencies, etc. | |||
In the case of multiplayer do not follow instructions for any reason for, say, 10 consecutives times, or just asks to leave the system, her/his instance and all her/his queries are wiped. | |||
Why the project has stopped? Because I was unable to send a correctly formatted UDP packet: the position message is different from C++... this was until I discover [http://www.swig.org/ swig] ([http://pigeond.net/git/?p=flightgear/fgmap.git;a=blob;f=sg_perl/README which is used on FGMap]). Swig can be the solution to allow a revival of autoATC, which is next on my TODO list. | |||
=Customizing [[Atlas]] for use as an ATC client = | =Customizing [[Atlas]] for use as an ATC client = | ||