Skip to content

[FEATURE] Persist Transmit Enable at End of Startup Sequence #300

@Mikefly123

Description

@Mikefly123

Short summary

Keeping the radio enabled through reboots after antennas deploy

Motivation and user story

At the moment the transmitting capabilities are disabled on the radios by default at compile time. This is to ensure that the satellites are compliant with regulations that restrict the use of radios until an operator sends a command to enable them.

The startup sequence calls ReferenceDeployment.lora.TRANSMIT ENABLED after it deploys the antennas, but a reboot will return the radio to the default disabled state. We don't want this behavior, assuming that (at least in the early days of the mission) we want to have a constant beacon coming from the satellite to help with identification.

Proposed implementation

Update the startup.seq with another line the saves the ReferenceDeployment.lora.TRANSMIT ENABLED parameter after it is set. This will persist the value between reboots.

While you're under the hood, it may also be a good idea to adjust the timing so that transmit enable is offset by a few seconds from the antenna deploy call. Something like this:

R00:45:00 ReferenceDeployment.antennaDeployer.DEPLOY
R00:10:00 ReferenceDeployment.lora.TRANSMIT ENABLED

This is to make sure there is enough time for the antenna deploy to complete before the radio comes online.

Reference Documentation

https://fprime.jpl.nasa.gov/latest/docs/user-manual/gds/seqgen/#time-details

Priority

Low

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    Status

    New Features

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions