I not sure if this helps but have installed a few of the Yaapu with full color on the TX16s but I downgrade flash the receiver. Amazon.com: FrSky R-XSR Ultra SBUS/CPPM D16 16CH Mini Redundancy Receiver for RC Multirotor FPV Racing Drone : Toys & Games
FW-RXSR-ACCST_v191128-1.zip (499.6 KB)
My experience has more closely reflected xfacta’s than atex’s. Mission Planner connects via UDP or TCP, loading parameters is slow but not too bad. With my current settings the number of false Yaapu audible alerts (flight mode changes and arm/disarm status) is now only once every 5-10min or so, but about 5% of the text messages are still mixed up.
One difference in my settings to ATex’s is that I have RTS/CTS enabled on both ends (which on the FC end requires the extra cables to be connected and BRD_SER1_RTSCTS set to 1, RFDesign states that auto is unreliable). RFDesign said this will “help with both the system being overwhelmed with data on start up and any potentially corrupted packet issues, as UART buffer overflow is a factor in both of those problems”.
Reducing message rates (in Mission Planner config) to 1Hz reduces the Yaapu errors. This still results in a lot of un-necessary information being sent, so some further fine tuning beyond what is easily done through the GUI might resolve the issue. I found reducing the baud rate to 57600 also helped (I guess this forces the FC to reduce the amount of data it’s sending which seems to address shortcomings in the TX Mod). This is also why I think that Yaapu has more errors when Mission Planner first starts or if you refresh the parameters, it causes the FC to send more data which the Tx Mod can’t handle. Maybe a further reduction in baud rate might fix it… I’ll test that soon.
I’ve stuck with EdgeTX firmware 2.8.0. With the current version of the firmware it does work again, but I get a much higher Yaapu error rate and Yaapu sometimes crashes when it tries to convert erroneous non-numeric data to a number. It’s interesting that recent firmware is working for xfacta.
I will be doing some range testing in the next few days. I’m legally restricted to VLOS, so nothing impressive like ATex’s missions, but I do want it ultra reliable in a 500m range. ATex – what antennas were you using?
One further observation is that for me I haven’t noticed different outcomes if I start the receiver or FC first.
Thanks for the responses guys, I have some good options to look at.
xfacta ive gone blank on the port 23 ? I connect wifi from Tx mod to laptop, no password required, port 23 sounds familiar but is that a generic thing in Tx settings or is it in MP. Then i connect to mp via udp, i dont remember if i get an option for port 23 or not? Btw i will go back through your guide and try again. Note: my version atm is 2.8.4, i will also try 57600
I am not home atm so will be back at it in a month. Thanks Quadzilla and Klaash that info is useful and validates
Range wise I am happy at this stage - AC has 2 x right angle small 900 aerials (located under Vtail) Tx has done well with 2 x standard longer tx 900s and similar range tested with 1 x standard longer 900 tx aerial plus 1 x white 500mm omni fiberglass aerial from rfdesign website. I think i can improve range by testing with better locations and type of aerials on ac. Fyi i have not proven the white omni to be affective as yet. more to be done. Thanks again
Port 23 is specified in the MissionPlanner connect disalog, along with the TCP IP address of the TX-MOD
Thanks Shawn, yes no silly error their
Can you please share radio settings for ETX 2.10.6?
I haven’t had any success with this setup, but Crossfire works well.
I’m still using EdgeTX version 2.9.4 so far, I havent had a chance to do the update.
What sort of settings are you after?
Oh, I was reflashing back my Radiomaster TX16S yesterday and messed up the settings, so I had to restore the model configuration file all this time XD.
Yeah, my RFD was also fine working with Yaapu on version 2.9.4.
Are the ETX developers aware of the issue?
I use the Companion extensively and save the config as a file. Some updates convert the models during the update, so you cannot easily go back. You have to do the downgrade then restore your models from the previously saved file.
I could send you my TXMOD model config but you wont be able to make sense of all the switches and stuff I have set up - it will be easier for you to reconstruct yours the way you were familiar with.
