DIY Onocoy Ntrip Server and Reference Station Setup

DIY Onocoy Reference Station Setup Guide

In this guide, we’ll walk you through the process of setting up your own GPS Onocoy server using cost-effective hardware options and reliable GPS receivers. Whether you’re interested in enhancing the accuracy of your location-based applications, conducting precision surveys, or simply exploring the world of DIY technology, this guide provides step-by-step instructions to help you get started with creating your DIY Onocoy reference station.

What is Onocoy?: Advancing GNSS Correction Data #

Onocoy is an innovative platform that harnesses GNSS devices and correction data to create a decentralized network for precise positioning and navigation. It offers users the opportunity to contribute to this network while earning rewards based on their data contributions.

Enhancing Your GNSS and RTK Setup #

Onocoy offers a fresh perspective on GNSS stations. Beyond pinpoint accuracy, it’s about becoming part of a global network that benefits users worldwide. Discover the key considerations for setting up your station: from selecting the right equipment to optimizing antenna placement and ensuring reliable internet connectivity.

Contribution and Rewards #

At its heart, Onocoy not only improves accuracy but also recognizes your contributions. Uncover how your role in enabling specific NTRIP messages and maintaining low latency translates into tangible rewards. Onocoy’s approach ensures a fair distribution of rewards through blockchain technology, providing transparency in recognition.

Understanding Onocoy’s GNSS Capabilities and Requirements. #

Exploring the GNSS capabilities of Onocoy sheds light on the diverse channels and bands it supports. As a rule of thumb, a broader range of bands and constellations translates to enhanced rewards within the network. For an in-depth understanding, refer to the insights shared in section 4.2.1 of the whitepaper, which is accessible on LinkedIn here and soon on the official website.

Update rates, a crucial factor, cater differently to miners and RTK Rovers, who are the data consumers utilizing the Onocoy service. Miners find stability with a rate of 1Hz, ensuring steady data contribution. In contrast, higher update rates like 10Hz, 20Hz, or even 100Hz predominantly serve RTK Rovers’ needs for real-time precision.

Addressing the notion of minimum required position accuracy, Onocoy adopts a pragmatic approach. Straying from stringent demands, the system’s meticulous processing accurately determines device positions during validation steps, ensuring reliability without undue accuracy expectations.

Signal-to-Noise Ratio (SNR) and signal levels emerge as pivotal factors. SNR above 40 dBHz, preferably reaching around 45 dBHz, signifies optimal performance. Lower SNR values, stemming from factors like extended cables or antenna quality, can elevate code/carrier noise, potentially affecting measurement quality. Two fundamental principles guide this aspect:

• Ensuring an unobstructed 360-degree sky view for the antenna, ensuring unhindered signal access.
• Aiming for a secure and stable antenna mount to counteract vibrations and instability.

This comprehensive approach forms the bedrock of reliable and robust data contribution to the Onocoy network.

Why DIY a Onocoy Reference Station? #

Creating your own DIY Onocoy reference station offers several compelling advantages. Firstly, it provides a cost-effective solution, enabling you to save on setup expenses while achieving high precision in location-based applications. Secondly, the customization options allow you to tailor the hardware and software to your specific needs, enhancing flexibility and adaptability. Moreover, DIY setup empowers you with a deeper understanding of the technology, enabling you to troubleshoot and innovate. Lastly, contributing to the Onocoy network not only improves your own accuracy but also lets you play a vital role in advancing global navigation systems while earning rewards for your data contributions.

Ideal Setup Setup For Onocoy #

For Onocoy, we recommend the following components for an optimal setup. This combination ensures high precision, versatility, and reliable performance.

This combination ensures a powerful computing platform with the Beelink U59 Mini PC, coupled with the high-precision positioning provided by the UM980 RTK GNSS USB Dongle and the reliable performance of the HARXON CSX627A Triple Band RTK Antenna. The recommended GNSS USB Dongle is our preferred choice for its exceptional precision and features, making it the ideal solution for Onocoy applications.

Below we’ve included other alternatives.

Recommended Hardware for Onocoy: #

One of the following is required. We basically just need any efficient and low powered computer we can get our hands on that also runs Linux. Any Raspberry PI, Intel NUC, or similar will do. They don’t have to be all that powerful. However, we will recommend you have at least 32g-64g of flash-based storage (for longevity of the SSD). For this, we will be targeting a budget of around $50-$200 for compute hardware, but feel free to go higher if it suits your needs. Our power target is approximately 10w average.

Raspberry Pi and Pi Clones: #

Hard to get ahold of these days but they are super low power and are quite customizable. For info on how to install Raspbian on your Raspberry PI.

Any Mini PC with Intel N5100 or similar: #

For super low power Raspberry Pi equivalent but on x64 platform.

Ultra Low Power / Low Budget #

Compute Notable Mentions #

Older Raspberry Pi models (1, 2, 3) should be sufficient. But newer models should be significantly more efficient and allow you do run multiple low powered mining setups on a single device. This is why we recommend newer compute hardware.

Recommended GPS Receivers for DIY Onocoy Deployments #

There are many receivers on the market but at a bare minimum it must support RTCM (Radio Technical Commission for Maritime Services) and ideally have the ability to be hooked up to an antenna outside of the install location with 360 degree unobstructed view of the sky.

• U-Blox Based Receivers
  • NEO-M8P RTK GPS GNSS receiver board with SMA and mini USB for UAV, Robots - $150
    • Single-Band (L1 only), 72 Channels, supports USB; I2C; and UART, Accurate within 6 feet, 10hz pull rate. Rewards will be limited, 8-10% only.
    • Shows up as /dev/ttyACM0 instead of /dev/ttyUSB0 in the instructions below. Same goes for all U-BLOX based devices.
  • NEO-F9P-15B Multi-band - $220
    • Dual-Band L1+L2 (or L1+L5), 184 Channels, supports USB only, Accurate within 6 feet, 20hz pull rate. Rewards will be limited, 30% of possibly maximum rewards.
  • SparkFun GPS-RTK Board - NEO-M8P-2 (Qwiic) - $180
    • NEO-M8P-2 Based, Single-Band (L1 only), 6 Foot Accuracy. Rewards will be limited, 8-10% only.
  • SparkFun GPS-RTK-SMA Breakout - ZED-F9P (Qwiic) - $275
    • ZED-F9P Based, Dual-Band L1+L2 (or L1+L5), 184 Channels, 20hz pull rate, USB or GPIO Breakout. Rewards are limited, 30% of possibly maximum rewards.
  • ZED-F9P RTK GNSS receiver board with SMA Base or Rover - $210
    • ZED-F9P Based, Dual-Band L1+L2 (or L1+L5), 184 Channels, 20hz pull rate, USB Only. Rewards are limited, 30% of possibly maximum rewards.
• Unicorecomm UM980/UM982 Based USB Receivers The preferred option overall and by far for almost every setup. Requires FTDI Drivers .
  • (Preferred) UM980 RTK GNSS USB Dongle - $225
    • Unicorecomm UM980 Based, Triple Band L1, L2 and L5, All-Constellation, High Precision, 1408 Channels, 20hz pull rate, 80% Rewards.
    • Use discount code SIMEONSECURITY_GNSS for an additional 5% discount.
  • (Preferred) UM982 Dual Channel RTK GNSS USB Dongle - $235
    • Unicorecomm UM982 Based, Triple Band L1, L2 and L5, All-Constellation, High Precision, 1408 Channels, 20hz pull rate, 80% Rewards.
    • Use discount code SIMEONSECURITY_GNSS for an additional 5% discount.

Advanced Receivers for DIY Onocoy Deployments #

These are all going to be devices that are Triple-Band, High Pull Rate, Extreme Position Receivers. They likely won’t support USB. They will require PCI-E, UART, I2C, or Serial Connections. If you don’t know what that is or you aren’t experienced, please use the options above. However these will allow you to be capable of at most 80% of Onocoy Rewards in the case of the Unicorecomm UM980 and Unicorecomm UM982 based boards and 100% of rewards in the Septentrio Mosaic X5 based boards. While you’ll be able to use the same software we mention below, the instructions we’ve provided won’t exactly line up. Be advised.

• Unicorecomm UM980 Capable of 80%-90% of the Onocoy rewards if installed correctly. 100% is possible after planned future firmware update. Fimware updates are dependent on the manufacture of the device providing them. Unicorecomm will not provide them to the public.

  • UM980 module + DSD TECH SH-U05A USB to I2C + GH1.25 to Dupont2.54 Pre-Crimped Cables - $180 - $220
    • Unicorecomm UM980 Based, Triple Band L1, L2 and L5.
    • For more details on how to install this, we recommend you read this article on how to set up the I2C connection on the UM980
    • Don’t expect the aliexpress manufactures to be able to provide firmware updates.
  • UM980 M.2
    • Unicorecomm UM980 Based, Triple Band L1, L2 and L5.
    • May not be recognized by all systems, it uses USB protocols over M.2
    • Use discount code SIMEONSECURITY_GNSS for an additional 5% discount.
  • UM980 mPCIe
    • Unicorecomm UM980 Based, Triple Band L1, L2 and L5.
    • May not be recognized by all systems, it uses USB protocols over mPCIe
    • Use discount code SIMEONSECURITY_GNSS for an additional 5% discount.

• Unicorecomm UM982 Capable of 80%-90% of the Onocoy rewards if installed correctly. 100% is possible after planned future firmware update. Fimware updates are dependent on the manufacture of the device providing them. Unicorecomm will not provide them to the public.

  • UM982 M.2
    • Unicorecomm UM982 Based, Triple Band L1, L2 and L5.
    • May not be recognized by all systems, it uses USB protocols over M.2
    • Use discount code SIMEONSECURITY_GNSS for an additional 5% discount.
  • UM982 mPICe
    • Unicorecomm UM982 Based, Triple Band L1, L2 and L5.
    • May not be recognized by all systems, it uses USB protocols over mPCIe
    • Use discount code SIMEONSECURITY_GNSS for an additional 5% discount.

• Septentrio Mosaic X5 Capable of up to 100% of the Onocoy rewards. Requires already available firmware update .

  • mosaic-go GNSS module receiver evaluation kit
    • Septentrio Mosaic X5 Based, 50-100hz Pull Rate, Anti-Interference, Anti-Jamming, Anti-Spoofing.
  • (Preferred) simpleRTK3B mPCIe
    • Septentrio Mosaic X5 Based, 50-100hz Pull Rate, Anti-Interference, Anti-Jamming, Anti-Spoofing.

Recommended Antennas for Onocoy #

We’ve covered this in a more in depth guide about the Best GPS Base Station Antennas .

Basic Antennas for Onocoy #

For U-Blox based receivers, we recommend the following antenna options to enhance GPS navigation accuracy.

Advanced Antennas for Onocoy #

Antenna Options for Recommended GNSS Receivers: #

For optimal performance with the recommended GNSS receivers, we suggest the following antenna options to ensure accurate and reliable navigation.

OS Installation: #

We won’t go into the technical details of how to install an operating system here. However here are some great resources to get you started.

Raspbian: #

• Getting started
• The New Method to Setup Raspberry Pi

Ubuntu: #

• Install Ubuntu desktop
• Ubuntu Server - Basic installation
• Ubuntu Complete Beginner’s Guide: Download & Installing Ubuntu

Proper Onocoy Base Station Antenna Placement #

Onocoy has published antenna placement requirements , but to summarize you should understand the following:

1. Optimal Location Selection: To optimize station placement,** choose a location at least 20 kilometers away from the nearest Onocoy station**. Stations located close to three or more others will receive reduced rewards. Utilize the Onocoy Explore function to easily check the distance to the nearest Onocoy station for any location.

   

2. Ideal Surroundings: Ensure that the antenna has an unobstructed 360-degree view of the sky, with no obstructions such as buildings, trees, or mountains above 10 degrees elevation. Limited sky visibility or signal multipath can result in scaled-down rewards. The antenna must be rigidly mounted to prevent movement exceeding 1-2 millimeters, as excessive vibrations or movement can lead to reward pausing.

3. Stable Internet Connection: Maintain a stable and permanent internet connection for the station. The required bandwidth is relatively low, typically around 1 kB/s, and no inbound traffic is necessary. There is no need to open ports on typical firewalls, as connections are established from inside-out.

Setting up the Onocoy Base Station and NTRIP Software #

Once you’ve set up your device and properly placed your antenna , you can start configuring the required software.

For this section we assume some basic technical experience and that you have installed your operating system already as well as know how to get into the terminal.

1. We need to create an account and get our credentials from the onocoy website . You will need to grab the server address, username, password, and port number from this step. Once it is completed, go to the reference station tab and grab the mount point, which we also need.

• Refer to the Onocoy documentation if you need help.

2. Install some base dependencies.

   sudo apt install -y gpsd gpsd-clients minicom socat git make build-essential
   

3. Follow one of the Options Below. Either NTRIP Server or RTKLIB

4. Wait and Verify Your Station on the Onocoy Dashboard

   1. Visit the Onocoy Console Dashboard and check to see your device has finished it’s validation period. If it hasn’t check back later, it can take up to 3 days.

5. Profit?

   1. You can view the following Onocoy documentation to learn more.

Option 1: NTRIP Server #

1. On your linux device download the ntripserver software.

   git clone https://github.com/simeononsecurity/ntripserver.git
   cd ./ntripserver
   make
   

2. Identify the USB Source

   1. Idendify that linux recognizes the device is plugged in.

   lsusb
   

   Ex. Bus 00x Device 00x: ID xxxx:xxxx Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P or Bus xxx Device xxx: ID xxxx:xxxx U-Blox AG [u-blox 8]

   2. Identify the propper ttyUSB/ttyACM path. Note: Some devices may show up as ttyUSB0, ttyACM0, etc. You’ll have to look this up per your device.*

   ls /dev/ttyUSB*
   

   Note: Minicom is a tool used to view the serial output of devices. To use it, you’ll need to read this guide on using minicom . If this sounds difficult to you, skip this step.

   sudo minicom -D /dev/ttyUSB0
   

3. Now we get to configure the software

Note: The onocoy dashboard/explorer won’t provide you with the mountpoint information until they verify you can send them data. Omit the mountpoint details from this section until after you initially get past that window. Then test it again.

1. Test the configuration.

       ~/ntripserver/ntripserver -M 1 -i /dev/ttyUSB0 -b 921600 -O 1 -a servers.onocoy.com -p 2101 -m {{mountpointhere}} -n {{usernamehere}} -c {{passwordhere}}
   

2. Now that you confirmed it works. We need to create a service to have it restart on boot.

   1. Create a Service File:

   sudo nano /etc/systemd/system/ntripserver.service
   

   Remember to replace /path/to/ntripserver with the actual path to your ntripserver executable.

   [Unit]
   Description=NTRIP Server Service
   After=network.target
   Wants=network-online.target
   After=network-online.target
   
   [Service]
   ExecStart=/path/to/ntripserver -M 1 -i /dev/ttyUSB0 -b 921600 -O 1 -a servers.onocoy.com -p 2101 -m {{mountpointhere}} -n {{usernamehere}} -c {{passwordhere}}
   Restart=always
   RestartSec=120  # 2 minutes (in seconds)
   TimeoutStartSec=300 # Set a 5-minute timeout (adjust as needed)
   User=root
   
   [Install]
   WantedBy=default.target
   

   2. Enable and Start the Service:

   sudo systemctl enable ntripserver.service
   sudo systemctl start ntripserver.service
   

   3. Check the Service Status:

   sudo systemctl status ntripserver.service
   

   ex.

   ntripserver[815]: serial input: device = /dev/ttyUSB0, speed = 921600
   systemd[1]: Started NTRIP Server Service.
   ntripserver[815]: caster output: host = xxx.xxx.xxx.xxx, port = 2101, mountpoint = Mount1, mode = http
   ntripserver[815]: transfering data ...
   

