Magnet field to Star*Net

The conversions are rarely 100%. There is usually some tweaking needed. Post the converted .dat file here so we can have a look at it.

StarNet will only read the .dat file. There are ton of StarNet gurus on here. You need to explain what error message(s) you are getting, maybe some screenshots of your .dat file and somebody on here will help you.

I was a Star*Net guru a decade or two ago... I still have a licensed copy of the old software before Ron Sawyer retired and sold it to TDS.
---
At this point I used to edit the .dat file to correct the errors made with the raw data converter.
Use "notepad" or some such so that weird characters don't get created, and Edit a Copy, save the Original 😉
It might look like greek but it is a common text file... study it for a bit and you will see the pattern

(change your settings so that Every measurement is recorded, including that BS distance, good for blunder detection)

You said you exported a dat file from magnet.
My flow is to export a raw or rw5 and send it through the starcarlson converter to get a starnet dat file.
Might that be the hangup?

Scott Zelenak, post: 446171, member: 327 wrote: You said you exported a dat file from magnet.
My flow is to export a raw or rw5 and send it through the starcarlson converter to get a starnet dat file.
Might that be the hangup?

I've tried that too with both of those raw formats. Errors on import.

Here is a link to my .dat file.

https://cpls.egnyte.com/dl/PkfcIz88MG

Sent from my SAMSUNG-SM-N920A using Tapatalk

Peter Ehlert, post: 446169, member: 60 wrote: Ron Sawyer retired and sold it to TDS.

And now Trimble owns star*net.
Maybe that's related, to why it does not work well with other software.

you have bearings held as fixed, you need all but one of them to float.... I think after the coordinate you enter * * * or something like that.
do you have a manual? it gives the correct format

Nate The Surveyor, post: 446181, member: 291 wrote: And now Trimble owns star*net.
Maybe that's related, to why it does not work well with other software.

I don't think so (but could be wrong...again)

Star*Net was sold to MicroSurvey, not TDS, and Trimble hasn't bought MicroSurvey (yet).

Loyal

correction needed Star*net is now part of the Microsurvey family which is owned by Hexagon.

Loyal, post: 446184, member: 228 wrote: Star*Net was sold to MicroSurvey,

Thanks for the clarification.
N

Loyal, post: 446184, member: 228 wrote: Star*Net was sold to MicroSurvey....

Dane Mince, post: 446185, member: 296 wrote: ....Microsurvey family which is owned by Hexagon...

Hexagon being the parent company of Leica. So Leica owns StarNet. But I can assure you that there is zero communication between the two. For example, StarNet doesn't sell a Leica format converter. You have to get that direct from Leica.

This is exactly what I don't understand. Star*Net is around for many many years and the developer can't even figure out a very simple parsing algorithm. I always end cleaning up in every project. This is the reason why I am considering the Move3.

Give the "developer" some slack.
there have been many owners and apparently probably lots of fiddling with the code. 😉
===
Ron Sawyer made a DOS program for manual data entry. It worked great.
Later, people started using data collectors, and the format of those files were not standardized... so he created a one off for each type, but that was a moving target. Maybe it still is.
He sold the converter software as a separate module, and would rapidly work out the bugs as they became known.
Then, later people wanted a Windows version, he managed that, then he retired....

What happened then I don't really know, nor do I know what happened to Mr. Sawyer.
My version is the DOS version.

Peter Ehlert, post: 446194, member: 60 wrote: Then, later people wanted a Windows version, he managed that, then he retired....

I think "managed" is the right word. I recall a conversation with him in which he said that he hired a Windows-savvy coder to do the Windows UI, so any requested changes had to get passed along through the Windows guy.

amdomag, post: 446189, member: 1683 wrote: This is the reason why I am considering the Move3.

If you use only Leica, will always use Leica, and nothing but Leica, then LGO/Move3 is a great choice.

OK, there are several issues.
None of the coordinates or bearings are fixed.

So, I fixed the first coordinate and bearing - a minimally constrained adjustment.
And it worked enough to give me the rest of the errors.

Here is how I fixed one point and one orientation with the "!".

Here, I let the rest of the coordinates and bearings float by using a "*".

Assuming the 500 points are topo they should be "SS" and not "M".

In this pic, I believe the software isn't recognizing that you're doubling angles?

Scott Zelenak, post: 446200, member: 327 wrote: OK, there are several issues.
None of the coordinates or bearings are fixed.

So, I fixed the first coordinate and bearing - a minimally constrained adjustment.
And it worked enough to give me the rest of the errors.

Here is how I fixed one point and one orientation with the "!".

Here, I let the rest of the coordinates and bearings float by using a "*".

Assuming the 500 points are topo they should be "SS" and not "M".

In this pic, I believe the software isn't recognizing that you're doubling angles?

Wow! Thanks Scott. The coordinate that I want to be fixed is point number 2. After looking at the .dat file, the software thinks that I zero set on point number 2 when in actuality, I just had a general north direction pointed at a tower light. So how do I fix that?

So I went into my raw data and changed the name of the point number for #2 to 2a. Does this work out now?
https://cpls.egnyte.com/fl/qfQmNKRMa6

Do you have a .prj (project) file?

Because I'm really guessing at a lot of required info.