Search the Community
Showing results for tags 'frsky'.
Found 5 results
-
What is going on at FrSky? Late last year FrSky introduced a firmware update to the TX RF module along with a corresponding RX firmware. This was listed as V 3.0.1. Almost immediately there were reports of "bricked" RX's! It was later learned that the common thread with the bricked RXs was that the customer tried to update the RX using the much touted OTA (over the air) feature. In early January conscientious dealers (not FrSky) put out a warning to not update to the new RF firmware v3.0.1. It is now March and this RF issue hasn't been resolved! This is typical Frsky not having a robust quality system in place for firmware updates. (Using their customer base as unpaid beta testers!) This is unacceptable for a consumer product. I knew FrSky had employed a professional software engineer to develop their fantastic Ethos OS. I had hoped that the discipline need to write solid code would have trickled down to FrSky's engineering house. This fiasco that is the latest RF debacle is so disheartening proves to me that this is not the case. What is going on with FrSky? Are they working on the issue? Tis RF issue is hampering many of the upgrade features that were to come out with the Ethos 1.6 upgrade. Has FrSky abandoned the RC market? I love the dual RF bands of the Frsky product line! But the it is clear to me that FrSky still lacks the corporate structure to effectively manage the software and firmware side of the product line. These corporate and cultural issues of discounting the customer, customer experience is really getting old! Anybody know what is going on at FrSky and more to the point what is going on with the follow up the RF firmware to v3.0.1? Where's the link to Jeti?
-
I'd like to point out what I see as an engineering flaw in the IDS servo trays from FrSky. Here I'll be showing FrSky's IDS (5611) but the issue is the same for the larger FrSky IDS (5101). I'm planing to use these FrSky IDS servo trays for their external bearing support feature on my NoBody build. I'll go into more detail in that thread but thought it might be good to give notice in the FrSky forum. The core issue is that there is no bearing retention feature for the ball bearing. Most external bearing support trays from Servorahmen had the bearing held captive between an outer lip and the servo arm. With these two trays the bearing stop lip is on the inside of the pillow block rather than on the outside. This means the the bearing is free to fall out of the pillow block and get lost in the wing. The only fix I've come up with is to use some thin CA and allow it to wick by capillary action between the bearing and the pillow block. This is very dangerous as there is a high probability that the CA might get inside the bearing and lock up the rolling elements. P.S. While not mentioned in the documents I've seen, the IDS for the 5611 will fit the W5651H servo.
-
This might not be the best place to place this notice as I see it has been dead here for close to a year. But here goes. Earlier this month I spent 2 weeks in Denver helping my good friend Matt acquire his AMA turbine waiver. I was acting as his spotter and engineer. It went rather easily but for one nagging problem. The new Kingtech turbine a K102 kept having start issues with premature shut down. This traced to the lack of proper heat rise recorded by the thermo coupler. We noticed that prior to start up the EGT was bouncing around 0°C to 125°C and this was with the ambient temp at around 22°C. We changed out the turbine and after a few flight notice that this low time turbine was also exhibiting start problems. Again we say the EGT bouncing wildly prior to any start attempts. We borrowed a third low time turbine (I think a K85) and again noticed the bouncing EGT. This lead me to think that Kingtech had a problem with their vendor for the EGT thermocouples. We had sent the first K102 back as soon as we removed it. Matt was able to get in the required time and perform the demonstration/qualification flight with the borrowed turbine. You can see some of it here. (He just had to show off with a touch and go to show mastery of the required energy management). https://www.youtube.com/watch?v=-dDSsrVQKiU&t=169s Well, Kingtech just got back to us with their findings of no faults found. As a safety guy this always bothers me! But they did suggest where the problem might lie. They asked what radio we were using. I was thinking what does this have to do with anything? Well, they suggest with the dual band FrSky radio we were using that if we had the 900 mHz power output raised that is was very likely that the thermocouples was picking up RF noise resulting in the ECU thinking this was temp data and putting out erroneous data. Well Matt and I had set the 900mHz power level at 200 mW and 100mW respectively. I just did an engine start with the 900 mHz band's power level set at 25 mW and the EGT on the borrowed turbine was stable prior to the start. As a result we have had constant starts with the borrowed turbine. I look forward to seeing if this was in fact the issue with the turbine we sent back. So if you are having inconsistent start issue with your turbine check the RF power output of your TX. I suspect that there is a weakness in the RF shielding allowing the ECU to see too much RF noice.
-
I’m having issues setting up a wired buddy box link between a QX7 and a Radiomaster TX16S. i have tried many things spent a lot of time and read lots on the internet but nothing works. I have tried mono and stereo leads, I have tried either tx as master or slave, I have tried different switches to transfer control, I have read RCDIY’s posting on the net and Sean Culls posting and many others too. I am obviously missing something basic but I have no idea what it is. I have programmed over 30 models using OpenTx, updated firmware many times and am familiar with companion but this is the first time I am truly puzzled as to why this doesn’t work. Does anyone have any thoughts please?
-
So Frsky have announced the X18, apparently incoming in the next month or two - ETHOS based with touch capability, Tandem RF equipped (giving redundant links via simultaneous 2.4GHz ACCESS/D16 ACCST and 900MHz transmission), smaller lower res screen vs the X20 and a price around the same as the current X9D+: (It also comes in black) I personally love the Open source firmware projects and feel conflicted about supporting Frsky given how they end of lifed D8 and tried to “lock” their ecosystem with the changes to D16 and introduction of ACCESS. It seems they are becoming another proprietary manufacturer (probably time to change the subtitle of this forum… ?), but the absence of affordable alternatives that offer similar functionality AND build quality along with a form factor that fits my hands has me pondering options. My original X9D is nearly 10 years old now, and the RM TX16S I bought for quads just doesn’t feel hat solid in my hands though nothing has actually gone wrong with it. Decisions decisions… RCGroups product release thread on the X18
