Cheers Sar - I'm hoping they'll agree.This looks like a clear warranty case to me - just make sure that you send the DAT file to DJI.
So would you say that's user error or one of those software glitches?Looks to me like the MA got confused and the motors were left enabled after the simulator was started.
There were several start/stops of the simulator. When started the eventLog stream would show starting to run the simulator and also disabling the PWM output
-147.311 : 2621 [L-SIM]Agree to run. lon:2.006320, lat:0.393345, alt:0.010000, svn:10, type:0, ver:0
-147.296 : 2622 [L-PWM]disable actuator pwm output
When stopping the PWM output would be disabled
-147.109 : 2631 [L-SIM]Agree to stop!
-147.096 : 2632 [L-PWM]enable actuator pwm output
But the last time the simulator was started the PWM was left enabled
47.818 : 12403 [L-SIM]Agree to stop!
47.821 : 12403 [L-SIM]Agree to run. lon:2.006320, lat:0.393345, alt:0.010000, svn:10, type:0, ver:0
47.821 : 12403 [L-SIM]use_bat_sim:0
48.748 : 12449 [L-SIM]Agree to stop!
48.753 : 12450 [L-SIM]Agree to run. lon:2.006320, lat:0.393345, alt:0.010000, svn:10, type:0, ver:0
48.753 : 12450 [L-SIM]use_bat_sim:0
48.754 : 12450 [L-PWM]enable actuator pwm output
It looks like the simulator was stop/started multiple times in a very short span. I'd guess that it was both stopping the simulator and starting it.
Software error. Switching states, both to and from simulator mode, should be run as a critical section. I.e., there can't be any overlap where a switch starts and then gets overlaid with another switch. This is implemented by a software lock that prevents other processes from having access to the critical section. Either the critical section (if there was one) didn't include enough resources or the lock wasn't set properly. You may have managed to tickle the bug but it's a bug never the less.So would you say that's user error or one of those software glitches?
I do not recall any message of that sort appearing when it insisted I do the simulator.Yep, if your using Sim mode you are advised to remove the props.
I have never tried it with go4 but I know in dji assistant it will warn you to remove the props to prevent unwanted or unexpected movement of the aircraft. I would hope dji takes care of this and since it doesn't warn you in go4 but does in assistant that could be your loophole for getting it replaced.Whilst I agree with the recommendation of removing the props, I can’t find a statement in the manual saying that
I have no idea what they are looking at there. It looks like the correct DAT file name but those data don't correspond to any acceleration data in the mobile device DAT. You should continue to escalate this issue in my opinion.Further update -
DJI is saying that Simulator Mode worked and that there was no flight or crash of my drone.... seriously. That's what they've come back with and are now insisting I pay for repairs to the drone that apparently never even took flight, according to them. So I guess I played in Simulator Mode and then decided to toss the MA around and smash it myself?!
This is the data they returned to me:
View attachment 79708
I'd be grateful to any of you for your help with this as the data that we've previously discussed clearly shows and replicates my version of the events. Is there full detail that anyone can share? It seems it's been snippets and I'd love to show them the fuller picture, if possible.
Also, I have a Google Drive link with absolutely every bit of data from the app if there is more needed - I just don't think I should drop the link here.
At this point I'm quite stunned that they're not seeing what we're all seeing. Anyone know why that might be the case?
As always - thank you.