Mavlink Autopilot Rtk Configuration

Will I be able to use EZ-B v4 with this Mavlink Autopilot system? I am already familiar with them and they give many inputs and output as well as many other nice features.

Yes - you can absolutely use an EZ-B v4 alongside the Mavlink Autopilot robot skill in ARCx.

How they work together

The Mavlink Autopilot skill is the movement panel for the vehicle, while the EZ-B v4 can handle everything else ARC is great at:

• servos
• sensors
• audio / speech
• custom logic
• camera skills
• digital I/O
• PWM
• I2C / UART peripherals

So a very common setup is:

• Pixhawk / flight controller handles stabilization, navigation, and vehicle control
• EZ-B v4 handles payloads, turret servos, sensors, lights, voice, etc.
• ARCx coordinates it all

RTK corrections

The RTK part is handled in the Rtk Gps robot skill, not inside Mavlink Autopilot itself.

ARCx’s RTK support includes:

• NTRIP caster corrections
• base station mode
• rover mode
• RTK fixed / float handling

If your goal is GPS correction for the Pixhawk, the usual approach is:

1. Add Rtk Gps
2. Configure it for your receiver / corrections source
3. Let Mavlink Autopilot consume the autopilot’s telemetry/mode/movement
4. Use QGroundControl in parallel if you want

RTK terminology you mentioned:

• Rover = the vehicle receiver
• Base station = stationary receiver sending corrections
• RTK fixed = the high-precision state
• RTK float = valid corrections, but not yet fully fixed

About the Pixhawk hardware list

If the Mavlink Autopilot skill didn’t populate a hardware product list, that’s not unusual if the connection isn’t configured yet or if it’s expecting the MAVLink device details rather than a "product list" like an EZ-B skill would.

The important part is usually:

• connection type: USB/serial, telemetry radio, UDP/TCP, etc.
• baud rate if serial
• whether QGroundControl is also sharing the link

Best-practice setup

If you want ARCx + Pixhawk + QGroundControl + EZ-B v4, the cleanest architecture is:

• Pixhawk = flight controller
• Rtk Gps = RTK receiver / correction handling
• Mavlink Autopilot = ARCx Movement Panel and mission control
• EZ-B v4 = auxiliary robot hardware

That’s the proven way to do it instead of trying to force everything through one skill.

Helpful reference

• Mavlink Autopilot skill: https://synthiam.com/Support/Skills/Gps/Mavlink-Autopilot?id=23708
• RTK GPS skill: https://synthiam.com/Support/Skills/Gps/Rtk-Gps?id=23711

What I need from you

To give you the right setup steps, what are you trying to accomplish overall?

For example:

• rover / mower / boat / drone?
• do you want Pixhawk to drive, or just provide telemetry while ARC controls payloads?
• is your RTK receiver connected to the Pixhawk, the PC, or the EZ-B v4?
• are you planning to share the MAVLink link with QGroundControl at the same time?

If you share your exact connection path, I can tell you the recommended ARCx wiring/configuration layout.

You do not need to use the RTK GPS robot skill since you already have the software on the robot. Your question merges two robot skills but they're seperate things and entirely unrelated.

Mavlink Autopilot is what you want to use, answered by me in your other thread.

You do not need any gps robot skills. The only robot skill you need is the MavLink Autopilot. It uses all of the sensors and computing of the existing firmware of your lawncare product. If you are to ask another question, specifically ask about Mavlink and do not mention the RTK GPS robot skill because you have no reason to use both together.

I recommend printing the Mavlink Autopilot manual and giving it a read.

Ok understand, I think that I used wrong words to describe the base station. The base station is using RTK for corrections. This is all somewhat new to me the different types of software and sensors for locations. Finally got rover moving this morning with waypoints so it's a little encouraging. There are so many variables that have to be perfect to make it work. Will take a little while to digest all of this new information.

That makes sense - and getting the rover moving with waypoints is a big milestone. Nice work.

You’re right: there are a lot of variables in the MAVLink/RTK/GPS stack, and it can feel like several systems are all talking at once. The good news is that once the Pixhawk + MAVLink Autopilot path is working, ARCx can sit on top of it cleanly without needing separate GPS skills.

The key idea

For your setup:

• Pixhawk / autopilot firmware handles the navigation and RTK/GPS side
• Mavlink Autopilot in ARCx talks to that firmware
• QGroundControl can still be used alongside it for calibration, tuning, mission work, and telemetry
• EZ-B v4 can be added for servos, lights, sensors, audio, and other robot hardware

Important clarification

There usually is not a separate field in the Mavlink Autopilot skill where you manually type in "base station RTK correction settings" the way you might expect in a generic GPS skill.

Instead, the RTK/base-station side is typically configured in the autopilot / GPS hardware / companion GNSS system itself, not in ARCx.

So the workflow is usually:

1. Get the autopilot and GPS/RTK hardware configured correctly
2. Confirm the vehicle reports valid GPS/RTK status
3. Connect ARCx with Mavlink Autopilot
4. Use QGroundControl if needed for flight controller setup and parameter tuning

Why this matters

ARCx is not replacing the autopilot’s GPS stack - it is driving and coordinating with it over MAVLink. That’s why the skill is focused on modes, arming, missions, hold, return home, pose, and movement commands rather than base-station setup.

A good next step

If you want, I can help you narrow down the exact ARCx setup based on how your Pixhawk is connected:

• USB to the PC
• Telemetry radio
• Wi-Fi / network UDP
• Through an EZ-B / companion computer path

And if you want to keep moving forward without getting buried in the terminology, I can also help you make a simple checklist for:

• Pixhawk connection
• MAVLink Autopilot skill setup
• QGroundControl coexistence
• RTK sanity checks

What exact hardware are you using for the GPS/RTK side, and how is it connected to the Pixhawk?