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.
Hi,
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
Baud 115200
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.
I am having trouble getting the Yaapu script + TXMOD to work properly on my new TX16S Max. I am running TXMOD 1.46/ modem 3.38 and airside 900x 3.38. The script seems to be partially working. I am getting GPS info but the HUD is choppy and delayed, it will not display flight modes and displayed amps is erroneous.
When I go to the Telemetry page on the TX16S and discover new sensors it only shows RSSI and GPS. To the folks that have this working, should there be additional sensors shown in this list when connected? BTW, I am powering on the drone first and RC second. Thanks for any input.
The sensors screen really doesnt matter once you are using yaapu scripts
What does the TXMOD web interface list for all the radio settings? (channels, baud rates, air rates and so on…)
Does the TXMOD and the remote radio both have solid green link LEDs the whole time? or do they periodically blink?
We use a TX16S with TXMOD V2 with SBUS for RC control, these are the settings:
Those were captured using the RFD Tools, but the TXMOD web interface allows you to change all the same settings. SBUS control options weren’t shown when I captured this screenshot.
There’s other threads around here with more screenshots.
Edit:
In the TXMOD web interface there’s a WiFi section where right down the bottom there’s a baud rate, and you need to set that to be the same as the main Baud that you set for the RFD radios, such as 115200
I figured it out. I did not have mavlink enabled on the airside radio (it was on Raw). All seems to be working now. All settings other than that were good except I prefer 57600 baud to increase range.
Everything also appears to still work normally if the RC is powered on first (which is preferred).
what range do you need? I would do some sort of range check, and also test all you failsafes are working.
My high baud rate settings are probably good for near the published official range of 40km. On the default baud rate settings I know of these RFDs doing over 150km.
sorry… long time since I finished my setup… what do you mean with UGCS ?
The main problem in my case, apart from the software/firmware configuration what in the wiring… the cable provided by Holybro were for PPM not for S.BUS…
It’s been a while since I used UgCS with the TXMod radios so I don’t remember the details but at the same time I don’t remember it being a lot of trouble for me. If the computer running UgCS is connected to the WiFi from the TXMod radios then it should be TCP or UDP link. I don’t have access to the TXMod unit otherwise I’d check the link format. Double check your port settings. I’m going to guess it’s either 8080 or 14550.
Hi everyone, I am having the following issue with my TX MOD + RFD900x setup:
I have both units connected, PPM pass-through working, WiFi connection to the GCS - and the system seems quite nice.
However when I power cycle the system, turn everything back on, connect to the WiFi access point, the radios either don’t connect, or they do but the S16/S17 parameters have reverted to 0/0 so ppm pass through doesn’t work. In the case that the radios don’t connect at all, I pull up parameters and it is because they revert to the default NETID etc.
It appears I cannot get these radios to save and remember their settings! Does anyone have thoughts / experience on this?
Thanks
After some more tests, power cycling the tx mod side of things always resets s16: from 1 to 0 and can even revert the airside 900x back to default netID=25
Thanks, yeah that was the first thing I did in order to get them talking to begin with. Have both on 3.56.
I’ll try contacting support but otherwise quite puzzled.
