LS+ Freezing up randomly

aaronf187

New Member
Hello all, I'm running an LS+& T3 base. Had it for around 3 weeks now and just in the past few days it has been freezing up on us. We start the base and shoot a couple of shots like always, then it will randomly kick itself from the action screen to showing the "Yocto" home screen and not do anything. You have to hard re-boot it. From here, it will freeze 4 to 5 more times after going to the Action screen before it finally fixes itself. I never have to restart the base.

Anyone chime in on this? Software issue? Anyone else having similar problems? I mostly want to make the developers aware of this.
 

Adam

Well-Known Member
5PLS
Aaron, it is a issue they are looking into. Perhaps you can set your unit up on RAMs so Moscow can look into it sometime? Just respond here to let @Eugene Aksyonov know when it is on.
 

Michael Stazhkov

Developer
JAVAD GNSS
Hello all, I'm running an LS+& T3 base. Had it for around 3 weeks now and just in the past few days it has been freezing up on us. We start the base and shoot a couple of shots like always, then it will randomly kick itself from the action screen to showing the "Yocto" home screen and not do anything. You have to hard re-boot it. From here, it will freeze 4 to 5 more times after going to the Action screen before it finally fixes itself. I never have to restart the base.

Anyone chime in on this? Software issue? Anyone else having similar problems? I mostly want to make the developers aware of this.
Please tel your receiver serial number. And could you send the project to support.
 

aaronf187

New Member
Another LS+ Problem, We located a corner, let it run through and accept itself. Now its gone in the point files, but I can see the screenshot of where It saved it. What gives?
This could have cost us another half a day of going back out to locate what we already shot!
 

Michael Stazhkov

Developer
JAVAD GNSS
Another LS+ Problem, We located a corner, let it run through and accept itself. Now its gone in the point files, but I can see the screenshot of where It saved it. What gives?
This could have cost us another half a day of going back out to locate what we already shot!
Could you send the project to support and tell the point name / file / screenshot.
 

aaronf187

New Member
I'm sending the "Application Log" Now...the point name is 100, but the coordinate differs from the screenshot that says point 100.
Point 100 "Saved" is N:3,398,028.259 E:10,396,786.298 but the Screen shot file (20200928-22.48.56_100) has the correct coordinate of N:3,398,017.655 E:10,396,932.2007
 

Michael Stazhkov

Developer
JAVAD GNSS
I'm sending the "Application Log" Now...the point name is 100, but the coordinate differs from the screenshot that says point 100.
Point 100 "Saved" is N:3,398,028.259 E:10,396,786.298 but the Screen shot file (20200928-22.48.56_100) has the correct coordinate of N:3,398,017.655 E:10,396,932.2007
I need your project, not the application log (Projects screen -> "Send Project to Support" button)
 

Adam

Well-Known Member
5PLS
I'm sending the "Application Log" Now...the point name is 100, but the coordinate differs from the screenshot that says point 100.
Point 100 "Saved" is N:3,398,028.259 E:10,396,786.298 but the Screen shot file (20200928-22.48.56_100) has the correct coordinate of N:3,398,017.655 E:10,396,932.2007
Highlight the point and tap the chart button under DPOS. Are there 2 solutions there? If you have prefer rtpk checked it would show the rtk coordinate at the bottom of the screen but save the rtpk solution.
 

aaronf187

New Member
Thanks Adam, I know exactly what you are talking about and there is an RTK & RTPK (Now PPK since I sent to DPOS) solution for each point. This seems to have over-wrote my original point 100. I'm sure there is a chance that I could have deleted the point by accident, and it just saved the original screen shot of that point, but I never delete points...ever!
My partner and I both remember inversing and checking to line how close certain fence post corners were to pipes found so we knew exactly where it should have been. Luckily the screen shot saved us.
 

Adam

Well-Known Member
5PLS
This seems to have over-wrote my original point 100.
I think DPOS auto selected the ppk solution for you. When DPOS'in always review the points to make sure the solution you want is selected. You should be able to select the rtk solution by tapping the radio button in the chart screen.
 

aaronf187

New Member
I think DPOS auto selected the ppk solution for you. When DPOS'in always review the points to make sure the solution you want is selected. You should be able to select the rtk solution by tapping the radio button in the chart screen.
Right, But in this case its 145 feet away and is completely missing. I understand the PPK and RTK choosing for me, but usually in the wide open they only differ by a few hundredths.
The point I'm after is just missing altogether
 

Adam

Well-Known Member
5PLS
I see, you didn't happen to press accept instead of accept as in stakeout did you? The saved point would be under the design points if so.
 

aaronf187

New Member
I see, you didn't happen to press accept instead of accept as in stakeout did you? The saved point would be under the design points if so.
In this case no, because we had nothing to stake out for. But yes If in stakeout mode I stake to-then go back to regular collection screen as I don't like the over-writing of the design points in stakeout collection mode.
 

Adam

Well-Known Member
5PLS
In this case no, because we had nothing to stake out for. But yes If in stakeout mode I stake to-then go back to regular collection screen as I don't like the over-writing of the design points in stakeout collection mode.
You don't have to "overwrite the design point" if you tap the compass button, then how to stop, then check accept as.
 

aaronf187

New Member
Update on freezing issue. I've noticed it struggles when you open the action screen, or map screen from the point list. I disabled the "Worldlite" background map image and I have not had freezing issues since then. But I still have random touch screen issues.
 
Top