maxwelltub
Member
That's the million dollar question. I'm switching to super X for their data logging.
IMHO, that's a complicated question. These FC systems are all prone to failures as they're essentially consumer-level and not designed and built to industrial or military standards. Most (if not all) of them lack any true redundancy in any part of their design, so they can all fail in spectacular and catastrophic ways. My strong recommendation is to choose a system based on the availability of support, the transparency of engineering, and the frequency of updates. And, most importantly, you need to spend the serious amount of time actually flying the system to get a good feel for it and to anticipate situations in which it could behave badly or fail altogether.So.... what IS the best pro-level FC with the fewest issues and best customer service?
So.... what IS the best pro-level FC with the fewest issues and best customer service?
Sounds perfect. Like the presidential motorcades that have a fully kitted out paramedic squad just in case. Or test pilots who wear parachutes and have ballistic ejection seats. You can't be too careful.Because this is a new world so I would think the best way to go is to hire someone with a Computer Science degree and use one of those FC with open source firmware and keep them close to you on the job site at all time.
Sounds perfect. Like the presidential motorcades that have a fully kitted out paramedic squad just in case. Or test pilots who wear parachutes and have ballistic ejection seats. You can't be too careful.
But seriously, we kind of have to move away from requiring Chuck Yeager (or Chuck Norris) to fly a multirotor and get a decent shot.
With all due respect, I'll stick with the professional software devs at Freefly and their closed system. I developed software for 20 years at Apple, Microsoft and other companies. I am well aware of what it takes. And there's no way in hell I'm trusting my $10,000 copter and $10,000 camera and gimbal to a guy who's writing code in his spare time. Sure, maybe for a 250 tree racer. That'd be exciting. But for paying customers? No f'ing way.If you hunt around you probably will find several coders willing to work during their off hours from their regular jobs with you for a reasonable cost to code your firmware to suit your needs.
Logging has become a necessity with me at this point. You get spoiled real quick.A requirement for me is logging. I just can't believe that some of the systems out there claim to be professional but have no way to record where the system has been or to repeat a previous flight. Not to mention troubleshooting if something goes wrong.
Because this is a new world so I would think the best way to go is to hire someone with a Computer Science degree and use one of those FC with open source firmware and keep them close to you on the job site at all time.
Bill
From what i have seen others post, it's light years ahead. Never owned a dji fc.So I'm assuming the logging from Super X is better (or at least easier to interpret) than what I got from the iOSD mkII?
With all due respect, I'll stick with the professional software devs at Freefly and their closed system. I developed software for 20 years at Apple, Microsoft and other companies. I am well aware of what it takes. And there's no way in hell I'm trusting my $10,000 copter and $10,000 camera and gimbal to a guy who's writing code in his spare time. Sure, maybe for a 250 tree racer. That'd be exciting. But for paying customers? No f'ing way.
I think the reality is that to create a custom firmware, even if forked from a pre-existing code, would take many months (at least) of coding - and that's not factoring in the R&D that would need to accompany the development between revisions.
Bottom line, you are talking 10's of thousands of dollars to develop such an FC, and if the folks who have been dedicated to designing these things full-time haven't nailed it yet, I find it unlikely that the prof working for vacation money will be able to combat the complexities in a part-time manner.
So I'm assuming the logging from Super X is better (or at least easier to interpret) than what I got from the iOSD mkII?