In America we use a common law system and within that is something called setting precedent. luckily everybody's favorite fearless leader trappy came through here with backing and has proven the faa has nothing to stand on when it comes to the charge of "flying for hire".TRM is on the advisory boards, there all up in the USA uav/uas rule making advisories. if you got a rig and are worried about crashing, get this stuff..... full hull coverage and it's real. Support Transport Risk... i feel like there my biggest advocate in going forward with a voice and a mind with alot of thought for the good of the industry.
All insurance companies investigate crashes, bring forth suits to cover there losses and it forces the companies at fault to not be so negligent by the almighty dollar. they have resources no one person can bring to the table, across countries
of course we all want to not have an issue in the first place. You act like i'm your enemy, i'm just the guy that'll listen and respond to the whining. It's a pretty easy thing to deal with, if the heats too hot, get out of the kitchen
Just one question to finish this non-sense: wouldn't you rather NOT crash and maybe kill someone because the car accelerated by itself, like a very well-known case in the US?
gtranquilla, that's true, and proving that there was a problem with the equipment is not easy. Fortunately, I had the iOSD which saves a log of every flight. I have the iOSD log file which I sent to DJI, and of course, they haven't responded (and probably won't). However, tonight I'll go ahead and publish a graph from the iOSD that will show something very interesting.
Yes the iOSD in theory can function like a black box recording evidence that "might" lead to the root cause of the incident. However I found myself in a situation where I was reading the motor current data with a biased mind set so as to intrepret it in a way to help justify a preconceived notion which proved later to be false. Also the iOSD needs the graphs to show meaninful scales on both axes. With some additional firmware development it should be possible for it to retain more complete information as does the MK equivalent. In the meantime it is not in the best interest for a manufacturer to record all possible data, especially data that tends to lead toward self-incrimination!
of course we all want to not have an issue in the first place. You act like i'm your enemy, i'm just the guy that'll listen and respond to the whining. It's a pretty easy thing to deal with, if the heats too hot, get out of the kitchen
You have made me curious.
Looking forward to seeing iOSD results.
Wouldn't it be great if you could see the radio inputs and compare them to the FC outputs to the system? For now, it's only a start...
@ Tahoe Ed
Not sure if the post about you working for DJI is true or not but you seem to be a good guy so please, if you have an affiliation with DJI please ask one of their chicken sh*t mouthpieces to respond here, namely Colin "ShamWow" Guin. If you do not have an affiliation, my apologies and please carry on and ignore the egregious post that was referred to. I am so sick of the MBA parasites ruining our world's economy and it's creeping into our domain. Time to call a Turnip a Turnip and take these wankers to task! Somewhere in China there is a brilliant team that is doing some amazing programming but they are rushed and products are being released that are nowhere near ready for the market place so why not fire the idiots ruining a good company, step back, ready the products and produce a rockin' product??? Sorry about the rant but my Greed-O-Meter just peaked!
The SuperX black box function does this, has saved me hours of head scratching trying to solve a certain "flight event".
The SuperX black box function does this, has saved me hours of head scratching trying to solve a certain "flight event".
jazzboy, what post are you refering to?
i've watched $70k fly off the hook for no reason, you don't gotta tell me about how it feels. All we can do is protect ourselves financialy. In my case and logs, i could see me moving the sticks but the controller did nothing... it was a supposed ppm interpetation problem. sent all my stuff to dji, nothing, and that was with WK...... naza has had the same issue, all with futaba but all with immersion long range rx's using ppm
dunno, my wk flew amazing, the a2 is even better, i've been trying other stuff and i'm good here. Hoverfly pro threw my skyjib in the ocean, just powered off mid flight and rolled over...... had another hfp looked like it swapped x axis and just went 90 degrees and came down in a few seconds,,,,, all i did was turn on alt hold. They all can and will have a problem sooner or later.......I've been involved with rc since 81 and single rotor helis since 91..... i get it
I haved a superX here i'm building for a guy. it isn't the best heavy lifter controller.... theres no place to input the cg info to the controller so it behaves weird gimbaled. Also it needs the black box cause theres no live input feed to see as in if your sticks are setup proper or if the mode switches/gains are moving/adjusting right. It's like hoverfly, reverse ch 1-4 for this radio, leave normal for that radio, good luck
we are starting a relationship with APM. got some pixhawk coming soon to look at. i've seen so many problems arrise with apm 2.5 that my hopes aren't too high but it appears to be the real deal.