Dane Mince, post: 425030, member: 296 wrote: Microsurvey has been bought by hexagon and is part of the Leica family now, so I expect updates to Star*Net to make it work better with Leica equipment.... just a guess...
You would think so. And at one time I did also. But a problem with converting Microsurvey Fieldgenius/ Leica GS15 data to StarNet disabused me of that notion.
StarNet was converting Fieldgenius/Topcon data flawlessly while it was failing to properly convert Fieldgenius/ Leica GS15 data. Answer from Microsurvey was "we can't get the codes from Leica". Huh.
For the record there doesn't seem to be much cooperation between Trimble & TDS/Spectra Precision either.
Mark Mayer, post: 425082, member: 424 wrote: You would think so. And at one time I did also. But a problem with converting Microsurvey Fieldgenius/ Leica GS15 data to StarNet disabused me of that notion.
StarNet was converting Fieldgenius/Topcon data flawlessly while it was failing to properly convert Fieldgenius/ Leica GS15 data. Answer from Microsurvey was "we can't get the codes from Leica". Huh.
For the record there doesn't seem to be much cooperation between Trimble & TDS/Spectra Precision either.
For what it's worth, years ago, after Ron Sawyer sold Star*Net to MicroSurvey, I was chatting with Sean Curry (who worked with Ron and did a considerable amount of programming work on the later versions of Star*Net with Ron at the helm) about future enhancements that I thought would be useful. At the time, I told him that probably the most important thing they could do was to get the converters in a state that would support as many of the formats in common use as possible and maintain them, and I still think that would have probably been more bang for the programming buck. I'm still running V6-Pro, though, so your mileage may vary.
Kent McMillan, post: 425097, member: 3 wrote: At the time, I told him that probably the most important thing they could do was to get the converters in a state that would support as many of the formats in common use as possible and maintain them, and I still think that would have probably been more bang for the programming buck.
I once had a conversation with Ron himself in which he stated that he spent the bulk of his time trying to keep the converters working. He said that he felt like some of the changes the dc software vendors were making seemed to have no other purpose than to make his converters fail.
Mark Mayer, post: 425098, member: 424 wrote: I once had a conversation with Ron himself in which he stated that he spent the bulk of his time trying to keep the converters working. He said that he felt like some of the changes the dc software vendors were making seemed to have no other purpose than to make his converters fail.
Yes, Ron told me as much as well - that he'd get a vendor to provide their data format, only to find that they'd revised it soon afterwards without telling him. I doubt they were trying to defeat compatibility with Star*Net so much as it just being a characteristic of the chaos in their patch-it-up-and-out-the-door operations, While Star*Net maintained backwards compatibility over more than seven different versions, apparently the folks writing DC software were challenged by other things.
I bought fieldgenius after testing it only to find that the latest version did in fact NOT WORK with my 5600.... bummer. I now hate all the instrument makers.....officially hate them all....
We use Trimble S7 total stations with TSC3 with Access. The data can be processed in TBC (which has improved considerably over the past few years) or be exported to a RW5 on the TSC3 which we have the old converter which makes a StarNet DAT file.
StarNet has the advantage of being very versatile, almost anything can be adjusted in (like old field notes).