SF2 Fallback

IMPORTANT: Do not enable SF2 Fallback in situations where real time kinematic (RTK) accuracy is critical. Accuracy while operating in SF2 mode does not equal the performance of RTK.

PC22009-UN-12JAN16

A - Setup Tab

B - Use SF2 if RTK Signal Lost Checkbox

Enabling SF2 Fallback allows RTK users to transition directly to SF2 after RTK corrections are lost and RTK extend (RTK-X) times out. By default, SF2 Fallback system is off. To enable SF2 Fallback, select StarFire™ 3000 Main softkey > Setup tab (A) > Use SF2 if RTK Signal Lost checkbox (B).

Radio-based RTK: If base receiver has acquired full StarFire™ signal before RTK corrections are lost (average time of 45 min), the rover receiver will go into RTK-X for 15 minutes. After 15 min, SF2 Fallback allows a direct transition from RTK-X to SF2.

Mobile RTK (M-RTK): Since there is no base station, the rover needs to acquire full StarFire™ signal before M-RTK-X is available. M-RTK-X also lasts 15 min with M-RTK before SF2 Fallback is utilized.

Accuracy while operating in SF2 mode is not equal to RTK performance. SF2 Fallback can be enabled or disabled, and used for up to 14 days after RTK corrections are lost. The receiver then defaults to WAAS or EGNOS if available. After 14 days, a connection to RTK is required to use this feature again.

PC22008-UN-12JAN16

SF2 Fallback

Selecting this option will provide RTK users the ability to use SF2 accuracy when RTK is unavailable.

Applications that require RTK accuracy should not use this feature. When returning to RTK corrections, a guidance line jump may be experienced.