I have a question regarding Foresite DXM and level reports from a Topocon DL-101c.
When I export my Level Report to a txt file (import it into Excel for some additional reporting and graphs i've set up), the BS VD is being ommitted (reported as 0.00) on the last TP shot of every setup, also if any sideshots are taken, the SS elevations is being mis-calculated by subtracting the FS VD from the next TP HI and not the current setup HI. Take a look at the data set below to see what it looks like. I've been working around this by creating formulas in excel to handle the re-calc from the correct setup. Any help to correct this in Foresite DXM prior to exporting the data to a txt file would be greatly appreciated and save me alot of time working with the data.
thanks.
Station _BS(+)_ _BS Dist_ __HI___ IS(-) IS Dist _FS(-)_ _FS Dist_ _Elev__ ___Desc___
3 2.754 268.760 217.115 214.361 CONTROL
100 3.601 124.070 212.044 8.672 174.530 208.443 TP
103 0.000 0.000 204.310 7.734 199.430 204.310 TP
101 5.170 133.740 199.140 CHK 2
102 5.075 93.230 199.235 CHK 19
104 9.050 50.760 218.940 2.067 60.230 209.890 TP
105 8.343 148.470 225.043 2.240 102.470 216.700 TP
107 0.000 0.000 220.879 4.164 176.770 220.879 TP
106 7.602 139.290 213.277 CHK20
108 0.000 0.000 220.858 8.824 178.230 220.858 TP
22 5.775 84.860 215.083 XCUT ON MH
23 5.346 323.420 215.512 XCUT ON MH
110 0.000 0.000 215.275 8.484 91.950 215.275 TP
109 6.320 37.100 208.955 CHK20
111 3.108 224.690 210.498 9.473 73.260 207.390 TP
112 8.050 273.570 213.015 5.533 100.770 204.964 TP
114 0.000 0.000 210.185 2.829 119.940 210.185 TP
113 6.098 101.020 204.088 CHK 2
3 3.652 209.260 214.405 TP
James,
Sent I sent you here from the other site and still your questions (with 120 views) generated no response. I'll take another look.;-)
Thanks!
for some reason it has to do with the software taking the TP shot and moving it "above" the SS taken from the same setup. see the first setup data:
Station _BS(+)_ _BS Dist_ __HI___ IS(-) IS Dist _FS(-)_ _FS Dist_ _Elev__ ___Desc___
3 2.754 268.760 217.115 214.361 CONTROL
100 3.601 124.070 212.044 8.672 174.530 208.443 TP
103 0.000 0.000 204.310 7.734 199.430 204.310 TP
101 5.170 133.740 199.140 CHK 2
102 5.075 93.230 199.235 CHK 19
104 9.050 50.760 218.940 2.067 60.230 209.890 TP
in this example 3 was the starting BM, 100 was a single turn, 101 was a SS from the next setup, 102 was another SS from the same setup, 103 was the next TP and 104 is the next TP after that, with no SS taken between 103 and 104 TP's
when Foresite moves the TP shot above the SS, its calcing the elevation on the sideshots incorrectly from the wrong HI when i generate the level report. The raw data is correct, i need to go in and add the BS VD for the TP shot manully and recalc all sideshots accordingly... pretty time consuming and tedious as you can imagine... this snipit of data is only a fraction of my complete dataset.
James,
Your problem seems to simply be within the software of Forsight DXM and its ability to decipher what your are feeding it. It probably doesn't matter the actual mistake that is being made in the conversion process, omitting of an HI or miscalculation along the way. It's that fact that you have a piece of hardware (Topcon Dig Level) that collects data and your software Forsight DXM is incorrectly reading it. Forsight may not be the best tool to process, reduce and or view the level data but it simply may need some tweeks in the settings to get what you need.
You may try posting your question to support@spectraprecision.com
This should go to the same crew the was TDS, formerly TechSupport@tdsway.com since they created Forsight.
I wish I could offer a tip or trick, or an updated driver for Forsight DXM,:-( but I rarely use and and in doing so I've never used it with Digital Level data. If you send me the files in question, I could try it out.
Maybe someone else has your answer.
Bumping this TTT for Jhenry. 🙂
Jhenry, if you received an answer or if you still need this bumped until you do, please let me know. Thanks!! :beer:
no answer yet, still waiting.... please bump.
> no answer yet, still waiting.... please bump.
Will do. I have it saved in my "Bump Folder". So until you get an answer, I'll bump it every couple days or so. 🙂
Well geeze....I dunno buddy,
WHY aren't you using the Topcon export routine that came with the instrument?
Your problem is obviously a BUG in the TDS Foresight DXM Program, and now that Trimble has absorbed TDS, you can probably forget about getting the bug fixed (especially on a Topcon instrument).
Aside from that route, these types of formatting/exporting (binary to ASCII) problems are “usually” VERY systematic. IF (big if) this is true in the case that you are talking about (and it appears that it might be), then the path of least resistance MIGHT be to simply write a program (BASIC, C++ whatever) to FIX the (TDS/DXM) file problem (reformat/compute the RAW data).
Good Luck,
Loyal
> no answer yet, still waiting.... please bump.
JHenry, Was Loyals answer Ok for ya or did you still want me to bump this a few more times? Just let me know. Thanks! 🙂
Thanks Loyal and Angel. No need to bump.
I emailed spectra tech support and they actually got back to me within 24 hours!
They told me that version 3.4 of the software has known issues with level reports and I needed to downgrade to 3.3.1. Which I just did and all seems to be working fine now.
thanks again for your help
> Thanks Loyal and Angel. No need to bump.
> I emailed spectra tech support and they actually got back to me within 24 hours!
> They told me that version 3.4 of the software has known issues with level reports and I needed to downgrade to 3.3.1. Which I just did and all seems to be working fine now.
>
> thanks again for your help
Anytime. Glad ya finally got an answer!! :clap:
