So that may be normal than. I guess it’s because people would raise their throttle t slowly and the copter would start to tilt on the ground. Or in case you start on uneven terain.
Thanks!
1 Like
I found this in the 4.3.0 documentation, TKOFF_SLEW_TIME. This parameter is used to control takeoff speed. Maybe the default value is quite jumpy.
1 Like
I’ve conducted a second test flight using the PSC_VELXY_FLTD you suggested. It didn’t solve the issue. I got an internal error. I don’t know what that particular one means so for safety reasons I decided not to continue to test the rest of the parameters until I know what the internal error means. See in detail below
Log file: https://drive.google.com/file/d/14uZRf9g8-GhHSG_-BvS0AFAEev7r67MT/view?usp=sharing
I’m unsure of the message “I” as well. The picture shows the flow of messages after landing.
Flow of manuvers:
Arm, than takeoff
The jump motion on takeoff is still there, this should be normal.
Landing gear folded up.
I hovered in alt hold for about 30 sec than flew around a bit just so that there is some maneuvering in the log to.
Next, I switched to loiter at around 1min 30 sec
30 sec hover in loiter
Than forward flight, stop, than backwards flight.
During the flights there was jerking but more of them. They seemed smaller in angle but larger in quantity. The jerks appeared as both forward and backwards jerk during the backwards flight.
Landing, the jerks became worse during the decent so I switched to alt.hold and landed. The landing was detected this time but that might have been because I switched to alt.hold. I don’t remember if I landed in alt.hold in my previous flight.
…flow_of_ctr
Using GPS for Yaw?
No, confusing this with rover.
no, i’m using gps for altitude though.
I need two gps units to use gps for yaw right? I only have one here2. Also, what parameter should I check to make sure the drone wont try to use gps for way??
Nevermind. It’s on the issues list which is combined for Copter and Rover. Not applicable.
1 Like
ah okay, but what could it be in my case? if you have any clue?
Thanks!
No, but it’s the 2nd of the same error I have seen today.
Yours:
Another one:
1 Like
Could it be an unnoticed bug in 4.3? It has gone through some a lot of testing in beta but as stable release a lot more are using it.
Not sure. There was some tracking of this error as it applied to H743’s and it was fixed in a release. But these are not H743’s… It was a loop/timing error.
There is a new Rover post with the same error.
1 Like
Is there anything I can do to check or let anyone else check if it’s a timing error?
Has rover been updated recently as well?
Yes, everything is on the same release schedule more or less.
I suppose create a new post with that error in the title.
I’m working remote for some months and unfortunately I don’t have any RC hardware at hand to test stuff on. Feels a bit naked…
1 Like
Ok, I’ll do.
Xfacta haven’t answered yet so maybe he knows something. Is there anyone I should tag in that post who have the necessary means to investigate further.
I can do tests for the developers but my knowledge is too limited to solve this myself
Is there any way to get a list of all the internal errors?
Or how do you figure out what each number mean?
The number is the line of code where the error is generated so it could be different between vehicle types and firmware level. I grabbed this from another older post:
1 Like
@dkemxr ah ok,
So the error number is not that important than? Not for me at least. So, flow_of_control is what I want to look at?
Can that mean different things or does it only regard yaw, or altitude or something like that?
There was an I:“number” too. What is that for?
Thanks!
Thanks, I’ll take a look at that and do some tests when I can.
2 Likes
Not exactly, they are coded with these numbers but have these strings associated for better explanation.
1 Like
Ah okay,
That’s a bit abow my knowlage so far. But some day!
Thanks!
1 Like