Annoying Hiccup

[Jim Frame]

I've been seeing a problem with some regularity in the last few days. I don't know if it's a problem with the LS hardware or with J-Field software, but I decided to post it here. I'll be going along picking up topo shots using my T2 base and a UHF connection, when for no apparent reason the LS freezes and, after awhile -- meaning something on the order of 30 seconds or a minute -- I'll get this error message:

Even after I hit OK, the system is very sluggish and takes a long time to respond to the Start or Stop buttons. A hard reset seems to fix it, but it's happened at least once per day for the last 4 days.

 

[Matthew D. Sibole]

I have seen this issue as well. However, it has not happened with any regular pattern that I have found.

 

[Jim Campi]

Hi Jim,

I haven't seen this particular error.

Have you tried a force update of system software? I'm not familiar with the OS file structure so I don't know if the path listed in your error message is internal or removrable storage. If removeable, then perhaps the problem is your SD card...

 

[Jim Frame]

If removeable, then perhaps the problem is your SD card...

I had it set to internal memory, not the SD card. This morning I turned recording off, and didn't encounter the problem.

Ever since g-file export became functional I haven't needed to record the rover shots as JPS files, so this is no longer an urgent issue for me. I think it's a glitch worth investigating, though; there may be situations in which users will want the vector data files.

 

[Matt Johnson]

I asked Mikhail Drakin about this error message, he said:

"The error message actually means not file creation error, but a communication problem. It seems to be not connected with our SD/USB file writing problems (though everything is possible in our strange world). Our communication guys will investigated the issue"
​

So this why turning off data recording stops this issue.

 

[Michael Stazhkov]

This is a strange behavior and I am afraid switching off file recording just hid one of symptoms.
Jim, after switching off recording do you have "the system is very sluggish" or "takes a long time to respond to the Start or Stop buttons"?
I mean it could be high CPU usage causes such problems like timeout in communication with internal GNSS receiver.

 

[Jim Frame]

Jim, after switching off recording do you have "the system is very sluggish" or "takes a long time to respond to the Start or Stop buttons"?

No, since I turned off recording the system has been responding consistently well.

 

[Sean Joyce]

I had this same error before the last updates. (I have the current updates now)
Leading up to the error I had started an RTK survey by staking out a previously surveyed point as a check.
The message appeared when surveying the first new point on the session.
Had to shut receiver off and back on to clear the error.
The system worked fine the rest of the day. (no more stakout)
I have noticed that error messages and system freezes that I have experienced are when mixing stakeout and data collection.