Serial Connection Settings #

Note: Always consult your receiver manufactures documentation to get the correct serial connection information such as baud rate, data bits, partity, and stop bits.

Known Default Serial Settings for the Following GPS Receivers

Option 2: RTKLIB #

1. On your linux device install the rtklib software.

   sudo apt-get update
   sudo apt-get -y install rtklib
   

2. Identify the USB Source

   lsusb
   

   Ex. Bus 00x Device 00x: ID xxxx:xxxx Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P or Bus xxx Device xxx: ID xxxx:xxxx U-Blox AG [u-blox 8]

   Note: Some devices may show up as ttyUSB0, ttyACM0, etc. You’ll have to look this up per your device.

   ls /dev/ttyUSB*
   

   sudo minicom -D /dev/ttyUSB0
   

3. Create a Rtkrcv.conf RTKLIB Configuration File

   1. Create the paths and conf file

   sudo mkdir ~/rtklib/
   sudo nano ~/rtklib/rtkrcv.conf
   

   2. Conf File Contents

   Note: The onocoy dashboard/explorer won’t provide you with the mountpoint information until they verify you can send them data. Omit the mountpoint details from this section until after you initially get past that window. Then test it again.

   [serial]
   port = /dev/ttyUSB0
   bitrate = 921600
   [ntrip]
   caster = servers.onocoy.com
   port = 2101
   mountpoint = {{mountpointhere}} 
   user = {{usernamehere}}
   passwd = {{passwordhere}}
   [output]  
   format = rtcm3
   path = /path/to/output/file.rtcm
   

   3. Test the RTKLIB config

     rtkrcv -s -o ~/rtklib/rtkrcv.conf
   

4. Create the RTKLIB Service

5. Create the Service Unit File bash sudo nano /etc/systemd/system/rtklib.service

6. Add the Service Configuration ```toml [Unit] Description=RTKLIB Service After=network.target Wants=network-online.target After=network-online.target

[Service]
ExecStart=/path/to/rtkrcv -s -o /path/to/rtkrcv.conf
Restart=always
RestartSec=120  # 2 minutes (in seconds)
TimeoutStartSec=300 # Set a 5-minute timeout (adjust as needed)
User=root

[Install]
WantedBy=default.target
```

3. Enable and Start The Service bash sudo systemctl daemon-reload sudo systemctl enable rtklib.service sudo systemctl start rtklib.service
4. Verify the Service bash sudo systemctl status rtklib.service

Serial Connection Settings #

Note: Always consult your receiver manufactures documentation to get the correct serial connection information such as baud rate, data bits, partity, and stop bits.

Known Default Serial Settings for the Following GPS Receivers

Option 3 (The Easiest): Docker Container #

1. Install Docker #

Consult the following guides for more information on how to install docker

• https://www.digitalocean.com/community/tutorial-collections/how-to-install-and-use-docker
• https://docs.docker.com/engine/install/
• https://docs.docker.com/engine/install/ubuntu/

2. Run the Docker Container #

Run the Docker container, ensuring that you provide the necessary environment variables and parameters:

> You don't have to specify both Onocoy and RTKDirect credentials. The backend script is smart and looks to see if they have been set. You can use one or both and this should function perfectly.

If the environment variable ONCOCOY_MOUNTPOINT or ONOCOY_USE_NTRIPSERVER or RTKDIRECT_USE_NTRIPSERVER is specified, the docker container will use NTRIPSERVER for Onocoy or RTKDirect respectively, otherwise it’ll use RTKLIB for the connection to Onocoy and/or RTKDirect. The container will still use RTKLIB for the splitting of the feed no matter what. LAT, LONG, ELEVATION, INSTRAMENT, and ANTENNA are all optional and are only used if RTKLIB is being used and NTRIPSERVER is not.

You may specify TCP_OUTPUT_PORT to change the tcp server’s output port if using docker’s host networking mode . Otherwise use the appropriate docker port mappings .

You can host any RTKLIB or tcp server instance on another machine and retreive the data using our dockers tcp client mode by defining TCP_INPUT_IP and TCP_INPUT_PORT. In which you’ll specify your tcp servers ip and port.

Note: The onocoy dashboard/explorer won’t provide you with the mountpoint information until they verify you can send them data. Omit the mountpoint details from this section until after you initially get past that window. Then run the command again.

Serial Connection Settings #

Note: Always consult your receiver manufactures documentation to get the correct serial connection information such as baud rate, data bits, partity, and stop bits.

Known Default Serial Settings for the Following GPS Receivers

Docker Config Examples #

 docker run \
   -td \
   --restart unless-stopped \
   --name sosrtk \
   --device=/dev/<YOUR_USB_PORT> \
   -e USB_PORT=<YOUR_USB_PORT> \
   -e BAUD_RATE=<YOUR_SERIAL_BAUD_RATE> \
   -e DATA_BITS=<YOUR_SERIAL_DATA_BITS> \
   -e PARITY=<YOUR_SERIAL_PARITY> \
   -e STOP_BITS=<YOUR_SERIAL_STOP_BITS> \
   -e ONOCOY_MOUNTPOINT=<YOUR_ONOCOY_MOUNTPOINT> \
   -e ONOCOY_USERNAME=<YOUR_ONOCOY_MOUNTPOINT_USERNAME> \
   -e ONOCOY_PASSWORD=<YOUR_ONOCOY_MOUNTPOINT_PASSWORD> \
   -e LAT=<OPTIONAL_YOUR_LATITUDE> \
   -e LONG=<OPTIONAL_YOUR_LONGITUDE> \
   -e ELEVATION=<OPTIONAL_YOUR_ELEVATION_FROM_SEA_LEVEL_IN_METERS> \
   -e INSTRUMENT=<OPTIONAL_YOUR_GPS_RECEIVER_DESCRIPTION> \
   -e ANTENNA=<OPTIONAL_YOUR_ANTENNA_DESCRIPTION> \
   simeononsecurity/docker-rtklib-onocoy-rtkdirect:latest

Ensure you replace the placeholder values (<...>) with your specific configuration.

Ex.

 docker run \
  -td \
  --restart unless-stopped \
  --name sosrtk \
  --device=/dev/ttyUSB0 \
  -e USB_PORT=ttyUSB0 \
  -e BAUD_RATE=921600 \
  -e DATA_BITS=8 \
  -e PARITY=n \
  -e STOP_BITS=1 \
  -e ONOCOY_MOUNTPOINT=YOUR_ONOCOY_MOUNTPOINT \
  -e ONOCOY_USERNAME=YOUR_ONOCOY_MOUNTPOINT_USERNAME \
  -e ONOCOY_PASSWORD=YOUR_ONOCOY_MOUNTPOINT_PASSWORD \
  -e PORT_NUMBER=32377 \
  -e LAT=37.7749 \
  -e LONG=-122.4194 \
  -e ELEVATION=50 \
  -e INSTRUMENT="Your GPS Receiver" \
  -e ANTENNA="Your Antenna" \
  simeononsecurity/docker-rtklib-onocoy-rtkdirect:latest

Windows Option 1: STRSVR #

On windows, one of our best options and arguably our best free option is STRSVR , which is based on RTKLIB.

1. Download and save STRSVR.exe from the github releases page . Be sure to save it to a good location that you can easily find again later.

2. Execute STRSVR.exe, select Serial as your input device, and configure the correct COM Port for your serial reciever.

Note: Your com port will be different on your device. Consult your manufactures documentation and the Windows Device Manager on to identify the correct com port

3. Select NTRIP Server as one of your output devices and configure it using the credentials and settings you got from the onocoy console .

4. Hit the Start Button

Serial Connection Settings #

Note: Always consult your receiver manufactures documentation to get the correct serial connection information such as baud rate, data bits, partity, and stop bits.

Known Default Serial Settings for the Following GPS Receivers

Windows Option 2: SNIP #

On windows, our options are limited. One of the NTRIP communities favorite options for Windows is Snip . While there is a trial available, you’ll need to purchase the software long term if you plan on ever using it for more than an hour at any given time.

1. Download and install Snip from the download page .

You’ll have to give them an email and get the download link in your email. Use a service like 10minutemail to avoid getting spam in your email.

2. Once installed, go to the relay streams tab tab and delete all options from that page.

3. Under the Serial Streams Tab add your COM device and create a serial stream device.

Learn more about how to add a serial stream source device on Snip

4. On the Pushed-Out Data Tab manually add the Ntrip server information from the onocoy console .

Learn more on how to add pushed-out data streams on snip

Serial Connection Settings #

Note: Always consult your receiver manufactures documentation to get the correct serial connection information such as baud rate, data bits, partity, and stop bits.

Known Default Serial Settings for the Following GPS Receivers

Troubleshooting and Verifying GPS Connectivity on Linux #

1. Stop the ntripserver service

  sudo systemctl stop ntripserver.service

2. Use a GPS tool to verify connectivity
   1. First, make sure you have gpsd installed:

      sudo apt-get install gpsd
      

   2. Then start gpsd to connect to your GPS device:

      sudo gpsd /dev/ttyACM0 -F /var/run/gpsd.sock
      gpsmon
      

3. When finished either reboot your device or run

sudo systemctl start ntripserver.service

Troubleshooting Serial Connection Issues #

Failures occur for several reasons:

1. Limiting the Frequency of Buffer Amplifiers #

GNSS.store has TTL outputs on most boards. They come without buffer amplifiers and level shapers. The problem only exists on boards with RS232 output (and not just UART). There is a maximum of 230400 on RS232. Other boards support everything that the receiver can do. Many boards have USB with an FTDI chip, which supports up to 3 MHz.

2. Clock Frequency #

If the receiver processor clock frequency is 16 MHz, then we can either use 883011 (divisor 19, deviation -4.2%) or 932067 (divisor 18, deviation +1%). What happens next depends on the computer’s COM port. Some work at any frequency, others fail. This problem is twice as bad with 921600 as it is with 460800. This is important for both TTL and RS232.

