Developing ARGOS support in AOS

Questions for the development of ARGOS interface

Starting in October 2013 the AOS is being modified to support communication with ARGOS.

ARGOS compatible AOS will have versions number starting at 12.0

General Architecture

The previous AOS main loop was structured as follows:

  • External loop:
    • Initialize and start AOSaoApp (The interface application for FLAO)
    • wait for communication with FLAO established
    • Internal loop (~ 0.5 Hz):
      • IF communication with FLAO closed or terminate signal: EXIT internal loop
    • IF terminate signal: EXIT external loop

Here the AOSAoApp interface application is "blocking" and terminates only when the communication with FLAO is closed. Then the external loop code creates a new AOSAoApp to wait for the re-establishment of communication.

Starting with version 12.0 the AOS was reorganized as follows:

  • Initialize FLAOifApp (FLAO interface application)
  • External loop (~ 2 Hz):
    • check FLAOifApp status
    • IF terminate signal: EXIT external loop

In summary: the FLAOifApp interface application is no longer "blocking" and provides a method to check its current status. The management of connection/disconnection with the server is managed internally.

With the above modification, it is possible to add the support for the connection with the ARGOS server, as follows:

  • Initialize FLAOifApp (FLAO interface application)
  • Initialize ARGOSifApp (ARGOS interface application)
  • External loop (~ 2 Hz):
    • check FLAOifApp status
    • check ARGOSifApp status
    • IF terminate signal: EXIT external loop

Details of interface applications

The interface applications FLAOifApp and ARGOSifApp ....
Topic revision: r2 - 21 Nov 2013, LucaFini
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback