I processed earlier today, said not enough time or noisy data. But I look at points and they did actually process. But the software stuck with the Auto base position and chose the ppk solutions instead of RTK, but no bcp anything (so I'm not seeing a bcp ppk versus cors ppk as usual). The ppk were within less than a tenth of RTK so looks good. Two points I checked into were within 0.002 of previous known locations so that looks good too. It wasn't an unusually bad base position, and it was there for an hour and 45 minutes. The rtk/ppk were 5 to 20 minutes.
Just tried reprocessing and now "no cors in range", same as you got earlier.
These were yesterday afternoon occupations. Don't see any unusual solar activity. Not sure what's going on.
We are getting the same message "no CORS in range". It's nice to say, it will be fixed sometime, soon, maybe; and we go back hours later and everything works. Is there an answer, or solution, or process?
Still having troubles with DPOS. The Debug Server has worked, but something still not quite right; I don't get the rover cors processing anymore or the bcp processing. So, tried manually submitting one from the Triumph 2 on the user site. Got the same error of not enough time or noisy data and would not process. Converted to rinex and submitted to OPUS, received excellent results. The CORS in NY are now broadcasting Galileo corrections, could this be confusing the process in some way?
I am having trouble with DPOS too. Reports no CORS in range. Processed files from southern Indiana just fine, but won't process files from Nashville TN.
I am getting frustrated with the unreliability of DPOS lately.
I am having trouble with DPOS too. Reports no CORS in range. Processed files from southern Indiana just fine, but won't process files from Nashville TN.
I am getting frustrated with the unreliability of DPOS lately.