Verizon Jetpack Hiccup

Jim Frame

Active Member
Adam got my Jetpack set up weeks ago, but I was in the office at the time so I couldn't test it beyond verifying that everything seemed to connect. I've been using an RTN connection since then whenever I've needed RTK, but I've got a project coming up for which I'll need to use my own base, so I decided to set everything up in my yard today and make sure the system works.

I got the Triumph-2 and Jetpack going, though I continue to find the whole Connect, To Base/From Base, and Start Base sequence confusing. (I think I need to spend a little more time going through this with manual in hand.) I then got as far as trying to connect the LS rover using my phone as a hotspot (which is what I normally use with the RTN), but the rover kept cycling through INIT, CONNECTING, and SOCKET FAILED. I checked all the settings I could think of, did a lot of head scratching, reloaded profiles and restarted everything a couple of times, but still no joy.

I started to wonder if the Jetpack was working properly, so I launched a network utilities app on my phone and pinged the fixed IP address. The pings came back without delay, and as soon as they did the rover connected and continued to work as expected. I suspect that the sudden change from no connection to connection following the ping was more than coincidence, but I can't offer a rational explanation.

Any other Jetpack users run into this?
 

Adam

Well-Known Member
5PLS
Jim, thanks for posting. I had trouble Friday exactly like you. Remind me what modem you had at the base 791l? And your phone at the rover? I had 791l at the base and 6620 at the rover and thought the problem was only with the 6620 devices. I think this is on the Verizon side of things.
 

Adam

Well-Known Member
5PLS
Adam got my Jetpack set up weeks ago, but I was in the office at the time so I couldn't test it beyond verifying that everything seemed to connect. I've been using an RTN connection since then whenever I've needed RTK, but I've got a project coming up for which I'll need to use my own base, so I decided to set everything up in my yard today and make sure the system works.

I got the Triumph-2 and Jetpack going, though I continue to find the whole Connect, To Base/From Base, and Start Base sequence confusing. (I think I need to spend a little more time going through this with manual in hand.) I then got as far as trying to connect the LS rover using my phone as a hotspot (which is what I normally use with the RTN), but the rover kept cycling through INIT, CONNECTING, and SOCKET FAILED. I checked all the settings I could think of, did a lot of head scratching, reloaded profiles and restarted everything a couple of times, but still no joy.

I started to wonder if the Jetpack was working properly, so I launched a network utilities app on my phone and pinged the fixed IP address. The pings came back without delay, and as soon as they did the rover connected and continued to work as expected. I suspect that the sudden change from no connection to connection following the ping was more than coincidence, but I can't offer a rational explanation.

Any other Jetpack users run into this?
@Michael Glutting check out Jim's post. It appears to not be isolated to me.
 

Jim Frame

Active Member
I have the AC791L at the base, and my Samsung Galaxy S5 at the rover. J-Field version is 2.0.0.332, but I just noticed that 2.0.3.1877 is now available (along with updates to GeoData, GNSS and WinCE).
 

Wes Cole

Active Member
Adam that link says I don't have permission to view the page. I'll check out the notes in jfield tomorrow, didn't realize it was in there. still need to get up with you to reconfigure my TCP connection after I upgraded my firmware. Maybe this week some time?
 

Adam

Well-Known Member
5PLS
J-Field 2.0.3.1877
GeoData 2.1.0.21019
J-Tip 0.0.0.10
GNSS 3.6.7.160919
WinCE OS 7.0.62.7

Since 2.0.0.332:
- Added J-Tip support
- Added possibility to Pause Collect
- Added CoGo Clustering
- Added SPAIN network support in DPOS
- Added restoring tags&codes from Full Backup on another device
- Added 3G\2G support for Verizon Network
- Added auto-connection to last 3 favourite Base Stations
- Added support of networks modes for MC73xx GSM modules (LTE/3G/2G automatic, 3G/2G Automatic, 2G only)
- Base/Rover: added possibility to update the Base receiver firmware and options
- Improved Collect with Verify
- Improved Stake-Out
- Improved Import/Export
- Improved Points and Resources lists
- Improved Localization
- Improved M-Local
- Improved Base/Rover Setup
- Improved DPOS
- Improved GeoData
- Improved CoGo
- Improved UHF frequency scanner
- Improved support of FH915 spread spectrum and SSRX dual band radios
- Improved WiFi
- Improved Software Update
- Improved Keyboard
- Improved stability
 

Jim Frame

Active Member
I updated my LS, but when I tried my Jetpack setup again it did the INIT, CONNECTING, SOCKET TIMEOUT thing again, and this time the ping didn't help it. I wasn't able to get it to work, and eventually gave up. :(
 

Adam

Well-Known Member
5PLS
Jim, do you have a home wifi or some other non Verizon means of getting an internet connection to the LS? I was able to link to my LS on my home wifi and there was no problem. I think Verizon is possibly blocking Verizon to Verizon traffic. It would be good to confirm it if you can.
 

Jim Frame

Active Member
Jim, do you have a home wifi or some other non Verizon means of getting an internet connection to the LS? I was able to link to my LS on my home wifi and there was no problem. I think Verizon is possibly blocking Verizon to Verizon traffic. It would be good to confirm it if you can.
Yes, when I connect the LS via my office network I can connect to the T2 and receive corrections. But then I tried going through my phone and that worked, too, though it didn't earlier today. Color me confused...
 

Jim Frame

Active Member
I tried it again just now and it worked first try. I wish I was confident that it'll do that every time. Not knowing what causes a problem makes you wonder if it's going to come back just when you need an operational system the most.
 

Adam

Well-Known Member
5PLS
Jim, mine has been working yesterday and this morning. Hopefully, Verizon was doing something these past few days and all is good now.
 

Jim Frame

Active Member
I took my Jetpack out for its first real job today. I got all set up and communicating, then took off to start tying in corners. The first shot, about 1,100 feet from the base, was a little dicey, being at the toe of a tall levee and right next to an irrigation standpipe. However, I had tied it last week using an RTN, and that worked fine. Today, though, the LS really struggled, going in and out of fix. I stuck with it for 20 minutes before giving up. I grudgingly chalked it up to a bad constellation.

The next corner was about 2,200 feet from the base and pretty much wide open. But I ran into the same problem, getting a fixed epoch or two and then float, float, float. I got frustrated and gave up on that one, too. I switched back to the RTN and clicked off the shot without trouble.

At the next corner, when the RTN shot was finished, I called Shawn. He asked a bunch of questions and had me read him various settings and status values, but everything looked good. He agreed to think about it, and suggested I might want to call John or Michael, who have been playing with TCP base connections more intensively of late. Meanwhile I drove back to the base to scratch my own head a bit more.

While at the base I took an RTN shot about 10 feet away, then switched back to the TCP connection and took a shot (which fixed right away and stayed fixed) on the same point. Then I compared coordinates: I had the TCP base coordinate about 3 miles from where the receiver actually was sitting. Doh! Once I rectified that, everything worked as expected, and I was able to get the rest of my ties without incident.
 

Shawn Billings

Shawn Billings
5PLS
Good of you to share your struggle, Jim, and the cause.

For readers, be sure to look at 2D delta and delta H in base rover setup. It will indicate if the base position is too far away to be good. As far as I know, J-Field is the only software out there that provides a distance from the programmed base coordinate and the current autonomous position of the base receiver.
 

Adam

Well-Known Member
5PLS
I also like to check the wifi screen. On the right hand side you will see st id and dist, this is the distance from the LS to the Base.
 
Top