Wiki source code of ERAS C3
Version 2.1 by Barry Bishop on 2015/11/15 12:31
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | **Description:** Command & Control software project for data processing in the field | ||
2 | **PI:** Franco Carbonari | ||
3 | **Organization:** Mars Society, IT | ||
4 | |||
5 | === Summary === | ||
6 | |||
7 | Within the European MaRs Analog Station for Advanced Technologies Integration Project (ERAS), a Command, Control and Communication (C3) subsystem will provide the data processing and communications equipment required to: | ||
8 | |||
9 | * monitor and control the habitat’s environment and subsystems | ||
10 | * monitor and maintain crew health and safety | ||
11 | * communicate with mission support, rovers and EVA crewmembers | ||
12 | * support data processing related to the mission objectives | ||
13 | * host the core part of the crew operations planning and scheduling support system (Crew Mission Assistant, CMA) | ||
14 | |||
15 | For the MARS2013 tests a C3 simulation will be running on top of the TANGO Distributed Control Software Framework. | ||
16 | During the proposed experiment the remote communication with the Aouda.X on-board computer (in particular all main biomedical and engineering telemetry) and the interfacing to the CMA will be tested. | ||
17 | |||
18 | === Objectives === | ||
19 | |||
20 | Location transparency: a location (naming) service should allow to locate a service over the network by name and/or required functionality. | ||
21 | Message delivery and format integrity: the system must warranty that messages are not lost or duplicated and that they are delivered uncorrupted. | ||
22 | Dynamic invocation of server processes: the client shall not be responsible for starting up the services it needs, but the system shall be able to do it transparently | ||
23 | Load balancing: if needed, the system shall be able to redistribute the services to allow load balancing over the distributed servers | ||
24 | Security: if needed, the system must be able to handle security of communication using appropriate secure protocols. | ||
25 | |||
26 | === Experiment Data === | ||
27 | |||
28 | |=Directories/files|=Description | ||
29 | |[[ERAS-C3>>url:https://mission.oewf.org/archive/downloads/2/03-ERAS-C3/]]| <none> |