Verizon Jetpack Hiccup

Jim Frame

Well-Known Member
Installing the driver took care of that.

The only thing in the T2 parameters that didn't seem to match was the encryption type. I changed the Jetpack encryption setting to WPA/WPA2 and will see if that's the magic bullet.
 

Jim Frame

Well-Known Member
I'm still nowhere on the connection. I can ping the IP address, but the LS still goes through the INIT, CONNECTING, CONNECTED, SOCKET FAILED sequence:

WiFi_20170315-23.58.39.png
 

Jim Frame

Well-Known Member
When I look at my T2 through Netbrowser, it shows an IP address of 192.168.1.11, but when I look at the Jetpack's connected devices, it shows the T2 with an IP of 0.0.0.0. When I went in through Netview, I saw that on the TCPO tab all of the output settings were set to "none." (I have no idea how that got changed.) I revised the 8010 setting to RTK RTCM3 3.0 and applied the setting.

Here are my current WLAN and TCPO settings:
t.jpg

t.jpg


The Jetpack settings are still confusing me, as my interface doesn't look like the on in Matt's PDF. The port forwarding setup doesn't permit a range of ports to be entered. This is what I currently have:

t.jpg


But still no corrections coming through...
 

Jim Frame

Well-Known Member
Also, on my T2 the WiFi LED is red, which indicates error.

Edit: Oops, that's the BT light. WiFi is okay.
 
Last edited:

Wes Cole

Active Member
Also, on my T2 the WiFi LED is red, which indicates error.
When Adam/Michael were helping me get my T1M set up for TCP last year we had fits with it connecting to my Jetpack. I had named the Jetpack "Jetpack1" and the unit would never connect to it. If memory serves me we finally renamed it "Jetpack" taking the number out of its name and it instantly connected. It didn't make any sense to me but that's what seemed to fix it. That may not be your problem though.
 

Jim Frame

Well-Known Member
This is the head-scratcher for me right now:

t.jpg


I don't understand why the Jetpack isn't showing the T2's IP address.
 

Jim Frame

Well-Known Member
Can one of you with a Jetpack see if your T2 shows up with a legit IP address under connected devices?

Thanks!
 

Jim Frame

Well-Known Member
Changing the Jetpack name to all letters didn't appear to have any effect.

I did a search on Jetpacks and connected devices and IP 0.0.0.0 and found a reference to a D-Link device that shows 0.0.0.0 when it's a static IP instead of DHCP. Not sure if that's why mine shows 0.0.0.0.

Another question: In my T2 Server setup there's a TCP/FTP Password field. It's currently set to something other than my Jetpack password. Where is the corresponding entry for this on the client configuration found?
 

Jim Frame

Well-Known Member
While I'm displaying my ignorance, if the T2 is set up with a fixed IP address in its configuration, why does the Jetpack have to be set up for DHCP? If DHCP were disabled on the Jetpack, wouldn't it accept the IP address configured in the T2?

(I decided to try this, and then realized that I couldn't access the device's advanced settings because my phone couldn't get an IP address from the Jetpack. The advanced settings -- most of the important stuff -- are only accessible via web browser on an external device. I had to do a factory reset in order to regain control of the device. Oops.)
 

Jim Frame

Well-Known Member
I'm still getting the INIT-CONNECTING-CONNECTED-INIT cycle (the SOCKET FAILED is gone). It occurs to me that this might be because I'm in my office with very few SVs in view. I'll try outside tomorrow.
 
Top