EdgeTX / edgetx

EdgeTX is the cutting edge open source firmware for your R/C radio
https://edgetx.org
GNU General Public License v2.0
1.55k stars 331 forks source link

Receiver name does not appear in the bind menu #1152

Open Skippydi opened 2 years ago

Skippydi commented 2 years ago

When binding, the receiver name does not appear in the registration menu or in the bind menu The binding itself works, however. Hardware Horus 10s with ISRM Modul OpenTX Version 2.6.0 (d775e75e) main version

pfeerick commented 2 years ago

I think you meant EdgeTX there ;)

Skippydi commented 2 years ago

Sure

Peter Feerick @.***> schrieb am Fr. 26. Nov. 2021 um 02:55:

I think you meant EdgeTX there ;)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EdgeTX/edgetx/issues/1152#issuecomment-979521471, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQMQ6OQ67YREMFOJKNHVQJLUN3EFLANCNFSM5IYQX6FQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

raphaelcoeffic commented 2 years ago

Just to be sure: you power the registered receiver after entering the bind menu, right?

Skippydi commented 2 years ago

Yes, of course.

Raphael Coeffic @.***> schrieb am Fr. 26. Nov. 2021 um 10:24:

Just to be sure: you power the registered receiver after entering the bind menu, right?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/EdgeTX/edgetx/issues/1152#issuecomment-979748488, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQMQ6OTCM3SYRIHWEWMU3B3UN4Y35ANCNFSM5IYQX6FQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

ChrisOhara57 commented 2 years ago

interesting fact. By any way, have you swapped the receiver from one model to a new programmed model??

I do ask because I have the same effect on my X9liteS but I'm using openTx 2.3.11 (Access) I have 3 receiver which I do use in two models each. The names of the receivers (rx6r, gr6 and gr8) only display in the original model and not in the new created model ([Bnd] instead) But the receivers work fine in all models. But when I copy a model the receiver name shows up in both models new and old.

Meanwhile I got an info how to correct it. In the second model I had to register once more but with the same registration ID as in the first model. (changed manually) Then turned the receiver off and did a new bind this time the receiver name popped up and could be selected.

raphaelcoeffic commented 2 years ago

In the second model I had to register once more but with the same registration ID as in the first model. (changed manually) Then turned the receiver off and did a new bind this time the receiver name popped up and could be selected.

Does that mean the error is actually in the RX firmware? (not transmitting stuff when not registered with that model ID?)

ChrisOhara57 commented 2 years ago

In the second model I had to register once more but with the same registration ID as in the first model. (changed manually) Then turned the receiver off and did a new bind this time the receiver name popped up and could be selected.

Does that mean the error is actually in the RX firmware? (not transmitting stuff when not registered with that model ID?)

No; As said transmitting is ok, I flew with this three receivers about have a year. But in the menu the receiver name does not appear instead it shows [BND] where [RX6R] should be. Also you should be able to select the receiver name and get an option menu, that is not possible in the second model. But transmitting works. The origin of the problem seems to be that I either bound or registered the receiver in a second model on the same transmitter. Probably I should have taken care to use the same ID manually. (it is half a year ago now that I did the bind) I do not know how the procedure works but is it possible that either the transmitter or the receiver does choose a different ID in case of a second model. (In all other models the procedure automatically used the same ID)