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

Bayang protocol Autobind #47

Open
SirDomsen opened this issue Feb 10, 2019 · 14 comments
Open

Bayang protocol Autobind #47

SirDomsen opened this issue Feb 10, 2019 · 14 comments

Comments

@SirDomsen
Copy link

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

@goebish
Copy link
Owner

goebish commented Feb 10, 2019

Fixed.

@SirDomsen
Copy link
Author

Awesome, thanks!

@SirDomsen
Copy link
Author

Sorry for bugging you, but I just recognized something strange that I can't get sorted:
The MZ-24 uses the same channel mapping as Spektrum, so I commented in #define SPEKTRUM. So far so good, all 4 analogue channels (TAER) work as intended. Min and max values fit, middle also. I use a Silverized FC to debug, so I can actually see the channel values. Strange: All digital Bayang channels switch not at 50% ("0) as intended but at around 70% ("+40").
Another interesting thing is throttle channel: in Silverware it has a 10% safety travel. So My Devo starts to switch on the motors at -80 (Deviation). The Multipro does the same at -74. No big deal, just curious why...

@goebish
Copy link
Owner

goebish commented Feb 11, 2019

the #define SPEKTRUM is only for TXs such as the DX4e with limited throw, you don't need it with the MZ-24.

@goebish
Copy link
Owner

goebish commented Feb 11, 2019

Mapping is TAER by default, same as Spektrum transmitters.

@SirDomsen
Copy link
Author

Ah, thanks, I didn't know. Now The analogue channels appear to be correct, digital channels switch at +50% though...

@SirDomsen
Copy link
Author

#define PPM_MIN 1100
#define PPM_SAFE_THROTTLE 1100
#define PPM_MID 1500
#define PPM_MAX 1900
#define PPM_MIN_COMMAND 1300
#define PPM_MAX_COMMAND 1700

@goebish
Copy link
Owner

goebish commented Feb 11, 2019

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

@SirDomsen
Copy link
Author

SirDomsen commented Feb 11, 2019

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%

@goebish
Copy link
Owner

goebish commented Feb 11, 2019

Ok that's weird, you can modify PPM_MAX_COMMAND if required, but not PPM_MIN & PPM_MAX

@SirDomsen
Copy link
Author

SirDomsen commented Feb 11, 2019

Got it sorted.
#define PPM_MIN_COMMAND 1100
#define PPM_MAX_COMMAND 1500
did the trick. Thanks for your advise!

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 :)

@ANS-HAFEEZ
Copy link

Hey,
I am getting issue in binding with silverware. on powering on FC it first blinks fast. As, I turned on transmitter FC start blinking slowly but never get constant.
Any suggestion?

@JamesKingdon
Copy link

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.

@goebish
Copy link
Owner

goebish commented Apr 4, 2019

No idea, sorry, I offer no support for those modules.

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

No branches or pull requests

4 participants