A little background information:
Version 6 Pro purchased around 2002, I think. (I did find the dongle)
I found the program on an old XP machine that does not have a printer port, I reckon I could get a printer port added or try to find a compatible USB to parallel adapter or pay $1,195 for an upgrade, I am probably like a lot of others on here and should have retired and donÛªt see that an upgrade would do me much good for my normal work.
I used to do a lot of subdivision work and had someone that used Star Net, now I do communication tower surveys with 3 or 4 points using fixed tripods and 3Û Leica robots with error of closure usually around 0.005Ûª and have not seen the need to run through Star Net.
The computer that it was on crashed and I do not have it installed on a computer with a printer port for the dongle to be plugged into, I know that I can run demo mode for ten points or less, but I have started surveying the family farm of a few hundred acres and thought it would be a good project to try to get familiar with LS again. I did several cross ties and mini loops inside the main traverse, turned to a radio tower and observed several points using the NC VRS network.
I know that getting the instrument and centering weighting errors is very important.
Can someone that is experienced give me some starting values using a 3Û robot using fix targets on a tripod for all sights?
TIA
Ed Killough, NCPLS
ekillo, post: 363302, member: 773 wrote: Can someone that is experienced give me some starting values using a 3Û robot using fix targets on a tripod for all sights?
This is what I use for my GeoMax Zoom80, which is basically a rebranded TCRP1202:
You could start with these (or maybe change the 2" entries to 3") and see if they produce the kinds of results you expect.
Jim's numbers are similar to what I use. Ditto on the 2" to 3" , since you've said that you are using a 3"gun.
Mark Mayer, post: 363311, member: 424 wrote: Jim's numbers are similar to what I use. Ditto on the 2" to 3" , since you've said that you are using a 3"gun.
Thanks, that is what I needed was a starting point.
ekillo, post: 363326, member: 773 wrote: Thanks, that is what I needed was a starting point.
What is the best way to enter the VRS data into Star*Net? I have been doing GPS surveys for over 20 years, but do not know the best way to combine the VRS with the ground run traverse points. I have read about Star*Net processing static vectors, but have not seen much on using VRS points. I have grid coordinates on seven key traverse points scattered across the survey with point number 1 having grid and ground being the same. I am working inside a 6000' box and in our area the combined grid factor is 0.99985.
Data entry:
I have the StarSMI converter but can not remember if I purchased the StarSurvCE converter. Can I cut and paste the traverse data (AR, ZA and SD) from the Carlson rw5 file into the Star*Net dat file?
ekillo, post: 363329, member: 773 wrote: What is the best way to enter the VRS data into Star*Net?
This is going to depend on both your VRS and your data collector. If your data collector can export a standard NGS g-file for the vector from the nearest network station to your rover, you can import that directly into Star*Net Pro. (The vector from a virtual station to your rover won't be of much use.) If all you have are coordinates and the associated standard errors, you can use those instead.
The advantage of using the g-file is that you're not wedded to the network station's base coordinates; you can change those as desired in the Star*Net data file.
ekillo, post: 363329, member: 773 wrote: Can I cut and paste the traverse data (AR, ZA and SD) from the Carlson rw5 file into the Star*Net dat file?
That won't work -- you need to translate those records into Star*Net format, either via software or by hand.
If you do not have the appropriate StarNet converter you will have to manually create a .dat file. If you have to go that route try to get your raw data output to AutoCAD .fbk format. Some data collectors will do that and there are various free utilities that will get you there. The .fbk format is somewhat close to the StarNet .dat format, the necessary edits won't take too long.
I am using SurvCe and have to number each point shot with multiple numbers, is there a software package that will collect field survey data in Star*Net format that does not have to be converted? On this project I so many cross ties that it was hard to keep the numbers straight so that I occupied the correct point and back-sighted the point it was shot from. For my use, I could get by without it doing cogo in the field.
ekillo, post: 363363, member: 773 wrote: I am using SurvCe and have to number each point shot with multiple numbers, is there a software package that will collect field survey data in Star*Net format that does not have to be converted? On this project I so many cross ties that it was hard to keep the numbers straight so that I occupied the correct point and back-sighted the point it was shot from. For my use, I could get by without it doing cogo in the field.
When I use SurvCE I put in the number of the point and it asks overwrite or collect more sets. You want to collect more sets.
ekillo, post: 363363, member: 773 wrote: ...is there a software package that will collect field survey data in Star*Net format that does not have to be converted?
None that I know of. To my knowledge there is none that uses the .fbk format either.
My strategy for point numbering cross ties is to number them 99A, 99B, etc. Then it's easy to identify and edit those extra letters out.
When using Trimble Access it isn't necessary. Access will allow multiple ties using the same point number.
Is there anything later versions can do that version 6 can't do?
rfc, post: 363413, member: 8882 wrote: Is there anything later versions can do that version 6 can't do?
I did see that they added an inline command called .prism that you can use if you had the wrong prism constant entered on some of your shots.
rfc, post: 363413, member: 8882 wrote: Is there anything later versions can do that version 6 can't do?
Generate .kmz files, so you can view your points in google earth.
ekillo, post: 363417, member: 773 wrote: I did see that they added an inline command called .prism that you can use if you had the wrong prism constant entered on some of your shots.
Well, if that's it (and the .kmz thing too), then one option would be to sell me your version 6 dongle for a steep discount, and put that money towards a brand new shiny dongle for version 8.:-D
rfc, post: 363428, member: 8882 wrote: Well, if that's it (and the .kmz thing too), then one option would be to sell me your version 6 dongle for a steep discount, and put that money towards a brand new shiny dongle for version 8.:-D
If I decided to upgrade my version 6 to 8 it will cost me $1,195 to upgrade.
I can do the Google Earth thing out of Civil3D.
ekillo, post: 363436, member: 773 wrote: If I decided to upgrade my version 6 to 8 it will cost me $1,195 to upgrade.
I can do the Google Earth thing out of Civil3D.
Ekillo:
I don't get that. A full version with NO upgrade is $1200 last time I looked. They must be saying that version 6 is too old to give you any credit.
I'm still looking for an older version that I can afford. Lemme know if you upgrade and they tell you to just toss the dongle.:-)
On your initial question (and Jim Frame's suggestions): I learned that because angles are comprised of two directions, the standard error for angles would be more like the square root of the sum of the squares of the directions, or something like 1.5 x the directions...That'd make them 3" if you used 2" for directions. I might have mis understood the sages however.
rfc, post: 363438, member: 8882 wrote: A full version with NO upgrade is $1200 last time I looked.
Star*Net v8 is $1,995.00, the upgrade from Starplus Star*Net v6 is $1,195.00, according to the website.
I might have mis understood the sages however.
I think you partially understood the sages. You're correct about the nominal angle standard error of an angle versus the manufacturer's spec, but the proof of the pudding is in the adjustment. Assuming that all your standard error estimates are realistic, if the angle error factor comes out around unity, then the manufacturer's spec is irrelevant. For my nominal 2" gun, a 2" standard angle error works well.
Jim Frame, post: 363446, member: 10 wrote: Star*Net v8 is $1,995.00, the upgrade from Starplus Star*Net v6 is $1,195.00, according to the website.
I think you partially understood the sages. You're correct about the nominal angle standard error of an angle versus the manufacturer's spec, but the proof of the pudding is in the adjustment. Assuming that all your standard error estimates are realistic, if the angle error factor comes out around unity, then the manufacturer's spec is irrelevant. For my nominal 2" gun, a 2" standard angle error works well.
Jim:
You're right. That's the price for the Pro version, which does GPS. I've got the Standard version on my brain...I see it's $995.
Thanks for the clarification on the errors.
