RCP-3 remote control communication loss with Trinity Two head after failed wireless pairing attempt.

Gear

ZephyrCan I fly my Alexa or RED on a Zephyr?389

Master SeriesIs a used Master Series rig worth buying as a first big rig?191

BFDHow do I power my BFD receiver from my camera or sled?186

VoltCan I retrofit a Volt onto my existing sled or gimbal?168

ArtemisHow do I power my camera and accessories from an Artemis sled?166

MDRWhere can I mount my Preston MDR on my rig?143

ModulusIs there a Modulus option for HD wireless video?141

G-70Will my G-70 fit my vest, gimbal or sled?126

FI+ZCan I control iris and zoom wirelessly, not just focus?60

HU3Where can I get my HU3 repaired, refurbished or repainted?60

CineLiveHow do I pack and case my CineLive rig for transport?54

G-70XHow does the G-70X compare to Pro Titan, Xarm and other arms?46

Trinity 2Is Trinity 2 SUP 3.0 firmware safe to install or buggy?46

Ultra VestWhich vest should I choose for my body size, comfort and operator type?39

2025From SteadiHub members

Communication between RCP-3 and Trinity Two head failed after attempting to establish RF wireless pairing, which showed paired status briefly then disconnected.
The operator tried both wireless and wired connections via FS CAN connection and battery module base connection without restoring communication.
The system had operated reliably in the preceding weeks using hard-wired CAN connection only.
Motor control and MTG2 remote continued to function, indicating the head itself remained operational.
The failure occurred immediately after manually initiating RF wireless link pairing, suggesting the pairing attempt may have affected the control protocol state.

Current firmware version as of the troubleshooting session.
The specific RF wireless pairing procedure and firmware behavior are undocumented in this thread.