Fix and Float issues

Hi guys,

I have 2 LS's rover and a base. Yesterday I was conducting a straight forward topo survey of a hill with clear line of sight to my base. The issue I have been encountering lately is the flicking between RTK fix and float while trying to store a point, I struggle to even get 1 engine fixed let alone 6...

I didn't check for interference before beginning the job.

Has anyone come across this before?
 

Nate The Surveyor

Well-Known Member
Don't know if it will help you any, but I found a place on a job where I could NOT get a solid fix. I could move 50' away, and BING! We are back in the music. Since then, I have tried to pay attention, but have not knowingly had it happen again.
 

Michael Stazhkov

Developer
JAVAD GNSS
Hi guys,

I have 2 LS's rover and a base. Yesterday I was conducting a straight forward topo survey of a hill with clear line of sight to my base. The issue I have been encountering lately is the flicking between RTK fix and float while trying to store a point, I struggle to even get 1 engine fixed let alone 6...

I didn't check for interference before beginning the job.

Has anyone come across this before?
Also it can be the case when RTK computation rate is higher than transmitted corrections rate. For example you set 5 Hz on the rover but corrections is 1 Hz. A point collecting should not suffer from the issue. Mostly it has effect on the GUI.
 

Sean Joyce

Well-Known Member
I had this issue and it was as Michael mentioned, the corrections rate was wrong.
With the new update I made some new setups and did not send the new one I was using to the base because I thought the correction rate had not changed.With remote assistance Shawn had me running in 5 minutes.
 
Matt, I have a basic understanding yes, have read the section in the quick start guide a few times now and have adopted the 'quick topo' collection settings. I still seem to lose fix when I probably shouldn't... out in the open, plenty of sky for base and rover. What I can't find is the rtk computation rate on the rover? I set the base transmit rate at 5Hz.... I think.....
 

Shawn Billings

Shawn Billings
5PLS
What was the Hz value on the Fix Status button in collect, Blake. This will tell you if you are receiving at the rate you are anticipating. If it is showing 1Hz, then you will see the status go from Fix to Standalone very often. This condition would suggest the base receiver is not broadcasting at 5Hz but the rover is expecting 5 Hz. When the rover isn't getting 5Hz it shows Standalone about 80% of the time. To be clear, was the receiver alternating from Fix to FLT or Fix to STN. It makes a difference in diagnosis.

If it's Fix to STN, I've had a few calls about this lately. Here were the reasons for issues:

1. Triumph-2 OAF was never updated for 10Hz and old firmware was still installed (I realize this is not related to your problem, just putting it out there).
2. In Base Rover Setup, the transmit period was mismatched. The base was set to 1 while the rover was set to 0.2. Since you are not using base rover setup with two LS's, you don't have the mismatch warning that other users have, in this case it is best to go to Advanced as Adam recommends. The location is actually within the General Group profile now, so there is an extra button to get there: Setup>General Group Setup>Advanced RTK, or you can press the hardware button for settings twice.
3. Yesterday was a curious one. It took the customer and me a few minutes to figure out. The wrong modulation was being applied. Make sure that the base is set for D16QAM when running at 5Hz.
 
Thanks for the reply Shawn, Showing 5Hz in the fix status button in the collect screen mate. Sometimes this jumps around too which I found odd. It alternates from Fix to FLT, It has done Fix to STN on occasion, but no where near as frequent as Fix to FLT.

Im trying to replicate the problem at home and also trying to make a video of my issues and take a few screen shots of my settings.

Thanks for all the help.
 
Top