The NTRIP client is built in. Enter your caster details in the web panel and the rover receives corrections over Wi-Fi.
Two ways to get RTK corrections. One way to read the result.
An RTK rover needs correction data to reach centimetre accuracy. RTK-EASY takes it from the internet or from your own base station.
Switch one board to BASE mode and it becomes your own RTK base station, generating corrections for your rovers. No dependence on a public service.
Connect the rover to an ESP32, Arduino, computer or any controller and read:
Connect antenna and power
Attach the GNSS antenna and power the module. Mount the antenna with a clear view of the sky.
Open the web panel
Join the module over Wi-Fi from a phone or laptop. Choose BASE or ROVER, set Wi-Fi and the correction source.
Use the position
Watch status and RTK fix in the browser, or read NMEA from the UART output in your own code.
See RTK-EASY working
From RTK basics and first setup to a robot driving RTK waypoints on its own.
RTK modules
Both modules come in two GNSS series, L1/L2 and L1/L5. Pick the series under each product to see its board.
RTK Base/Rover
A ready-made module for precise RTK positioning. Use it as a rover that knows its exact location, or switch it to base mode and run your own RTK base station.
- Rover mode: corrections from an NTRIP service over the internet, or from your own base.
- Base mode: the same board generates RTK corrections for other rovers.
- No programming: choose the mode, Wi-Fi and correction source in the web panel, and see live module status.
- Open output: standard NMEA over UART with position and RTK status.
- Modes
- BASE or ROVER, set in the browser
- Corrections
- NTRIP client built in, or RTK-EASY base
- Output
- NMEA over UART (TX, RX, 3.3V, GND)
- Indicators
- LINK and PPS LEDs, optional 0.96" OLED header
- Good for
- Surveying, recording coordinates, staking out points, robots, DIY projects
RTK Rover/Autopilot
For robots and other autonomous platforms. It knows where the robot is, works out where it has to go next, and sends drive commands to the wheel controllers. No separate computer is needed to turn RTK coordinates into motion.
- Waypoint navigation: START → WP1 → WP2 → WP3 … On reaching a point it heads for the next one automatically.
- Two GNSS antenna inputs for heading from RTK, without a magnetic compass.
- Motor UART output: simple left and right wheel commands for the wheel controllers.
- Web control: robot and RTK status, manual driving and autonomous functions from a phone or computer.
- Corrections
- NTRIP built in, or RTK-EASY base
- Drive output
- UART to wheel controllers, 115200 baud
- Interface
- Web panel over Wi-Fi, OLED status display
- Works with
- RTK-EASY DC and BLDC wheel controllers
Set the waypoints. The autopilot drives.
A plain rover knows where it is. The Rover/Autopilot also knows where it needs to go, and tells the wheel controllers how to get there.
The autopilot compares its RTK position with the next waypoint, calculates the heading and speed, and sends wheel commands until it arrives.
Wheel commands
UART · 115200 baud| L[50] R[-50] | Both wheels forward |
| L[30] R[60] | Turning |
| L[-40] R[40] | Reversing |
| [0] | Stop |
The autopilot does not drive high-current motors directly. It decides where and how the robot moves. The wheel controllers handle the motors.
One universal board. Two jobs.
An ESP32 server board that plans routes for the autopilot, or turns any RTK-EASY wheel controller into a web-controlled robot without writing a line of code.
Draw the perimeter and any obstacles in the browser, set the coverage angle and row spacing, and click Plan route — the server board computes the full coverage path and lets you preview it with the built-in rover simulation before driving anywhere.
The last plot you save becomes the live route. On its next run, the RTK Rover/Autopilot reads that saved route straight from the server over Wi-Fi — nothing to re-upload to the rover.
It also works the other way: transfer a plot recorded by the autopilot back to the server, generate a route from it there, then drive that generated route once it's back on the rover.
Route planner board
Upload the server firmware and the board becomes a route planning server on your network. Plan the waypoints in the browser; the RTK Rover/Autopilot receives them from the server over Wi-Fi.
Don't want to program your own ESP32? Connect this board to a wheel controller and you have a robot you drive from a web page.
- Power
- 5 V input (+5V, GND), on-board 3.3 V regulator
- UART2
- TX, RX, GND · RX is 5 V tolerant
- GPIO
- 33, 25, 26, 27, 14, GND for your own add-ons
- Display
- 0.96" OLED header (GND, VCC, SCL, SDA)
- Firmware
- UART header for uploading the server or Wi-Fi robot firmware
L1/L2 or L1/L5?
Both reach centimetre-level accuracy with RTK corrections. The difference is which satellite signals they use.
The all-round choice for varied conditions.
- RTK base and rover
- Robots and autopilots
- Surveying and measurements
- Fields, yards and mixed sites
Choose L1/L2 if you don't yet know where the device will be used.
A strong choice for open areas with a clear sky.
- Robots and autopilots in open terrain
- Field work
- Sites without many trees or tall buildings
L5 is a newer GNSS signal, but fewer satellites broadcast it than the older signals. In harder environments L1/L2 is usually the more versatile choice.
What about trees and buildings?
Neither series can work miracles here. A GNSS receiver needs the widest possible view of the sky. Under dense trees, next to tall buildings, under a roof or between buildings, RTK performance can drop, or an RTK FIX may not be reached at all.
Wheel controllers that close the loop
A robot has to know where it is and where to go. Something also has to turn the wheels. RTK-EASY supports two drive types with the same simple command interface.
DC wheel controller
For robots with ordinary brushed DC motors. More than a simple power stage: it monitors each motor and works to hold the set speed when the load changes. When the robot climbs a slope or drives into grass, it adds power so the wheel speed changes as little as possible.
- Direction: forward and reverse
- Speed: slower and faster, held under load
- Stop on command
- Battery monitoring
- Motors
- 2 × brushed DC (left, right)
- Speed feedback
- Motor back-EMF. No encoder or optical sensor needed.
- Interface
- UART (RX, TX, GND), +12 V and +5 V supply terminals
BLDC wheel controller
For larger and more powerful robots with BLDC hub or wheel motors driven by ZS-X11H power stages. The board sends them speed and direction signals and reads the wheel Hall sensors.
- Constant wheel speed with torque held at low speed
- Hall sensor inputs for both wheels
- Battery monitoring
- The autopilot only says: left wheel at this speed, right wheel at this speed.
- Motors
- 2 × BLDC via ZS-X11H drivers
- Connections
- Hall (yellow, blue, green, VCC, GND), pulse, Hall power, serial
- Interface
- Same UART commands as the DC controller
Same autopilot, different drivetrains. A small robot can use brushed DC motors, the next project BLDC motors, with no changes to the autopilot logic.
Build a Wi-Fi robot first. No RTK needed.
Connect a standard ESP32 Dev board to any of our wheel controllers and upload the free, ready-made firmware. Your phone becomes the remote.
The ESP32 creates a Wi-Fi network and a web control page. Connect with your phone, open the browser and drive with the on-screen joystick. No app, no dedicated remote, no extra hardware. Try the joystick demo, or watch the real robot.
Drive it from your phone
Wheel controller + ESP32 Dev + free firmware. Or skip the ESP32 setup: use the Route planner board, ready to connect.
Make it autonomous
Replace the ESP32 with an RTK Rover/Autopilot. The robot knows its exact position and drives the waypoints on its own.
Start with two motors, a wheel controller and an ESP32. Upload the firmware, connect the ESP32, and your robot is driving.
Wiring: ESP32 Serial2 to wheel controller
SchematicController TX is 5 V. Use a divider.
The ESP32 and the RTK Rover/Autopilot RX inputs are 3.3 V only. Connecting the 5 V controller TX directly can damage them.
Power the ESP32 from the battery, not from the controller
In Wi-Fi mode the ESP32 draws current peaks of several hundred milliamps. Feed its 5V pin from a 5 V DC-DC regulator on the robot battery, or from a separate 5 V supply. Do not take 5 V from the wheel controller.
TX2 → RX needs no divider. Connect all grounds together.
Using the Route planner board instead of an ESP32 Dev? Its UART2 RX accepts 5 V, so connect the controller TX directly.
A module you build with, not a closed box
A professional RTK receiver is usually a finished measuring instrument. RTK-EASY is an RTK module designed to be easy to understand, connect, configure and use in your own project.
| Typical survey receiver | RTK-EASY | |
|---|---|---|
| Designed as | A finished measuring tool | A module you build into your own device |
| Configuration | Vendor software or GNSS commands, often via a PC | Web panel in any browser over Wi-Fi |
| Position output | Tied to the vendor's app or controller | Standard NMEA over UART |
| Corrections | NTRIP or a separate base | NTRIP built in, or your own RTK-EASY base |
| Robot navigation | Needs an extra computer and software | Built-in waypoint autopilot with wheel control output |
Less complex configuration. More freedom to build.
Find the right set in four answers
Answer four questions and get a recommended set of modules. Copy the list and send it with your enquiry.
Recommended set
Common questions
Do I need a base station?
Only if you have no access to an NTRIP correction service, or you prefer not to depend on one. With NTRIP, one rover is enough. Without it, use two modules: one in BASE mode and one rover.
What accuracy can I expect?
With RTK corrections and a good view of the sky, both series can reach centimetre-level accuracy once the rover has an RTK FIX. Trees, buildings and roofs reduce performance.
How do I read coordinates in my own code?
The rover sends standard NMEA sentences over UART. Any ESP32, Arduino or computer with a serial port can parse latitude, longitude, altitude and fix status (GPS, FLOAT, FIX).
Do I need to program the module?
No. All settings, including BASE or ROVER mode, Wi-Fi and the correction source, are made in the web panel from a phone or computer.
Which series should I buy?
If you are unsure, choose L1/L2. It is the more versatile option across varied conditions. L1/L5 is a good fit for open terrain with a clear sky.
What voltage do the logic pins use?
3.3 V. Never apply 5 V to the UART pins. When connecting a 5 V motor controller TX line, use the resistor divider shown in the wiring section.
Can I use my own motor drivers?
Yes, if they accept the autopilot's simple UART wheel commands. The RTK-EASY DC and BLDC controllers support them out of the box and add speed regulation and battery monitoring.
Do I have to program an ESP32 myself?
No. The Route planner board works as a ready-made Wi-Fi robot controller. Connect it to a wheel controller and drive from the web page. Its UART2 RX accepts the controller's 5 V signal directly.
Is the Wi-Fi robot firmware really free?
Yes. Upload the ready-made firmware to a standard ESP32 Dev board, connect it to an RTK-EASY wheel controller and drive from your phone.
Tell us about your project
Modules are made to order. Send us your recommended set from the kit builder, or describe what you are building, and we will confirm the configuration and lead time.
- Which series: L1/L2 or L1/L5
- Which modules: Base/Rover, Rover/Autopilot, wheel controllers
- Corrections: NTRIP service or your own base
- Your platform: robot size, motors, controller
