Flying Dutchman
Strong User
Is there a way to effectively test an SD card on your PC? Will the "Error check" function show anything if using one of these 'low quality' cards?
Aloft Forums
Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Almost made the Jump to Jeti !!! ( ACCST v2.1.0 Frustration)
Konrad
Very Strong User
I know it is futile with FrSky's management.
But somebody needs to try to get them to be responsive to the customer interface/experience. If nobody bitches nothing will change.
Here I try to show the issue, how I identified the issue and "MY" final solution. (No, not jumping ship to Jeti, but the need for a new SD card when making software updates).
All the best,
Konrad
But somebody needs to try to get them to be responsive to the customer interface/experience. If nobody bitches nothing will change.
Here I try to show the issue, how I identified the issue and "MY" final solution. (No, not jumping ship to Jeti, but the need for a new SD card when making software updates).
All the best,
Konrad
Last edited:
Flying Dutchman
Strong User
Do what you must, Konrad, but do you really believe that the folks at FrSky are reading this forum to see another rant from you? OK, eventually Google may pick them up, but be careful and selective in what you say and how you say it, or you'll simply be seen (and dismissed) as a FrSky hater. The regular users of this forum (e.g. me) may be willing to read a lengthy article or diatribe on the subject, but most others won't. If you want to have any chance of making an impact, then (1) succinctly state the problem and why, (2) propose a solution, and (3) close. The more words, the less impact.
Konrad
Very Strong User
Thank you Dutch.
I do write for the Google search engine. I know the 5 or so of us on this site know each others position and expectation with regards to quality from FrSky.
I wrote this thread in a story format. So as to not be so dry.
I answer posts that don't make since with a question or clarification. Like my issues were as a result of using a Mac to upgrade to ACCST. What hog wash. In fact I get much better results with the Mac as opposed to the driver issues with Windows.
Wayne said to move to the latest and greatest OpenTX. I still don't understand why one would make this recommendation as it introduces possible incompatibility issue with the model programs already written on the older versions.
No,I know the management of FrSky does not read this forum. Heck they rarely even follow the advice from their own dealer network. But if they loose enough potential sales from the honest post we user make about the poor user interface. Maybe, just maybe the management of FrSky will give "some thought" to the customer experience.
But the real reason for the many threads I make on Aloft's forum is to expose folks to the issues I see with products I've purchased and to post the work arounds I have used to address these issue. I want you the customer to get the most from your hobby time and money. And the best way I know to do that is to show what has worked for me.
Now there is a bit of give and take on this forum, as I ask those that I think are in the know for their solutions to issues I've seen. Doc. Hammond, Kilrah, and Wayne are just a few of the many contributors who's knowledge I appreciate. They have pull my butt out of a jambs many times.
Rant? Isn't the failed upgrade process a legitimate concern. Be it all the way back to the beginning with the disregard of the advice from their own dealers to the lack of configuration control (new RX's wouldn't talk with new TX's as they were incompatible with v1/ v2 firmware) with in the current production time line. To my personal issue with so many faulty SD cards. You are correct I don't turn the other check. I try to fight back against unresponsive management with the limited tools I have, the check book and the forums.
To be clear Aloft has been doing a yeoman's job at customer support, with the limited customer support offering from FrSky. With FrSky it is real important where (whom) you get your equipment from.
Wayne, told me not to buy the stabilized RX as they weren't stable at the time I bought them. He pointed me to the high page count on this forum. It was he who said not to update to the latest OpenTX as the current model programs will not in all likelihood work with the latest and greatest without a bit (lot) of rewriting. It was he who told me that my first set of firmware updates (way back in 2017) were due to me trying to perform the updates on a Windows machine. It was Chris (Aloft's great tech) who twice got my FrSky machines to work simply by replacing the SD card.
So whatever pissing match you might be reading between me and some fan boy, thinking I'm being unfair in my assessment of FrSky. I try to give a history for why I make the statements I do. Be it FrSky or other faulty, substandard product. (Now my product reviews are aimed a bit towards helping one make the correct purchase in the hopes that Aloft will make a sale and that the customer will be happy with the purchase. The product review is a different platform than these forum).
No, not all FrSky products are substandard. But enough have issues that if FrSky put some effort into solving the customer interface issue BEFORE release we would all be much happier!
I do write for the Google search engine. I know the 5 or so of us on this site know each others position and expectation with regards to quality from FrSky.
I wrote this thread in a story format. So as to not be so dry.
I answer posts that don't make since with a question or clarification. Like my issues were as a result of using a Mac to upgrade to ACCST. What hog wash. In fact I get much better results with the Mac as opposed to the driver issues with Windows.
Wayne said to move to the latest and greatest OpenTX. I still don't understand why one would make this recommendation as it introduces possible incompatibility issue with the model programs already written on the older versions.
No,I know the management of FrSky does not read this forum. Heck they rarely even follow the advice from their own dealer network. But if they loose enough potential sales from the honest post we user make about the poor user interface. Maybe, just maybe the management of FrSky will give "some thought" to the customer experience.
But the real reason for the many threads I make on Aloft's forum is to expose folks to the issues I see with products I've purchased and to post the work arounds I have used to address these issue. I want you the customer to get the most from your hobby time and money. And the best way I know to do that is to show what has worked for me.
Now there is a bit of give and take on this forum, as I ask those that I think are in the know for their solutions to issues I've seen. Doc. Hammond, Kilrah, and Wayne are just a few of the many contributors who's knowledge I appreciate. They have pull my butt out of a jambs many times.
Rant? Isn't the failed upgrade process a legitimate concern. Be it all the way back to the beginning with the disregard of the advice from their own dealers to the lack of configuration control (new RX's wouldn't talk with new TX's as they were incompatible with v1/ v2 firmware) with in the current production time line. To my personal issue with so many faulty SD cards. You are correct I don't turn the other check. I try to fight back against unresponsive management with the limited tools I have, the check book and the forums.
To be clear Aloft has been doing a yeoman's job at customer support, with the limited customer support offering from FrSky. With FrSky it is real important where (whom) you get your equipment from.
Wayne, told me not to buy the stabilized RX as they weren't stable at the time I bought them. He pointed me to the high page count on this forum. It was he who said not to update to the latest OpenTX as the current model programs will not in all likelihood work with the latest and greatest without a bit (lot) of rewriting. It was he who told me that my first set of firmware updates (way back in 2017) were due to me trying to perform the updates on a Windows machine. It was Chris (Aloft's great tech) who twice got my FrSky machines to work simply by replacing the SD card.
So whatever pissing match you might be reading between me and some fan boy, thinking I'm being unfair in my assessment of FrSky. I try to give a history for why I make the statements I do. Be it FrSky or other faulty, substandard product. (Now my product reviews are aimed a bit towards helping one make the correct purchase in the hopes that Aloft will make a sale and that the customer will be happy with the purchase. The product review is a different platform than these forum).
No, not all FrSky products are substandard. But enough have issues that if FrSky put some effort into solving the customer interface issue BEFORE release we would all be much happier!
Last edited:
Flying Dutchman
Strong User
Konrad, I probably agree with you most of the time, especially when it's about nuts & bolts issues.
But my point was really about something else.
There is a time for going into minute detail, and perhaps repeating something a few times, such as in technical reviews and build logs; and yours are very good. E.g. your Samsara log was a big help to me in my recent builds, and I appreciate that. Your background in engineering shows, as does your tenacity in certain areas.
But those qualities do not necessarily help when trying to convince others to see/do things differently. As an ex-Marketing guy (originally trained as a ME) I value a clear and succinct message, one that actually does convince others, and is actionable. The trick is to understand your audience, whether it's consumers or company management, and connect with them in a way they can (and want to) relate to. If you don't, your message is simply an expression of your opinions and feelings, i.e. a rant. Rants can be cathartic for the originator, and entertaining for some readers, but they have little further impact. Too many rants, and the ranter is ignored. And that would be a shame.
Therefore, keep critiques focused, short and sweet, and try to think like the intended recipient. You have a lot to say, so when you do, make sure it has impact. And then, let it go. No point in repeating it 10 times if the first 3 made no difference. Unless you simply feel like ranting, which is fine, but in the long run probably not satisfying.
But my point was really about something else.
There is a time for going into minute detail, and perhaps repeating something a few times, such as in technical reviews and build logs; and yours are very good. E.g. your Samsara log was a big help to me in my recent builds, and I appreciate that. Your background in engineering shows, as does your tenacity in certain areas.
But those qualities do not necessarily help when trying to convince others to see/do things differently. As an ex-Marketing guy (originally trained as a ME) I value a clear and succinct message, one that actually does convince others, and is actionable. The trick is to understand your audience, whether it's consumers or company management, and connect with them in a way they can (and want to) relate to. If you don't, your message is simply an expression of your opinions and feelings, i.e. a rant. Rants can be cathartic for the originator, and entertaining for some readers, but they have little further impact. Too many rants, and the ranter is ignored. And that would be a shame.
Therefore, keep critiques focused, short and sweet, and try to think like the intended recipient. You have a lot to say, so when you do, make sure it has impact. And then, let it go. No point in repeating it 10 times if the first 3 made no difference. Unless you simply feel like ranting, which is fine, but in the long run probably not satisfying.
Konrad
Very Strong User
Wayne, I understand your frustration in that I seem to find fault with just about every "new" FrSky product I've purchase. You have addressed these issues, with great customer service!
In this case my first post was a bit long in that I tried to use a bit of a story narrative. I could have said FrSky supplied SD cards are junk. If having upgrade problems with ACCST v2.1.0 replace SD card with new one of higher quality. To my thinking that is a bit too dry and leaves out some clues that might help others identify a faulty SD card.
Yes, I agree AHHH with the constant FrSky quality issues, from the SD-card, to the poor fitting large battery caps on the "NEW" X Lite-S. It really is a testament to the power of OpenTX that I've stayed with FrSky*.
So, yes I have a love/hate relationship with FrSky.
Now could you tell me how moving up to the latest OpenTX would have alleviated this particular ACCST update problem.
To whomever made the windows statement, I'm still willing to learn how using a windows machine would have helped.
Of the may issues brought to my attention in this thread. These two are still open.
Not only am I here to identify product issues and offer my solution. I'm here to learn about how to properly interface with our hobby products.
* I know of no other OEM that runs OpenTX that comes anywhere near the engineering chops as FrSky. So while there are other radios that run OpenTX. FrSky is still the vendor of choice (by a long shoot) if one wishes to run OpenTX. Unfortunately Jeti does not run OpenTX. So the jump to Jeti real was a hollow threat
In this case my first post was a bit long in that I tried to use a bit of a story narrative. I could have said FrSky supplied SD cards are junk. If having upgrade problems with ACCST v2.1.0 replace SD card with new one of higher quality. To my thinking that is a bit too dry and leaves out some clues that might help others identify a faulty SD card.
Yes, I agree AHHH with the constant FrSky quality issues, from the SD-card, to the poor fitting large battery caps on the "NEW" X Lite-S. It really is a testament to the power of OpenTX that I've stayed with FrSky*.
So, yes I have a love/hate relationship with FrSky.
Now could you tell me how moving up to the latest OpenTX would have alleviated this particular ACCST update problem.
To whomever made the windows statement, I'm still willing to learn how using a windows machine would have helped.
Of the may issues brought to my attention in this thread. These two are still open.
Not only am I here to identify product issues and offer my solution. I'm here to learn about how to properly interface with our hobby products.
* I know of no other OEM that runs OpenTX that comes anywhere near the engineering chops as FrSky. So while there are other radios that run OpenTX. FrSky is still the vendor of choice (by a long shoot) if one wishes to run OpenTX. Unfortunately Jeti does not run OpenTX. So the jump to Jeti real was a hollow threat
Last edited:
Konrad I also agree and enjoy your nuts and bolts builds. I find then very informative and well presented.
However some of your technical frustrations and dislikes leaves your readers disconnected because you are expressing a view point possibly not shared by others. Ranting in multiple posts about the subject does not fix that issue.
So keep the posts short, positive and to the point. I was not saying a Mac is bad and a PC is good, just have you tried another solution.
There is so much we can share and that's what the blog site is about.
Henny
However some of your technical frustrations and dislikes leaves your readers disconnected because you are expressing a view point possibly not shared by others. Ranting in multiple posts about the subject does not fix that issue.
So keep the posts short, positive and to the point. I was not saying a Mac is bad and a PC is good, just have you tried another solution.
There is so much we can share and that's what the blog site is about.
Henny
Kilrah
Very Strong User
You complained about not being able to flash .frsk files and were told in response that an update was needed for that, and as such you would not have had this problem if you were up to date. That's it.
From a support point of view it's also easier to have people on the latest version since when you deal with it every day you're not going to remember what a version from 2 years ago had or didn't have and how it'd relate or not to the issue at hand, hence "update and come back if you still have the issue" is a common support answer everywhere in consumer tech.
Konrad
Very Strong User
Thank you.
I could have made a short and sweet statement and just said; that FrSky sucks, and run away. That statement isn't accurate and I don't see how that would have helped anybody.
But I can't in all good conscience say anything positive about features or products that are a failure or are flawed. Yes, just about anything in science or engineering that isn't a first principle has a component of ones view point. As engineering is the science of compromise I try to point that out. When it comes to software I don't know the code (line by line). So I can only complain about the output's lack of cohesiveness. I hope my posts don't come off as the definitive answers. Remote troubleshooting (using the forums) is all about probabilities.
I read your comment about the Mac as being the source of the SC card mis-read. Your quote "Get a windows machine, this will be at much lower cost to a Jeti solution.". I have never seen this. In fact, I have seen where the OS Windows has given the user many problems with the drivers. So much so that the service center (Aloft Hobbies) had to upgrade my radio from OpenTX 2.1.9 to 2.2.1 on a Mac. I was trying to originally do the upgrade on a windows machine. (Yes, I've had USB driver issues with both the Mac, and Windows machine. But these are often addressed by just plugging into another USB port on the same machine). I'm harping on the idea that the problem was with the Mac as this is not the case and there was no need to muddy the issue with such a comment. I have history to show just the opposite, in that the Windows machines are often the issue.
That is exactly what I did in my first post. I was sharing my experience with the ACCST v2.1.0 upgrade, my frustrations and my solutions. I hope that sharing my experience will give other user of FrSky a more enjoyable experience than the one I just had. ( To be clear I just had over 65 hour on ACCST v2.1 of RC flying without a radio glitch
).All the best,
Konrad
Last edited:
Konrad
Very Strong User
Oh, the more modern OpenTX comment was aimed at the .frsk issue!
You are correct in that I wanted to update all my ACCST rx to ACCST v.2 for the simplification that having all my RX on one protocol affords me. As an engineer I do track what maintenance actions I've performed on what equipment. So having multiple protocols isn't going to be as much a problem for me as it might be for others. But it still is a good practice to try to bring as much as possible to a common protocol.
Try "X" and come back if the issue still persists is a common practice. But in the case of an OS update one needs to say what might be some of the secondary ramifications of making the change. In the case of the more modern OpenTX, Wayne has told me that many of the model programs I've written in the classic version will not run properly on the modern versions of OpenTX without a lot of rework.
My reason for being in this hobby is to fly toy airplanes, NOT rework code or my model programs.
The .frsk was a secondary observation and really wasn't much of a concern as I don't fly with gyros. I'd gladly give up on the use of the stabilized rx ACCST v2.1.1 .frsk to keep the programs for models I have written on the older OpenTX full functional. So the next time I see the need to upgrade I may just upgrade these stabilized receiver to ACCST v2.1.0 .frk (Actually I'm thinking that maybe I'll just assign these receivers to the modern TXs running OpenTX v2.3.10 and higher and upgrade the receiver to ACCST v2.1.1 .frsk).
All the best,
Konrad
Last edited:
Konrad
Very Strong User
THANKS!
To be clear. Moving from OpenTX 2.2.4 to OpenTX 2.3.xx will allow the old model programs to work as originally written? The Module is the RF module? So I might have to identify the use of ACCST vs ACCeSS. Sounds like a very minor nuisance for a major upgrade in revision number.
All the best,
Konrad
To be clear. Moving from OpenTX 2.2.4 to OpenTX 2.3.xx will allow the old model programs to work as originally written? The Module is the RF module? So I might have to identify the use of ACCST vs ACCeSS. Sounds like a very minor nuisance for a major upgrade in revision number.
All the best,
Konrad
Last edited:
Scott Page
Very Strong User
Simple case of Dunning-Kruger Effect.
Konrad
Very Strong User
Me or Frsky's management thinking they can manage the implementation of a major software change?
I do admit that the corrupted SD card did throw me for a loop.
As to the Stabilized RX .frsk file extension needing OpenTX above some revision number. I admit I don't see this requirement in the read me files. I again admit I don't have the secret decoder ring for FrSky's software. That is why I read the READ ME files, in the false hope that there are clear concise instructions on how to proceed with the implementation of any new software.
Heck, I even watch the videos linked in the READ ME files. Gawd, what a painfully slow way to transmit information!
All the best,
Konrad
The READ ME FILE in the SxR-ACCST_2.1.0 folder
*******************************Release Note******************************************
This Package is for S6R/S8R ACCST v2.1.0 firmware update.
Version and Files:
S6R_ACCST_2.1.0_FCC.frk Firmware under NonLbt mode which is certificated for FCC rules.
S6R_ACCST_2.1.0_LBT.frk Firmware under LBT mode which is certificated for CE rules.
S8R_ACCST_2.1.0_FCC.frk Firmware under NonLbt mode which is certificated for FCC rules.
S8R_ACCST_2.1.0_LBT.frk Firmware under LBT mode which is certificated for CE rules.
S6R_ACCST_2.1.0_vtail_FCC.frk Firmware under NonLbt mode which is certificated for FCC rules.
S6R_ACCST_2.1.0_vtail_LBT.frk Firmware under LBT mode which is certificated for CE rules.
S8R_ACCST_2.1.0_vtail_FCC.frk Firmware under NonLbt mode which is certificated for FCC rules.
S8R_ACCST_2.1.0_vtail_LBT.frk Firmware under LBT mode which is certificated for CE rules.
readme.txt Release note
Note:
The Vtail file is specifically for the users who fly Vtail mode. You may lose all previous settings after updating the device, please reset all calibrations again.
Firmware Version: v2.1.0
ACCST D16 2.x.x - This upgrade is designed to enhance the reliability and performance of radio transmission in all external conditions. It is strongly recommended that all FCC/LBT users update all their equipment to version 2.x.x. This includes all radios, RF modules and receivers.
We are grateful to you all for supporting FrSky. Especially thank those who reported the issue, provided the information, and assisted with many tests.
Please update the firmware of all your radios, RF modules and receivers accordingly.
The release history:
--------------------------------------------------------------------------------------------------------------------
v2.1.0
1.Fixed the channel output error (uncontrolled servo movements) under certain conditions.
2.Strengthened correction and verification capability.
Note: Please update the firmware of all your radios, RF modules and receivers accordingly.
---------------------------------------------------------------------------------------------------------------------------------
How to upgrade receivers please refer to the info below:
With X9DP:
With other radios which have s.port please choose [Flash s.port] in menu .
1. Put the firmware under the folder [FIRMWARE] of sd card.
2. Power on the radio and find the firmware,select it by press [ENT].
3. Select 'Flash S.port ', wait to end.
With Airlink S :
With STK:
---------------------------------------------------------------------------------------------------------------------
More details please check FrSky website:
S8R - FrSky - Lets you set the limits
The S8R is a FrSky X-series receiver with built in 3-axis stabilization.
www.frsky-rc.com
S6R - FrSky - Lets you set the limits
www.frsky-rc.com
**********************All rights reserved to FrSky Electronic ., Ltd.*********************************
And the READ ME FILE FOR v2.1.1 found in the SxR-ACCST-2.1.1-FCC folder
This Package is for S6R/S8R ACCST v2.1.0 firmware update.
Version and Files:
S6R_ACCST_2.1.1_FCC.frk S6R firmware under NonLbt mode which is certificated for FCC rules.
S8R_ACCST_2.1.1_FCC.frk S8R firmware under NonLbt mode which is certificated for FCC rules.
readme.txt Release note
Note:
Please use 2.1.0 firmware for other modes. Only FCC mode has the telemetry update issue which needs to be fixed .
Firmware Version: v2.1.0
ACCST D16 2.x.x - This upgrade is designed to enhance the reliability and performance of radio transmission in all external conditions. It is strongly recommended that all FCC/LBT users update all their equipment to version 2.x.x. This includes all radios, RF modules and receivers.
We are grateful to you all for supporting FrSky. Especially thank those who reported the issue, provided the information, and assisted with many tests.
Please update the firmware of all your radios, RF modules and receivers accordingly.
The release history:
v2.1.1 FCC ONLY
1.Fixed the issue of the telemetry update is slow when work with X20/X20S.
--------------------------------------------------------------------------------------------------------------------
v2.1.0
1.Fixed the channel output error (uncontrolled servo movements) under certain conditions.
2.Strengthened correction and verification capability.
Note: Please update the firmware of all your radios, RF modules and receivers accordingly.
---------------------------------------------------------------------------------------------------------------------------------
How to upgrade receivers please refer to the info below:
With X9DP:
With other radios which have s.port please choose [Flash s.port] in menu .
1. Put the firmware under the folder [FIRMWARE] of sd card.
2. Power on the radio and find the firmware,select it by press [ENT].
3. Select 'Flash S.port ', wait to end.
With Airlink S :
With STK:
---------------------------------------------------------------------------------------------------------------------
More details please check FrSky website:
S8R - FrSky - Lets you set the limits
The S8R is a FrSky X-series receiver with built in 3-axis stabilization.
www.frsky-rc.com
S6R - FrSky - Lets you set the limits
www.frsky-rc.com
**********************All rights reserved to FrSky Electronic ., Ltd.*********************************
Last edited:
Scott Page
Very Strong User
And that illustrates the Dunning-Kruger Paradox.
Similar threads
