Release 4.0

[Michael N. Sprouffske]

I have two T3's. After running them through the update routine there is no change in the release numbers shown in Netview. Each one has a different number, 4.2.00211012 and4.00.200818. Those release numbers do not change in the Netview screen after running the update. How does one know if the update was installed?

 

[gstjohn]

Today was my first opportunity to actually use v4.0 in the field after working through the glitches. When I first tried to get a TCP connection through my jetpack I got the dreaded "socket failed" message. Looking at the connections screen I saw that the mystery profile named with the IP address of my T2 had reappeared (I had deleted it a couple of days ago) and had a green arrow to the left of it. I deleted it again, restarted the base, and everything worked fine. I was even able to switch between TCP and UHF on the fly without having to send any GREIS commands directly.

Why does this connection keep getting recreated, and how can I prevent it from happening so I don't have to delete it and restart every time I set up?

Hi Jim,
My socket (SOCKET FAILED) has been failing ever since the 4.0 upgrade using TCP with my ATT wifi hotspot that worked before the upgrade. The configuration was set up pre-4.0. Have you had any resolution on this? suggestions?
The IP address repopulates and make itself current in the connections config every time i restart my base with v.4.
Greg

 

[Jim Frame]

Have you had any resolution on this? suggestions?

Great question! The problem seems to have gone away (I suppose it's *possible* that I've gotten so used to mindlessly deleting the bogus profile that I don't even notice it anymore), as I'm not aware of having any trouble in recent months. I haven't been using RTK all that much since summer (maybe 3 or 4 times), but I'm pretty sure I've just been setting up and going without having the mess with changing or deleting profiles. I do know that I haven't had to use my UHF radio in at least 6 months, maybe longer, it's all been via jetpack.

I'll be doing some RTK work on Thursday, so I'll pay attention and report back.

 

[gstjohn]

Well, Mr. Lynch got it working. The problem was on my att wifi hotspot end. The hotspot dmz address that it was using wasn't configured to be in the range of the DHCP settings for the hotspot. The hotspot for the base should be using DHCP but on the rover end, the Auto IP (DHCP settings) for the TCP connection should be 'off' with the IP agreeing with the dmz address on the hotspot. The encryption is WPA2-PSK for the TCP connection.
That being said, the software will always auto-create a wireless LAN profile with the IP address of the base. You just have to switch it to your default Wireless LAN connection profile.

 

[Jim Frame]

Here's what happened today: I setup with my Jetpack and operated normally. Then I shut down the LS, leaving the T2 collecting for OPUS while I did my total station work. When I was done with that (4 hours later) I fired up the LS and got the dreaded "socket failed" error message. I didn't see a bogus profile, but I'm not sure I was looking in the right place -- I'm still not used to the way all the connection buttons work with v4.0. I couldn't figure out how to fix it, but I was done with RTK work so just downloaded the T2 and called it a day.