Menu

Control Software Requirements

The design implied by the diagram shown on the Overview page indicates specific requirements for the PI written software.

Command/Control Software (on the ground)

  • Must send its commands via UDP datagrams
  • Must allow the operator to change the host (IP) and UDP socket to which those datagrams are sent
  • Must receive instrument status via UDP datagrams
  • Must allow the operator to change the host (IP) and UDP socket on which those datagrams are received

The control software running from the ground, needs the following:

UDP_IP = 127.0.0.1

with UDP_SEND_PORT and UDP_READ_PORT to be defined as given in the UDP-Data list (internal access only). For example, for the GNI instrument:

AWAS:
UDP_SEND_PORT = 32103
UDP_READ_PORT = 32102

Instrument Software (on the aircraft)

  • Must receive its commands via UDP datagrams
  • Must allow the operator to change the host (IP) and UDP socket on which those datagrams are received
  • Must generate either a status datagram or data datagram which will allow the ground operator to observe affect of command
    • Status datagrams will be forwarded to the command/control software running on the ground
    • Data datagrams will be pulled in by the RAF Aircraft Data System and made available through that system
    • Instrument PIs are encouraged to send both types of datagrams
  • Must allow the operator to change the host (IP) and UDP socket to which status and/or data datagrams are sent

For instruments mounted on the aircraft, the instrument software needs to write to: UDP_IP = 192.168.84.2

AWAS:
UDP_SEND_PORT = 32102
UDP_READ_PORT = 32103
UDP_NIDAS_PORT = 30131

Ports are also listed in the UDP-Data list (internal access only).