I have run into a situation where I am attempting to post process Topcon data from a NetG3A CORS station against data from my Leica 1200 receivers with very poor to no solution using Leica's LGO software. The data is GNSS and the Topcon data is provided as RINEX data.
I suspect either something in the conversion to RINEX or some sort of difference between the way Topcon and Leica handle clock offsets or timing between the GPS and GLONASS constellations.
I have sporadically run into similar issues previously, but four CORS from the same network are now giving me fits.
It has been awhile since I messed with this, BUT I think in the past I also attempted to post process using NovAtel software also with similarly dismal results.
I suspect that Topcan may still have a large "Javad" flavor even though they went separate ways, https://www.javad.com/jgnss/products/options/gclb.html&apos ;">here is a link to a page on the current Javad site about the biases, it seems to me it would be important for all makes to do this the same and my guess is they don't?
SHG
First, use teqc and strip out all but GPS and see what kind of solutions you will get with that.
Second look at the RINEX and check the format of the L2P and L2C, which may be in separate locations in one and combined in the other. If so reduce the files to L1, C1, L2, C2 or P2, They can be merged, but you want to match the other file.
Deeper into GNSS I cannot help.
In the past I had success with Leica data in Ashtech Solutions when LGO was choking.
Paul in PA
Still working toward a resolution. RINEX data from the same RTN that came from a Trimble NetR5 receiver processes fine in Leica LGO against my Leica receiver, so it is looking like an incompatibility between Leica data and software and Topcon NetG3A receivers (unknown about other Topcon hardware). What hasn't been determined yet is if there is something happening with the Topcon data between when it leaves the receiver and reaches me, or if it is the actual Topcon data. The way the RTN works (if I understand it correctly) is a RTCM stream is collected in RT and then stored at the RTN servers. When a user requests data later that can be one of several versions of RINEX or one of a few Trimble formats since the RTN is a VRS network, Trimble options are obviously offered. The stored data is then output in the requested format and can be downloaded to the end user. So there are at least two conversions, one to RTCM at the receiver to be streamed and one at the server to be sent to the end user, may be an intermediate step in between if the server stores in a different format?
Since the RINEX files the RTN servs have already been massaged a bit, looking to see if any users could provide me with some raw TPS files from a Topcon NetG3A receiver that is also in fairly close proximity to CORS data that I could also access, preferable a Leica CORS. If it turns out Topcan data from a NetG3A receiver works independant of the RTN, then it will close the gap on troubleshooting the issue.
So if you can help with some TPS data let me know.
Shelby
Update: I was able to obtain a raw file from one of the Topcon receivers I am fighting with, converted that to RINEX using Topcon's TPS2RIN (a DOS utility) and I was able to process that RINEX file just fine in Leica LGO. So, it appears either the streamed RTCM file to the RTN servers is bad or the conversion is bad at the RTN server (I had tried both a RINEX and a T02 file, both failed), Topcon data itself seems OK.
This greatly reduces the work required in troubleshooting the data coming from that RTN.
SHG