A critical operation is planned for later today. What preparations can I make within Verify-QC? After changing the L-band beam my RTCM station list is not fully populated, why is this? Does Verify-QC configure all my LD2/LD2S settings or are some manual entries required? How can I obtain a manual for Verify-QC v1.20? How do I add non-VERIPOS RTCM stations to the Verify-QC software? How do I archive data in Verify-QC? How do I check the version number of my Verify QC software? How do I configure an NTRIP RTCM input in Verify QC? How do I configure Verify QC to compute an Apex (Apex2) solution How do I configure Verify QC to compute an Ultra or Ultra2 solution? How do I extend the duration of or upgrade my Verify-QC dongle? How do I log RINEX data using the Verify-QC software? How do I setup Apex as backup within Verify QC? How do I upgrade my verify QC? How to Import Verify QC Config Files from a USB to an LD6 If I have too many windows open in Verify-QC, could this cause my computer to crash? I have rebooted my LD2, connected to Verify QC using the Ethernet Port and GNSS Rx in Calculation Status has turned red and stayed red. How do I get it green again? Tides - Can I change between Ultra and Apex? Tides - Can I use the Tides information in real-time? Tides - (How) does the Tides calculation compensate for Heave, Pitch and Roll? Tides - How do I configure and View Tides in Verify QC? Tides - How do I convert from MSS Tides to LAT? Tides - How do I know that MSS Tide and Geoid Tide give representative results? Tides - How do I know that the Tides calculation is giving continuous results? Tides-If I restart QC does Tides restart? Tides - We are leaving the work area to make a port call, should I reset Tides? Tides - What Antenna Height should be measured and what accuracy is required? Is this value fixed for the duration of a survey or should it be updated? Tides - What is the vertical reference for the VERIPOS Tides estimates? Tides-When will tides reset? Tides - Where can I find the Tides logging files? Verify-QC for LD6 Version User Manual Verify-QC v1.20 User Manual We have moved to a new area. Why am I not receiving corrections in Verify-QC? What are the new features of Verify-QC v1.20? What are the recommendations concerning Ultra Backup Positions in Verify-QC? What Geoid model is used within the Verify-QC software? What GNSS receivers does the Verify-QC software support? What is the current release verison of the Verify-QC software and where can I get a copy? What is the minimum specification for a PC to run Verify-QC? Is Windows Vista or Windows 7 supported? What is the purpose of the Tides function in Verify-QC? What is the Vio application included with Verify-QC and how can I use it? When I try to start Verify-QC, I receive a warning message about the dongle. What can I do? Why am I not receiving all the expected reference stations in Verify-QC? Why can’t Verify-QC compute an Ultra Position? Why is “Config” missing from my main menu in Verify-QC? Why is one section of the RINEX logging menu of Verify QC greyed out?

How do I add non-VERIPOS RTCM stations to the Verify-QC software?

The following information can be found within the Verify-QC manual (section 4.2.1.8).

Selecting Non-Veripos RTCM stations

Verify-QC is capable of using non-VERIPOS corrections providing that they adhere to the RTCM SC104 V2 format and are from stations coordinated in an ITRF reference frame with a sufficiently high accuracy to ensure compatibility with the VERIPOS reference station network.

Note: VERIPOS cannot guarantee the performance of position calculations that include 3rd party non-VERIPOS RTCM stations.

ERIPOS cannot guarantee the performance of position calculations that include 3rd party non-VERIPOS RTCM stations

When interfacing a non-VERIPOS RTCM source, the Veripos box is unchecked, to provide a new input dialogue box. It will now be possible to add new stations, or edit ones that already exist.

To do this, click on New, and the following New Station dialogue box for defining non-VERIPOS stations will open:

To do this, click on New, and the following New Station dialogue box for defining non-VERIPOS stations will open

Here the station Name and RTCM ID can be entered. The reference station ID should be obtained from the provider of the reference station. If the station ID is unknown then it can be read from the RTCM message header in the Verify-QC IO view once the Device IO settings have been entered. Open View/IO then right click and change the input source to RTCM.

The RTCM ID is stamped at the start of the decoded RTCM header information of each message. In this case RTCM messages with ID 0505 and 0506 are being input:

In this case RTCM messages with ID 0505 and 0506 are being input

Verify-QC requires the RTCM Type 3 (and the RTCM Type 32 from GLONASS stations) to determine the reference station location or it will reject the station data. If the reference station is known not to provide a Type 3 and/or Type 32 message and at a short range, then the user can tick the ‘Local Station’ box. Verify-QC will then use the correction data from the station and assume it is at the users’ location.

The WGS84-PZ90 datum shift used by the reference station receiver is normally automatically detected from the Type 3 and Type 32 messages. Users of the GLONASS functionality can also select the WGS84-PZ90 datum shift between the GPS and GLONASS reference frames. The following options are available:

  • Standard shift (Topcon/Javad default)
  • RTCM shift (RTCM v2.3)
  • NovAtel shift (NovAtel default)
  • Zero Shift

These shifts have the following predefined Helmert parameters:

Shift Standard RTCM NovAtel
dX (m) 0 0 0
dY (m) 0 0 2.5
dZ (m) 1 0 0
rX (rad) 0 0 0
rY (rad) 0 0 0
rZ (rad) -1.00E-06 -1.66E-06 -1.90E-06
Scale 1 1 1

IO Device

Please refer to the Verify-QC manual for further information on setting up the IO Device (section 4.2.1.9) or by pressing F1 when the dialogue is open in Verify-QC which will take you to the appropriate page in the manual.

The IO Device section supports RTCM inputs via Serial Port, Client Socket and Datagram.