-
Notifications
You must be signed in to change notification settings - Fork 199
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
Bayang protocol Autobind #47
Comments
Fixed. |
Awesome, thanks! |
Sorry for bugging you, but I just recognized something strange that I can't get sorted: |
the #define SPEKTRUM is only for TXs such as the DX4e with limited throw, you don't need it with the MZ-24. |
Mapping is TAER by default, same as Spektrum transmitters. |
Ah, thanks, I didn't know. Now The analogue channels appear to be correct, digital channels switch at +50% though... |
#define PPM_MIN 1100 |
PPM_MIN & PPM_MAX aren't meant to be modified, you should setup your controller endpoints to output 1000-2000µs, that's +/- 125% on the DX6i, not sure for the MZ-24 |
It does not matter strangely... Sure, if I set +- 125 i's ok with stock settings, but the digital channels still switch at around +50%. I set all channels to +-125% |
Ok that's weird, you can modify PPM_MAX_COMMAND if required, but not PPM_MIN & PPM_MAX |
Got it sorted. Edit: Now the PPM signal is lost sometimes - module stops sending. I guess I'll leave it as was and just set the channels to switch at higher values :) |
Hey, |
Hi @goebish I just ran into this problem with an iRangeX iRX6. Probably an unfair question, but do you happen to know if the module is directly compatible with your original code? I'm wondering if I can flash with your latest and bring it up to date. |
No idea, sorry, I offer no support for those modules. |
Hi again,
still experimenting with a Graupner MZ-24 and your module. I see everything works as intended, all 11 Bayang channels work, channel 12 hits reset. Issue is that once reset is hit or module is power cycled, it won't bind to the (Silverware) FC again. Is it possible that TX ID changes somehow? While using Deviation or toy TX, you can power cycle the TX and it will rebind to the (still powered) FC.
Also, Autobind does not work, it seems like the FC sees the module as a different tx every time the module is power cycled...
Is there a way to get autobind to work properly?
cheers
Domsen
The text was updated successfully, but these errors were encountered: