New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure injection using mavlink and systemcmd #15063
Conversation
af7ad5e
to
4912523
Compare
4912523
to
4aee4c2
Compare
4aee4c2
to
1819e83
Compare
The tests fail here because mavlink/MAVSDK#1124 is not merged and released yet. |
Are you guys still working on the failure injection? I think this feature is really cool. failure gyro off <-- it causes kernel panic I hope that the failure injection will be implemented soon! Thanks. |
@swham86 thanks for the interest and feedback. Yes I'm working on this, I was just on holiday last week. What do you mean with kernel panic? Does your Linux system actually panic? Stopping gyro or accel won't work properly yet because the lockstep simulation depends on it and without it, everything stops. And the others you listed are not implemented yet, but I'm going to add more functionality soon. |
@julianoes The kernel panic means just stopping simulation. I hope that the failure injection will be implemented soon. Thanks for your feedback! |
1819e83
to
3f59562
Compare
63f3f20
to
2800b69
Compare
358799b
to
c650b87
Compare
9c2d210
to
2b74826
Compare
388716d
to
f995e4c
Compare
If anyone feels like reviewing, now would be the time. I plan to get this in as soon as possible. FYI @jkflying |
This way we are less dependent on CPU load of the host.
This is after using PX4 time to check for timeouts.
Hopefully that's enough.
Again, hopefully that's enough.
Hopefully, that's long enough for slow VTOLs.
Thanks @bkueng for the review comment.
Instead of messing with existing params, use a separate rootfs for tests, as suggested by @bkueng.
3cc39dd
to
f6deb48
Compare
@dagar I think we can attempt to merge this. |
I just saw this invalidated some of the documentation (JFYI @hamishwillee): @julianoes Would it be possible to quickly change the param pointers to the new failsafe injection way? |
Thanks @MaEtUgR - any info on docs that need to be added here? |
I knew how the old way worked not the new way with this pr. That's why I was even looking for the docs. I could take the effort and figure it out but if the people write it who have implemented it and already know, that would probably be much quicker and more accurate. |
Thanks @MaEtUgR @julianoes On you > Would it be possible to quickly change the param pointers to the new failsafe injection way? |
@hamishwillee ignoring this right now, sorry. |
Work in progress to implement failure injection using MAVLink (mavlink/mavlink#1331) as well as a systemcmd.
Unlike the
SIM_BLOCK_...
param this can be generic to SITL, HITL, reality.