Trouble with the LS today

John Thompson

John Thompson

Well-Known Member
I had a rough start with the LS this morning. I sent project Yuma to support. (SN229)

When I pressed store point and start base using TCP, the starting base progress went to 85% at which point the notification ditty went off to announce that an update was available. It got to the last note of the tune, then got stuck in an infinite loop repeating that last note and became unresponsive. (As an aside, I wish I could turn that notification off. I find it a distraction and I think that the icon on the support button would suffice.)

I held in the button to power it off and restarted it. When it booted, I stopped the base since it had frozen at 85% and then I restarted the base. Couldn't get Fixed, just STN. Didn't troubleshoot why not, just rebooted the LS. Since the Linux update, it seems like a common occurence that I can't get RTK Fixed when I first start the base, but rebooting the LS is a quick and effective solution. When it rebooted and displayed the home screen, it was again unresponsive. No clicks when I tap the touchscreen, no response from hardware buttons. So I held in the button again to reboot. This time when it rebooted, it was responsive, but it was as if I had done a factory reset. Units were metric, white buttons were gone, U buttons were unassigned. I was able to recall General Group Profile and Action Group Profile. I tried all the options for Favorite Tags & Codes (I couldn't remember which one I was using), but none of them had my list of favorite tags & codes.

I called Matthew Sibole. He was a huge help. He connected with RAMS and got me back up and running. He suggested I go ahead and install the updates, so I did. J-Field went from 3.0.0.199 to 3.0.0.203 and GNSS went from 3.7.4.180724 to 3.7.3.180123. We tried to restore to an earlier point. All of the points we tried said there was no data to be restored. We also found that though we recalled the General and Action profiles (The profiles had the same names as before), it did not change the settings. So the profiles needed to be redefined. I'm still working on finding all the settings and putting things back like they were. I still need to rebuild my favorite codes list. UHF works, but I still can't get TCP to work.

Not sure what happened. I'm grateful for Matthew Sibole and for RAMS. Hope this doesn't happen to anyone else.
 
Adam

Adam

Well-Known Member
5PLS
John Thompson said:
I had a rough start with the LS this morning. I sent project Yuma to support. (SN229)

When I pressed store point and start base using TCP, the starting base progress went to 85% at which point the notification ditty went off to announce that an update was available. It got to the last note of the tune, then got stuck in an infinite loop repeating that last note and became unresponsive. (As an aside, I wish I could turn that notification off. I find it a distraction and I think that the icon on the support button would suffice.)

I held in the button to power it off and restarted it. When it booted, I stopped the base since it had frozen at 85% and then I restarted the base. Couldn't get Fixed, just STN. Didn't troubleshoot why not, just rebooted the LS. Since the Linux update, it seems like a common occurence that I can't get RTK Fixed when I first start the base, but rebooting the LS is a quick and effective solution. When it rebooted and displayed the home screen, it was again unresponsive. No clicks when I tap the touchscreen, no response from hardware buttons. So I held in the button again to reboot. This time when it rebooted, it was responsive, but it was as if I had done a factory reset. Units were metric, white buttons were gone, U buttons were unassigned. I was able to recall General Group Profile and Action Group Profile. I tried all the options for Favorite Tags & Codes (I couldn't remember which one I was using), but none of them had my list of favorite tags & codes.

I called Matthew Sibole. He was a huge help. He connected with RAMS and got me back up and running. He suggested I go ahead and install the updates, so I did. J-Field went from 3.0.0.199 to 3.0.0.203 and GNSS went from 3.7.4.180724 to 3.7.3.180123. We tried to restore to an earlier point. All of the points we tried said there was no data to be restored. We also found that though we recalled the General and Action profiles (The profiles had the same names as before), it did not change the settings. So the profiles needed to be redefined. I'm still working on finding all the settings and putting things back like they were. I still need to rebuild my favorite codes list. UHF works, but I still can't get TCP to work.

Not sure what happened. I'm grateful for Matthew Sibole and for RAMS. Hope this doesn't happen to anyone else.
Click to expand...
John, I might be able to help you get TCP working. Give me a call when you want to try.
 
John Thompson

John Thompson

Well-Known Member
This happened again yesterday. A lot happened yesterday and I came home so tired I didn't even plug in batteries. Now I'm trying to remember the sequence of events.

I've been running on Release versions and I installed updates on Friday 9/14/18. A couple updates were available yesterday morning, but I hadn't yet installed them. Several times yesterday (I think it was at least 4 times) the LS became unresponsive. No screen clicks, no hardware buttons worked. I think it was the second time that that happened that upon rebooting, the settings were gone again. Units, U buttons, white boxes, etc. set to defaults. The names of General Profiles were still there, but if I recall either of the general profiles I had set up (TCP or UHF), the settings are all gone. Both were standalone mode and other default settings. As for Action Profiles, all the profile names are there, but the one I was using was reset to default settings. But if I recall another Action Profile, my settings are still there. Same for Favorite codes lists. All of the profile names are there, but the favorite codes list for the profile I was using got erased. If I recall a different Code & ShapeTags Profile, those favorite codes are still there.

