Wes Hand
Active Member
I have sent a project called ALDOT to support. I also sent a log file but I’m not sure I did it correctly. Can you please look into this for me?
For the second weekend in a row, I was in Dothan, Alabama with a potential customer trying to get a working solution with their ALDOT RTN with little success. I have attached a pdf of the TCP/IP information and have highlighted in yellow the ones I tried with TCP/IP. I had no success with either. One was Nearest base type but I expected it not to work as I saw no way for the LS to send NMEA GGA with TCP/IP. I tried connecting directly to the Dothan base (ALDO) being only 4700 feet away with port 17105 and received error/timeout (I think) for the RTN Status. There is another port not listed on the attached pdf that was given to me by the RTN administrator and it works through NTRIP. The IP address of 205.17.52.26 stayed the same but the port is 10011. I tried RTCMIMAX, AutoMAX and near_RTCMv3_GG. I tried RTCMIMAX first and it initialized very quickly and I shot point 1.1 with all 4 engines fixed (all signals were identical on all 4 engines) for about 39 seconds but then I tapped auto setup engines. At this point the engines went to float and never would fix again. I held a long reset engines and still nothing. RTPK worked like a champ during this whole process. The only RTK and RTPK that ever agreed was this initial 39 seconds of RTK data. I subsequently tried the other 2 sources but they stayed in float mode almost the whole time. I did eventually get a fix with the near_RTCMv3_GG but if was off from the RTPK by +/-0.46’ predominately in the easting. I gathered data on the same point with 3 different sources/mountpoints and the RTPK results were repeating very well for each. The description for each point tells you which source/mountpoint I was using at that time.
FYI, the potential customer had a Trimble R6 and spectra precision collector software. He dialed in to each port & mount point I tried flawlessly. His positional values were checking mine that were derived from RTPK.
Thank you,
Wes Hand
For the second weekend in a row, I was in Dothan, Alabama with a potential customer trying to get a working solution with their ALDOT RTN with little success. I have attached a pdf of the TCP/IP information and have highlighted in yellow the ones I tried with TCP/IP. I had no success with either. One was Nearest base type but I expected it not to work as I saw no way for the LS to send NMEA GGA with TCP/IP. I tried connecting directly to the Dothan base (ALDO) being only 4700 feet away with port 17105 and received error/timeout (I think) for the RTN Status. There is another port not listed on the attached pdf that was given to me by the RTN administrator and it works through NTRIP. The IP address of 205.17.52.26 stayed the same but the port is 10011. I tried RTCMIMAX, AutoMAX and near_RTCMv3_GG. I tried RTCMIMAX first and it initialized very quickly and I shot point 1.1 with all 4 engines fixed (all signals were identical on all 4 engines) for about 39 seconds but then I tapped auto setup engines. At this point the engines went to float and never would fix again. I held a long reset engines and still nothing. RTPK worked like a champ during this whole process. The only RTK and RTPK that ever agreed was this initial 39 seconds of RTK data. I subsequently tried the other 2 sources but they stayed in float mode almost the whole time. I did eventually get a fix with the near_RTCMv3_GG but if was off from the RTPK by +/-0.46’ predominately in the easting. I gathered data on the same point with 3 different sources/mountpoints and the RTPK results were repeating very well for each. The description for each point tells you which source/mountpoint I was using at that time.
FYI, the potential customer had a Trimble R6 and spectra precision collector software. He dialed in to each port & mount point I tried flawlessly. His positional values were checking mine that were derived from RTPK.
Thank you,
Wes Hand