3. Poor Ground Connection Causes Echo #

A poor ground connection causes an echo. The echo from the transmitted signal mixes with the received one and causes reception errors. It is especially important for RS232, where it is better to have two ground wires: the signal ground and the shield ground from the connector body and the cable braid, which is connected first when the connector is plugged in. Good cables have two different grounds on the DB-9.

4. Signal Shape #

The signal shape depends on the receiver, computer, wires, and connectors. If there are errors, use an oscilloscope. Instead of rectangular pulses, there may be distorted signals.

5. Safest and Worst Configurations #

The safest configuration is a UART TTL to USB converter on the receiver board, built on an FTDI chip. The worst configuration is RS232 with DB-9 connectors.

6. System Components #

With the exception of USB, the system consists of a receiver, cable, connectors, and a computer. The error can be anywhere in this system.

By understanding and addressing these common issues, you can improve the reliability of your serial connections for GPS receivers.

Notible Mentions for Alternative Ntrip Server Software. #

While reviewing this topic and discussing with the Onocoy team on their discord, I came across the following. These may work better for you but we didn’t cover them here. We may review them another time.

• Ntrip Server
  • Seems to be a newer version of the software we used above. However it’s more difficult to access. It is created and maintained by the German Federal Agency for Cartography and Geodesy (BKG)
• RTKLIB STR2STR
  • A more widely used NTRIP server. However it can be significantly more technically involved and only supports NTRIPv1.
  • Hasn’t been updated in many years.
• rtklibexplorer/RTKLIB
  • A version of RTKLIB optimized for single and dual frequency low cost GPS receivers, especially u-blox receivers. It is based on RTKLIB 2.4.3 and is kept reasonably closely synced to that branch.
  • A fork of the original RTKLIB that is known to be more frequently updated and more optimized than the original RTKLIB.
  • The variant of RTKLIB we use in our docker container.
  • Also only supports NTRIPv1.
• esp32-xbee
  • Exclusive to the ESP32, this software enables you to build even cheaper base stations. Or more expensive…
  • Only supports NTRIPv1 communications.

Additional Configuration For Unicorecomm UM980 and UM982 Devices #

To enable all the bands and base station mode on the Unicorecomm devices you’ll need to serial into them using baud rate of 115200 and run the following commands. This can be done within terminal, putty, or the Unicorecomm UPrecise software.

• Alternate (More up to date) U-Precise Installer

The provided configuration adjustments are made to ensure the proper functionality of the reference station receiver, specifically tailored for the Onocoy system . Click here understand What RTCM Messages Onocoy supports .

Unicorecomm UM980 and UM982 Configuration Script #

Note: Not all of these commands will work on all UM980 or UM982 varients. Some commands are firmware specific some are redundant. Not all commands are required. These are just what we determined to be “most optimal” for most situations for both Onocoy and for any other service you may use your UM98x with. If there is a feature missing that you want, contact your device manufacture for firmware update instructions.

#RESET ALL SETTINGS TO FACTORY DEFAULTS
#FReset

#DISABLE ALL MESSAGE TYPES
UNLOG
UNILOGLIST
saveconfig

# Enable anti-jamming function
CONFIG ANTIJAM FORCE
saveconfig

# Maximum age of RTK data*, in seconds
CONFIG RTK TIMEOUT 600

# High reliability for RTK Positioning and ADR
CONFIG RTK RELIABILITY 4 4

# Enable multi-path mitigation
CONFIG MMP ENABLE

# RTCM Clock Offset Compensation
CONFIG RTCMCLOCKOFFSET ENABLE
saveconfig

# Doppler Position Prediction Configuration
CONFIG PSRVELDRPOS ENABLE

# Set up automatic base configuration with automatic gps location 
mode base time 60 2 2.5

# Enable the Largest Signal Group
config signalgroup 2
saveconfig
config RTCMB1CB2a enable
saveconfig

# ONLY IF MODULE IS UM982
# Dual Antennas on UM982
# CONFIG SIGNALGROUP 3 6
# Single Antenna on UM982
# CONFIG SIGNALGROUP 7 0

#Disable Undulation Fixes per GNSS.STORE Recommended Configuration
saveconfig
CONFIG UNDULATION 0
saveconfig

#Enable NEMA Messages
gpgsv 1
gpgsa 1
gpggah 1
gpgsvh 1
gngga 1
gnrmc 1
#gpgll 1
#gpvtg 1
#gprmch 1
#gpgst 1
#gpzda 1

# Enable All bands
UNMASK GPS
UNMASK BDS
UNMASK GLO
UNMASK GAL
UNMASK QZSS
UNMASK IRNSS
UNMASK ALL
saveconfig

# ONOCOY RTCM CONFIGURATION (If doing more than just onocoy, skip this section and continue to the next)
rtcm1005 30
rtcm1033 30
rtcm1077 1
rtcm1087 1
rtcm1097 1
rtcm1117 1
rtcm1127 1
saveconfig

# Full RTCM 3.2 Configuration (Skip if only doing onocoy)
rtcm1006 30
rtcm1007 30
rtcm1019 1
rtcm1020 1
rtcm1033 30
rtcm1042 1
rtcm1044 1
rtcm1045 1
rtcm1046 1
rtcm1077 1
rtcm1087 1
rtcm1097 1
rtcm1107 1
rtcm1117 1
rtcm1127 1
rtcm1137 1
saveconfig

