Earlier quoted context omitted.
The way the automated FTS works is essentially that the USAF blasts a "DO NOT BLOW UP" signal with a very high power transmitter to the FTS. If the FTS doesn't receive that signal, it triggers and then you have a RUD.
RUD: Rapid Unscheduled Dissassembly
Receiving SpaceX Falcon 9 Telemetry with a HackRF and 1.2m Satellite Dish
111–114 of 114 posts
I prefer the term distributed landing.
Re: Receiving SpaceX Falcon 9 Telemetry with a HackRF and 1.2m Satellite Dish
#112Earlier quoted context omitted.
> This doesn't strike me as particularly sensitive. I'm no rocket scientist but I would have thought you'd want to encrypt and sign everything... by default. Otherwise how do you stop spoofing as well?
I can't speak to SpaceX's decision, but in FCC rulings, they have proposed encryption when commanding vehicles, not for telemetry or tracking comms (satellites, specifically, although I'd assume similar guidance for vehicles, with the only command you're going to send to the vehicle would be boom for range safety).
For historical purposes, range safety on SpaceX vehicles has been autonomous and onboard since 2017. Vehicles emit telemetry, but do not receive commands.
https://www.spaceflightinsider.com/space-centers/ccafs/autom...
Re: Receiving SpaceX Falcon 9 Telemetry with a HackRF and 1.2m Satellite Dish
#113> Usual CCSDS frame format is not used, instead custom framing protocol is employed
I've worked with this before, and it can be a pain.