start	end	text
9780	14520	Welcome back to a Hack-A-Sat competition update. I'm your host, Jordan Wines.
14760	19320	Taking a look at the scoreboard so far, we've had an eventful last hour.
19360	23880	Our teams continue to make progress, with four teams now having solved Challenge 1.
24100	27480	Unfortunately, the window of time after a first solve has expired,
27480	31000	and the remaining four teams were given the solution with no points.
31000	39120	PFS and Colon Can Into Space were joined by 1553 and 1064 Seabred with solutions for Challenge 1.
100640	103200	1064 Seabred has been around for several years,
103200	107060	going all the way back to when they were first high school friends playing as CTFs.
107060	113260	In fact, I first met them five years ago as the only team of high school students at a collegiate CTF competition,
113260	115700	and the team even included a standout freshman.
115700	119840	Yep, a high school freshman competing with college freshmen and college seniors.
120180	122800	And while I don't personally know any of 1553,
122800	126460	after they gave me some interesting facts about them, I kind of feel like I do.
126460	133020	For example, one team member has additional sound dampening around his office due to his above-average laughter volume,
133020	135600	one member was fired from her previous job for, quote,
135600	137540	smiling too much, quote,
137540	140320	and another member was a college mascot.
140500	144040	Finally, their team logo, or team motto, rather, is
144040	146720	Preparation is the Enemy of Innovation,
146720	151120	which sounds a little bit like an excuse, but you can't argue with their results.
152000	155960	Let's take a look at the solution for Challenge 1, now that all teams have it.
157740	159560	Challenge number one.
159760	164320	Here's what we know. Having access to the ground station means we can attempt communication,
164320	168340	but the satellite is spinning out of control, which complicates everything.
168620	172460	The challenge. Teams must regain communication with the satellite.
173380	174880	Here's how they do it.
174880	179080	To get started, teams must set the command and telemetry rates appropriately,
179080	181040	and the power output to maximum.
181040	184540	Because the satellite is spinning, additional link margin is required.
184540	188660	The teams receive periodic telemetry, but are not able to command the vehicle.
188820	192320	Based on the review of the anomaly resolution section in the user's guide,
192320	194620	they realize that to increase the link margin,
194620	198160	they should increase radio output power and decrease link rate.
198160	200860	They command the radio to high power and low rate mode,
200860	203120	and regain communications with the satellite.
203220	204940	The link is limited to low rate,
204940	208140	meaning that what they can send and receive from the satellite is limited.
216770	221090	This is a good example of the type of challenge that is a little different in this type of CTF
221090	223410	versus many other types of CTF.
223410	226730	While teams were told to, quote, restore communication, quote,
226730	230430	that goal was much more ambiguous than often traditional CTF challenges,
230430	235290	and mirrors more of the real-world problem solving you run into in space-based applications.
235310	239150	Because our imaginary bad actors had intentionally modified the satellite's orientation,
239150	240850	and they were moving around uncontrollably,
240850	244330	communication between the ground station and the satellite was not stable.
244330	248530	To fix this, teams needed to both lower the transfer rates, boost the power,
248530	252130	and that would finally let them enable ground-based communications.
252130	254750	And that would let them control all the components of the satellite,
254750	257650	or at least the ones that they've been able to figure out so far.
257870	261790	In fact, the challenge was real-world enough that at least one team was able to solve it
261790	264030	in the normal order of just working with their satellite,
264030	267210	without even specifically realizing they had solved the challenge.
267350	269770	All that brings us to Challenge 2.
271230	272550	Challenge 2.
273530	274930	Here's what we know.
274930	276790	The satellite is spinning out of control
276790	281470	because the Guidance Navigation and Control System, or GNC, is inoperable.
281530	283590	We suspect sabotage.
283750	284850	The challenge?
284970	289950	Teams must repair the GNC system as quickly as possible to stop the dangerous spinning.
298980	303300	As teams now have regular communication with their satellites,
303300	305280	they'll need to get the movement under control.
305280	307020	But it's also worth mentioning at this point,
307020	310420	that these satellites do actually have their own battery and power supply.
310420	312620	They're taken off each night to be charged,
312620	316420	and while power utilization is not a scored metric in the game,
316420	320840	if one team does manage to cause too much movement or otherwise drain all of their power,
320840	324840	it could impact their ability to interact with the satellite for the remainder of the day.
324980	326700	Looking forward to seeing what they do.
326700	329820	We'll see you back here in another hour for our next competition update.