If you did have a problem between TDS and Carlson and phoned up Carlson for a fix they would likely blame TDS. When you called TDS they would blame Carlson. If you had both Carlson or both TDS (not an option) you would avoid that run around.
If you are just exporting ascii point files from your dc and working with that you aren't likely to have much problem with data compatability. But if you are doing something more advanced with your data the possibility of difficulties are greater.
Norman Oklahoma, post: 341330, member: 9981 wrote: If you did have a problem between TDS and Carlson and phoned up Carlson for a fix they would likely blame TDS. When you called TDS they would blame Carlson. If you had both Carlson or both TDS (not an option) you would avoid that run around.
If you are just exporting ascii point files from your dc and working with that you aren't likely to have much problem with data compatability. But if you are doing something more advanced with your data the possibility of difficulties are greater.
Not sure what advanced stuff I'd be doing. I import txt or csv control files to the DC, and I export raw or rw5 files to process in Carlson Survey.
(as an aside, what am I doing wrong here, that I see your post coming right under mine, and my reply to yours doesn't come in that way?)
You could always go back to transit and chain and write down angles and distances....[sarcasm][/sarcasm]
JPH, post: 341333, member: 6636 wrote: Not sure what advanced stuff I'd be doing. I import txt or csv control files to the DC, and I export raw or rw5 files to process in Carlson Survey.
A few things that come immediately to mind are:
1. load dxf line work to the dc for staking
2. load DTMs to the dc for staking
3. load Alignments to the dc for staking
Norman Oklahoma, post: 341336, member: 9981 wrote: A few things that come immediately to mind are:
1. load dxf line work to the dc for staking
2. load DTMs to the dc for staking
3. load Alignments to the dc for staking
Is that the issue, then?
I haven't come across any compatibility issues, between Survey Pro and Carlson Survey.
I'd encourage you to look into these functions - which are available on your TDS dc if it's under 10 years old. Very powerful. There is more to surveying than just points. If you aren't using functions like this then you would be as well off with an HP48.
Carlson has been very good about working with other manufacturers and TDS is one of the most well known. Trimble has not been so cooperative and they own TDS now. So it's not super surprising that you haven't had compatibility issues between those two. But that doesn't mean that you never will.
Norman Oklahoma, post: 341340, member: 9981 wrote: I'd encourage you to look into these functions - which are available on your TDS dc if it's under 10 years old. Very powerful. There is more to surveying than just points. If you aren't using functions like this then you would be as well off with an HP48.
Carlson has been very good about working with other manufacturers and TDS is one of the most well known. Trimble has not been so cooperative and they own TDS now. So it's not super surprising that you haven't had compatibility issues between those two. But that doesn't mean that you never will.
That may be true, and so far I haven't had the need for those functions. Most of the line/alignment staking we do is with Leica GPS.
But my question here, cptdent mentioned "burps", and you're saying that there might be issues in the future, but are you having compatibility issues now, between the two?
hlbennettpls, post: 341126, member: 10049 wrote: let me know what you got and why you like it!
Four of each:
LEICA-TC307
Nautiz x7, with Field Genius v7
ACAD LDD
Why? Perhaps outdated but still very productive. B-)
I don't know specifically what he was talking about. I've experienced things like dcs refusing to link with the computer until both have been rebooted. Or files that seemed to transfer but couldn't be found until the 3rd try. Stuff like that and sometimes worse. Like rw5 format changes that the software isn't coded to understand.
But just because something works in your office, with your computer system, and your dc doesn't mean it would work for him and vice versa. There are endless possible combinations of software, firmware, and operating system versions. No manufacturer can test them all. The essential fact is that if you use a dc and office software from the same manufacturer your chances of having a trouble free experience - and meaningful support if you don't - are better. That's all.
I put my hands on quite a few DCs over the last year looking for something to replace my favorite Ranger 200, and the Topcon FC 2500 that I really never cared for. After looking and holding quite a few, and narrowing the field by what plays with what, and what is owned by who, I ended up going with Carlson's Surveyor 2. I REALLY like the box, it sits in my hand well, and isn't overly heavy - well balanced. Screen is super bright and easily readable. Keys are good on the tactile, and touchscreen is really responsive. I am learning Survce, but it seems to mostly work like my old TDS and topsurv. I found a bug with Survce and the Javad GPS interface, and Carlson had it patched in 90 minutes!
Overall I really like the DC, and feel it will work the absolute best for me, but I will also note the little issues I see with it:
The text buttons are pretty small. I don't mind them that way, however this winter it may be a bit tough with any kind of gloves on.
I'm not too sure about battery life yet. I need to check the settings and profiles as it seems to drain down while sitting on the shelf for 4-5 days.
The rubber cover on the bottom of the DC I think could be a little thicker - or stiffer. It is a little tough to get seated, and just doesn't feel like it will last for 10 years.
With the way the industry is going so proprietary, it is tough to go with one specific manufacturer if you want to mix and match any different flavors at all.
We use Topcon TS, Javad GPS and Carlson in the office. The Surveyor 2 with SurveCE seemed like the best option for us.
Precision-geo-inc, post: 341243, member: 9801 wrote: You can also learn hot keys for all the shortcuts and avoid using a touchscreen all together.
Well, almost, anyway. I have a Surveyor+, and there are a couple of screens I can't fully navigate without using the touchscreen.
My only other gripe is that Carlson didn't pay close enough attention to highlighting the on-screen button that has the focus (i.e. the one that will be activated by pressing Return). That further complicates navigating without the touchscreen.
I think you want to hit the "comment" button on whatever post you want to directly reply to.
Licensed Land Surveyor
Finger Lakes Region, Upstate New York
Those 4 basic codes are fine, BUT there is so much more. Using just +7 and -7 can play havoc when shooting parking lot islands and try to reshoot that first point. Try "CLO" instead.
You can work wonders with the "/" or the"//" codes. Cuts down on field book use and allows you to not only draw lines, but, at the same time, label them. Works great for trees.
I understand that everyone LOVE their current setup and really do not want to change anything, but when it can allow you to create drawings 95% complete with line work, labels and symbols in under 3 minutes on most jobs, then maybe it's time to make a change.
Sometimes we have problems with our TDS DC's when we use expanded codes or multiple codes. Plus we do a lot of GPS and surface models for the local DOT and they want to be able to download the surfaces to check grades onsite.
It really all depends on what kind of work you do and how complex it can get. If you are a "basic 4 code" usesr, your TDS and maybe a new 48 are the real key for you. If it ain't broke, don't fix it.
Thanks
I've never dealt with processing raw data files. We download them to look for any mishaps, but we also get an ascii file too w/all the points that were collected. Does Carlson not operate this way, or am I misunderstanding?
Also, anyone use the Mini 2?
You can import your ascii files to Carlson. You can also "deal with processing raw data" in Carlson.
Personally, I rerun raw data every time. I find it all to easy to skip the reviewing the raw data part if I don't. It is, in fact, my way of doing that reviewing. If the data is correct in the first place it takes a few minutes. If it's not, any time I spend fixing it is time well spent.
For those using Carlson, what package are you using? I looked at the Civil Suite, but I think it may be a bit too much for what we do. We do boundary, topo, mortgage, and design surveys. We do have to compute quantities at times, so some of that would be useful. Just wondering what route to go. Also, we currently use CAD, is it better to get the embedded version, or just go straight Carlson?
I think you will find that most who are using "Carlson" in their office are using Carlson Survey. Carlson Survey will do all the usual things surveyors do, points, adjustments, alignments, surfaces, and so on.
What about finished product? Is that a separate program? Their website leaves a bit to be desired...
We have used Carlson SurvCE on a few different boxes for over a decade. We like it. It is powerful, but simple enough to get going quickly.
We use ACAD Civil 3D, with no Carlson office software. We use StarNet with the Carlson conversion utility for our balancing. It all plays very well together.
If needed, I could do a whole boundary survey on the DC, calcs, balancing (not least squares), Field to Finish (with .dxf export) and all. I wouldn't want to, but if I had a big tablet, it might be easier,
We exclusively use DC's with physical keyboards. The benefits are bigger if you have all the same units for every crew. That way you don't have to learn a new keyboard when you switch crews around.
You can export an ASCII/.txt file straight out of the DC, so your current workflow should be easy to maintain. There is desktop software for reading/printing/processing raw data files that comes with the software. (I think one copy of Carlson X-Port is free with each copy of SurvCE, it is a simple interface, no CAD or calc's or anything like that.)
