So, I sure wish that I would have searched the board before we allowed our dealer to install Topsurv 8.1 on our FC-2500 last week. According to them, 8.1 fixed all the problems with not being able to use spaces, dashes, etc. in the last version of the software, and has some cool new line staking features that we wanted to use. Suffice to say, it did not solve the problems. From our testing, it actually made them worse because now it also runs slower. Although I will say that some of the new line staking features look pretty cool. It was only when I started looking for solutions tonight that I noticed Stephen's post mentioning some of the issues with 8.1.
Fortunately, we have a good dealer, and now that they are aware of the issue, they will work with us on a solution. Unfortunately, the solution may be to go back to 7.5, since we use linework coding that requires spaces and dashes, and setting up a code list for every possible combination (using multiple codes in each description) just isn't feasible.
Just thought I'd send this out as a friendly warning. Also, if anyone has figured out a work around to this problem, I'd sure like to know what it is.
Thanks,
Paul
Depending on how you use the software there may be a solution. If you do not need to create linework in the DC, you can switch it from "code" to "note" mode for data entry and it will let you enter whatever you want as a description. I only loaded 8.1 yesterday so I've not had much time to test it. Topcon University has a good presentation that details the differences between the two methods. Its on their website under Software,topsurv8,manuals,look for "presentation" at the bottom of the page.
The setting is under Configure, Codes, Switch the data entry mode from "code" to "note".
I have been using 8.1 on my FC2500 when the upgrade to 8.1 first came out.
I like the upgrades except for the codes not taking spaces,as our codes uses spaces.
Yes,it is true that you can switch over to notes,but then have no linework in your dc,but I like having the linework,to see it as I am mapping.
John
Thanks! This will work for us as we don't do in data collector linework (only after the fact). Funny that our dealer didn't know this.
Several questions were asked in the TopSurv forum on TopconUniversity when v8 was first released. The codes vs. notes presentation was the ultimate result.
I've only been using TopSurv for 9 months so I watch the forum to find out about bugs/quirks that others run into. All software packages have bugs/quirks, knowing about them before you lose time to them is the secret.
7.5.1 had several:
1) After rotating a job you had to check your backsight or at least open the backsight menu or all subsequent shots would be on the original rotation of the job.
2)Translations and Rotations are not stored in the raw data, so editing HI's or HR's in the raw data and allowing it to recompute will undo any translations/rotations.
3) I often use a -30mm prism on a tripod for my backsight. On my initial setup on a job I occupy one unknown nail with assume coordinates and backsight a second unknown nail with an assumed azimuth of 0deg and allow TopSurv to store the pt for the backsight. I learned to always toggle the prism offset back to -2mm and check the backsight. Sometimes TopSurv will show the -30mm offset on screen but use -2mm for its calcs. Intentionally staking the backsight with the wrong offset tells me if it got the initial shot correct or not.
I'm sure there are others, but these are the ones that bit me personally. I know that #2 is still an issue in 8.1 but I have not had time to field check the other two yet.
I hadn't heard about the prism offset problem. That definitely sounds sketchy. Our solution to the rotation/translation issue is simply to not use these features, but to do all such operations in C3D or Starnet. Not what we really want, but it works.
I also did not realize that Topcon had a separate university site (besides the support site). I've requested a password, and will start browsing their forum.
Thanks again!
Paul
The prism issue may be a timing/communication issue between topsurv and my topcon 9003. If I check the "fixed backsight" box before locking onto the prism and setting the instrument zero, it will typically show but not use the -30 offset. I usually toggle it off then back on just prior to shooting the backsight and it seems to clear up the problem.
You can put in multiple codes . After the shot there is a button that says multiple code and you can add as many as you want . You dont need combination codes .
The trick is when you export the raw file ,The data collector will allow you to customize the way the data is presented . Its hard to find but when you export a Raw file you will see a code style button .I use Carlson in the office and I can format the exporting of the data in a carlson format.
Have not run into the prism problem , since we use 0 offsets on everything.
I only rotate,translate (computed) points but never Raw located job points , Due to the fact that most programs will not pick this up when processing raw data anyway . Then I fix the survey base in the office when I process the raw file. Safer less head aches .
