benjinne

I'm looking for a way to create PX4 MAVSDK tests to test offboard being lost. Currently, I only see the stop() function as a way to stop sending setpoints, however...

This attempts to solve: https://github.com/BehaviorTree/Groot/issues/125 and https://github.com/BehaviorTree/Groot/issues/42 By supporting the ` tag without loading or saving sub-tree files.

Here's my full stacktrace https://gist.github.com/benjinne/f7f28dd87489bdf9906b856601e18f5e

Hi @AlexKlimaj will the ethernet work on your flight controller? I have some of your FMUV6X FCUs, and I'm still waiting for the holybro carrier boards.

So I don't have much to offer here with to getting inverted telem to work, however if you want a quick fix you can always solder to some receivers between...

What is COM_OBL_ACT getting replaced with? COM_OBL_RC_ACT? Also, will rc failsafe still work while in offboard? For my use case, I need to always have RC available while in offboard.

I don't remember the exact issue I had, but around Oct 25th, the latest release wasn't working so I built it from the main branch and it started working

This also works if you need a temporary fix: Node( package='topic_tools', executable='throttle', name='throttle', output='screen', arguments=['messages', 'odom', '10.0', 'odom/throttle'], )

> The CRC errors have also been reported here #187. > > You could try removing the check here https://github.com/mac-zhou/midea-msmart/blob/97723d055d8e5a3775eaaca96807f2dbbd6db2aa/msmart/device/AC/command.py#L178-L182 > > Don't know what that recursion error is about...

I have the same problem with a standalone unity executable not being killed, but I can kill all the processes correctly if I Ctrl+C before the test is complete