What Causes "Socket Failed" Messages?

[Eugene Aksyonov]

At least TCP socket is okay.
Corrections are not coming from port.

 

[Jim Frame]

I thought you were going to tell me!

 

[Jim Frame]

The T2 is on a windowsill with very little sky view (and the LS has even less), so it may not be able to send useful data.

 

[Eugene Aksyonov]

It looks that T2 doesn't transmit any corrections

 

[Eugene Aksyonov]

just no data! Does it getting position at all?

 

[Eugene Aksyonov]

Okay, Start Base and we get corrections!

 

[Eugene Aksyonov]

Don't you aware of starting base is required?

 

[Jim Frame]

I just connected everything, I thought you were doing the investigation. You have the con, Mr. Aksyonov! (That's a Star Trek reference.)

 

[Eugene Aksyonov]

I don't see any issues to fix yet.

 

[Eugene Aksyonov]

I just connected everything, I thought you were doing the investigation. You have the con, Mr. Aksyonov! (That's a Star Trek reference.)

I would like to do it and was serious about to find out, but I could not see a problem yet.
Now it is working, so we suspect that it should stop working at some point in the next few hours, right?
If so, let us catch this situation. and see what is going on. Agree?

 

[Jim Frame]

I'll leave everything connected for now, but note that the problem is *very* intermittent. It has occurred maybe 3 times in the last 6 months.

 

[Eugene Aksyonov]

Having the conn I can log data and analyze it in few hours. How long you can keep this setup?

 

[Eugene Aksyonov]

I saw some intermittent lose of connection 30 minutes ago. It was continuously with small delays. now stopped and behaves stable.

 

[Jim Frame]

I can leave it on for a few more hours if that helps.

 

[Jim Frame]

I'm shutting down for the night. Let me know if you want me to reconnect in the morning (California time!).

 

[Eugene Aksyonov]

It seems no disconnect until you shutdown the unit. I would look at the collected log if you connect unit to RAMS one more time to verify. I think the connection drops on side of JetPack -> Cell provider. I can't watch this more precisely as I need to have access to whole stack of communication channel [ LS -> JetPack -> (Cellular ISP to Internet) -> LS ] simultaneously. I think we should reproduce your setup and test it to exclude any problems on T2 or LS units. If our tests successful this will mean that JetPack or CellProvider has issue of dropping TCP sockets.
Please report JetPack model and It's configuration for Cell Network.

 

[Jim Frame]

The LS is on RAMS now.

The JetPack is a Netgear AC791L. It has a fixed IP address on the Verizon network; is that what you mean by configuration?

 

[Jim Frame]

Taking the system down now...

 

[T.Guisewhite]

In Tim's case It was incorrect DMZ. That's the first thing to check.

so yeah like Adam said my IP address got switched in my Jetpack automatically...I think it did it when a different device connected to it??
I’ve been wondering about a “power up” sequence since this happened. I’m going to only power the base LS & Jetpack until it’s broadcasting. Then I’ll power the rover up.
Anyone else have a sequence they follow?

 

[Jim Frame]

I usually power up the T2 base first, to let it figure out where it is. Then the JetPack, then the LS, then my phone's hotspot. But I don't think this sequence is critical.