Skip to content
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.

Sign up for GitHub

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

Jump to bottom

AP_HAL_SITL: process inbound data in outqueue-length delay loop #28570

Merged
merged 1 commit into from
Nov 12, 2024
Merged

AP_HAL_SITL: process inbound data in outqueue-length delay loop #28570

merged 1 commit into from
Nov 12, 2024

Commits on Nov 10, 2024

  1. AP_HAL_SITL: process inbound data in outqueue-length delay loop 

    this is the loop which ensures the amount of data sent to the mavlink client (usually Python) is limited - if we don't do this then we lose vast amounts of data when running at large speedups.

By attempting to process inbound data we may realise that the TCP connection has been dropped, and in that case we will start to listen for another connection.

This allows you to terminate the sim_vehicle.py MAVProxy and have it automagically restart (when running under GDB).  This is very useful for testing MAVProxy patches with SITL; it's a different workflow to opening an output and connecting a new version of MAVProxy to that outout.
    @peterbarker
    peterbarker committed Nov 10, 2024
    Configuration menu
    Copy the full SHA
    4a7e0fd View commit details
    Browse the repository at this point in the history