Reading RPLS is free for the whole profession. Members post, reply, and get the members-only rooms.
I've occasionally?ÿ experienced this problem before,?ÿ with SurvCE. When?ÿ going straight to Stakeout after resection,?ÿ most of the time it works as it should, but when you try to Store Points?ÿ after resection?ÿ it forgets the orientation. By default the station is calculated by the resection and the backsight is the first point used in the resection (even if you turned it off in the calculation). When going to the backsight screen and press the Turn to Backsight?ÿ button,?ÿ it turns to a random angle, way off of the backsight. I?ÿ learned to always?ÿ backsight a point used in the calculation after each resection.
A friend of mine that has a one year old Carson tablet with?ÿ SurvPC 6.03 on it complained about the same thing. I wonder jf this is common for this software, or it is something that only a few of us experienced. It is just a minor inconvenience for me?ÿ to shoot the Backsight after resection.
I used to see that sporadically. We made it a point that once resection was done, to redo the set up as you would regularly, OP and BS.?ÿ
Yet another bug. All current software is full with them, even if we pay top $ for maintenance.?ÿ
The time i spent with bugs in lots of software is an outrage. They release new software functions much too soon all the time.
I have seen it on SurvCE 6.06. Thought it was me missing something.?ÿ
After the resection, I always make sure the backsight is reset to zero. I haven't had an issue yet, knock knock, with the backsight not being set.
Using RT4 with v6.11
@beuckie?ÿ
I agree 100%. I have lots of bugs with fieldgenius which I've been using on a Leica 1203+ the last couple of years, was even worse on the brand new Sokkia they bought, basically unusable for busy construction layout...
Now I'm using a new Trimble, which I thought would be much more stable and reliable, but because they had to rebuild the software for the android operating system, it too is now full of bugs.?ÿ
Magnet field was the least buggy software I used but the Sokkia hardware kept failing.?ÿ
@350rocketmike?ÿ
I run Magnet Field on a 11 year old Sokkia Srx5. Still works like a charm.
I must say i only do construction with the ts. All the rest is gnss or scanning.?ÿ
The bug thing i mentioned was a general remark. It is on all software nowadays.
Yet another bug. All current software is full with them, even if we pay top $ for maintenance.?ÿ
The time i spent with bugs in lots of software is an outrage. They release new software functions much too soon all the time.
Yea soooo true. I have asked software folks a time or two to just take a year off from new stuff and just go hard at making it bullet proof. They did not like that - so new version comes out, wait till the 2nd or?ÿ 3rd patch and?ÿ then upgrade ! ! !?ÿ
I actually had a list?ÿ of fixes that were sorta ignored until I was asked to do a beta test for a new version, I cut and pasted my old list in the review for the new release and , WAHHH LAAA, all fixed. LOL
G
When I used Carlson all the time, I got to know their tech support folks pretty well.?ÿ I have called them while in the field, documenting and explaining the bug with specific steps (I would build this so I knew I wasn't doing it wrong), I would sometimes have a patch to download before I could get back to the office.?ÿ Sometimes, they would set me straight on what I was doing wrong, too!?ÿ I always found their tech support to be top notch, and it was one of the things that made me a fan of Carlson....
@beuckie?ÿ
Sorry but I have to stick up for Carlson here.?ÿ They are about the best in the business for backing their software and one of the few that has not sold out to a monopoly.?ÿ I am also surprised that Ladd Nelson with Carlson hasn't weighed in yet, he is usually available for help on this forum.?ÿ Try to get service like that from the monopolies.?ÿ My 2 cents, Jp?ÿ
I've occasionally?ÿ experienced this problem before,?ÿ with SurvCE. When?ÿ going straight to Stakeout after resection,?ÿ most of the time it works as it should, but when you try to Store Points?ÿ after resection?ÿ it forgets the orientation. By default the station is calculated by the resection and the backsight is the first point used in the resection (even if you turned it off in the calculation). When going to the backsight screen and press the Turn to Backsight?ÿ button,?ÿ it turns to a random angle, way off of the backsight. I?ÿ learned to always?ÿ backsight a point used in the calculation after each resection.
A friend of mine that has a one year old Carson tablet with?ÿ SurvPC 6.03 on it complained about the same thing. I wonder jf this is common for this software, or it is something that only a few of us experienced. It is just a minor inconvenience for me?ÿ to shoot the Backsight after resection.
I experimented same problem sometimes, without stakeout, without understanding why it occurs, but I don't use resections frequently. Now I do as Gary said.
However, I remember many times where I tried to use?ÿ the "set collections" to get an average bearing and I got exactly the same problem, with stakeout. One day, it occurred three times, without stakeout, but each time that i used the virtual joystick to move the gun. Co-workers heard?ÿ me howling... I was using the 6.06.
My French reseller told me that he obviously never heard about such problem.
Just found that in SurvPC release notes :
Version 6.10
Release Date: May 28, 2021
(...)
Bug Fixes in SurvCE:
(...)
- It is no longer possible for the backsight circle measurement to be lost if a resection is performed, the BS D&R option is ON, and the resection D&R option is OFF.(...)
Version 6.04
Release Date: September 27, 2019
(...)
Other New Features and Improvements SurvCE:
(...)
- The resection routine has been revamped. Residuals and results will now appear on two different tabs to allow more space for residuals. Columns in the residual table can now be sorted. The On/Off options are now available inside the table. The user can now select the backsight point from all resection points.
So maybe your friend, @Ramses, has to upgrade.
