Verizon Jetpack Hiccup

[John Evers]

Could J-Field be modified to allow this functionality without the tablet and extra steps? Looks like this would be very useful at times.

I have pondered this for quite some time, and I can not see a way to do it that fits with our current Base/Rover interface. There really is quite a bit going on already in Base/Rover, and to double the amount of configuration options would be a little over the top for most users.

Keep in mind, that we currently have huge capabilities while using Netview. When you use the internet for your communication method, It is possible for your base to be sending out correction messages in many different formats, on different ports, all at the same time. This is rather simple to do with Netview. None of this can be done over UHF. With UHF, you are only sending one message type at a time.

If we add all of this capability and complication to the Base/Rover screens, I am afraid that the vast majority of people will end up unhappy.

FWIW, It takes me less than a minute to Bluetooth my tablet to my T2 base, and turn on RTCM3 Min for Port 8010.

 

[Matt Johnson]

Could J-Field be modified to allow this functionality without the tablet

The Javad NetBrowser will work on any iOS or Android phone so a tablet isn't necessary.

 

[John Evers]

Just a thought...if we added a place in the General Setup, named "Additional Startup Commands"...the user could select a text file to run as a script when performing Base/Rover Setup.

The user could build their script files easily using Netview, import them to the LS from a drive, and then select the file when creating the General Setup profile. No additional interface work would need to be done on the LS. The only programming change to J-Field would be to execute the selected script file after the current Base/Rover startup has completed.

As an example, I just used Netview to save my configuration as a script file, and did a copy/paste. If I could execute the following at the end of UHF startup I would be in business as a TCP Base also:
%dm,dev/tcpo/a% dm,dev/tcpo/a
%em tcpo/a% em,dev/tcpo/a,{rtcm3/1006:10,rtcm3/1008:10,rtcm3/1033:10,rtcm3/1003:1,rtcm3/1011:1}
%dm,dev/tcpo/b% dm,dev/tcpo/b
%dm,dev/tcpo/c% dm,dev/tcpo/c
%dm,dev/tcpo/d% dm,dev/tcpo/d
%dm,dev/tcpo/e% dm,dev/tcpo/e
%/par/net/tcpo/port% set,/par/net/tcpo/port,8010

The user could spend 352 hours studying the GREIS interface manual which I do recommend, or cheat and use Netview to capture the needed text, with the added benefit of never getting syntax wrong.

 

[Shawn Billings]

Used to be that once the port assignment was set that it always sent corrections over that port, I thought.

 

[John Evers]

Shawn,

If you use TCP with base/Rover, when you do a stop base, I believe that the following message is being sent to the base: dm,dev/tcpo/a

If you are only using a UHF profile, and you turn on a TCPO port, it will remain on until you clear NVRAM, or use a TCP profile which does the above mentioned behavior.

 

[Shawn Billings]

Maybe we could just stop sending that message.

 

[Jim Frame]

Could J-Field be modified to allow this functionality without the tablet and extra steps? Looks like this would be very useful at times.

I have pondered this for quite some time, and I can not see a way to do it that fits with our current Base/Rover interface. There really is quite a bit going on already in Base/Rover, and to double the amount of configuration options would be a little over the top for most users.

Keep in mind, that we currently have huge capabilities while using Netview. When you use the internet for your communication method, It is possible for your base to be sending out correction messages in many different formats, on different ports, all at the same time. This is rather simple to do with Netview. None of this can be done over UHF. With UHF, you are only sending one message type at a time.

If we add all of this capability and complication to the Base/Rover screens, I am afraid that the vast majority of people will end up unhappy.

FWIW, It takes me less than a minute to Bluetooth my tablet to my T2 base, and turn on RTCM3 Min for Port 8010.

The above post is 3 years old now. Has the ability to set up both UHF and TCP been streamlined in the interim, or is Netview/Netbrowser still needed to accomplish this? Anyone care to post a step-by-step instruction set?

Thanks!

 

[Adam]

Jim, TCP and UHF can be set up from the LS now. The only thing you may have to do is open up a browser with the jetpack wifi and go to the administrative webpage and set the DMZ address. This can be done with a smart phone or tablet.

 

[Jim Frame]

The only thing you may have to do is open up a browser with the jetpack wifi and go to the administrative webpage and set the DMZ address.

Can you clarify? I don't see a DMZ setting

 

[Jim Frame]

I tried to get this to work this morning, without success. On the initial attempt, I started the jetpack before connecting to the UHF, which didn't work (no corrections from either). Next I tried connecting the UHF first, which enabled me to get corrections, but when I tried switching the LS to WiFi, I got nothing. I tried restarting the T2 with the jetpack profile, which worked, but switching to UHF didn't. I gave up and ran on the jetpack all morning.

When I got back to the base I connected to download, and got a flashing "Downloading" message, but the timer was counting up instead of down, and taking about 3.5 seconds to advance each 1-second digit. After about 6 minutes I looked at the T2 and saw that the BT light was red. At that point I just turned everything off. I'll download the T2 when I get back to the office.

Suggestions?

 

[Adam]

Jim, sorry I wasn't able to take your call earlier today. I will have some time later this evening to help you out. Maybe 2 or 3 hours.

 

[Jim Frame]

Shall l try you again around 4:00 p.m. PDT?

 

[Adam]

That'll be ok

 

[Adam]

Edit to above post......

Jim wanted to start the base with UHF and then be able to swap back and forth from UHF to TCP. This isn't able to be set up via the LS. Netview is needed to start the TCP stream.

@Eugene Aksyonov can we add a check box in UHF base rover setup that will allow the stream to be sent out over TCP simultaneosly?

 

[Phillip Lancaster]

So you want to use UHF and TCP at the base at the same time and there is problems? I'm confused. I've been doing this for years.

 

[Adam]

Phillip, I wasnt able to get it to work on Jims system. I've never really tried it with mine. What are the steps you take?

 

[Phillip Lancaster]

Get his wifi name/password and insert that id into his base to where his base is always looking for that wifi id. Always start his base with uhf and the key is to always end the base with uhf. If for some reason its ended in tcp the port will close so next time. Either netview or what i use is mobile netbrowser to reopen the port. But once started in uhf at anytime you can switch over to tcp.

 

[Phillip Lancaster]

I work closely with another company and all jetpacks have the same wifi id/password so it doesn't matter what base or jetpack we use. And we have all the static ip's profiles in each of our rovers so we just got to know the last 3 digits of base jetpack ip.

 

[Phillip Lancaster]

wifi id and password in base is a one time setup through netview. btw.

 

[Jim Frame]

I have my T2 hooked up to Netview and Modem, and I'm looking to set 8010 output. Is there any reason not to use RTK RTCM3 MSM Full? Is there a better option?