Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Sending Satellite Commands

StellarStation collects uplinked command data from users, processes it, and provides it to the authorized ground station.

(API) Near Real-time Streaming Commands

Commands can be streamed during a pass via the SendSatelliteCommandsRequest.

Format

Commands are sent as raw bitstream data without formatting (i.e. adding headers and trailers).

For example, if the command '0xAABBCC' is given to StellarStation, then it will be sent out as '0xAABBCC'.

Ordering

Individual command request messages can arrive out-of-order due to how networks function. Multiple commands listed within a command request message will always be handled in-order.

For example, if the commands '0xAA', '0xBB', and '0xCC' must arrive at the satellite in-order, then SendSatelliteCommandsRequest.command should be set to [bytes('0xAA'), bytes('0xBB'), bytes('0xCC')]. Note that was just an example and the way to define lists or cast your commands to bytes depends on the coding language you use.

Timing

Command request messages should be sent between AoS and LoS. Infostellar generally recommends the last command be sent at least 10 seconds before LoS. StellarStation uplinks the commands immediately upon receipt and cannot be pre-set to execute at a specific time.

Control

Only one stream can have control of commanding the satellite at one time. For safety reasons, opening a new command stream takes control away from the previous commaning stream permanently.