Debug trace:

[Houskeeping] 20[s] actions..
[FlightPlan2] _4sec_check
[Dispatcher] Orig: 0x1105 | Cmd: 0x6001 | Param: 8
FSM_default => pay_i = dat_pay_expFis
fis_iterate..
len( ADC_period[] )\0xff\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00
--------- SUCHAI BOOT SEQUENCE ---------
.....

To perform persistent run time re-configuration

In the integration for the tests in Brasil the +-Z array cables are crossed.

Gomspace beacon only accept 20 characters (but adds auto generated telemetry as volt, rssi, temp) so we need to redefine beacon content.

Se constata que luego de iniciado el sistema y de queda disponible la consola, el comando "rtc_print" falla si se ejecuta mas de 1 vez, sin embargo el comando "ppc_osc" no lo hace, aunque se repita indefinidas veces. El comando "rtc_print" en resumen solo funciona la 1era vez, pegando el sistema si se reintenta.

Se probo comentando las lineas de spemaforo del comando rtc_print, sin exito

Lo extraño es que al dejar el flag SCH_TASKEXECUTER_VERBOSE con un valor de 2 si se puede re-ejecutar "rtc_print" indefinidamente. Sin embargo se pega a si se reintenta, a penas se cambia el valor de SCH_TASKEXECUTER_VERBOSE.

No se han probado con otros comandos, si tambien se pagan.

Please review and refactor this file:

• Follow global coding styles (functions separated by space, avoid lines with /***********************************************/ use an space instead, add documentation)
  • Restore pay_take_lagmuirProbe command
  • Remove unused code

The payloads state machine is designed to take a limited number of samples of each payloads. However, the execution counter is "initialized" (not properly initialized in the source code) after a reset. The later means that if the payload execution limit is set to 100 and before a reset it counter was set to 90, then after the reset the execution will continue from 0 resulting in 190 samples. This may cause issues with the payloads buffers.

See:

After a few operations libcsp get out of buffers.
Debugging of buffers usage is necessary.

Which versions of the MPLAB X IDE and XC16 compiler are required to build the SUCHAI project with the FreeRTOS and legacy PIC24 peripheral library?

This function is need to check system status

Falta crear la funcion eps_isAlive, para incluir el estado de la EPS en las variables de estado.
Existe una funcion VersionReadEPS(); para leer la version del la EPS, sin embargo no se ha encontrado que valor debe retornar. Una vez que se sepa la funcion eps_isAlive es trivial de terminar.

Use SD not microSD

Check that fligh plan variables are stored succesfully (by telecomands) and can be readed after a reset

Fundir FP y FP2 en una sola tarea y probar que no haya StackOverflow.
Posterior a ello probar que los comandos en FP se ejecuten en los horarios correspondientes.

Casting a int16 variable to char, causing a bug in the frame counter

At the moment printf (used in libcsp and nancom) and con_printf coexist. We need to:

• link con_printf with printf and
• make printf thread safe using mutexes (like con_printf)

Note: look in TRX_GOMSPACE for the solution.

TM frame are received with inverted endianess. Fix in trx_tm_addtoframe function

Las tareas no se inician cuando las EEPROM no están a bordo, debido a que hay una lectura de estado que causa un loop infinito antes de iniciar el funcionamiento efectivo.

Ejemplo TaskConsole.c

/*Avoid the acummulation of commands while the SUCHAI is still deploying.. */
#if (SCH_THOUSEKEEPING_USE == 1)
    portTickType xLastWakeTime = xTaskGetTickCount();
    portTickType check_deployment_time = (10000) / portTICK_RATE_MS;      /* check every 10sec  */
    while( TRUE ){

        /* TODO: Infinite loop if EEPROM is not onboard */
        if( sta_get_BusStateVar(sta_dep_ant_deployed)==1 ){
            break;
        }

        vTaskDelayUntil(&xLastWakeTime, check_deployment_time);
    }
#endif 

Relacionado: #23

El repositorio de datos no funciona sin el repositorio de datos. Hay que poner una condición para cuando las EEPROM no estén abordo y usar un buffer en RAM.

It is loose, probably broken.

Function execution causes pic reset

Este comando no revisa que efecitvamente el TRX siga vivo. Solo asume que lo hace.

Esta asi ya que al ejecutar sta_get_stateVar(sta_TRX_isAlive); desde un Listener se genera un stack overflow ya todas las transaciones CSP con el TRX sobrepasan el limite de RAM de un Listener.

SOC is 1 and Vbatt 8.2V instead of 8/9 it should be

A command to set trx baudrate is required. Please consider the ability to restore default settings if the new baudrate do not allow communication with ground station.