# Only configure if you know SBAS is available in your region
# Onocoy ignores SBAS you do not need to enable this unless you know what you're doing or you're following our dual or triple mining guides.
# CONFIG SBAS ENABLE Auto
# CONFIG SBAS TIMEOUT 600
# saveconfig

# Adjust Serial Output Settings
CONFIG COM1 115200 8 n 1
# ONLY CHANGE IF YOU WANT TO IMPROVE THE BAUDRATE OR IF YOU RUN INTO STABILITY ISSUES WITHOUT IT
# CONFIG COM1 921600 8 n 1
saveconfig

It should be noted that the Unicorecomm device does not have the ability to transmit the RTCM 1230 message type as required per Onocoy system’s requirements .

GNSS.STORE Suggested Base UM980 and UM982 Configurations #

For setting up the UM980 and UM982 devices, GNSS.STORE provides detailed configuration guides to ensure proper functionality and optimal performance. The configurations are documented in the following links:

• UM980 Configuration: UM980_RTCM3_OUT.txt

  This guide includes steps to configure the UM980 for outputting RTCM3 messages. It covers the necessary commands and settings to enable the device to send accurate positioning data, which is crucial for applications requiring real-time kinematic (RTK) corrections.

• UM982 Configuration: UM982_RTCM3_OUT.txt

  Similar to the UM980, this guide provides detailed instructions for configuring the UM982 device. It outlines the commands and parameters needed to set up the device for RTCM3 message output, ensuring it can deliver precise GNSS data for various applications.

Unicorecomm UM980 and UM982 Commands Reference Manuals #

For additional configuration guidance, consult the following documentation:

• UM980 / UM982 Commands Reference Manual
• NebulasIV Commands Reference Manual

Following these suggested configurations helps in achieving reliable and accurate GNSS data transmission, essential for high-precision navigation and surveying tasks.

Symlinking Serial Devices to Hardcoded Path #

When working with multiple serial devices, it’s common to encounter challenges related to device naming. By default, Linux assigns device names like ttyUSB0, ttyUSB1, etc., based on the order in which devices are connected. This can lead to confusion and issues when a specific device needs to be accessed consistently by the same name. One way to resolve this is by creating a symlink that assigns a stable, custom name to a device based on its attributes, such as its vendor and product IDs.

For instance, if you want your device to consistently appear as ttyUM980 instead of ttyUSB0, you can create a custom udev rule. Here’s how you can do it:

1. Create a udev Rule File:

   udev rules are stored in the /etc/udev/rules.d/ directory. Each rule is defined in a separate file. In this example, we will create a file named 00-um980.rules.

   $ sudo nano /etc/udev/rules.d/00-um980.rules
   

2. Define the udev Rule:

   Add the following rule to the file:

   KERNEL=="ttyUSB[0-9]", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015", SYMLINK+="ttyUM980"
   

   This rule does the following:

   • KERNEL==“ttyUSB[0-9]”: Matches any device named ttyUSB followed by a single digit.
   • ATTRS{idVendor}==“0403”: Matches devices with a vendor ID of 0403. This ID is unique to the manufacturer of the device.
   • ATTRS{idProduct}==“6015”: Matches devices with a product ID of 6015. This ID is unique to the specific product.
   • SYMLINK+=“ttyUM980”: Creates a symbolic link named ttyUM980 pointing to the matched device.

3. Identify Device Attributes:

   To create an appropriate udev rule, you need to identify the vendor ID and product ID of your device. You can use the lsusb command to list all USB devices and their attributes.

   $ lsusb
   

   This command will output a list of connected USB devices. Look for your device in the list. For example:

   Bus 002 Device 003: ID 0403:6015 Future Technology Devices International, Ltd FT231X USB UART
   

   In this example:

   • The vendor ID is 0403.
   • The product ID is 6015.

   You can also use the udevadm command to get more detailed information:

   $ udevadm info --name=/dev/ttyUSB0 --attribute-walk
   

   This command walks through the device tree and prints all attributes of the device, helping you identify the correct values for your udev rule.

4. Apply the udev Rule:

   After saving the file, reload the udev rules to apply the changes:

   $ sudo udevadm control --reload-rules
   

5. Verify the Symlink:

   Disconnect and reconnect your device. You should now see a new device named ttyUM980 in the /dev directory, in addition to the usual ttyUSB0.

   $ ls -l /dev/ttyUM980
   

   This should show a symlink pointing to the actual device, for example:

   lrwxrwxrwx 1 root root 7 Jul  7 12:34 /dev/ttyUM980 -> ttyUSB0
   

By following these steps, you ensure that your device will always appear as ttyUM980, regardless of the order in which it’s connected. This is particularly useful in scripts or applications where a consistent device name is required.

Maintaining UPrecise Access with Linux using Socat or our Docker Container #

To ensure uninterrupted UPrecise access when using Linux, you can utilize the socat application to connect to the UM980’s serial interface from a Windows machine.

Here’s the command to achieve this:

Note: If you’re using the docker container option above, you can skip this section and you can control the port you want to access the dongle by specifying the TCP_OUTPUT_PORT variable. It’ll function the same as below.

