Requirements

The requirements for the TTC module (called TMR, or TTC Module Requirement), for the FloripaSat project, are listed below. These requirements were made aiming the needs of the FloripaSat and the legal rules for this kind of device.

1. The FloripaSat shall have a physical device to inhibit radio frequency (RF) transmission.
   Compliance with CDS 3.3.9. The use of three independent inhibits is highly recommended and can reduce required documentation and analysis.

2. The CubeSat will have the RF power output to the transmitting antenna input no greater than 1,5 W.
   Compliance with CDS 3.3.9.1.

3. The CubeSat will have the RF power output to the transmitting antenna input no less than 1,0 W (or 30 dBm).
   Defined by team analysis.

4. No CubeSats shall generate or transmit any RF signal from the time of integration into the PPOD through 45 minutes after on-orbit deployment from the P-POD.
   Compliance with CDS.

5. TT&C transceiver shall transmit and receive on the frequency of 437,9 Mhz.
   Defined by the team, based on available spectrum allocation to Amateur communication.

6. TT&C beacon shall transmit on the frequency of 145,9 Mhz.
   Defined by the team, based on available spectrum allocation to Amateur communication.

7. TT&C shall modulate and demodulate information using GFSK.
   Defined by the team.

8. TT&C Beacon must transmit periodic beacon messages at an interval of 10 seconds, except when in hibernation or shutdown mode.
   Allows ground stations to track and receive satellite data even if telecommand was not sent to the satellite.

9. TT&C transceiver must receive signals from ground stations and demodulate them.

10. TT&C must interface with OBDH, exchanging encoded raw data received or to be transmitted.

11. TT&C must interface with OBDH using the SPI protocol (@2 KHz).
    Defined by the team.

12. TT&C radio must modulate raw data received from OBDH using GFSK, prior to transmission, and demodulate received data and forward raw data to OBDH.

13. TT&C transceiver shall transmit and receive data at a baud rate of 2400 bps.
    Defined by the team, based on link budget analysis.

14. TT&C beacon shall transmit data at a baud rate of 1200 bps.
    Defined by the team, based on link budget analysis.

15. TT&C beacon shall transmit packets using the NGHam and AX.25 protocols.
    Defined by the team.

16. A same beacon packet must be transmitted in both NGHam and AX.25 protocols.
    Defined by the team.

17. TT&C must receive the batteries voltages from the EPS module at every 10 seconds.
    Defined by the team.

18. The payload from the packets transmitted by the beacon must contain at least the satellite ID ("FLORIPASAT") and batteries voltages (received from the EPS module at every 10 seconds).

19. TT&C uC must perform the antenna deployment of the VHF band antenna.
    Defined by the team.

20. Between the beacon packets transmissions, the beacon MCU and radio must operate in low power mode, to save energy. Defined by the team.

21. TT&C PAs (Power amplifiers) must just only be activated during transmissions. When they are not in operation, they must be turned off.
    Defined by the team.

22. All the beacon critical data, like time control and antenna deployment status, must be stored in a non-volatile memory.
    Defined by the team.

23. TT&C beacon must be able to receive a 24 hour shutdown command from the OBDH module.
    Compliance with AMSAT/IARU regulations.