Problem with the latest software.

Phillip Lancaster

Active Member
Rolled back to 3.6.13 and it's no different. I don't know what to do. I broke my other T1 out of retirement and connected to Carlson and it cleaned up on the points the LS couldn't get. After that I have without a doubt in my mind there is something wrong with this LS. Got back in and upgraded back to the latest release because I cant tell a difference between the two. I'll try it again tomorrow. I hate working weekends but I had to because I'm behind. This weekend was awful.
 

Matt Johnson

Well-Known Member
5PLS
Rolled back to 3.6.13 and it's no different. I don't know what to do. I broke my other T1 out of retirement and connected to Carlson and it cleaned up on the points the LS couldn't get. After that I have without a doubt in my mind there is something wrong with this LS. Got back in and upgraded back to the latest release because I cant tell a difference between the two. I'll try it again tomorrow. I hate working weekends but I had to because I'm behind. This weekend was awful.

Have you tried clearing the NVRAM on the base? Have you checked the satellite status screen? If you have screenshots of this screen and GNSS data to share it would be useful to diagnose the problem.
 

Adam

Well-Known Member
5PLS
Is it recommended to rollback the GNSS firmware to 3.6.13 and if so how do you do it?
The Pre Release version has this and it performs okay. Give it a try.

UPDATE-SOFTWARE-SETTINGS_20180820-12.55.34.png
 

Darren Clemons

Well-Known Member
We've got a 3+ year old LS on Linux and running version 3.6.13 on pre release (although I never had the issues on 3.7.4 like some did). We had it in our typical dirty/dark/nasty spots today and it preformed fine - for where we were and it being late August. We collected about 15 to 20 average to horrible shots under cedars, oaks and thick, thick coverage. Not a spot I'd take any other GPS unit and expect RTK, that's for certian.

Like usual, some took 3 to 5 minutes, some took 15 minutes and we stored PPK on those to verify but ALL of those PPK had an RTK I'm sure of (400 seconds plus). Phillip's, Ron's, Nate's and others issues almost have to be something other than "GNSS version 3.7.4 is bad". I, of course, have no clue what that could be, but it's some combination of specific things in specific units it appears.

I'd be curious to see the video also Phillip if you'd like to share it with me darren3383@comcast.net
 

Phillip Lancaster

Active Member
Of course I say in the video that the sky is wide open which clearly isn't wide open. Just a figure of speech. But I have in the past taken shots that I would bet everything I owned that the little LS would not get a shot and it had no problem. The sky is fairly open. The T1 via Carlson had no problem. This shot would normally be taken with no problems at all. Now, its a problem.
 

Darren Clemons

Well-Known Member
Of course I say in the video that the sky is wide open which clearly isn't wide open. Just a figure of speech. But I have in the past taken shots that I would bet everything I owned that the little LS would not get a shot and it had no problem. The sky is fairly open. The T1 via Carlson had no problem. This shot would normally be taken with no problems at all. Now, its a problem.
Yeah, there's definitely not many places that are even a bit open we worry about the LS getting it. You definitely have an issue. May have to RMA it.
 

Shawn Billings

Shawn Billings
5PLS
Of course I say in the video that the sky is wide open which clearly isn't wide open. Just a figure of speech. But I have in the past taken shots that I would bet everything I owned that the little LS would not get a shot and it had no problem. The sky is fairly open. The T1 via Carlson had no problem. This shot would normally be taken with no problems at all. Now, its a problem.

Phillip, I finally had a chance to peek at your video. I notice that the interference values (on the right side of the LS screen) are pretty high. They seem higher than they should have been in that environment. With values of 5 for L1 and 8 for L2, I'd expect the LS to be able to get the shot but only after camping out for a while. The environment didn't look like 5-8 interference to me. But I could be wrong. Of course, the base site conditions could easily make a performance difference like that.
 

Matt Johnson

Well-Known Member
5PLS
So. What do you think about the video?

I saw the video, it is definitely not what I would consider open sky. There was open sky to the south but trees overhead and trees to the north. Your satellite screen only shows one satellite (GLN19) that definitely appears to have a clear view of the sky and has the full expected signal strength (blue font) for L1, P1, P2 and L2C signals:

1534804450252.png



As compared to a receiver that really has open sky on top of the Javad GNSS factory in San Jose, notice most signals are blue:

STATUSBAR-SATELLITES_20180820-20.45.01.png



Like Shawn said, your base location is very important too. I notice it is 1.61 miles away. The further it is away, the more the receiver will struggle to fix in locations like this.
 

Phillip Lancaster

Active Member
And yet a T1 will fix in this location in less than 30 seconds. So...... there goes that. I am using my Delta cors site. Open sky there.
 

Matt Johnson

Well-Known Member
5PLS
And yet a T1 will fix in this location in less than 30 seconds.

This is very similar to the rate the LS is fixing here too. 10 minutes into the video the sum of the confidence number from all the groups is 22 so there have been approximately 22 fixes and resets of the RTK engines during this period. 10 minutes / 23 = 26 seconds on average for the LS to fix. Remember that Carlson is not resetting the RTK engines as they fix like J-Field is doing.

1534814103376.png
 

Phillip Lancaster

Active Member
So after reinstall. I do believe I see an instant improvement. I will know more tomorrow but I have it on RAMS now and my SS numbers are actually blue and green again.
 
Top