I called Adam. He suggested I install the updates and then connect to RAMS so he could put the TCP settings back so I could finish working. I installed the updates and connected to RAMS. While Adam was on RAMS it again became unresponsive and I had to reboot it. Adam got TCP going so I could continue working, for which I am grateful.

This may be a separate issue, but at one point while Adam was restoring the TCP settings, I was having trouble connecting to the internet via SIM card. Adam suggested moving the card to the SIM 2 slot, which I did. It started working, but there were times both before and after the SIM slot switch that the RTK was having trouble staying fixed. Open skies and practically in the shadow of the cell antenna. I remember at one point having -75dBm on the cell signal level and the GSM box turned red and started counting.
 
Adam

Adam

Well-Known Member
5PLS
John Thompson said:
This happened again yesterday. A lot happened yesterday and I came home so tired I didn't even plug in batteries. Now I'm trying to remember the sequence of events.

I've been running on Release versions and I installed updates on Friday 9/14/18. A couple updates were available yesterday morning, but I hadn't yet installed them. Several times yesterday (I think it was at least 4 times) the LS became unresponsive. No screen clicks, no hardware buttons worked. I think it was the second time that that happened that upon rebooting, the settings were gone again. Units, U buttons, white boxes, etc. set to defaults. The names of General Profiles were still there, but if I recall either of the general profiles I had set up (TCP or UHF), the settings are all gone. Both were standalone mode and other default settings. As for Action Profiles, all the profile names are there, but the one I was using was reset to default settings. But if I recall another Action Profile, my settings are still there. Same for Favorite codes lists. All of the profile names are there, but the favorite codes list for the profile I was using got erased. If I recall a different Code & ShapeTags Profile, those favorite codes are still there.

I called Adam. He suggested I install the updates and then connect to RAMS so he could put the TCP settings back so I could finish working. I installed the updates and connected to RAMS. While Adam was on RAMS it again became unresponsive and I had to reboot it. Adam got TCP going so I could continue working, for which I am grateful.

This may be a separate issue, but at one point while Adam was restoring the TCP settings, I was having trouble connecting to the internet via SIM card. Adam suggested moving the card to the SIM 2 slot, which I did. It started working, but there were times both before and after the SIM slot switch that the RTK was having trouble staying fixed. Open skies and practically in the shadow of the cell antenna. I remember at one point having -75dBm on the cell signal level and the GSM box turned red and started counting.
Click to expand...
How'd it go today John?
 
John Thompson

John Thompson

Well-Known Member
Thanks a bunch for your help yesterday, Adam. I was in the office all day, so I didn't get to use the LS much except to restore settings. I made a list of all the settings I can find that got reset to defaults so that next time I can get back up and running quicker. I hope there isn't a next time. Here is the list so far.

Everything under General Group Profiles including Units and other Advanced Settings
UHF frequencies and call sign
White boxes
U buttons
Antenna Heights MR list
IP addresses MR list
Map View Attributes
Time zone
Show Popup Hints
Overheat Message
Power off on overheat
Receiver Details->Organization (But Operator was not reset.)
Batch Export Settings
Mount Cloud Drive
Load Export Preset
Export Header Line
Average Cluster Points settings
DPOS Show Current Project Base Files Only filter

I made copies of my Action Group profiles and Favorite Codes Profiles so that if they get erased again, I can use Copy As instead of having to rebuild them.

Some of the points I stored in Stake have dN, dE, dU, Distance, and Bearing Attributes. I've never seen that before. Is that a setting somewhere or is that from the latest software update?
 
Adam

Adam

Well-Known Member
5PLS
There is a setting in stakeout accept as to save those offsets as attributes.
 
John Thompson

John Thompson

Well-Known Member
The LS became unresponsive and required reboot 3 times in 4 hours this morning. Fortunately, it never set the settings to default. All 3 times it had just saved a point in Stake mode and was displaying a screen like this.

2018-09-21 07.15.12.jpg

The lower left LED cycled green-red-yellow then went to solid green.
 
John Thompson

John Thompson

Well-Known Member
I don't have permission for that link. Should I move up to PreRelease or Tesing? I kind of like staying on Release until the bugs get worked out.

I have not had any more trouble with settings reset to defaults, but every time I've been in the field, it has become unresponsive 3 or 4 times and I have to reboot. It usually is immediately after storing a point in Stake mode, but not always. I have been storing in Collect mode instead, and there have been two jobs now where points collected in Collect mode were not saved. I think it might be that after freezing up and rebooting that the first point collected in Collect mode is not saved. It reminds me of the problem I had a couple months ago when it wouldn't save the first trajectory.
 
Mikhail Drakin

Mikhail Drakin

Developer
Attributes are saved once and not updated, you can disable saving them in Accept As screen ("Save Offset Attributes"), where you enabled them before (as default setting value is off). If you want offsets updated, enable the "Add Design Coords" option to add source design point coordinates to the created point.

Crashes are not related to camera, there was a problem in system startup sequence, it seems to be fixed now and hopefully soon will be moved to the release branch.
 
You must log in or register to reply here.
Top