What Causes "Socket Failed" Messages?

Jim Frame

Well-Known Member
My usual -- and preferred -- means of operating an RTK base is via TCP over a cellular modem. Most days it works flawlessly, but every now and then (like today) I'll pull up to a site to take a shot and get a "socket failed" message on the comms screen. I've tried many things to correct this condition, including all of the following:

1. Turn WiFi off and then on again (rarely if ever works);

2. Stop and then restart the RTN (sometimes works, but not reliably);

3. Reboot the TLS (sometimes works, but not reliably);

4. Reboot my phone, which serves as my rover's WiFi access point (sometimes works, but not reliably);

5. Switch action profiles, then switch back again.

6. Reboot the Jetpack at the base (don't remember if that works or not);

7. Reboot the T2 (don't remember if that works or not).

When the problem cropped up today -- after several hours of trouble-free operation -- I tried 1 through 5. (Although I was only a couple of miles from my base and Jetpack, getting to them required hauling out a ladder and climbing up onto my roof, so I didn't try 6 or 7. ) No. 1 didn't work; No. 2 would sometimes work, the TLS would connect and get corrections, but after a few seconds the connection would drop and the TLS would go through the init procedure again, only to generate the "socket failed" message. Nos. 3, 4 and 5 didn't help. Note that I was in a spot with excellent cellular coverage, I could rapidly load web pages on my phone when I tested the connection, and the TLS WiFi showed 100% connection to the access point.

What finally "worked" (in quotes because I don't know if there's really a cause-and-effect relationship) was when I gave up and switched to my CRTN profile so I could at least collect a point. (That connection was rock-solid, but my regional CRTN stations are GPS-only, so I prefer using my own base.) After I got the shot I changed back to my TCP profile, and it worked flawlessly.

Rather than go through this circus every time the problem arises, I'd like to know more about the cause so I can approach the fix in an intelligent manner instead of just throwing everything I can find at it and hope I hit on the right thing. So what actually causes the "socket failed" message, and what's the recommended way of curing it?

Thanks!
 

Eugene Aksyonov

Administrator
JAVAD GNSS
5PLS
Hi Jim, well as far as there are rock solid CRTN connection, I would start investigate your setup really.
I am not sure this thread is handy to debug the issue. We could make a lot of flood. Usually I open private discussion and connect required people in case It is required. What I need to know is complete details of your setup with details about base settings, phone|jetpack rover settings. LS unit should be connected to RAMS JAVADGNSS server. I need to understand networks routing and related setting to assign IP addresses, etc.... I do suspect two things network setup and T2 firmware(or its CPU overloading). BTW, report revision of T2 please. Or its serial.
 

Adam

Well-Known Member
5PLS
My usual -- and preferred -- means of operating an RTK base is via TCP over a cellular modem. Most days it works flawlessly, but every now and then (like today) I'll pull up to a site to take a shot and get a "socket failed" message on the comms screen. I've tried many things to correct this condition, including all of the following:

1. Turn WiFi off and then on again (rarely if ever works);

2. Stop and then restart the RTN (sometimes works, but not reliably);

3. Reboot the TLS (sometimes works, but not reliably);

4. Reboot my phone, which serves as my rover's WiFi access point (sometimes works, but not reliably);

5. Switch action profiles, then switch back again.

6. Reboot the Jetpack at the base (don't remember if that works or not);

7. Reboot the T2 (don't remember if that works or not).

When the problem cropped up today -- after several hours of trouble-free operation -- I tried 1 through 5. (Although I was only a couple of miles from my base and Jetpack, getting to them required hauling out a ladder and climbing up onto my roof, so I didn't try 6 or 7. ) No. 1 didn't work; No. 2 would sometimes work, the TLS would connect and get corrections, but after a few seconds the connection would drop and the TLS would go through the init procedure again, only to generate the "socket failed" message. Nos. 3, 4 and 5 didn't help. Note that I was in a spot with excellent cellular coverage, I could rapidly load web pages on my phone when I tested the connection, and the TLS WiFi showed 100% connection to the access point.

What finally "worked" (in quotes because I don't know if there's really a cause-and-effect relationship) was when I gave up and switched to my CRTN profile so I could at least collect a point. (That connection was rock-solid, but my regional CRTN stations are GPS-only, so I prefer using my own base.) After I got the shot I changed back to my TCP profile, and it worked flawlessly.

Rather than go through this circus every time the problem arises, I'd like to know more about the cause so I can approach the fix in an intelligent manner instead of just throwing everything I can find at it and hope I hit on the right thing. So what actually causes the "socket failed" message, and what's the recommended way of curing it?

Thanks!
It's been really hot here. Any chance the jetpack for the base is getting hot? I know some folks keep there jetpacks in a cooler. Where you using different wifi at the rover when you went to the crtn? If so, this too points to the jetpack at the base.

Edit....just reread and saw number 4.
This really points to an issue with the jetpack itself.

If it works 1 minute but not the next then the next time it works it shouldn't be your settings.
I remember working with you on them getting it set up. All was good then.

That's all I got,I yeild to Eugene.
 
Last edited:

Jim Frame

Well-Known Member
It was a pretty mild day here, high of maybe 85. The Jetpack worked fine for a few hours before the trouble began, and worked fine again after whatever caused the problem ceased, so I'm inclined to think that it wasn't the Jetpack.
 

James Suttles

Active Member
I just replaced a jet pack, last week, because of the same issues. The salesman at Verizon tried to tell me that it was probably the battery. I told him this is a mission critical component, I cannot mess around with trying to figure out if its a battery issues or not, especially when a new Jet pack is $199, without a contract.

The trip to Verizon in order to replace it, cost me more than $199, in just lost time. Plus with Covid19, you have to go through an interrogation process to even get into the store.

Have not had the issue, since, and its used everyday. So I would start looking at the Jet Pack. Ours was not getting hot, it was about 2 years old, so guess they are built to die, around the time the contract expires, go figure.

Note: This is the second one that I have had to replace, from the exact same behavior.
 

avoidthelloyd

Active Member
When this happens to me, I reboot my T2 base and it connects again. It is super annoying. Rebooting the hotspot doesn't seem to work for me so it makes me think it is something in my base. My jetpack is not old but may have gotten hot a couple of times..
 

T.Guisewhite

Active Member
This is happening to me right now...
Dead in the water. Nothing different than the last time it worked.

I am able to measure with the VRS from both LS units... but TCP is a no go...
 

James Suttles

Active Member
Make sure both LS's say they have internet connection..... I have seen it connect VRS, but still show No Internet connection, which makes no sense.
 

Jim Frame

Well-Known Member
What I need to know is complete details of your setup with details about base settings, phone|jetpack rover settings. LS unit should be connected to RAMS JAVADGNSS server. I need to understand networks routing and related setting to assign IP addresses, etc.... I do suspect two things network setup and T2 firmware(or its CPU overloading). BTW, report revision of T2 please. Or its serial.

Sorry, I didn't see this message until just now. My T2 is S/N 00023, and my LS is on RAMS now. Let me know if there's a better time.

Thanks!
 
Last edited:

Adam

Well-Known Member
5PLS
This is happening to me right now...
Dead in the water. Nothing different than the last time it worked.

I am able to measure with the VRS from both LS units... but TCP is a no go...
In Tim's case It was incorrect DMZ. That's the first thing to check.
 

Eugene Aksyonov

Administrator
JAVAD GNSS
5PLS
So far I see that problem on [ JetPack - T2 ] end. LS is trying to reach IP 166.164.157.244 and no route to it. We can leave LS as is and fix JetPack. Then TLS will connect itself automatically.
I need access to JetPack web interface to see what is going on. Can you connect PC to JetPack WiFi and run teamviewer for me?
 
Top