- Jul 09, 2017
-
-
Daniel Agar authored
- closes #7550
-
- Jul 08, 2017
-
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Daniel Agar authored
-
Rogelio authored
-
Daniel Agar authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
This requires further investigation. Hotfix.
-
David Sidrane authored
-
David Sidrane authored
This commit fixed a bug were the mag was orphened on a reset. That resulted in MAG timeouts on reset or test operations and left the mag in a broken state.
-
David Sidrane authored
If the setup is unsucessful fo not register the devices or allocate resources.
-
David Sidrane authored
We want to setup the mag interface with retries and report failurs. Move retry logic to contol point, instead of hiding re-reading the ID in ak8963_check_id. Allow it to fail once to overcome a read of 0 on firt read. after 2 failure report error to console and reset the mpu9250's I2C master (SPI to I2C bridge) The same retry logic is used on the ak8963_read_adjustments with a reset of the I2C master module after 5 fails. If it fails fter 10 retires. Disabel the mad and report the failure on the console, stating it is disabled.
-
David Sidrane authored
Provide an API for the mag to use read-modify-write
-
David Sidrane authored
-
David Sidrane authored
On initialization, if after 3 retries to re-init the mpu9250 from the checked registers values, it fails. Ensure thath the fact the driver is exitting is logged to console.
-
David Sidrane authored
Check that the mpu9250's configured registers match the settings written to them. Attempt to fix any that do not up to 3 times. printing erros to the console on mismatches and returning faliure if after 3 attempts the any of the values are still wrong.
-
David Sidrane authored
-
David Sidrane authored
Remove delays on each register write in the reset function. Leaving only the delay following chip reset prior to configurations.
-
David Sidrane authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Lorenz Meier authored
-
Julian Oes authored
-
Julian Oes authored
-
Julian Oes authored
-
Julian Oes authored
-
Julian Oes authored
-
Julian Oes authored
- change/add a few printfs so they make more sense - don't accidentally ignore command_acks - don't forward commands to the same component id, and don't forward commands that are broadcast to all components (target component 0)
-
Julian Oes authored
This adds a class to allow for retransmission of outgoing commands. The sent commands are kept in a timestamped list to check if they are acked as required by the mavlink protocol. If they are not acked within a timeout, they can be retransmitted.
-
Julian Oes authored
The vehicle_command uORB messages had the timestamp unset at 0.
-
Julian Oes authored
-
ChristophTobler authored
-