Intermittent issues w/ soft keys on Action Screen

[Jim Campi]

Gentlemen,

I have recently noticed that the soft keys on the action screen are not working as intended.

For example, I have programmed one of the on-screen keys to display the current code. This key also conveniently allows me to easily change codes quickly. Lately the key has been brining up the default list of preprogrammed soft key options rather than my code list. Essentially its behaving as though I am presssing the key for several seconds.

Any thoughts on resolving this problem?

 

[Matt Johnson]

Do you have the Level Vial Camera as one of the white boxes? This option puts more demand on the processor and causes this bug. For now the work around is to increase the Long Click Time. This setting is found in: System->Customize

 

[Jim Campi]

Hi Matt,

No on level vial camera.

I'm assuming this doesnt change the workaround.

As a side note, I have also noticed that when the LS is taking longer than expected for a fixed solution, the base rover stats page is empty. No info on any parameters, including base coordinates.

 

[Shawn Billings]

If standalone with no corrections coming in, base rover statistics screen will be empty.

 

[Jim Campi]

If standalone with no corrections coming in, base rover statistics screen will be empty.

Hi Shawn,

I am referring to use in a base rober setup. Do you mean if communication via UHF are temporarily disrupted? In any event, I don't believe thats the case. Corrections are received, there is simply no fix. When a fixed solution occurs, the stats page populates. This is an intermittent problem.

 

[Shawn Billings]

I'll try to watch for it myself. Thanks.

 

[Matt Johnson]

Hi Jim, you aren't going to see any statistics in that screen until epochs are recorded for the point. If you have the mode set to fixed solutions only, then you won't see the statistics until after you have a fix.

 

[Steve Chatelle]

I believe that I am having issues similar to Jim Campi.

The LS seems to function normally for 10-15 minutes after setup, but then degrades. Even in the open it alternates through fix, float, stn. Check the RTK V6 screen, and the table may completely disappear. Just a zero in the brown rectangle. It then may come back and show some engines stn or float or some fixed.

I believe that this is a result of a UHF malfunction. If I stay in the collection screen, the UHF goes yellow & RTK engine shows float, and then the UHF comes back green, but the RTK V6 shows stn. A quick switch to the RTK V6 screen show no V6 table.

Once the performance degrades, the UHF info screen shows the LQ at about 40% and low RSSI even within 300' of the base. I have attached the external antenna and performance improves a bit, but still erratic. We had a Triumph 1 operating off the same base seemingly normally, but I am going to have to verify that later today. I am also going run the LS rover off a Triumph 1 base.

It may be an unrelated issue, but I can no longer get the LS to recognize a thumb drive.

 

[Brett Chappell PLS]

My LS does not recognize a thumb drive either. I have tried a few. Evan after reset with the thumb drive attached, the LS will not recognize it.

 

[Steve Chatelle]

I forced a software update of all six files. I got my thumb drive back, at least after a hard reset. I am not sure which reloaded file reset the USB.

On fix/float/standalone problem, I set up a Triumph-1 rover as well as the LS rover with the Tri-2/HPT401BT base. The Tri-1 rover had the same problem basically - rapidly alternating fixed/autonomous.

I set up a Triumph-1 base on the same point. Both the LS and Triumph-1 rovers performed normally, so I guess my problem is with the Tri-2 or HPT401BT.

How do you clear NVRAM in the Triumph-2? I have not had to do that with this unit yet. Also, I cannot see the firmware file for the HPT401BT. Any help?

Thanks

 

[Steve Chatelle]

My problem has resolved. I cleared NVRAM on the Triumph-2 via NetView, and set up the base to transmit on a different frequency. Before we reset the frequency, we scanned around the frequency that the base was transmitting. The plot looked like the letter M, with the low spot centered on our set frequency. I didn't think to check the scan once it started working on the new frequency. I would expect an inverted V?

The LS is working great again, and reports that the radio Link Quality is over 90% and RSSI is very good.

We have to clear NVRAM now and then on the Triumph-1s when they start acting flaky, so I guess it doesn't hurt the Triumph-2 either.