The latest build of QGC (below) doesn’t detect the GCS GPS for remote ID, even though the herelink settings show a GPS fix has been acquired. All the other remote ID features in QGC work. Yes, it has location permissions.
What does the remote ID page in the herelink settings actually do? I’d love to use it to bypass using an app, but I can’t get them to do literally anything. I can turn it off and QGC’s remote ID still functions, which indicates it is a completely separate control path, I think.
I got remote ID set up. Here’s my configuration:
Cube orange+
Here4 blue (up to date, dronecan)
ArduCopter 4.5.6 ODID build
Herelink black 1.1
QGC herelink build 5.0.8.1
We are developing our own GCS app to replace QGC. If the herelink remoteID settings can be made functional, then that would be great. It would save us the software development. In either case, we certainly need to be able to access the location of the herelink.
This looks like two separate paths may be involved:
QGC Remote ID handling inside the QGC app itself.
The HereLink system Remote ID / location handling exposed through the HereLink settings layer.
The fact that QGC Remote ID still functions when the HereLink Remote ID setting is turned off suggests that the HereLink settings page may not be directly controlling the same QGC Remote ID workflow, or at least not in the way expected.
For the location issue, I would suggest checking whether QGC is actually receiving Android location updates from the HereLink controller, not only whether the HereLink settings app shows a GNSS fix. Those can be different application-level permission / API paths.
My suspicion is that the vehicle-side Remote ID path is working, but the controller GPS location is not being exposed to QGC through the expected Android/QGC location path. So this may need confirmation from CubePilot/HereLink maintainers on whether the HereLink Remote ID settings page is intended to feed QGC directly, or whether it is a separate implementation path.