Great to hear! Glad to help.
If you do notice anything strange about the failsafe work around please share it.
Great to hear! Glad to help.
If you do notice anything strange about the failsafe work around please share it.
Hey @Yasiinm, @Allister, thank you for posting this, I will try the suggestion and inform on my results. I have the TXMod V2 and RFD900x combo, also on a TX16S and I’m also having trouble getting it to work correctly. I would like to set it up to have this where I can get the Yaapu telemetry working on the Tx and sending Mavlink to a GCS via wifi. Please let me know if you guys have pointers on the telemetry piece as well.
The Yaapu telemetry does work, but there are some errors with the warnings. In fact I’ve turned off all the audible warnings because I get these random “Telemetry Lost” or “Disarmed” messages. They clear up and they are very obviously false warnings, but It just gets my heart rate up when I don’t need it.
I’ve found the wifi connection for the GCS is solid, once you get it connected. I have altered my start sequence to get everything going and it’s works very reliably:
I don’t wait long between the steps. In fact I’ll power up the plane with the radio sitting right beside me and turn it on as soon as finished securing the battery. I only do it this way because of the Yaapu telemetry. If I have the radio on first then power the plane (the traditional way to power things up) then I find the Yaapu script has errors. Most annoying it’s displaying the wrong flight modes, the battery voltage is wrong. But I discovered if the airplane (probably more importantly the RDF900X) is powered before the TX16S, then all the scripts are correct.
Once the plane and the radio are connected then mission planner will start up just fine. MissionPlanner should automatically detect the wifi connection to the flight controller and start to download parameters. Again, if Mission planner is running before the connection is made, I found it quirky to connect.
The system has it’s quirks. But so far I’ve found it to be solid in flight. The wifi connection to the GCS has been one of the most reliable that I’ve used. The warnings that come up for on Yaapu are script errors and not real issues. It’s disappointing that I had to turn them off, but for the plane I’m using this with I’m usually right beside the laptop once it’s flying so it’s not a big deal.
I’ve also done some ground testing with UgCS and QGroundControl and those both work over this connection. I haven’t flown with them on this system but I wouldn’t expect any problems.
The “start craft before starting radio” routine is something I’ll have to try. I’ve noticed my yaapu telemetry has minor errors or data not displaying like battery capacity, this might just fix that. And I second the link to GCS being rock solid.
Did you have any issues with channel ranges? I found my ranges were weird and have had to tweak them in opentx quite a bit to get the end and midpoints correct.
There’s also a new fw version out for the txmod, I’ve not tried it yet but changelog indicated some change to rssi reporting which might help the intermittent telemetry lost warning.
I remember that the channel ranges were just crazy before I did all the firmware updates to 3.16. I could adjust everything to get it to work but the values were like nothing I was used to seeing. I can’t remember what they are now after the updates but I don’t think they’re anything too abnormal.
Thanks, I just looked: 3.20 is now out. I’ll be doing those updates first chance I get. Unfortunately where I live winter is setting in so our flying time is on hold for a while. Could be some time before I get to test it.
Gents, I can report that with your kind suggestions I have been able to get RC Control, Mavlink telemetry, and Yappu scripts working on my TX16S correctly. Your inputs are much appreciated.
@Allister, The start sequence you outlined is still needed. I was also getting Yaapu script issues until I used your recommended sequence and the issues went away. They were the same ones, incorrect flight modes, and some incorrect values.
I did have to update firmware on both the TXMod V2 and the RFD 900x radio, both to the latest versions, below is how TXMod reports it. By the way, I have not seen Telemetry Lost messages, there is a note in the latest TXMod version that they increased RSSI reporting frequency to address this, and for the past 30 minutes I’ve had it working; I have not got those messages so far.
Software Version: 1.4.6
Build date: Nov 30 2020 10:57:11
Internal modem version: RFD SiK 3.16 on RFD900X
Remote modem version: RFD SiK 3.20 on RFD900X
I decided to go with these versions, even though they are not the same internal and remote RFD900x versions because of the release notes, which I’ll post below for completeness.
I’m going to make a separate post with my full setup showing FC and all pieces, both for my own reference in the future and so it can help others. I’ll post back a link to that thread once I have it done.
The current version of the TX MOD firmware is 1.4.4
This firmware will update the internal modem to V3.15 or V3.16 depending on selected SPIFFS file and will require the paired modem to be updated to the same version.
30/11/20 - 1.4.6 Addresses issues relating to telemetry loss warnings by increasing RSSI report frequency
01/09/20 - 1.4.5 Bugfix: clears cached radio parameters once First Run Wizard is executed
28/08/20 - 1.4.4 Bugfixes and code refactoring: RSSI figure is now reported without an active WiFi connection
06/08/20 - 1.4.2 Added feature that initiates datastreams, without GCS connected to the WiFi, and some minor enhancements.
18/06/20 - 1.4.1 Bugfix: S.PORT also working while connected via TCP
25/05/20 - 1.4.0 Added MavLink to S.PORT support. The user is required to modify the hardware to get the feature working.
12/05/20 - 1.3.12 Bugfix: TXMOD no longer resets modems during bootup
And for the 900x:
RFD X V3.X series modems SiK firmware version release log
The recommended firmware version.
That sounds great! I’m glad that worked for you.
The Telemetry lost messages and disarmed/armed messages are issues with the Yaapu script, they aren’t radio issues. When I’ve verified the telemetry logs for my flights there has been no issue with telemetry and arm status. The RSSI is excellent at all times in my flights. The fault is very rare on the bench, and I only seem to get them in flight and not consistently enough for me to figure out a trigger.
The big take away, is once your aircraft is flying, don’t panic if you hear your RADIO say “DISARMED” from the radio.
The false warnings have never happened on the laptop with MissionPlanner.
I look forward to hearing about your testing with the new firmware!
Just wanted to confirm that with the newest firmware (1.46 TXMod, 3.20 on vehicle radio), I haven’t received any random telemetry lost/motors disarmed messages during flight.
That’s good to know. Flying season is back here and I was just looking into those updates.
thank goodness I found this post. I freaked a bit when the yaapu script randomly told me my motors had armed. I just got my TXMOD V2 setup working, and I can confirm it has the same insanity issues with the audible script warnings.
Question that wasn’t completely obvious to me: when you use the suggested startup sequence, do you still get insane warnings coming through or are they completely resolved?
Also, if the RFdesign folks are listening, this behavior is definitely something to a) note prominently in the manual b) hopefully resolve… Aside from that, I was really impressed with the quality of the instruction manual and how easy it was to set up. I’m eager to see how it all works, hopefully without excessive anxiety from those warnings. There’s just no way for me to hear a random “motors disarmed” while flying and not freak out a bit. I really like the audible notices so I don’t want to have to turn them off, that would defeat some of the purpose of getting the telemetry.
thanks again, I’m really appreciative that you guys sorted this out and posted about it
What version of firmware are you running on the txmod/UAV side radio? I’ve not had the random warnings yet since I upgraded to the latest version (1.46 TXMod, 3.20 UAV side)
I assumed that it would be the latest since they arrived in the mail earlier this week, but I just took a look and discovered that ASSuming is not a good idea.
I have 1.4.5 on the TXMod and 3.16 on the radios. I’ll have to dig back into the manual and figure out how to update them properly, thanks for that heads up.
They’re easy enough to update, manual walks through it well. However, I’ve not had success updating the UAV side radio OTA the way it’s described in the manual, and have had to resort to using an ftdi cable to connect the UAV side radio to my laptop and use rfd tools to update that way. Just a heads up to verify the firmware did update on the UAV side radio if you’re following the txmod manual.
Ok I updated firmware, 1.4.6 on the TXMOD V2 and 3.20 on both of the modems. Definitely still getting the incorrect spastic audible alerts, even when using the recommended power-up order. What’s the consensus, are there any other troubleshooting steps or am I going to have to just live with this for now?
I’ve just flashed the 1.4.6/3.2 firmware. Between lockdowns and weather I can’t fly right now but I wasn’t getting any warnings in the shop. The only thing I noticed was the battery voltage on Yaapu would sometimes go to 0.0v, but come back right away. There was no issues on the battery display on MP.
I’ve also turned the TXpower down to 25 (~310mW if my math is right). Mostly just to reduce heat when I’m working on the bench, but honestly for most of the VLOS flights I’m doing right now it’s probably more than enough.
I’m still having constant issues, both with incorrect verbal warnings as well as incorrect telemetry appearing on the Yaapu screen. 1.4.6 on the TXMODV2 and 3.20 on both modems. What can I do here? Is this simply a product that doesn’t function as advertised? I’m a bit frustrated; the RFD900x have been solid, reliable products, and this TXMOD version is just about opposite that experience.
Maybe you have a faulty product? Factory reset the modems and try again, maybe a baud rate or something got sent out of wack? Set up correctly on ardupilot i.e. Baud rate? Might be worth getting in touch with Rfdesign directly?
Those are the things I can think of, as I’ve not had any random telemetry loss messages since the update and we’ve clocked in another half an hour or so today without issue on our TXMod.
I have a RadioMaster TX16S and have tried using SBUS with the TXMOD V2, I can’t get SBUS working, I can get PPM working with it.
I tried my older Horus X12S and that works perfectly OK with the TXMOD V2.
It looks to me like the RadioMaster TX16S Has a problem talking to the TXMOD V2
Unless anybody else has actually managed to get the TX16S working with SBUS on the TXMOD V2.
We’ve got a TXMOD v2 with Taranis and yaapu telemetry script. Everything functions as expected and no strange issues with flight modes being called wrong or anything similar. Latest OpenTX, latest RFD firmwares.
I couldn’t get the throttle failsafe to work, setting it to -110% didn’t seem respected by the TXMOD (or maybe the Taranis output) and throttle channel did not go below normal in MissionPlanner and the remote end.
I had to set failsafe to mid throttle (and armed, we use a arming switch and channel) and RTL mode, then press the PPM failsafe button.
We use the RFD radios set to high baud rate as per below
Air speed 125
Max window 80ms
R/C In and R/C Out as required by TXMOD and the remote radio
This will give some reduction in range, so do you’re own checks. Unless you are working BVLOS you probably wont be affected by any range limitation.
EDIT: I also meant to say that the higher baud rate also gives an increased update rate on the screen (HUD movement), not just faster than 56k RFD’s but faster than standard Frsky telemetry.
Has anyone run the latest version of fw on the txmod/air side modem for longer than 15-20 mins continuously, with the drone armed and airborne? I’ve not had any false messages come through until last week when we were carrying out endurance flights and we started hearing “Motors disarmed, Motors armed, auto flight mode” blaring out from the transmitter after 15 minutes or so. I thought the latest firmware had fixed the issue but seems like it’s still around.