On two occasions/days I have had a stationary reciever running for several hours (same file) which crosses UTM Hour O or a change in the Julian Date. While two rover recievers collecting 20-30 minute static files. All lines process just fine until the rover files change days. The time view/Top left window shows each file the graph shows the baseline but the processor will process the line between the rovers but not the line to the base unit. I have deleted the files in the processor and edit files names to the same day and reloaded same problem. Present running Software v1.1 have V1.2 to load will this help? What am I missing. P.S. good sat coverage and visibility baseline between rovers passed no problem.
Modified By Stan Piper on 7/16/2001 at 9:21 PM

Stan,

I know I have run several sessions past 2400 UTC and have not noticed any glitches. I was a bit concerned though that there may be a glitch as you have noted. I'm sure though that all the sessionS we've done like that have been processed with ver 1.2. I hope you get a good answer, I'm curious too.

J.D.

Stan,

I can't tell you specifically if using ver. 1.1 is the cause of the problem, but I urge you to use the later version. It isn't cheap for us to produce a new version (development, testing and distribution costs), so when we do so as a free update, that generally means that the purpose was to fix defects in the previous version. Be sure you register Locus 1.2 so that you will receive Solutions 2.40 (about to ship).

Regards,
---Brian
Modified By Brian D. Ewing, PLS on 7/17/2001 at 9:23 AM

Being 7 or 8 hours away from UTM midnight, I have run hundreds of sessions that cross the line at Greenwich o hour, and have had no problems. File names are downloaded using the "end date" but that doesnt interfere with processing.

I only have one rover (can I have a cheap second?..?..?) and still no problem.