This guide is intended for first time Multi-Sensor RTK Module (MSRTK) users and provides an overview of how to handle with the required software, connect to and configure the MSRTK module, and acquire position and attitude solutions.
By the end of this guide, you will be able to acquire a fixed RTK solution using ANavS® MSRTK modules. The steps in this guide should take you about half an hour and should be performed outdoors.
The Multi-Sensor RTK Module (MSRTK) has three different options for power supply.
The first option for power supply is via Powerbank (see Figure 1).
For this option please use the delivered Powerbank (Capacity: 10000mAh) and the USB cable with Typ-C connector at one end.
If more capacity is required, please use Powerbanks without intelligent iSmart technologie.
The second option for power supply is via standard 230V AC Power plug (see Figure 2).
For this option please use the delivered Power adapter and the USB cable with Typ-C connector at one end.
The third option for power supply is via Wires (see Figure 3).
For this option please take care of the polarity(+/-), the voltage-range of 9V – 24V and a minimum current supply of 1A.
The following section describes the different standard connectors and interfaces.
Figure 4 shows the antenna-connections with up to 3 GNSS antennas.
HINT: Please connect for a One-Antenna setup to GNSS 1, for Two-Antenna setup to GNSS 1+2 and for a Three-Antenna setup to GNSS 1+2+3.
Figure 5 shows the standard interfaces lead to the casing:
Special interfaces like UART, CAN, FPGA for incremental-decoder and GPIOs are described in the Knowledgebase-Articles “Developer Information” .
This chapter is intended to properly set-up the MSRTK board for the rover (car, roboter, UAV, etc). The following figure 6 shows a typical setup of the ANavS® RTK- and Attitude Determination sensor fusion.
With three GNSS-antennas on top of the car/rover the software can calculate the yaw, pitch and roll angle of the rover. Furthermore you need a RTK Base Station for streaming correction data. The data of reference station is typically streamed from an ANavS® RTCM Base Station or from an external service-provider with internet-connection or Wi-Fi. The RTK-Baseline defines the centimeter-accurate position of the rover.
This is a very important step of your setup and has an direct impact on the position- and attitude performance of the sensor fusion. The placement of the antennas defines the attitude-baseline (e.q. in figure 6 the baseline b12), that means the yaw, pitch and roll angle of your rover. Please mount the antennas in accordance of your use-case and measure the distances between the antennas (measurement-accuracy < 1 cm). The configuration of the sensor fusion with this measured distances happens in the ANavS® Wizard and is described in the section The ANavS® Wizard to configure the MSRTK Module.
Please pay attention on the following:
* The minimum distance between antennas is 30 cm
* The larger the distance of the antennas, the better is the accuracy of the attitude determination (0.25° heading-accuracy per meter antenna spacing)
* Please align your antennas in the same way. The high-grade antennas have an arrow marked on the bottom for alignment. The orientation of the low-cost patch antennas is defined by the cable-output.
* Please consider and measure also a height-gap between the mounted antennas. We recommend a placement at the same heigth level for the beginning to get familiar with the ANavS® system
* For setups with three antennas (3D-Setup with yaw, pitch and roll angle determination), please use a right-angle measurement equipment to get correct distance measurements
The following figure 7 shows a placement example of MSRTK Module and GNSS antennas in the body-frame of your rover (top-view).
Please pay attention on the following:
* The x-direction shown in this figure is always defining the movement-direction of your rover
* The orientation of the MSRTK Module is fixed defined by the mounted IMUs, please pay attention for this. As one can see in the figure, the SMA-connector of LTE must be orientated in the moving direction
* To get best performance it’s good practice to mount the MSRTK Module in the center of rotation of your rover
Now that you are familiar with the hardware and the system is also properly set-up, the installed software for the ANavS® Wizard can be started. The ANavS® Wizard can be found in the installed folder-structure <Installation-Folder>/ANavS_RTK_Wizard. To be able to configure and receive data of the module, please connect with the WiFi Access-Point “ANAVS_MSRTK_AP” (Password: anavsrtk) of your powered-on MSRTK Module. Please note, the boot time of the Linux-OS is approximately 1-2 min.
Figure 8 shows Step 1 of the ANavS® Wizard application:
Please select the first option “Starting ANavS Sensor Fusion on MSRTK-Module”
Figure 9 and 10 shows Step 2 of the ANavS® Wizard application:
In this step the Wizard is proving the communication between your Laptop/PC and the MSRTK Module. If you get the shown error message in figure 9, please prove again your WiFi connection.
Figure 10 shows the typical window when the WiFi connection is working. One can adjust the settings for the 4G module, the WiFi module and CAN (TBD). The settings are described in the following.
4G-Settings of inserted SIM-Card:
* To use the internal 4G-module, please insert a micro-SIM card into the slot of the MSRTK Module
* The 4G antenna must also be screwed on the board
* After inserting SIM-card and screwing Antenna, please define all necessary informations for dial-in your SIM-card in the mobile-network of your service provider. Information for APN, Dial-UP Number, Username and Password of your service provider can be found in the internet
* To send the information to the MSRTK Module, click the button “SEND CONFIG”
* After that, click “(RE-)START 4G” button. If all provided information for the SIM-card are correct and LTE-reception is available at your position, the “4G Is Inactive” in red becomes “4G is Active” in green.
* The configuration is saved and should connect with mobile-network also after reboot
The WiFi-module is delivered with two different modis.
* Access-Point (AP): The standard way is the Access-Point (AP) functionallity. This means the MSRTK Module spans his own WiFi-Network with the SSID “ANAVS_MSRTK_AP” with Passwort “msrtk”. Please use this mode for your first steps to get familiar with the system.
* Connect to existing Network: Additionally, one can toggle to the functionallity where the MSRTK Module connects to an existing WiFi-Network. To give the information to the MSRTK module, please use the input-boxes for SSID and PASSWORD with the buttons “ADD WLAN-Setting” or “REMOVE WLAN-SETTING”. It’s possible to define a lot of known WiFi-networks. But take care, you must know the assigned IP-address of your MSRTK Module in your network to be able to communicate with the ANavS® Wizard to the MSRTK Module. The new IP must be signed in the file ip_table.conf (<Installation-Folder>/ANavS_RTK_Wizard/ANavS_PAD/configs) in the line IP_MSRTK_module =192.168.42.1, where the IP of the Access-Point functionallity 192.168.42.1 must be changed to the new one. How you can find out the IP of your MSRTK Module and how you connect per WiFi to the RTCM Base Station is described in the article TBD.
Figure 11 shows Step 3 of the ANavS® Wizard application:
You have to define the count of used GNSS antennas mounted on the rover respectively screwed on the MSRTK Module.
The impact of your selection:
1-Dimensional: The attitude is estimated solely using Doppler-measurements and coupled with the IMU-gyroscope (one GNSS antenna connected).
2-Dimensional: The attitude (yaw and pitch angle) is determined using fixed carrier-phase GNSS measurements and coupled with the IMU-gyroscopes (two GNSS antennas connected).
3-Dimensional: The attitude (yaw, pitch and roll angles) is determined using carrier-phase GNSS measurements and coupled with the IMU-gyroscopes (three GNSS antennas connected).
Figure 12 shows Step 4 of the ANavS® Wizard application:
The next step proves the GNSS antenna connection and if the count of founded GNSS antennas match with the previous selected Attiutde dimensionality (Step. 3). You only can go further if it matches in a proper way.
Figure 13 shows Step 5 of the ANavS® Wizard application:
The following figure shows the placement input of your GNSS antennas in the body-frame of your rover (tow-view). Only when everything has been defined correctly, the user can proceed to the next steps (the right arrow on the top right part of the window appears).
Please pay attention on the following:
* The x-direction shown in this figure defines the movement-direction of your rover
* Please measure the distances as accurate as possible. The measurement-error should be below 1 cm
* Defining the z-Axis corresponds to the right-hand-rule. The thumb shows in movement-direction
* For setups with three GNSS Antennas, please use a right angle measurement-tool
* With the Auto-Set button the last configuration is reloaded
Figure 14 shows Step 6 of the ANavS® Wizard application:
In Step 6, for streaming correction data of an (ANavS-)RTCM Base Station in the appropriate RTCM3.X-format, one has to define the correct input-stream. A hint for the suitable input-format notation is given in the Wizard-Window. To facilitate the user input, the last three streams are cached in a selectable history.
Figure 15 shows Step 7 of the ANavS® Wizard application:
The ANavS® sensor fusion is customizable with some specific a priori information.
* For using a priori information about the reference station, an input-option is given here. One has to fill the dimension in the NED (North-East-Down)-Frame format to use this mask. Additionally, the accuracy of the measurement has to be set and needs to be activated with the appropriate button. Use this possibility only if the information is really exactly known and you are introduced in the NED-frame and how you can set this parameter in a correct manner.
* The additional setting “Up-Velocity” is for constraining the velocity mainly in the horizontal plane. One can activate this options for applications like automotive or robotics. Please deactivate this option for UAV-applications or something similiar.
* The additional setting “Heading<->Velocity” is for constraining the velocity mainly to the heading direction. Again, one can activate this option for applications like automotive or robotics but not for UAV-applications.
Figure 16 shows Step 8 of the ANavS® Wizard application:
In the last step of the Wizard, the user can start the ANavS® sensor fusion with the green start-button. But before you start, please check further settings.
* The option “Save solution file” activates saving the realtime sensor fusion solution in a file. The format of the file depends on the selected type of solution output. Furthermore one gets a kml-file, which gives the user the opportunity to see the most interesting information (position, attitude, velocity, and acceleration) in a Google-Earth plot. The files are saved in <installation-folder>/ANavS_PAD/output_data
* The option “Save raw-data” activates saving all processed sensor-data (GNSS, IMU, Barometer, Odometry, Visual-Odometry, …) with highly accurate timestamps to use it for postprocessing. The files are saved in <installation-folder>/ANavS_PAD/output_data
* The option “Activate fast RTK-Fixing” is a fast-mode for RTK-Fixing. But keep in mind that the reliability of RTK-fixing can suffer with this option
* The option “Enable Autostart of RTK-Service” effects an automated start of sensor fusion after booting-up the MSRTK Module with the last configuration. Your setting is transmitted to the MSRTK Module after Start- and Stopping the sensor fusion software with the ANavS® Wizard
* The option “Enable Attitude-Calibration” is only for experts with appropriate support-level. If this option is activated, no sensor fusion is running, but a distance measurement for the GNSS antennas mounted on the rover. This procedure helps to evaluate the correct measurement of GNSS antenna distances but needs expertise to interpret the solutions correctly
* The option “Type of Solution-Output” is exlained in the Developer-Information articles ANavS® Binary Solution Output Format and NMEA Solution Output Format
* The option “Define Output-Port” is described in more detail in the article “TBD”. The default-value is 6001.
* The option “Customer-Code” is only for experts with appropriate support-level. The default-value is 0.
* The option “Output-Rate” is selectable wiht Low (5Hz), Medium(55-65Hz), and High(105-125Hz). The exact rate depends on the used sensors.
After pushing the green start-button for triggering the ANavS® sensor fusion on the MSRTK Module, the ANavS® GUI (figure 17) pops-up and the sensor fusion starts to run. The ANavS® GUI visualizes all sensor fusion estimates per graphs and on a map.
For example, the map shows three different stages of solution estimates:
* SPP-Solution (red): This solution is very inaccurate and a standard car-navi or smartphone solution
* DGNSS-Solution (orange): This solution uses correction data from a reference station but only the inaccurate GNSS pseudoranges. A tight coupling with other sensors (IMU, Odometry, …) is performed.
* RTK-Solution (green): This is the highly precise sensor fusion solution with centimeter accuracy. A tight coupling with other sensors (IMU, Odometry, …) is performed.
Hints for ANavS® GUI handling and some Information:
* Left-Mouse clicking in the Google-Earth plot zooms-in
* Right-Mouse clicking in the Google-Earth plot zooms-out
* The Google-Earth map is only with scale-level 5 meter or higher
* In the Tab “Settings”, one can define the IP-address to which the GUI should connect
* The “Data rate” shows the amount of solution output data streamed to your Laptop/PC
* The “Relative Position” shows the baseline-vector from RTCM Reference Station to your Rover
* A red traffic-light signals that the attitude is not determined
* The “Last corrections” in the left upper corner shows the time since last RTCM correction data was processed. The counter should always be under 10 seconds to get best RTK performance. If no second-counter appears but only “N/A”, there is no connection between MSRTK Module and your RTCM Base Station.
Important to get best performance:
* A gray or red light for the attitude signals that the attitude-solution is not fixed with GNSS phase measurements (no highly accurate attitude information)
* A gray or red light for the RTK-position signals that the position-solution is not fixed with GNSS phase measurements (no highly accurate position information)
* An orange light for Attitude/RTK signals that the sensor fusion solution lost the fixed state and Filters perform in a float mode
*A green light for Attitude/RTK signal that the position and/or attitude is fixed with GNSS phase measurements and a highly accurate solution is available
* Please start movement only with float (orange signal) or fixed (green signal) mode