Hi there,
So the Short answer: No — not for RTK. The Air530 (and Air530Z) only outputs NMEA 0183 positioning sentences and accepts a few proprietary “$PGKC...” control commands. It does not expose the raw observations (carrier phase + code pseudorange) that RTKLIB needs for RTK/PPP. So you can feed its NMEA stream into RTKLIB as a plain “single” position source, but you can’t do centimeter-level RTK with it if that’s the objective?
The official Air530 manual shows NMEA 0183 output and device control via $PGKC commands, with no mention of raw/phase outputs. That’s a dead giveaway it’s a navigation-solution receiver, not a raw-data receiver.
RTKLIB’s own docs/wiki make it clear: it needs receivers that output raw carrier phase + pseudorange (u-blox M8T/M8P/ZED-F9P, SkyTraq, NovAtel, etc.). Those are listed on the OSM “RTKLIB-compatible devices” page; Air530 isn’t one of them.
the Air530 is a solid low-cost GNSS for position/time, but it’s not an RTK-class sensor. If the goal is centimeter-level demos, bite the bullet and spec a true raw-capable receiver.
HTH
GL 
PJ 
Here are some solid options:
- u‑blox ZED-F9P — A dual-frequency (L1/L2) RTK/PPP capable module; very popular with RTKLIB users.
- u-blox M8T or M8P — Single-frequency modules that output raw measurements and are supported by RTKLIB. RTKLIB Explorer+2RTKLIB Explorer+2
- ComNav receivers — professional-grade, dual-frequency, used with RTKLIB in survey/precision fields. RTKLIB Explorer+1
- Emlid RS+ (and other Emlid boards) — built on raw-capable GNSS hardware and supported by RTKLIB setups. RTKLIB Explorer+1
