Can't seem to make my StarTDS data converter work to give me a .dat file today. The last few months, it has be acting strange, but I've been able to work around it (hack out sections of the .raw that I didn't need, change setting in the converter to go around certain pieces of data that were giving it fits, etc.). Unfortunately, this time I haven't found a work around (other than take out all the topo data and not handle it through Starnet - which I'd prefer not to do). I get this error: ERROR [Line: 2089] Input file read failure. When I go to line 2089, this is what I get:
Any ideas on what I'm doing wrong, or not seeing in the .raw? The Microsurvey help site had a post about it not converting correctly for offsets, and that version 5.1 of Survey Pro fixed it. We have version 5.5, so it seems like we should be good.
Anyone else have these kinds of issues?
Thanks! - Paul
Consider that Windows updates are slowly eating away at older programs. Usually you can find away to get it back working, but every day Windows is making some old internal program work a little differently to please some newer software problem.
Restore Windows to the previous update and see if TDS is happy.
Paul in PA
That's an idea. Thanks. I'm using the latest and greatest version of Microsurvey Starnet, and StarTDS, so it shouldn't be an operating system thing, but you never know. I'll keep that in mind if the geeks at Microsurvey can't figure it out.
I've always thought that this converter was weird, since it requires that you first convert the .survey file to a .raw file in the data collector before you can use the StarTDS converter, so it isn't grabbing information from the file in it's native format out of the DC. I'm guessing that the .survey file is some proprietary format that Spectra won't give the keys to Microsurvey.
If you are using Survey Pro you can also convert your .survey file to .jxl and then use the StarXML converter for Trimble format files.
Mark Mayer, post: 433475, member: 424 wrote: If you are using Survey Pro you can also convert your .survey file to .jxl and then use the StarXML converter for Trimble format files.
Except that it won't let me open that converter because they want me to pay for it first. I suppose I could download a free trial onto another machine and do it that way.
Do you know why they give us all the GPS converters, but make us pay for the conventional converters? I wouldn't even mind paying a little more and getting all the conventional converters. Back before Microscurvy, I don't remember the converters being an issue.
To be honest, I've been making this crappy converter work for the past few months now, and I think I've reached the point where I just want them to fix the darn thing, or tell me what I'm doing wrong. Ed connected me to Tech Support, so I'm hoping they'll come up with an answer.
I was also thinking that surely others have been having issues with it, which is why I posted here, but perhaps it is just me.
Paul, post: 433479, member: 624 wrote: Do you know why they give us all the GPS converters, but make us pay for the conventional converters?
I suppose because StarNet Pro, which you need to work with GPS, costs more than StarNet Standard.
Fyi - they figured it out. My guys translated and rotated the job in the field. Spectra now shows all the point numbers which made startds have fits. Apparently, this is a newer thing that the starnet converter hasn't been updated for yet. I just chopped out the point numbers and it was fixed.
Sent from my LG-M257 using Tapatalk
Paul, post: 433736, member: 624 wrote: Fyi - they figured it out.
I was going to suggest - I've found that the StarTDS converter fails on me most often when a set of angles is aborted. So looking into your crews field procedure might be useful.
James from MicroSurvey Support here,
As Mark mentioned, sometimes the solution to TDS converter problems is to use the jxl output format as well. If you're reluctant to purchase another converter just to solve a one-time problem once contact us in support and we can run the converter for you.
But in this case, Paul and I did get this sorted out yesterday simply by removing some extra long comment lines, and our developers are going to make a change in the next update so that long comments are handled more gracefully in the future. We've seen a related issue with large jobs in which a transformation has been applied with JXL files that are exported from Surveypro. If you're in MicroSurvey Helpdesk search for an article entitled: Missing data from Jobxml files
Thanks James.
Sent from my LG-M257 using Tapatalk
