THEMA:

Hi,

please don't remave it because this menue-item is very helpful if the receiver is in a small fuselage somewhere unreachable.

But please make it more secure

regards

gecko

Hi, first of all, sorry for the crashed airplane. As you said, there might be several reasons for this - receiver reset due to weak battery, sensor low logical level on input, or you kept Jetibox Rx menu on Pairing screen (just possibility). In normal operation the receiver cannot bind to another transmitter without user input.

However, the binding menu will be made more secure, there will be a timeout and you will hear "Range test" tone on your tx module/transmitter.

Hi Raf,

thanks for the positive response.

regards

gecko

Hi Raf,

I've just checked the new Firmware 3.07.

I hope the slightly modified pairing procedure is not the solution you where talking about.

I expected a timeout that allows starting the paiting only 60 seconds after the receiver powered up.

regards

gecko

Hi all,

I'm a bit confused with the pairing problems. I own a brand new DC-16 transmitter and have now converted two big towing planes and three big gliders to Jeti. Additionally I've converted one MPX transmitter to Jeti to allow other pilots towing me. So, I'll face the situation having two Jeti transmitters controlling same receivers in towing events...

I made a test: Having models A and B fully programmed and paired with DC-16. If I switch-on the DC-16 with model memory A but only the receiver B is turned on, it starts asking a question to connect with B. And it ask and ask forever, even if I switch-on the right receiver A or Turn-off and -on the
DC-16. Nothing helps... The only way is to switch off the receiver B .

Even worrier: If I have connected DC-16 with receiver A and then turn-on the receiver B (without second transmitter). Everything works fine as long I turn-off and -on the DC-16. It should repair the lost connection with A because it has been alive all the time. But DC-16 starts asking the connection with B !!! And the same never ending story follows... Nothing helps as long the B is alive.

This might not be an everyday Problem, but could happen if the transmitter boots for some reason. For me it shows, that there is some weakness still on Jeti's binding procedure!

My proposal is to force the user make the whole binding procedure with connector plugged in every time he wants to change the receiver. It his happens, he will have the whole thing in his hands anyhow and easy access to it.

I'm bit worry now and hope the next update comes soon.

Juha

Hi Juha,
ich tippe auf einen Bedienfehler.
Modell A und B sind mit dem Sender gebunden.
Wenn Du Den Sender mit Modell A in Betrieb hast und Modell B einschaltest, passiert nix, wie du ja auch schreibst.
Wenn Du Modell A und B einschaltest und dann den Sender, ordnet er sich mit dem letzten Gesteuerten Modell zu, in dem Beispiel A.
Jedoch: er bringt danach die Meldung: unbekanter Empfaenger entdeckt- verbinden? Wenn du jetzt Ja sagst, ordnet er mit Modell B zu, wenn Du Nein auswaehlst, bleibt er bei A.
Solltest Du versehenlich auf Ja gedrueckt haben, so musst du beide Empfaenger wieder aus- und einschalten und den Vorgang wiederholen um den Sender wieder mit Modell A auf dem Speicherplatz von A zu verbinden.

Achtung: das hat nix mit dem sogenannten Pairing zu tun!
Hier geht es um die Zuordnung der bereits gebundenen Empfaenger zu einem Modellspeicher!

In der Praxis im Flug auch bei einem sehr unwahrscheinlichen Senderreboot irrelevant da du nicht mit zwei eingeschalteten und auf ein und demselben Sender gebundenen Empfaengern fliegst!
Und selbst dann kommt immer noch eine Sicherheitsabfrage
Gruss Stephan