are you familiar with the Yuneec hardware? In particular, the recievers?
When you say the LEDs flash yellow - are you referring to the LED indicators under the motors of the air frame? or the LEDs on the actual RX board?
The LEDs on my RX are blinking orange when powered - but I was operating on the understanding that a ‘slow’ blink indicates bound, but not connected. ‘fast’ blink indicates bind mode and solid light means bound and connected.
actually I don’t have experience with yuneec hw.
I just bought 2 SR24 rx from Taobao, very cheap ($5 in total). but I don’t have any yuneec drone, so I can not capture the data.
after power on, the led on my rx is also blinking slowly. according to some video, it should flash quickly when in bind mode.
according to yuneec’s document, the link command should be send to yuneec FC0, FC0 will “translate” it to some other command which yuneec rx can understand.
This is the actual command I’m interested. Sending this command directly to SR24 through a usb-serial cable should switch SR24 to bind mode.
yes, you are correct. the st24.cpp does not have bind functionality. It only has protocol functionality after binding some other way. @tridge confirmed this for me:
I have been sending the MAV_CMD_START_RX_PAIR according to the Yuneec developer page. See post #8
To do this, I have been using MAVproxy connected to my flight controller via USB. see my post #8 and #9
However…none of these attempts have been successful. Likely because I thought the MAV command was all the RX needed.
Do you have a link to the document you are refering to? If this is the case - then this confirms that we really need to get our hands on a yuneec flight controller (“FC0”) and capture the bind command and also explains why my attempts to send the bind command to a Pixhawk is not working, lol.
I can test that, but I am a novice with regards to serial connections. Can you give me some guidance on how you connected it? Maybe a picture or diagram of the wiring? Is it as simple at TX<>RX, RX<>TX, Vcc and GND? only thing is i think the sr24 is 3.3v - isnt USB 5v?
Any recommendations on serial port tool? Ive used PuTTy at work a few times - will that do the trick?
I am using RealTerm set for 115200, n, 8, 1. But there are also a ton of other settings that i dont have enough knowledge to understand.
I accidentally put 5v on the RX/gray wire…just got the wrong pin. TX light on my serial/usb converter flickers and the terminal sent it, but no reaction on SR24. Did I kill it with 5v on gray?
I tried an OSEPP ftdi and another no-name silabs converter
I have not been successful with the hex command, but I am not fully confident I am getting the command sent. is there anything special about hex format? as long as the numbers and letters 55 55 08 04 00 00 42 49 4E 44 B0 get sent in that format, it should be all good, right?
maybe i am just second guessing myself…
The TX light of my serial converter flickers but its a really weak flicker
another possibility is that your sr24 module is for tx but not for rx.
you know yuneec use the same sr24 module in both the transmitter and drone
it is difficult to judge if one sr24 is for rx or tx from its appearance, since only the firmware inside is different.
sorry, I don’t have any experience with pixhawk.
what I’m trying now is to make an adaptor board using arduino, which can convert sr24 to standard pwm. then I can use it in my rc toys