I was gave a following advice from Randy.
I think we should just make a new library similar to AP_FrSky_Telem then integrate it and see if people like it.. and then make it better let's start with something very simple.. like sending vehicle position and flight mode? .. and maybe accepting arm/disarm commands? what do you think?
Then I agreed this proposal .
I would like to sending a small amount of log data(i.e, drone identification number and vehicle position and flight mode), and accepting a small amount of command(i.e, arm and disarm...).
Maybe it would be an easier way to process commands by converting MQTT messages into MAVLink messages.
@rmackay9 Sorry for late reply, and thank you for creating AP_Telemetry class !
One thing I don't understand is how we will physically connect a UART to make it send the serial to a webserver..
First, we would like to send MQTT Messages to the web server without using serial or UART.
For Navio 2 platform, we expect to be able to connect to Web server directly from ArduPilot's program using TCP / IP socket.
Also, we would like to link Paho MQTT Client library to ArduPilot. Using this Paho library, connect to a web server.
for the structure of "pixhawk" -> "companion computer" -> "Web Server", we will consider how to send to the web server using UART or serial.
@rmackay9 The flight on March 12th fails with latest version of ardupilot(at this time) where the MQTT features have been include. During this try the motor emit a strange sound.
However before the drone crash, we had successfully done another try in the morning with an older version of arducopter (Copter-3.4-rc1) download from the emild HP.
At home, we have done some tries (no flight, just motor) with the base version of ardupilot( Copter-3.5 without MQTT). The result is that the motors have a strange behaviour and making some strange noise, the same that we noticed during the failure and probably make the drone crashes.
Currentely, locally we moved the commit where you had the AP_Telemetry library on the Copter-3.4 branch. The compile successed and the motor seems to be fine. We are now trying to import the MQTT features on that new local branch based on Copter-3.4.