The "Devices" list inside the Web App for Point One Navigation's - Polaris service includes a "Health" status which is a rough indicator of how that device is functioning in real time.
 |
"Unknown" Device is not enabled in the web app or unknown(never connected). |
 |
"Action Required" Not currently connected, configuration issue, or network issue. |
 |
"Limited Performance" Device is in "Float" state or "Fixed" with some issues. |
 |
"Good" Device is in a "Fixed" state. |
For more specific information on what your device's status is, click on that device. A drawer should open and inside there you can click on Details.
Grey Status Details :
| Device disabled. To get positioning, enable your device. | Under the Details tab where this message shows up the Enabled option is not a green check. |
| Unknown position. Check device power and connection status. | The system has not seen this device log in. Check your Configuration. |
Red Status Details:
| Check device network connectivity. | No current connection to Polaris open. |
| Check device configuration. | Possible connection but something unexpected happened. |
| Correction data not being used by receiver. Check device configuration. | The receiver is connected and receiving corrections but is not utilizing them. RTK may need to be toggled on. |
| Device connected but no position being sent. Check device configuration. | Connected but GGA/NMEA position message not sent. |
| Positioning failed. Check device configuration and clear antenna obstructions. | Connecting but bad positional message (like lat 0.0 lon 0.0) |
| Positioning failed. Clear antenna obstructions. | Connecting but bad positional message (like lat 0.0 lon 0.0) |
| Carrier phase not in use. Confirm receiver is RTK compatible and clear antenna obstructions. | The receiver is connected but is reporting using DGPS. Possibly the device is connected to another source of corrections while also connected to Polaris. |
Most issues a Red status points to are related to either the device not connecting or in some way not being configured correctly. If you are new to the system please read through our Quickstart Guide for connecting. If you have been using the system for a bit please check our Configuration Settings. Note that the device needs to provide an NMEA/GGA positional message for Polaris to associate it to a corrections stream from a nearby local beacon (True RTK) or emulation(Virtual RTK).
Yellow Status Details:
| Antenna doesn't have line of sight to enough satellites. Clear obstructions for better results. | Device is reporting using 12 or fewer satellites in view in the solution but is reporting a Float or even Fix status. |
| Device too far from base station for RTK fix. Clear antenna obstructions for better results. | Device was associated with a local beacon that is 51+km away using True RTK, <12 satellites in view used in the solution, and unable to achieve a Fix. |
| Position quality may be impacted. Device too far from base station for RTK fix. | Device is associated with a local beacon approaching 100km while using True RTK and unable to achieve a Fix. |
| Check device configuration. | Device is in range of a local beacon and reporting using 12+ satellites in the solution but is only reporting a Float state. A hard reboot might resolve issue or check the configuration. |
| Device is prioritizing IMU positioning data over GNSS. | Device is connected and receiving RTK corrections but is utilizing its internal positioning system. |
Most issues a Yellow status points to are related to the number of satellites available to use in the solution or distance to the source of corrections. Note that a True RTK subscription includes Virtual RTK where available. If you are outside coverage for True RTK but within Virtual RTK coverage you can use the Virtual RTK URL for access. Check our coverage.
In rare cases an unstable internet connection could contribute to a Yellow status.
Green Status Detail:
| Antenna doesn't have line of sight to enough satellites. Clear obstructions for better results. | Device is reporting using 12 or fewer satellites in view in the solution and is reporting a Fix state. |
| Expected accuracy better than 10cm. | Device in Float state using Virtual RTK or Fix state >50km baseline using True RTK. |
| Expected accuracy better than 7cm. | Device in Fix state using Virtual RTK or Float state using True RTK and <50km from local base station. |
| Expected accuracy better than 5cm. | Device in a Fix state using True RTK <50km from local base station. |
Not all troubleshooting options are covered here. If you have issues or even just questions please feel free to Submit a Ticket with our Customer Support team.