Steve Douty
Well-Known Member
The last two times I have worked a project, using a T2/LS combination, I have had issues getting a successful DPOS solution. Although I had been on the site for a significant time; DPOS would indicate that my base file contained only a few minutes of collected data, and the base file was not correct. I sent my files to Adam and he coordinated with corporate support. Several hours of effort by the support team.
When I start the day this is what I do:
1 - Turn on all of my equipment; T2, LS, Jetpacks.
2 - I then set up the T2 on the base point; measure the height of the base, etc.
3 - Then I PUSH THE RECORD BUTTON ON THE T2!
4 - Then I use Bluetooth and Base/Rover setup to pair and start the base.
I was doing this because the green record light was not on (on the T2) and I wanted to ensure that the base data was recorded for later CORS and PPK analysis during DPOS. Because I pushed the record button on the T2 before I paired and started the base the session the data collected is being labeled as a standalone session in the T2 and not exported to the LS when I stop the base. The thing that I did not know is that when I start the base from the LS during Base/Rover setup, the T2 starts a file that later is downloaded and paired.
All of this is "operator error"; however it is difficult for support to find or correct stupid by the end user!
The reason for this post is two fold:
1 - To thank support for their, knowledge, time and patients.
2 - To suggest that, as a software update, it might be good if the software checked for this user error when stopping the base.
As was often stated on "Hill Street Blues", "Be careful out there".
When I start the day this is what I do:
1 - Turn on all of my equipment; T2, LS, Jetpacks.
2 - I then set up the T2 on the base point; measure the height of the base, etc.
3 - Then I PUSH THE RECORD BUTTON ON THE T2!
4 - Then I use Bluetooth and Base/Rover setup to pair and start the base.
I was doing this because the green record light was not on (on the T2) and I wanted to ensure that the base data was recorded for later CORS and PPK analysis during DPOS. Because I pushed the record button on the T2 before I paired and started the base the session the data collected is being labeled as a standalone session in the T2 and not exported to the LS when I stop the base. The thing that I did not know is that when I start the base from the LS during Base/Rover setup, the T2 starts a file that later is downloaded and paired.
All of this is "operator error"; however it is difficult for support to find or correct stupid by the end user!
The reason for this post is two fold:
1 - To thank support for their, knowledge, time and patients.
2 - To suggest that, as a software update, it might be good if the software checked for this user error when stopping the base.
As was often stated on "Hill Street Blues", "Be careful out there".