Replace {{portnumber}} with a port number of your choosing

sudo socat tcp-listen:{{portnumber}},reuseaddr /dev/ttyUSB0,b115200,raw,echo=0

Next, follow these steps to set up UPrecise on a Windows PC within the same network:

1. Launch UPrecise.
2. Navigate to the “Connections” menu.
3. Select “TCP/IP” as the connection type.
4. Enter the IP address of your Linux host and the port number specified in the previous command.
5. You will now have access to the Data Stream and can continue sending commands as usual.

Onocoy FAQ #

Onocoy Setup #

Q1: Which equipment can be used to set up a station?

• A1: Any GNSS device capable of data transfer via NTRIP is recommended, with featured bundles listed on the dedicated onocoy device page or recommended in this article above .

Q2: Where should the antenna be placed?

• A2: Ideally, fix the antenna in a location with a full sky view, such as a roof, chimney, or open field. Ensure no obstructions exist above 10 degrees elevation angle, and secure the antenna against movement during adverse weather.

Q3: What is needed to connect the device, and is WiFi necessary?

• A3: A stable internet connection is required, whether through WiFi or Ethernet, depending on the device.

Q4: What happens if I want to change the location of my station/antenna/receiver?

• A4: Moving the device to another location is not a problem; you just need to successfully pass the data validation process again.

Onocoy Devices & Streams #

Q5: Can streams be retrieved directly if my station only supports NTRIP caster and is exposed on the internet?

• A5: No, due to complexities, it is not a reliable method. Contact your station manufacturer to add NTRIP server functionality.

Q6: What NTRIP Messages need to be enabled on my GNSS reference receivers for the best rewards?

• A6: Enable RTCM 3.0 MSM7 Messages for optimal rewards, including messages for various constellations. Lower tier messages are supported, while certain message types are ignored.

Q7: What latency is tolerable from the GNSS receiver to the onocoy system?

• A7: The end-to-end latency should be below 1 second; larger latencies result in reduced rewards and potential disconnection.

Q8: Do I have to set the receiver in a special Reference station mode to determine its accurate location?

• A8: No, the onocoy system’s validation procedures determine the precise location of your station.

Q9: How does onocoy prevent fraudulent correction streams?

• A9: onocoy employs sophisticated methods, including regular data consistency checks, real-time supervision, and checks over long-term periods to detect fraudulent streams.

Q10: Can I provide data from a 3rd party service, such as public networks like IGS or other networks?

• A10: Yes, with acceptance of terms and conditions, provided you have the rights. Multiple submissions from free networks may result in banning.

Q11: My station frequently disconnects. What can I do?

• A11: Disconnections are observed due to updates but should not affect operations. No action is needed on the user’s network side.

Onocoy Rewards #

Q12: My wallet is not connecting. What can I do?

• A12: Ensure you are using Chrome or Brave Browser on a Desktop device. Follow instructions on the page, and if issues persist, contact support through the onocoy discord .

Q13: How is the location scale calculated?

• A13: Factors include the number and distance of nearby stations, with the quality of neighboring stations influencing rewards.

Q14: How much will I earn streaming RTK correction data to onocoy?

• A14: Earnings depend on factors like signals, satellites, and location. Specific numbers are yet to be decided, but users can earn tokens even before they are officially listed.

Q15: Why does onocoy use blockchain technology?

• A15: onocoy uses blockchain to stabilize token prices, with mechanisms like required tokens for data access, constant burn, locked tokens for governance, a capped maximum supply, and a staking function.

Q16: How do I claim my rewards?

• A16: Click the “Claim Rewards” button in your NTRIP server list in the Onocoy Dashboard. Rewards can be claimed anytime, and changes in the reward factor trigger automatic claiming. Review your current balance in the upper right corner of the validator.

Conclusion #

Setting up your own DIY GPS Onocoy server doesn’t have to be a daunting task. With the right hardware choices, reliable GPS receivers, and a clear understanding of the process, you can achieve remarkable precision and accuracy in your location-based applications.

By following the step-by-step instructions outlined in this guide, you’ve unlocked the potential to enhance your navigation, positioning, and surveying endeavors. The affordable hardware options, such as Raspberry Pi and Intel NUC , coupled with accurate GPS receivers, pave the way for effortless and efficient server setup.

So, go ahead and set up your Onocoy Reference Station, refine your skills, and enjoy the results that await you. Whether you’re navigating remote terrains, conducting surveys, or exploring new possibilities, your DIY Onocoy Reference Station will be your trusty companion in the pursuit of precision.

Stay inspired, stay innovative, and keep pushing the boundaries of what’s possible with technology.

Lastly, check out our article on more low powered mining setups .

or

References #

• German Federal Agency for Cartography and Geodesy (BKG)
• NebulasIV Commands Reference Manual
• Ntrip Server
• Onocoy - Get GNSS correction data
• Onocoy - Connect your station to onocoy
• Onocoy - Whitepaper
• Onocoy - Linkedin
• Onocoy - Twitter
• Onocoy - Discord
• Onocoy - YouTube
• RTKLIB
• UM980 / UM982 Commands Reference Manual
• Unicorecomm UPrecise
• esp32-xbee
• WhoLovesBurrito - Chinese UM980 Dongle Implementation