Wiki source code of ERAS C3
Last modified by Barry Bishop on 2016/10/09 15:35
- Manage
Copy- Actions
Export
Print Preview- Viewers
Source
Children
Content
Attachments (1)
Likes
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
3.1 | 1 | [[image:ERASC3.jpg||style="float: right;"]] |
| 2 | |||
| |
1.1 | 3 | **Description:** Command & Control software project for data processing in the field |
| 4 | **PI:** Franco Carbonari | ||
| 5 | **Organization:** Mars Society, IT | ||
| 6 | |||
| 7 | === Summary === | ||
| 8 | |||
| 9 | 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: | ||
| 10 | |||
| 11 | * monitor and control the habitat’s environment and subsystems | ||
| 12 | * monitor and maintain crew health and safety | ||
| 13 | * communicate with mission support, rovers and EVA crewmembers | ||
| 14 | * support data processing related to the mission objectives | ||
| 15 | * host the core part of the crew operations planning and scheduling support system (Crew Mission Assistant, CMA) | ||
| 16 | |||
| 17 | For the MARS2013 tests a C3 simulation will be running on top of the TANGO Distributed Control Software Framework. | ||
| 18 | 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. | ||
| 19 | |||
| 20 | === Objectives === | ||
| 21 | |||
| 22 | Location transparency: a location (naming) service should allow to locate a service over the network by name and/or required functionality. | ||
| 23 | Message delivery and format integrity: the system must warranty that messages are not lost or duplicated and that they are delivered uncorrupted. | ||
| 24 | 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 | ||
| 25 | Load balancing: if needed, the system shall be able to redistribute the services to allow load balancing over the distributed servers | ||
| 26 | Security: if needed, the system must be able to handle security of communication using appropriate secure protocols. | ||
| 27 | |||
| 28 | === Experiment Data === | ||
| 29 | |||
| 30 | |=Directories/files|=Description | ||
| |
4.1 | 31 | |[[ERAS-C3>>url:https://mission.oewf.org/archive_downloads/2/03-ERAS-C3/]]| <none> |