Leap Second: Receivers+, OPUS-

I came back to the office after 7:00 pm tonight to test the pile of receivers that I had set out earlier in the day. I figured I should get a head start on any problems that the leap second might generate.

I used my ProFlex 500 at the house (3 KM baseline to office) to test the following receivers:
[INDENT=1]ZMax[/INDENT]
[INDENT=1]ProMark 500[/INDENT]
[INDENT=1]ProFlex Lite[/INDENT]
[INDENT=1]ProMark 800[/INDENT]
[INDENT=1]ProMark 220 (which reflects on the ProMark 120 and MobileMapper 120)[/INDENT]
[INDENT=1]ProMark 200 (which reflects on the ProMark 100 and MobileMapper 100)[/INDENT]
[INDENT=1]SP80[/INDENT]
[INDENT=1]X91+[/INDENT]
[INDENT=1]X900+[/INDENT]

I am happy to report that they all tracked GLONASS (except for the ZMax of course), got fixed solutions, got the correct position and had the usual elevation range. (If there were any big failures, I was going to take the next couple of weeks off :pissed:.)

All of the receivers just started tracking and fixed. I did not need to do a reset, or wait for new ephemeris on any of them (even the ZMax!) They seemed to just work.

I also collected 1.5 hours of static data with a X90-OPUS and a X900S-OPUS. They too just turned on and started tracking SV's.

I was able to succesfully process the baseline between the two receivers using GNSS Solutions.

However, OPUS-RS rejects the files with this complaint:

1021 The year and day-of-year could not be determined from the submitted data set.
1021 The data set may be corrupt. OPUS can not continue the processing.
1021 Aborting...
1021

So I downloaded a hour's data from the NGS CORS SLCU and submitted it, but got the same failure.

Loyal correctly/wisely suggests that I wait until the morning and resubmit. But I thought I would post a note to warn others that there 'may' be something up.