LS+ not working with ALDOT RTN

Wes Hand

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
 

Attachments

  • ALDOT_CORS_Network.pdf
    538.3 KB · Views: 67
  • _DUMP_report.txt
    254.8 KB · Views: 46

Michael Stazhkov

Developer
JAVAD GNSS
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
I see only project 1440_DAVIS on support. It could be that your ALDOT project is too large for the service. You can try http://storage.javad.com/ service:
Login: customer
Password: obpiWmoLM6feqDqaI7iG
 

Wes Hand

Member
Michael,

I just Sent Project 1442 PARTIN to support. Issues were seen during base session called BASEG5 122221A. Data was gathered with LS+ with T3 as base. Base was set in a wide-open field.

Points ranging from 4062-4074…I had the auto start on at least 3 points not restart when it involved the shot getting stored by RTPK (min verification level 3). I manually had to hit start to get the process going.

I also really struggled at point 4068 and 8168 getting rtk data. Maybe I am spoiled but I just don’t recall my old standard with GPS/GLONASS unit taking this long to get an RTK shot in the same environment. Maybe you have spoiled me and I just can’t remember correctly. On these 2 particular shots I have sent videos to http://storage.javad.com/ videos with names corresponding to the point number. The camera is going out on my iPhone so I apologize for the shaking. I was in canopy but leaves are gone and I had some open sky above. It just seemed to struggle and not perform like it has in the past.
 

Wes Hand

Member
Just sent log file. 1442B PARTIN is project. Point 4076.1 just stored with rtpk and it’s not restarted. Am I sending you what I need to for support?
 

Wes Hand

Member
John,

I hijacked my very own thread. My issues were with rtpk not auto restarting and I was not on the ALDOT network. T3 base and LS+. I should have started another thread. I think michael and I had the conversation in previous post or I posted to wrong one.
 

Eugene Aksyonov

Administrator
JAVAD GNSS
5PLS
Latest news... As far as I understood by debugging unit of Ralph Mcvay ALDOT CORS uses Leica software for NTRIP service and something old that manages TCP socket connection. But despite the NTRIP connection TCP doesn't required authorization with login/password. So it would not work if you set this credentials. Wes, remove it and test if you want.
Is any one knows about more documents but "http://aldotcors.dot.state.al.us/SpiderWeb/frmIndex.aspx" only?
 

Eugene Aksyonov

Administrator
JAVAD GNSS
5PLS
1644182100631.png
 

Adam Plumley

Active Member
JAVAD GNSS
Latest news... As far as I understood by debugging unit of Ralph Mcvay ALDOT CORS uses Leica software for NTRIP service and something old that manages TCP socket connection. But despite the NTRIP connection TCP doesn't required authorization with login/password. So it would not work if you set this credentials. Wes, remove it and test if you want.
Is any one knows about more documents but "http://aldotcors.dot.state.al.us/SpiderWeb/frmIndex.aspx" only?
The web address returns a 404 warning for me Eugene.

Nice work figuring out the user name and password.
 

rbriang

New Member
We cannot connect to the ALDOT CORs network nearest site port with our Triumph-LS after an update. To still be able to use the ALDOT CORs network we connect using the port number for a specific site. Our LS is currently being upgraded to a LS+ or I would check the nearest site port. I connected to the network yesterday using the nearest site port with our Carlson data collector connected to our Triumph-2.

The ALDOT CORs website is https://aldotcors.dot.state.al.us/SBC.

I previously contacted Robert Harris with ALDOT by email with questions. alcors@dot.state.al.us
 

Adam Plumley

Active Member
JAVAD GNSS
Hey Brian, you should be able to connect to it on Prerelease or use the ntrip port. I don't recall what the port number is but i think its 11005. Give Wes Hand a call, he knows the port. 229-507-1031
 
Top