no, we have no implemented receive in the esp32 code yet. It wouldn’t be hard to do, just not a priority right now
1 Like
Hello, We trying to compile Ardupilot tag Copter-4.3.0 with opendroneid enabled for Pixhawk 4. We want to get the opendroneid mavlink message through UART without using an ESP32-S3, so we follow the video in the OpenDroneID — Dev documentation , but we was not able to get the opendroneid message through UART,
we always get this error ‘PreArm: OpenDroneID: ARM_STATUS not available’, do you have an idea how to fix this issue ?
Without information regarding this blog, I post an issue on aonther thread about ardupilot firmware building for remote ID as flollows.
The core Issue in this post is that the ardupilot bootloader with AP_OPENDRONEID_ENABLED 1 (for open hardware (such as pixhawk Cube Black) whose RAM size is 256KB) can’t be made.
Do you have idea on that?
Does it work with this board:
https://www.aliexpress.com/item/1005006170017637.html?spm=a2g0o.cart.0.0.f6da38daFXZzWF&mp=1
And can i use it with elrs?
Would anyone be interested in unprogrammed versions of the mRID from Phoenix UAS? It has a ESP-32-C3, an FCC ID and has obtained a DOC. http://www.phoenixuas.us
I understand that this use case does not need a DOC and the individuals would be looking to make a standard Remote ID module integrated into UAS and do not need a serialized RID module. For this case we would just build the module and leave it up programmed and unincripted. Depending on the quantity wanted we could produce a special batch to fill the Ardu-Remote ID needs.
1 Like