Sentinel flips during takeoff

[stevedan]

@Eric-Katzfey Maybe you can help me fixed but the vio result on Qgroundcontrol is streaming at 1hz, and the reaction speed of the remote control on Qgroundcontrol is really bad. It reacts slow, is there something I am doing wrong

What is strange is that from the drone, the vio data ms is fine voxl2:~$ voxl-inspect-qvio
waiting for server

dt(ms) | T_imu_wrt_vio (m) |Roll Pitch Yaw (deg)|features|quality| state| error_codes |
29.3 | -0.00 -0.00 -0.00| -0.0 0.0 0.0| 28 | 27% | OKAY | ^C

[stevedan]

@Eric-Katzfey This is a video of what I mean-> https://drive.google.com/drive/folders/122cPZ1S3Z_gP0yo8nipRGJHqpJTSj9c3?usp=sharing

[Eric Katzfey]

@stevedan Sorry, but could you start a new forum thread for this new issue?

[Eric Katzfey]

@stevedan Can you tell if the new software release fixed the motor not spinning issue or do you need to resolve the new issue before you can test?

[stevedan]

@Eric-Katzfey i would love to solve that issue first but it seems that the fact that the telemetry is low was done intentionally. I will stress test the drone on Tuesday when i go back to the office and give feedback. Although with the new code during arming the motors spins way smoother compared to before and doesn't do what happens before. I will stress test and let you know.

[stevedan]

@Eric-Katzfey Does this version work with mavros, is there any specific detting to enable the ise of mavros?

[Eric Katzfey]

@stevedan Happy to hear that the new software fixed the motor issue! As for the new question, can you please open that up as a new forum topic? Thanks!

[stevedan]

@Eric-Katzfey For now, it seems that the problem is solved because during arming the drone spins faster and smother, if anything occur I will let you know. Thanks for the support.

[Eric Katzfey]

@stevedan Excellent, thanks for letting us know!

[stevedan]

This post is deleted!

[stevedan]

@Eric-Katzfey I am having issue with the new image, it seems like when I am running a docker and I reset for exampe a ros node inside the docker, after doing it 2 times, the whole ubuntu shuts down. In order to acces it I have to unplug and plug the drone to the batteries and then it works. Do you know what could possible be the problem to this. I monitored the dockers stats and the cpu usage is 80% of one core and the memory usage is like 1.16%, which is not that high. This only happens on the sentinel.

[Eric Katzfey]

@stevedan No, we have not encountered that. But can you open this up in a new thread so that it has an appropriate title? Thanks!