- Posts: 60
Binding question
- Blayd
- Topic Author
- Offline
Less
More
13 May 2013 21:32 #9948
by Blayd
Devo 8S
Trex500ESP
Trex500ESP (Belted tail)
HC500SE
Trex700N2E
Binding question was created by Blayd
I was planning on doing some test flights tomorrow after work using my Devo8S with 3.0 installed.
I am curently trying to set up two 500's for tomorrow, and was going to start with Throttle calibration to the CC ESC's, but came upon a snag..
Several of my heli's use the zero numeral ("0") as the first in the ID bind...it appears Deviation wont recognize this?
My 2801Pro binds in an instant, but the Devo 8S omits the "0" as the first numeral in the ID code so it wont bind...
The model is currently in 2801 mode 8 channel.
Do I have to redo the ID codes I have with "0" as the first numeral?
Right now, I am assuming so?
I am curently trying to set up two 500's for tomorrow, and was going to start with Throttle calibration to the CC ESC's, but came upon a snag..
Several of my heli's use the zero numeral ("0") as the first in the ID bind...it appears Deviation wont recognize this?
My 2801Pro binds in an instant, but the Devo 8S omits the "0" as the first numeral in the ID code so it wont bind...
The model is currently in 2801 mode 8 channel.
Do I have to redo the ID codes I have with "0" as the first numeral?
Right now, I am assuming so?
Devo 8S
Trex500ESP
Trex500ESP (Belted tail)
HC500SE
Trex700N2E
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
Less
More
- Posts: 4402
13 May 2013 22:15 #9955
by PhracturedBlue
Replied by PhracturedBlue on topic Binding question
On the WK2801 protocol, matching the id should let you bind (this isn't true on the Devo protocol where a unique ID of your radio is also used). Deviation automatically adds the leading 0s, so this shouldn't be the reason binding fails.
Unfortunately, I don't have a WK2801 radio, so I can't test with it.
Unfortunately, I don't have a WK2801 radio, so I can't test with it.
Please Log in or Create an account to join the conversation.
- Blayd
- Topic Author
- Offline
Less
More
- Posts: 60
13 May 2013 23:16 - 13 May 2013 23:16 #9960
by Blayd
Devo 8S
Trex500ESP
Trex500ESP (Belted tail)
HC500SE
Trex700N2E
Replied by Blayd on topic Binding question
Thanks for the reply PB.
Well, I tried it with the ID code, I tried it with the NONE, it wont bind with WK2801 selected and 8 channels. I also powered up the 2801Pro Tx and it bound immediately. In the 2801Tx, it shows the "0" in the Fixed ID code.. In the Deviation, it omits the "0" and leaves just the 5 numerals behind it, so that's why I assumed the 2801Rx wasn't seeing 6 digits of the fixed ID.
I'm in the process of seeing if the 8S will bind to a code that doesn't have "0" as its first numeral....
Well, I tried it with the ID code, I tried it with the NONE, it wont bind with WK2801 selected and 8 channels. I also powered up the 2801Pro Tx and it bound immediately. In the 2801Tx, it shows the "0" in the Fixed ID code.. In the Deviation, it omits the "0" and leaves just the 5 numerals behind it, so that's why I assumed the 2801Rx wasn't seeing 6 digits of the fixed ID.
I'm in the process of seeing if the 8S will bind to a code that doesn't have "0" as its first numeral....
Devo 8S
Trex500ESP
Trex500ESP (Belted tail)
HC500SE
Trex700N2E
Last edit: 13 May 2013 23:16 by Blayd.
Please Log in or Create an account to join the conversation.
- Blayd
- Topic Author
- Offline
Less
More
- Posts: 60
13 May 2013 23:32 #9962
by Blayd
Devo 8S
Trex500ESP
Trex500ESP (Belted tail)
HC500SE
Trex700N2E
Replied by Blayd on topic Binding question
OK.. The others didnt bind as well.. ( fixed ID codes that have a number other then "0" first.) so it's something else I've got messed up. It bound immediatly to the 2801ProTx. Perhaps I need to wipe the fixed ID code from the 2801Rx's and re-set them through the 8S?
Devo 8S
Trex500ESP
Trex500ESP (Belted tail)
HC500SE
Trex700N2E
Please Log in or Create an account to join the conversation.
- RoJAck
- Offline
Less
More
- Posts: 15
14 May 2013 04:19 #9969
by RoJAck
Replied by RoJAck on topic Binding question
I had issues with fixed number binding, so I deleted all the id digits in the Tx and then turned off the Tx, turned it on, then connected the model battery (typical Walkera bind) they bound immediately. Maybe try that once, and then go back to fixed number. Just guessing here.
Please Log in or Create an account to join the conversation.
- Blayd
- Topic Author
- Offline
Less
More
- Posts: 60
15 May 2013 20:44 #10041
by Blayd
Devo 8S
Trex500ESP
Trex500ESP (Belted tail)
HC500SE
Trex700N2E
Replied by Blayd on topic Binding question
Thanks Jerry, I had tried that.. I'm used to the "Walkera Bind" from my V400d02 days...
I deleted all the digits in Deviation, until it displayed NONE, but then realized, it wont bind as a random bind unless I wipe the 2801Pro Rx clean too. I may have to clear one of the 2801Pro Rx's of it's ID, then try either binding to Deviation as a random bind, or re-set up fixed ID through Deviation.
I was hoping I could just set the ID code in Deviation, and it would bind to the 2801Pro rx's.
When I get a chance, I'll clear one of the 500's and see if it will bind with Deviation as a random bind... then work on setting a fixed ID.
I deleted all the digits in Deviation, until it displayed NONE, but then realized, it wont bind as a random bind unless I wipe the 2801Pro Rx clean too. I may have to clear one of the 2801Pro Rx's of it's ID, then try either binding to Deviation as a random bind, or re-set up fixed ID through Deviation.
I was hoping I could just set the ID code in Deviation, and it would bind to the 2801Pro rx's.
When I get a chance, I'll clear one of the 500's and see if it will bind with Deviation as a random bind... then work on setting a fixed ID.
Devo 8S
Trex500ESP
Trex500ESP (Belted tail)
HC500SE
Trex700N2E
Please Log in or Create an account to join the conversation.
Time to create page: 0.034 seconds
- Home
- Forum
- General
- General Discussions
- Binding question