Pre-Processing Messages
Unless specified otherwise, pre-processing checks are conducted before processing begins. If there are any warnings or critical errors, a dialog will appear to describe the issues present. There are three different message types.
-
Critical errors – which will cause a poor solution or prevent processing
-
Warnings – which may cause a processing error
-
Informative messages – typically will not bring up the pre-processing window as these are generally minor and are just for your knowledge
Message Name |
Description |
---|---|
Remote Antenna Setting |
When processing with IMU data, you cannot have the remote antenna settings set to the ARP. With IMU processing, you must enter a lever arm in the processing window and select whether the lever arm is measured to the L1 phase center or to the ARP. For this reason, the Measured height must be zero and the Measured to must be to the L1 Phase Center. By default, the processing dialog will fix this if the Try to fix the issue box is checked. |
Master Coordinate |
When you load a master station, an average single point position is computed. If you enter coordinates that have a large discrepancy to those coordinates, a warning is provided. In this case, before processing, you should review the master station coordinates to ensure that you have entered them properly. You can open the coordinates to review under View | Coordinate/Antenna. |
Corrupt IMR |
This message is typically caused by incorrect file formatting through a third-party application. If you are using a third-party application, review how the file is converted. If you get this issue using the Waypoint Convert tool, contact support at support.novatel@hexagon.com. |
Empty IMR |
This warning notifies you that the IMR file in the project is empty. This is most likely due to third party conversion tools. Verify that the data has properly been converted to the IMR file. |
IMR All Zero Measurements |
This typically occurs when not using the provided convert tool to convert to the IMR format. Changes to the external application used for conversion to fix the issue are typically required to fix this issue. If you see this issue with a SPAN system using the Convert tool, there could be a problem with your raw data collection. Contact support (support.novatel@hexagon.com). |
IMR Blunder Measurements |
Before processing, the Waypoint software checks to ensure that the IMU values in the IMR file are within a reasonable range. If you get this error, the IMU scale factor is likely incorrect. A less likely cause could be from the raw data collection. If it is the latter, contact support (support.novatel@hexagon.com). |
Processing Datum Error |
If you selected the Leica workflow for processing in your preferences, your project must be processed using WGS84. Change the selected processing datum to WGS84 to continue. |
Ephemeris Error |
No ephemeris, precise or broadcast, is present in the project. While precise ephemeris will work as a substitute for most constellations, GLONASS data usage requires the broadcast ephemeris. Use the Download Service Utility to download both precise and broadcast ephemeris, see Download Service Data for more information. |
No NRT file for PPP-AR |
An NRT file is required to perform PPP-AR processing. Without an NRT file, the processor will use the legacy PPP engine. By default, the dialog will try to download the NRT files needed when the Try to fix the issue box is checked. |
Not a NovAtel receiver |
PPP-AR only supports NovAtel receivers for processing. Without a NovAtel receiver. the processor will use the legacy PPP engine. |
Invalid NRT file for PPP-AR |
PPP-AR can only be used if your data was collected after July 4th of 2019 as this is when the new corrections began being supplied. Any survey completed before this date will not be able to use the PPP-AR functionality and will use the legacy PPP filter instead. |
Message Name |
Description |
---|---|
Data Rate |
When processing differential GNSS, the remote and master station data rates should match. If the master station has a lower data rate than the remote, only the common epochs can be processed. By default, the pre-processing dialog will try to fix the issue by resampling the master station. If you want to keep the master station at the lower rate, uncheck the Try to fix the issue box. |
Dual Clock |
Many Trimble receivers use different clocks for their phase and C/A measurements. For this reason, the Waypoint software needs to compensate for the additional possible errors in the solution. By default, the pre-processing dialog will automatically turn the feature on if needed. You can disable the feature from being turned on by unchecking the “Try to fix the issue” box. |
IMR Large Gaps |
Large data gaps (3 or more missing epochs) can sometimes appear in your solution. If they are at the beginning of the survey, the processing time can be adjusted accordingly. If they are in the middle of the project, there are no adjustments that can be made. To check when the data gaps occurred, open the IMR file using the binary viewer under View or by double clicking the file. If you repeatedly see this warning, check your raw data collection and contact support at support.novatel@hexagon.com. |
L2C Present |
This is a message to notify you that there are L2C measurements present in the GPB file. L2C signals have offsets that need to be applied. These offsets differ not only between receiver manufacturers but also possibly between firmware versions. If ARTK continuously fails, this may be due to an improper L2C offset. More information on how to adjust this offset can be found in Edit GPS L2C Phase Correction. |
Too Many Small Gaps |
When processing with differential GNSS, only the overlapping times can be output as common data is needed for computations. This message warns you that there are many data gaps that could impact your solution. If these data gaps impact your solution, you can use the Download utility to get a new master station (see Download Service Data). |
Time Range |
You will receive this warning when the time range supplied by the master station does not cover the entire time range of the survey. By selecting this message, you can see how much time is missing. If it is only a few seconds, you can ignore this message. However, if there is a large time period missing, and it is not intended, we recommend downloading a new master station using the Download utility (see Download Service Data). |
IMU to GNSS Lever Arm |
This error appears if you have not entered any values for your lever arm. The lever arm values should not be zeros. Enter the proper lever arm values or solve for your lever arm values if you do not know the values. |
Secondary Lever Arm |
This error appears if you have not entered lever arm values for your secondary antenna. The lever arm values should not be zeros. Enter the proper lever arm values or solve for your lever arm values if you do not know the values. |
Missing GLONASS Broadcast Ephemerides |
The GLONASS broadcast ephemeris are always required to use GLONASS in a project. The frequency number for the GLONASS SVIDs are required and are only found in the broadcast ephemeris. Therefore, the precise ephemeris cannot replace the broadcast for GLONASS. You can download the broadcast ephemeris to fix the issue. For more information on how to download the broadcast ephemeris, see Download Service Data. |
Message Name |
Description |
---|---|
Ephemeris Check |
Some satellites are missing broadcast or precise ephemerides and cannot be used in processing. You can use the Download Service Utility to download global GNSS precise and broadcast ephemeris, see Download Service Data for more information. Note that GLONASS must have broadcast ephemerides to be used in processing process. |
IMR Small Gaps |
If there are small data gaps (1 or 2 IMU epochs), this warning will appear. Typically, this is seen at the beginning of a survey for which the processing time can be adjusted. If they appear in the middle of the solution, you can generally ignore the warning as a couple of small gaps should not impact the solution. In the case that you get a processing failure with this warning, there are raw data collection issues that need to be resolved, as there are too many small data gaps for the filter to handle. |
No Precise Files |
When processing with PPP, you require precise files to get a proper solution. By default, clicking continue will download the files and add them to the project. If you want to continue without downloading the precise files and use the broadcast ephemeris data, clear the Try to fix the issue box. |
Processing Time Interval |
The processing interval cannot be at a higher rate than the remote data collection rate. Before processing, the Waypoint software will automatically set the processing rate to match the remote data collection rate. |
Master Data Gaps |
When processing with differential GNSS, only the overlapping times can be output as common data is needed for computations. Therefore, if your master station has a data gap then you cannot obtain a solution for the missing time period. You can fix this by downloading a different master station using the download utility (see Download Service Data) or by using PPP. |
IMR Time Reversals |
This warning notifies you that the IMR file has times that run backwards in time and the solution will fail when processing. You will not see this issue with SPAN data as the converter knows how to handle these cases. Only third party IMU users will see this issue. If you are repeatedly seeing this issue , there is likely a raw data collection or data conversion issue. |
IMR Record Repeats |
In most cases, processing should be able to handle repeat records in the IMR file. If you are continuously getting this error or processing is failing, there is likely an issue with either your raw data collection or your data conversion. Contact support at support.novatel@hexagon.com. |