Totalsurv, post: 339973, member: 8202 wrote: I am using Topcon Topsurv and when I export a raw file to rw5 format it shows a VD error on the Backsight check that is not there in the field check screen. Is this the same thing that is happening? It usually shows quite a large error.
I'll try the image here again..
Looks like Topcon has corrected the backsight errors in Magnet Field version 3.2, just released this week.
Improvements and Resolved Issues
The following Improvements and Resolved issues, where applicable, apply to all versions of MAGNET Field
software (Field/Site/Layout).
âá Addressed an issue when exporting RAW data in APA-SIMA format, the VA is now included in the records
âá Corrected an issue when importing drawings (*.dwg) into MAGNET Field; curves in polylines would import as
tangents. The curves are now imported correctly.
âá Corrected an issue when creating custom Classes for observations, the Class definitions are now recognized
correctly.
âá Resolved an issue where photos would not link to a point. Photos now correctly link to points.
âá Addressed an issue in Angle Set reports when displaying the slope distance in the SD Residual field. The
Residuals are now correctly displayed
âá Addressed an issue when importing .dxf files. In some instances the linework was not shown correctly.
âá[hl] Corrected an issue when exporting Raw Data. The resulting HD, VD, HA and, VA errors were not reported
correctly.[/hl]
âá Resolved an issue when updating jobs with Localizations from a previous version of MAGNET Field software.
The Localization residuals are now shown.
âá Addressed an issue when Exporting to GTS format, all data is now included.
âá Addressed an issue in Resection when Û÷Setup for 3DMCÛª is checked. Resections performed with the 3DMC
function enabled would rotate and shift the resection after accepting the results.
âá Resolved an issue when creating and storing a Custom Datum on a Field Controller. The coordinate offsets
and rotation are now stored after saving the Custom Datum.
âá Resolved an issue when creating a surface with a boundary when there are closed breaklines that contain the
triangulation area. Closed boundaries are now recognized.
âá Corrected an issue In Set Collection. Set collection now allows for the user to search for the prism if the line of
sight to the prism was lost. Set Collection will continue once the prism is found.
âá Updated Set Collection to use Auto Pointing instead of Auto Tracking after turning to a point.
âá Addressed an issue in Resection, the residual calculation now show the correct distance measurement units.
âá Addressed an issue in mmGPS. The Field calibration routine has been updated to show the calculated values
I just loaded Magnet 3.2 onto one of our instruments with the Onboard software.
The Raw data is still showing that the backsights are perfect. HD error = 0.000 VD error = 0.000.
This is after I slid the instrument 0.05' back and then shot it again.
I tried exporting a .raw file, a .rw5 file and others and all had the same result.
I have not tried this yet on a controller so hopefully it will work on there
Gregg Gaffney, post: 342551, member: 1111 wrote: I just loaded Magnet 3.2 onto one of our instruments with the Onboard software.
The Raw data is still showing that the backsights are perfect. HD error = 0.000 VD error = 0.000.
This is after I slid the instrument 0.05' back and then shot it again.I tried exporting a .raw file, a .rw5 file and others and all had the same result.
I have not tried this yet on a controller so hopefully it will work on there
Errors read correctly for me on the ToughPad with v3.2.
leegreen, post: 342562, member: 2332 wrote: Errors read correctly for me on the ToughPad with v3.2.
Ver 3.2 does not use my pre-set backsight prism. On screen and raw data both indicate it is using my foresight prism.
I have not created any new jobs in the data collector since installing, but I doubt this is the problem. Raw data in the same job before upgrading from 3.1 shows it was working in 3.1.
This is with a Tesla and QS Total Station.
