Triump LS not getting fixes like it used to

John Branner

New Member
When the first RTK verification came out it I got verified fixes in difficult environments in short order.(1- 2 minutes) Now it struggles to get fixes in less hostile environments. I use it both as a network rover and with the T2 base. and it does not seem to make much difference. The engines seem to reset with great frequency .
Any suggestions?
 

Matt Johnson

Well-Known Member
5PLS
Hi John have you noticed any issues with the number of Glonass satellites decreasing as shown in RTK 6 pack screen and being less than shown in the satellite status screen after using the LS for a few hours? If this happens resetting the LS will fix it.
 

Shawn Billings

Shawn Billings
5PLS
There are two verify methods: with v6 engine resets and without. Read the manual discussing how the two differ. Basically "with resets" continuously resets until a predefined number of resets has occurred. It requires more time on site but gives more confidence to results. Professional judgment and experience will guide the user on which to use.
 

Matt Johnson

Well-Known Member
5PLS
He is using verify without resets. I looked at his LS briefly last night but I noticed the Glonass issue today with my LS so it may still be an issue.
 

Joe Paulin

Well-Known Member
Hi John have you noticed any issues with the number of Glonass satellites decreasing as shown in RTK 6 pack screen and being less than shown in the satellite status screen after using the LS for a few hours? If this happens resetting the LS will fix it.

During my RTK session yesterday using the T-2 as a base, I experienced this above described behavior with my T-LS.
0039_RTK_V6_20150328-21.38.24.png

This is a screen shot when it was going on. I looked at the satellite screen and it would show the GLONASS satelites, but this screen confirms what was going on. I had to do a hard restart on the LS to fix the problem. Earlier during the same session, I had a problem getting a fix and I looked at this screen and it appeared that the engines were constantly resetting every few seconds. Same thing, I had to do a hard restart. In fact, I had to restart the unit 3 times in about two hours. This is very discouraging. This was, however, during the session where I set up on a base which I had named with a space in it (see my previous recent post in the J-Field Forum) which we now know causes problems. Could you guys shed any light on this problem and the status of it being fixed? Matt, it seems like you have experienced this before according to your quoted post above.

Thanks!
 

Shawn Billings

Shawn Billings
5PLS
You've covered a couple of things I'd like to comment on:

1. The space in the base name issue has been resolved in beta versions and should be available as a release version soon.

2. GLONASS satellite processing issue is being addressed. The developers thought they had it, but the problem persists.

3. Fix to Float. Could be caused by a few things. First, of course, is making sure the base and rover are in open sky. Second, was this during collection (after pressing start) with "V6 Resets" turned on? This is the desired behavior in this scenario as the LS accumulates independent fixes based on user settings. What is the acceptable delay set for? Default is none. This can cause the LS to ignore corrections that are one or more seconds old. You can tell what the acceptable latency is by looking at the button in collect left of the start button. The acceptable latency is show. If it is zero, I'd recommend changing it to 10.
 
Last edited:

Joe Paulin

Well-Known Member
Thanks for all the replies today. It is refreshing to see that these issues are being worked on. Being an end user and not "in the loop" I don't know whats being worked on, so I have been sharing all my issues as they come up. The neat thing is that most of my issues and suggestions are already being worked on!
Shawn, concerning my fix/float issue that I experienced, I have my signal latency set to 15 seconds. This was not during collection. It would bounce from STN to FLOAT to STN back and forth when it should have fixed. My radio connection was fine, and when I looked at the 6 rtk engine screen, it was like the engines were resetting every 2 to 3 secounds with no apparent reason. After I reset the LS, it seemed to be fine. I will pay attention next time I have it up and running and see if it does it again.

Thanks
 
Top