GDRIVER
GDriver checks the Bluetooth link, communication through the module, valid controller data, maintenance-load reliability, and editing access— directly from your browser, with no app install.
Connection results will appear here as each layer is tested.
Every attempted test is recorded automatically for 30 days using only the decoded health summary, device name, controller identity, and connection results. Raw Bluetooth bytes are analyzed temporarily and are never saved.
Your browser stays in control. The page cannot scan silently, reconnect after you close it, or change controller parameters during this diagnostic.
A FarDriver Bluetooth module can connect normally while still failing to exchange usable data with the controller. GDriver separates the browser-to-module link from the module-to-controller data path, then checks whether valid legacy or newer FarDriver frames arrive.
Because the dongle is powered and advertising over Bluetooth, zero received bytes points farther downstream: the controller may not be outputting serial data, the dongle may not be forwarding it, or the controller-to-dongle connection may be faulty.
Received bytes with zero valid frames are different from silence. They can indicate corrupted serial data, an incompatible dongle, poor wiring, or a controller protocol mismatch.
Communication health, write access, and save authorization are separate states. A controller can return valid telemetry while still requiring authorization for protected or persistent changes.
Yes. The Bluetooth radio can connect normally even when the dongle is not receiving data from the controller. That is why the test reports the Bluetooth link, raw bytes, and valid controller frames separately.
Zero frames with zero bytes means the controller side stayed silent. Bytes received with zero valid frames means data arrived but failed FarDriver frame validation. Either result can involve the dongle, but they call for different checks.
Reading telemetry proves the basic inbound path works, but saving adds maintenance, authorization, write, and response traffic. A weak or faulty dongle can stall or drop data under that back-pressure, so reads may look normal while saves fail. GDriver's maintenance-load result checks for this separately from the controller's reported write access and save authorization.
Yes. The server-side analyzer recognizes legacy additive-checksum frames and newer mapped CRC frames. When the controller reports that the optional authorization request is available, the result is verified from fresh controller data.
The diagnostic sends safe connection probes and, when supported, one temporary authorization request. It never writes controller parameters or performs Flash Save.