Verizon Jetpack Hiccup

Jim Frame

Well-Known Member
Hmmm...I tried Full but got an error message about a "wrong second parameter" when I attempted to apply it. I then tried RTK RTCM3.0, and that appears to have worked. I'll give it a try tomorrow and see what happens.
 

Jim Frame

Well-Known Member
Things went better today, since I wasn't trying to get any work done and had time to futz around with it. Some questions linger, however.

Last night I used Netview & Modem to send RTCM3 3.0 to TCP0 a 8010 on the T2 and saved the setting. This afternoon I set everything up -- TLS, T2, HPT435BT, and Jetpack -- and started off with UHF, which went fine once I got the TLS more than a dozen or so feet away from the UHF antenna (too close and it didn't work, must be too much RF). However, when I switched to TCP I got nothing. I scratched my head, turned things off, rebooted, tried starting up the devices in a different order, but still no TCP. Then I tried turning the TLS WiFi radio off before switching to the TCP profile, and turning it on after. That worked -- I found I could switch between UHF and TCP as long as I turned off the WiFi radio before changing profiles.

Then I remembered Phillip's comment that you had to end with UHF or port 8010 would close, so I tried ending with TCP and shutting everything down. When I fired everything back up again, I was still able to switch, as long as I turned the TLS WiFi radio off before launching the TCP profile. Happy with the result, I put it all away.

However: just now I hooked the T2 up to Netview & Modem so I could store the settings, and I see that TCPO a is showing no output protocol. I don't know if the TLS TCP profile will open that up again. I'll have to set everything up again tomorrow to see, but in any case I'd like to learn how to open that port while in the field. I tried nosing around Netbrowser on my phone, but didn't see any way to do that. If anyone can point me in the right direction, I'd be grateful.
 

Phillip Lancaster

Active Member
If you have netbrowser (i think its netbrowser) on your phone you can connect via ip and port 8002 with password and control your T2 and turn on/set your ports (8010-8014) to whatever. "end with UHF or port 8010 would close" And that is the reason I set the other ports the same. If you somehow shut down 8010 then just go edit profile in the LS to port 8011, 8012, 8013.....
 
Last edited:

Jim Frame

Well-Known Member
Last night I used Netbrowser's Terminal applet to connect my phone to the T2 (not sure what kind of connection it was, I didn't have to log in and my phone's BT light wasn't on, so likely WiFi) to send a stripped-down version of the script John Evers posted a few years ago. I removed the statement identifiers -- the stuff between the percent signs at the beginning of each line -- as they're not needed and I initially thought I'd have to hand-type the script into the applet. However, I found that I could copy-and-paste the entire script into the applet's command line, and it seemed to work: when I connected via NetView, port 8010 was open and sending RTCM3 min, which I hadn't specified earlier.

When the rain lets up I'll try this away from my office in order to make sure that my office WiFi wasn't responsible for the connection between phone and T2.
 

Jim Frame

Well-Known Member
If you have netbrowser (i think its netbrowser) on your phone you can connect via ip and port 8002 with password and control your T2 and turn on/set your ports (8010-8014) to whatever. "end with UHF or port 8010 would close" And that is the reason I set the other ports the same. If you somehow shut down 8010 then just go edit profile in the LS to port 8011, 8012, 8013.....

What worked in the office didn't work in the field -- I found out the hard way today that simply turning off the WiFi radio in the LS before switching from UHF to TCP isn't enough to keep 8010 open on the T2. I was several miles from the base, but -- somewhat miraculously -- I figured out how to connect over the network using the Netbrowser terminal applet and ran John's script to open the port. Then I was back in business.
 
Top