Error Message on DPOS screen?

[Sean Joyce]

For this project I have 2 other DPOS sessions that worked and 1 that did not due to the T2 not recording Glonass. (don't have a clue why that happened)
I was able to process that base point and the PPK data on the website.
Base 2 and 3 DPOS'd through the L.S..
Base 4 will not DPOS. "DPOS task already exists"
Could the previous DPOS solutions in the project cause this error message?
The L.S. does not recognize my base 4 data as a base file.

 

[Shawn Billings]

Give me a call at your convenience, Sean.

9039850102

 

[Michael Stazhkov]

Michael
How is the first DPOS session deleted ?
without deleting my data.

I mean DPOS sessions on the DPOS screen. The session just describes your collected data during one collecting session and prepare the data to send to DPOS service. It doesn't contain any unique data itself. So you can delete the DPOS session and recover it later. All your data are points and data connected to the points.

 

[Sean Joyce]

Thanks Michael and Shawn,
FYI on this issue, Shawn got me squared away on the project above after I updated the L.S. to the latest pre-release version.
On Friday I was working on another survey for 3 hours and experienced the same issue again on that project.
This time I was watching the base file download and it lost connection half way through the download just like before.
Was able to correct the problem with manage base files and DPOS worked, but my problem with the download persists.

 

[Michael Stazhkov]

Trying to process through DPOS and getting the message at the top of the screen
"Checking Base Presence".................WAIT
The base file 30 mb is in the list on the right column along with my sideshots.
Any ideas out there what this might be?

I have fixed a bug in the DPOS area. This caused the "Wait" state of a DPOS task even if the base file was downloaded.
Since PreRelease 2.0.5.743 it should pass the state for tasks related to the current project and after the base file downloading.

 

[Robert P Stenerson]

Greetings,

For the last week we have been experiencing some problems with the DPOS:

Anyone have any ideas what this is, and how do we get back on track?

Thanks,

 

[Shawn Billings]

Go to settings in DPOS (center button on the screen in your picture). Select CORS(US) as the preferable network. It's attempting to process using CORS in Texas.

 

[Shawn Billings]

Attention @Eugene Aksyonov

 

[Shawn Billings]

Rory, when is the last time you updated the software (what version are you running for J-Field).

 

[Robert P Stenerson]

Hi Shawn,
My crew has been experiencing this for the last three working sessions. Yesterday, they updated to 2.0.5.759, and they tried to DPOS, and were stopped. It makes the connection to the server, appears to upload the file okay, and then it freezes with the above message. I'm going to have them call you later this afternoon when they get back into the office (winter has returned up here.)

Thanks,

 

[Shawn Billings]

I'll be happy to talk to them, but I can see that they just need to change the preferable network to CORS(US). You can see in the picture that it is trying to connect to the Texas CORS, which would be a long way from you.

 

[Robert P Stenerson]

Thanks Shawn, well I can tell you with great confidence that's a setting they didn't mess with, we don't even know how do you change that setting, i.e. choose server? I saw in your earlier reply how to fix, again thanks for the great help.

P.S. It was set to Auto select previously...now it's set to CORS(US)

 

[Nate The Surveyor]

Apparently, "auto select" was broke, and it was defaulting to txcors.
I had the same issue, and applied the same fix as above. It worked.
I'm close enough to texas, that SOME files did process, but weren't very good...
Meaning that it had previous data on it. So, it was saying that my base coord was off by some 0.09' in easting... Which seemed sloppy, (long sessions).
This did fix it..
Thanks Shawn.

 

[Nate The Surveyor]

Oops

 

[Shawn Billings]

It wasn't so much broken as it was simply using an algorithm that wasn't valid. We had a circle drawn from Austin, TX. Any jps files from inside that circle were being automatically processed to the TxDOT CORS when auto select was turned on. Since Texas is so irregular, this approach was too simplistic and adversely affected users in nearby States. Newer updates to DPOS are being developed to remove this issue.

We added the TxDOT CORS because there are several stations in the TxDOT network that are not in the NGS CORS network. Some time ago, NGS started a policy of only accepting new CORS stations in areas of the country that lacked CORS. TxDOT has stations in most, if not all, counties in the State, so there are a lot of stations that have been disregarded by NGS. As a result, Alexey added access to TxDOT's FTP. This allows Texas users to have a much more dense coverage for DPOS solutions. I suspect other States could be added as well if there is a good reason to do so.

One other benefit to adding alternate FTP sites is that if NGS is down for maintenance or politics, the CORS data is still available to DPOS.

 

[Nate The Surveyor]

Thanks Shawn.
N

 

[Eugene Aksyonov]

Robert, I work on PreRelease version that is not checked completelly. We do modofications on DPOS to detect acceptable networks by point location. It is not supported on Production server yet as we test it on our Staging server. BTW, you can select checkbox of Debug Server in Advanced settings to try it.
But, I would not recomment to work on PreRelease until we issue it to Release state. Hopfully version will be released on this week.