@Eric-Katzfey said in Mavlink messages through voxl-logging:
@ndwe -z in the voxl-logger command, not the voxl-replay command. But looks like voxl-replay sees the data and there is a raw data file for it to parse. Are you still having an issue?
@Eric-Katzfey is there any way to view the mavlink messages in plaintext (not raw)? We want to plot the data on LOCAL_POSITION_NED and MAVLINK_ATTITUDE hence our need for the data in CSV.