Closed pgiacalo closed 11 years ago
Its actually Mavproxy which is responsible for accepting mavlink streams as input. The Mavelous server is a module loaded by Mavproxy on startup, and mavlink streams, regardless of their source, are internally plumbed into the Mavelous server.
By default, Mavproxy will attempt to connect to a serial port, but by using the --master command line switch, you can connect to either TCP or UDP streams as well. See the following page for an example in the "Starting Mavproxy" section: http://qgroundcontrol.org/mavlink/mavproxy_startpage
Fantastic, thanks. You're making my day.
From: Pat Hickey notifications@github.com To: wiseman/mavelous mavelous@noreply.github.com Cc: Philip Giacalone philip_giacalone@yahoo.com Sent: Friday, January 18, 2013 10:34 AM Subject: Re: [mavelous] Question about TCP or UDP protocol (#45)
Its actually Mavproxy which is responsible for accepting mavlink streams as input. The Mavelous server is a module loaded by Mavproxy on startup, and mavlink streams, regardless of their source, are internally plumbed into the Mavelous server. By default, Mavproxy will attempt to connect to a serial port, but by using the --master command line switch, you can connect to either TCP or UDP streams as well. See the following page for an example in the "Starting Mavproxy" section: http://qgroundcontrol.org/mavlink/mavproxy_startpage — Reply to this email directly or view it on GitHub.
Hi, In addition to serial data input, does mavelous support telemetry input over TCP or UDP? Thanks, Phil