Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rotate 2nd frequency for HORUS_V2 (not continously) #65

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

whallmann
Copy link

Puh, i got it Mikael,
this is how i realized the roating 2nd frequency on HORUS_V2 flights.
If you acknowledge the code, i will add some hints in the documentation at least.
73 Wolf

@mikaelnousiainen
Copy link
Owner

@whallmann Thanks for the effort here. However, I think there are quite many -- slightly unrelated -- changes here mixed.

It would be great to have a separate PR at least for the hardware watchdog feature (and maybe to clean up the code a bit).

Regarding the alternate frequency for Horus, I would prefer a different approach altogether that would allow easy configuration of multiple frequencies for any mode.

In practice, the current radio_transmit_schedule allows any kind of combinations regarding modes and frequencies, but the problem is that the data structure will take quite a lot of space if it's copied for multiple frequencies. One possibility would be to add support for multiple frequencies per mode in this struct (maybe just an array with 3-4 slots?) and a "counter" indicating the index for the current frequency so that the frequencies can be used in rotation.

@whallmann
Copy link
Author

@mikaelnousiainen thanks for your time to answer. Meanwhile i done more then this. While you parallel worked on the support for DFM17 i would not longer hack into. I made an fork and added the wishes of our crowd here. Maybe you already discovered it on github.com/whallmann/RS41ng.

Your idea for adding a additional frequency on the shedule array sounds interessting. The buissines logic to switch is still nessesarry. So i wounder how you get this realized ;-)

Also i forked the RS41HUP from Mike because he told me that he will not support this any longer.
This earlier release is still interessting. Its need only the half of power (mAh) then RS41ng while its sleeps between the tx-delays. So i refurbished it a little bit - main changes were: Horus V2 protocol added, also sync it to the gps with offset to the minute like RS41ng it does and also nessesary is the recovery for GPS on flight. Many probes flying to gps jamming zones like ukraine and russian borders. The people here mostly do more floating and are happy for every additional mA on the flight and need a chance to get gps back online after leaving the war zones.

Maybe one day you think about to optimize the interupt control of RS41ng to safe more energie (CPU-WFI)? Then RS41HUP will get to retirement ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants