Coyle, ShaneClauer, C. RobertHartinger, Michael D.Xu, ZhonghuaPeng, Yuxiang2022-04-072022-04-072021-07-282193-0856http://hdl.handle.net/10919/109578Instrument platforms the world over often rely on GPS or similar satellite constellations for accurate timekeeping and synchronization. This reliance can create problems when the timekeeping counter aboard a satellite overflows and begins a new epoch. Due to the rarity of these events (19.6 years for GPS), software designers may be unaware of such circumstance or may choose to ignore it for development complexity considerations. Although it is impossible to predict every fault that may occur in a complicated system, there are a few "best practices" that can allow for graceful fault recovery and restorative action. These guiding principles are especially pertinent for instrument platforms operating in space or in remote locations like Antarctica, where restorative maintenance is both difficult and expensive. In this work, we describe how these principles apply to a communications failure on autonomous adaptive low-power instrument platforms (AAL-PIP) deployed in Antarctica. In particular, we describe how code execution patterns were subtly altered after the GPS week number rollover of April 2019, how this led to Iridium satellite communications and data collection failures, and how communications and data collection were ultimately restored. Finally, we offer some core tenets of instrument platform design as guidance for future development.application/pdfenCreative Commons Attribution 4.0 InternationalArticle - Refereedhttps://doi.org/10.5194/gi-10-161-20211022193-0864