Weekly Digest (11 August, 2019 - 18 August, 2019) #12733

 dc26ccd 2019-08-15 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/e5597b68bd5a98bf689aa056c623da480e7ef17a](https://github.com/PX4/Firmware/commit/48f5ab2896ce1eff20401ab887cc0a8e792288bf) by [dagar](https://github.com/dagar)

🛠️ introduce sensor_gyro_control message for vehicle_angular_velocity (#12145) by dagar
🛠️ [uavcan: add optical flow support (Here Flow) * move uavcan dsdlc generation to module

20200.Measurement.uavcan sync with upstream project (https://github.com/OpenMotorDrive/flow/blob/master/dsdl/com/hex/equipment/flow/20200.Measurement.uavcan)

Signed-off-by: DanielePettenuzzo [email protected]](be3d09c) by DanielePettenuzzo
🛠️ Fix typo by bresch
🛠️ Orbit failsafe: switch internal_state to Posctrl such that Manual-Positionctrl is activated after failsafe recovery. This is needed because Orbit can only be invoked via vehicle_command msg. by Stifael
🛠️ motor_ramp: set fmu in test mode and cleanup (#11249) and restore pwm min after test by DanielePettenuzzo
🛠️ Rename _accel_horz_lp -> _xy_accel_filtered to standardize naming, use time literal, and delete unneeded #includes in the FixedwingLandDetector class. by mcsauder
🛠️ mavlink_main: stream OBSTACLE_DISTANCE to GCS by mrivi
🛠️ mavlink: match commands aimed at any sysid/compid When we send a command to any sysid or any compid, we need to match an ack from a specific sysid or compid. If we don't do that, we keep sending retransmissions and eventually time out. by julianoes
🛠️ commander: fix arming auth param translation The int32 param COM_ARM_AUTH is mapped to a packed struct. However, this struct was not actually packed (anymore) and therefore the values were applied incorrectly. I fixed this by applying the packed attribute. By using a union with a int32_t I could rid of the warning about address-of-packed-member. by julianoes
🛠️ mRo Control Zero F7 initial board support by dagar
🛠️ px_mkfw: add git commit hash to .px4 file by bkueng
🛠️ Implement ModuleParams inheritance in the VtolLandDetector class. Requires PR #12356. by mcsauder
🛠️ Update commander_params.c Addressing parameter description syntax by catch-twenty-two
🛠️ updating pre-takeoff and landding values to defaults by catch-twenty-two
🛠️ splitting preflight and land disarm times into 2 parameters by catch-twenty-two
🛠️ [Mavlink: Fix forwarding of messages with target system/component id (#12559) Mavlink does not correctly forward messages that have the target_system or target_component routing fields in the message.

Some investigation revealed that the Mavlink::forward_message function is incorrectly utilizing the mavlink_msg_entry_t.target_system_ofs and mavlink_msg_entry_t.target_component_ofs fields. These offsets are intended to be used relative to the start of the message payload. But, as implemented, these offsets are incorrectly being used relative to the start of the message. This pull-request corrects that problem.

I also correctly made use of the mavlink_msg_entry_t.flags field to determine if a message contains a target_system or target component field. The previous check incorrectly assumed that they would always be non-zero if present.

Signed-off-by: Mark Owen [email protected]](e25db01) by maowen
🛠️ logger: unconditionally call _writer.notify() The file writer thread could get into a state where it blocked infinitely on pthread_cond_wait() (or rather until the logging stops). This is very rare and the following conditions must be met: - the buffer is almost empty (<4KB filled), so that the writer thread does not write anything. - an fsync call is scheduled (happens once every second) - the fsync call takes a long time (several 100ms), during which time the complete log buffer fills up. The main thread would then get into dropout state where it does not call _writer.notify() anymore. Notifying the writer thread on every loop update of the main thread fixes that. It does not increase resource usage. by bkueng

CONTRIBUTORS

Last week there were 11 contributors.
👤 dagar
👤 fghanei
👤 DanielePettenuzzo
👤 bresch
👤 Stifael
👤 mcsauder
👤 mrivi
👤 julianoes
👤 bkueng
👤 catch-twenty-two
👤 maowen

STARGAZERS

Last week there were 21 stagazers.
⭐ danielhe
⭐ netesheng
⭐ zhanne88
⭐ BillYJT
⭐ hacklock
⭐ chenchuhan
⭐ sona-19
⭐ habedi
⭐ Jian-Yin-Shine
⭐ vas59
⭐ D3473R
⭐ scoos
⭐ BanthaRage
⭐ ZeroX-86
⭐ Luog1994
⭐ nocord
⭐ ViatorSun
⭐ jdzlxm
⭐ NineLivesCat
⭐ martinliangtz
⭐ dsaffo
You all are the stars! 🌟

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository PX4/Firmware to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

The text was updated successfully, but these errors were encountered:

weekly-digest bot added the [ARCHIVED] weekly-digest (depreciated) label Aug 18, 2019

julianoes closed this as completed Aug 19, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Weekly Digest (11 August, 2019 - 18 August, 2019) #12733

Weekly Digest (11 August, 2019 - 18 August, 2019) #12733

weekly-digest bot commented Aug 18, 2019

Weekly Digest (11 August, 2019 - 18 August, 2019) #12733

Weekly Digest (11 August, 2019 - 18 August, 2019) #12733

Comments

weekly-digest bot commented Aug 18, 2019

ISSUES

OPEN ISSUES

CLOSED ISSUES

LIKED ISSUE

NOISY ISSUE

PULL REQUESTS

OPEN PULL REQUEST

UPDATED PULL REQUEST

MERGED PULL REQUEST

COMMITS

CONTRIBUTORS

STARGAZERS

RELEASES