Permanently arm DJI (or other MSP displayport) air units using an RX#3028
Permanently arm DJI (or other MSP displayport) air units using an RX#3028
Conversation
|
I'm still waiting for Ian to test this latest iteration and confirm it matches expectations. |
JyeSmith
left a comment
There was a problem hiding this comment.
Im unable to test but have no comment re code.
|
Hey Matt,
Try updating your configurator version. Should fix it for you.
I just tried building using v1.7.7 (latest) configurator, and got a green
build.
Wez
…On Mon, Dec 23, 2024 at 12:28 AM MatCron ***@***.***> wrote:
I am trying to test this pr, but i get error
image.png (view on web)
<https://github.com/user-attachments/assets/a1c80939-434d-4da9-89ce-2d728476def0>
image.png (view on web)
<https://github.com/user-attachments/assets/d8389f57-9d39-4d69-b849-daada6ca2a70>
image.png (view on web)
<https://github.com/user-attachments/assets/7b1ac95f-8093-41da-bcc0-4e9597dbb81c>
—
Reply to this email directly, view it on GitHub
<#3028 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOIZRZUSFBQVMMHKLDWOUBT2G3EBXAVCNFSM6AAAAABRQ3I5IKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJYGQ3TINZVHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yeah building and importing the bin via web works fine, flashing straight via wifi returns the error |
# Conflicts: # src/src/rx-serial/SerialDisplayport.cpp
pkendall64
left a comment
There was a problem hiding this comment.
I merged master and changed to use the isArmed flag as per comment by @mha1
|
Nice! Thanks @pkendall64 |
Tested the latest changes with:
|
|
I can confirm this is working now as expected with O3, Arming and recording are working as expected with correct RF behavior and display messaging. Note: I have found that sometimes the rx needs to be powered after O3 to work but this has not been consistent. DJI O4 - Not Working - Not Required BUT I have tested this with O4 and its not working at all, its not allowing arming and there appears to be no change. Its worth Noting that this is not actually required for O4 as DJI have resolved the low power mode behavior and it now works as expected with full RF power available when not armed. But this feature still may be useful for some and its worth understanding why its not working incase future O3 update causes same behavior. This is a great feature for the community and a big thanks to the ELRS dev team for implementing this based on feedback. |


This is a feature request from the community:
Ian (Madstech):
There was an original PR that was merged a few weeks back that added MSP displayport as a protocol on the RX. This is what Ian is referring to above. In that PR, I am currently tieing the
armedstate of the O3 VTX to the arm state in ELRS (channel 5 state).Ian now wants enhancements that allow someone to force the O3 to arm, even if they dont use ELRS at all.
I.e. they buy an ELRS RX and set the protocol to Displayport via the web ui, then enable the permanent arm option, and then whenever they power up, the RX spams the armed command, and O3 exits low power mode.
This PR adds a new checkbox to the receiver's web UI, which enables permanent arming, even if the RX isn't linked or used with a ELRS TX at all.
https://youtu.be/cDwpVcaxmxI
A few notes:
armed = truefrom boot. It needs to befalsefirst, then gotrueafter (in terms of what the O3 sees). This PR should now wait for some UART activity from the O3, then wait an additional 10s before changing toarmed. This will happen ONLY if permanent arming is enabled.txandrxpads connected to the O3). This is so we can detect activity on the UART. If you are using ELRS switch arming (CH5) then you don't need a full UART, and can get away with only connecting to thetxpad on the receiver.