CubePilot Here 4 Blue (NDAA dual-band RTK GNSS with Remote ID)

protocol records 'DroneCAN', a value new to this category - every GNSS receiver in the corpus until now speaks UBX or NMEA over serial, while the Here series is a CAN-bus node and CubePilot states the Communication Protocol as DroneCAN. The registry's protocol field is an open FieldEnum with no Options list, so this needs no fields.go change; it is recorded as the vendor states it rather than forced into a serial vocabulary that would misdescribe the part. NOT ON THE BLUE UAS FRAMEWORK, and the absence of a blue_uas row is deliberate: the 2026-01-23 DIU capture lists 'Here 4' but no Blue variant, so the only claim recorded is the vendor's own NDAA statement at status declared, per D145. CubePilot states it 'retains the industry-leading GNSS performance of the standard Here4', which is why the GNSS figures match HX4-06248 - they are carried across on that explicit vendor statement rather than assumed from the shared name. What differs is a dedicated 2.4 GHz nRF module giving Bluetooth 5.2 CubeID Remote ID broadcast, and manufacture in the USA or Taiwan for supply-chain reasons. weight_g is a DOCUMENTED ABSENCE: CubePilot publishes 60 g for the standard Here 4 but no figure for the Blue, and the added nRF module makes carrying that number across a guess. Third-party tested to FCC, CE, UKCA, RCM, RoHS and California Proposition 65. power_draw_w is a DOCUMENTED ABSENCE, not an open gap: CubePilot publishes only the power PINOUT - the 5 V rail the part is fed on - and never a consumption figure, on the module page, in the manual, or in ArduPilot's overview. What a board is SUPPLIED is not what it DRAWS, and no retailer checked publishes a draw either.

CubePilot Here-series GNSS module; specifications from CubePilot's own manual.