<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hello Mitch,</div><div><br></div><div>We (Anza Network) had the same glitch with our XL-AKs.</div><div><br></div><div>You may have resolved it already, but the "fix" for us was (via the serial interface):</div><div><br></div><div>CTRL-C (stop time string output)</div><div>F68 (view GPS epoch year - probably won't be 2013)</div><div>F68 2013 (set to current year)</div><div>F08 (restart time string output)</div><div><br></div><div>Power cycle the unit and all should be good. For how long, dunno.</div><div><br></div><div>best regards,</div><div><br></div><div><div>D. Glen Offield</div><div>University of California, San Diego</div><div>858.534.7274</div></div><div><br></div><div><br></div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><b>From: </b></span><span style="font-family: Helvetica; font-size: medium; "><<a href="mailto:mwithers@memphis.edu">mwithers@memphis.edu</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><b>Subject: </b></span><span style="font-family: Helvetica; font-size: medium; "><b>[ANSS-netops] xlak date stamp wrong</b><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><b>Date: </b></span><span style="font-family: Helvetica; font-size: medium; ">August 18, 2013 10:18:10 AM MDT<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><b>To: </b></span><span style="font-family: Helvetica; font-size: medium; "><<a href="mailto:anss-netops@geohazards.usgs.gov">anss-netops@geohazards.usgs.gov</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><span style="font-family: Helvetica; font-size: medium; color: rgb(0, 0, 0); "><b>Reply-To: </b></span><span style="font-family: Helvetica; font-size: medium; "><a href="mailto:mwithers@memphis.edu">mwithers@memphis.edu</a><br></span></div><br><div><br>Is anyone else who still uses analog data and gets time from an XLAK having<br>problems? All of our clocks appear to have reset to Jan 2, 2013 at UTC<br>midnight last night. This causes adsend to have the wrong date. And if<br>you have adsend set to sync the system time to it, your system date is wrong.<br><br>Mitch<br><br>Center for Earthquake Research and Information (CERI)<br>University of Memphis Ph: 901-678-4940<br>Memphis, TN 38152 Fax: 901-678-4734<br><br><br>_______________________________________________<br>ANSS-netops mailing list<br><a href="mailto:ANSS-netops@geohazards.usgs.gov">ANSS-netops@geohazards.usgs.gov</a><br><a href="https://geohazards.usgs.gov/mailman/listinfo/anss-netops">https://geohazards.usgs.gov/mailman/listinfo/anss-netops</a><br></div></blockquote></div><br></div></div></blockquote></div></body></html>