Topics created by Meytal Lempel

Hi again,

From investigating the voxl-vision-hub code with added prints for debug, I see that the setpoint SETPOINT_POSITION_MAGIC_NUMBER is sent to mavlink-server from two functions -

(1) _send_current_position()
sending the current position, and type-mask ignoring vx,vy,vz,ax,ay,az,yaw_rate

// fetch latest position and attitude from px4 itself so the setpoint // we are about to send is a close as possible to where we currently are

(2) execute_setpoint_position_command()
sending the setpoint as recieved from voxl-planner

The implemented behaviour of (1) suits the situation of position+yaw command. However for vx+vy+z+yaw_rate command I think something is missing.

Any help will be appreciated.
Thank you, Meytal

@Eric-Katzfey Thank you! I now use journalctl and write to a file in a logger service, for example:

voxl-mapper-logger.service

[Unit] Description=Logs voxl-mapper log output to file After=voxl-wait-for-fs.service network.target network-online.target Requires=voxl-wait-for-fs.service network.target network-online.target voxl-mapper.service [Service] Type=simple ExecStart=/bin/bash -c "sleep 45 && journalctl -f -u voxl-mapper.service >> /data/logs/voxl_mapper.log" StartLimitInterval=0 Restart=always RestartSec=2s [Install] WantedBy=multi-user.target