You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be convenient for some users to be able to easily download/install a firmware that includes RemoteID support. It could either be included in the standard firmware or perhaps it could be added to the custom build server.
Part of the reason that AP does not currently include the feature by default is that it would only be used by a small subset of AP users but also because the FAA requirements include a "temper resistance" clause which means there are additional steps required to produce a compliant firmware (see video here).
As a recreational user (non-Part 107), and in the interests of timely regulatory compliance, I welcome the ability to optionally include RemoteID/ODID options in the custom-build server, and possibly in the standard firmware downloads for common FCs. Not being an OEM/Builder/Reseller, instantiating the infrastructure to perform custom FW generation organically for the FC and the RID modules is a daunting proposition. Just tossing in my vote in favor of this enhancement. Thanks for the opportunity to comment.
It would be convenient for some users to be able to easily download/install a firmware that includes RemoteID support. It could either be included in the standard firmware or perhaps it could be added to the custom build server.
Part of the reason that AP does not currently include the feature by default is that it would only be used by a small subset of AP users but also because the FAA requirements include a "temper resistance" clause which means there are additional steps required to produce a compliant firmware (see video here).
This request comes from this discussion.
The text was updated successfully, but these errors were encountered: