Hello all,
I am totally pissed with Yuneec's customer service - or lack thereof. I experienced a fly away last month. and haven't been able to recover the drone. Shortly after I sent the log files I could locate on the remote to Yuneec. They said they needed the RC to make sure the files had not been manipulated. Ok, fair enough, even if they could have started looking at the files before receiving the RC. Now, they received the RC three weeks ago but nothing happened. They claim to have no "tool" to analyse the data coming from the ST16S. Even worse, they "wonder" how I could retrieve the log data. Very simple, I replied, I used the android file explorer and navigated to the Flight2Log directory. But they claim it is anyway impossible to find GPS coordinates in the RC log, even though the data looks like this
,fskRssi,voltage,current,altitude,latitude,longitude,tas,gpsUsed,fixType,satellitesNum,roll,yaw,pitch,motorStatus,imuStatus,gpsStatus,cgpsStatus,pressCompassStatus,fMode,gpsPosUsed,vehicleType,errorFlags1,gpsAccH,vSpeed,hSpeed
20180818 18:17:48:421,-91,14.3,14.0,4.83,67.10671,-50.18795,8.67467,true,0,20,0.0,90.0,0.0,255,245,1,3,255,13,false,5,0,0.0,-0.77,8.640429
20180818 18:17:51:791,-90,14.3,14.0,3.12,67.10658,-50.188305,8.639508,true,0,20,0.0,90.0,0.0,255,245,1,3,255,13,false,5,0,0.0,-0.75,8.606893
And there are more files, containing the input of the various channels, etc. So, to me, it is pretty obvious that one can indeed come to a conclusion as to whether there was a malfunction or not. If it was pilot error, which I don't believe, I'd like them to explain to me how they come to this conclusion instead of making a series of inconsistent, nonsensical claims about which type of data is available or is not.
If anybody here has some knowledge of what the various flags mean, I would be very grateful and would be happy to send the complete logs of the ill-fated flight.
Best,
David
I am totally pissed with Yuneec's customer service - or lack thereof. I experienced a fly away last month. and haven't been able to recover the drone. Shortly after I sent the log files I could locate on the remote to Yuneec. They said they needed the RC to make sure the files had not been manipulated. Ok, fair enough, even if they could have started looking at the files before receiving the RC. Now, they received the RC three weeks ago but nothing happened. They claim to have no "tool" to analyse the data coming from the ST16S. Even worse, they "wonder" how I could retrieve the log data. Very simple, I replied, I used the android file explorer and navigated to the Flight2Log directory. But they claim it is anyway impossible to find GPS coordinates in the RC log, even though the data looks like this
,fskRssi,voltage,current,altitude,latitude,longitude,tas,gpsUsed,fixType,satellitesNum,roll,yaw,pitch,motorStatus,imuStatus,gpsStatus,cgpsStatus,pressCompassStatus,fMode,gpsPosUsed,vehicleType,errorFlags1,gpsAccH,vSpeed,hSpeed
20180818 18:17:48:421,-91,14.3,14.0,4.83,67.10671,-50.18795,8.67467,true,0,20,0.0,90.0,0.0,255,245,1,3,255,13,false,5,0,0.0,-0.77,8.640429
20180818 18:17:51:791,-90,14.3,14.0,3.12,67.10658,-50.188305,8.639508,true,0,20,0.0,90.0,0.0,255,245,1,3,255,13,false,5,0,0.0,-0.75,8.606893
And there are more files, containing the input of the various channels, etc. So, to me, it is pretty obvious that one can indeed come to a conclusion as to whether there was a malfunction or not. If it was pilot error, which I don't believe, I'd like them to explain to me how they come to this conclusion instead of making a series of inconsistent, nonsensical claims about which type of data is available or is not.
If anybody here has some knowledge of what the various flags mean, I would be very grateful and would be happy to send the complete logs of the ill-fated flight.
Best,
David