I have used Carlson SurvCE for over a decade with several different Sokkia and Topcon RTK units. I am currently successfully running a pair of Topcon GR5s with SurvCE.
I "upgraded" to Topcon HR units a few months ago and even though I was told they would work with SurvCE, they do not. Topcon has closed its architecture to third parties. The only way to run an HR is with Topcon Magnet Field!
My salesman gave me a Topcon 5000 with Magnet Field for free to make things right, but now I have to learn to use Magnet Field and it is way different than SurvCE. I am dead in the water with it.
SurvCE is intuitive and has an easy flow. 10 plus years ago, I had a 15 min tutorial with SurvCE and was up and running and learning new things on my own. This Magnet Field is NOT like that. I have had two half-day lessons and am still lost. Magnet Field seems to over complicate the simplest procedures with so many settings and different ways it can be configured. It is easy to have one setting off and make it unusable. I don't dare experiment for fear of messing everything up beyond recovery. EX1: layers: you can tie down points in different layers. Sounds good, but over complicates simple tasks. EX2: point types: I just want all of the data I spent all day collecting to dump to my PC. BUT you better have the settings just right or some of your data won't make the download b/c it's a type not selected to output.
At this point I am convinced I will have to learn a whole new philosophy of field surveying in order to use Magnet Field. Is there anyone out there who is fluent in both SurvCE and Magnet Field who can help convert me? or show me how to trim down Magnet Field so it works more like SurvCE? All I can do is setup a job and the base and rover. I can get a fix - which does allow me to tie down points. But I cannot localize the way I want and get good data. I therefore cannot stake out points. All data I have gotten without localization is good data. Data I have gotten after I localize is bad data.
Here's an example of how I have to significantly alter my use pattern to use Magnet Field: Magnet Field cannot read a Carlson .CRD file. I have to dump my Carlson points to a thumb drive in ascii format (Pt,X,Y,Z,desc.). Then I have to create a job file and dump the ascii file into it. ...lots more steps that I don't have to do with SurvCE...
Then after the data is collected and it's time to dump it on my PC, Magnet Field cannot property create a Carlson raw data file (.rw5). It makes a .rw5 file, but it is not a real raw data file. I have found that different settings made in a Magnet Field session will yield different ".rw5" files. Raw data is raw data. It should not be affected by software settings in Magnet Field.
Here's what I mean: In Carlson SurvCE, if I set it to apply a geoid to the ties I make, the points in the point list on the data collector will have surface elevations in US feet, BUT only the points are affected NOT the raw data. No matter what settings I choose to affect the way I view the points on the data collector, the raw file stays pure. This does not happen in the fake rw5 file Magnet Field makes.
The raw data the receiver gets is in lat/lon and ellipsoid height for the z component . I believe this is WGS84??? When I get the raw data dump off the Carlson Mini II (SurvCE), in the office, I run it through Carlson Xport on my desktop. Xport is set to SPC 83, Texas South Central Zone and geoid 12b for my work area. The raw file is WGS84 and the output is my choosing.
Magnet Field does a poor job of outputting a Carlson raw data file and I cannot get past that.
The fake carlson raw data file that Magnet Field creates is NOT raw data. Settings like choosing to apply a geoid file so the Z component of the shot-in/collected data will be seen in US feet (on the data collector) will change the fake Magnet Field .rw5 file. This should not happen. The Z component in the raw data file should be an ellipsoid height.
The simple solution would be to uncheck the geoid option before making the fake Carlson raw file, but I found this not to work. The file appears to output with the Z in something close to ellipsoid height, but it is not.
I can dump ascii points to my PC from Magnet Field, but the whole reason I use raw data vs. dump collected coordinates is so I can process the data myself in the office and not rely on settings made in the field by my crew. What if they failed to update the rod height in the handheld when the pole was lowered? The output elevations would be off. If I can go into the raw file and add the rod height change and reprocess, I can "fix" the problem and get good output data.
This is just one problem I have. If someone has some experience and can help me make Magnet work like SurvCE, I would greatly appreciate it.