Trying to connect mavlink2rest to mavlink-router which is then connected to FC via serial.
Connecting mission planner via tcp as well as custom apps written using mavlink C library to mavlink-router both work, so some degree of confidence that mavlink-router is set up ok.
connecting mavlink2rest results in a continuous dump of these errors. curious as to if this is normal if so, seems like a lot of thrashing. Haven't sorted thru the messages to see if any actual data is coming in.
As an update everything is working as it should so able to send and read messages via the rest api. Not logging any errors for the time being. Kind of thinking this is a normal response to no data being available and wondering if it should be logged as an error.
pi@raspberrypi:~ $ ./mavlink2rest --mavlink 1 --connect tcpout:192.168.20.32:5760
Server running: http://0.0.0.0:8088
[2024-05-04T00:38:32Z ERROR mavlink2rest::mavlink_vehicle] Recv error: Io(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })
[2024-05-04T00:38:33Z ERROR mavlink2rest::mavlink_vehicle] Recv error: Io(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })
[2024-05-04T00:38:33Z ERROR mavlink2rest::mavlink_vehicle] Recv error: Io(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })
Trying to connect mavlink2rest to mavlink-router which is then connected to FC via serial.
Connecting mission planner via tcp as well as custom apps written using mavlink C library to mavlink-router both work, so some degree of confidence that mavlink-router is set up ok.
connecting mavlink2rest results in a continuous dump of these errors. curious as to if this is normal if so, seems like a lot of thrashing. Haven't sorted thru the messages to see if any actual data is coming in.
As an update everything is working as it should so able to send and read messages via the rest api. Not logging any errors for the time being. Kind of thinking this is a normal response to no data being available and wondering if it should be logged as an error.
pi@raspberrypi:~ $ ./mavlink2rest --mavlink 1 --connect tcpout:192.168.20.32:5760
Server running: http://0.0.0.0:8088
[2024-05-04T00:38:32Z ERROR mavlink2rest::mavlink_vehicle] Recv error: Io(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })
[2024-05-04T00:38:33Z ERROR mavlink2rest::mavlink_vehicle] Recv error: Io(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })
[2024-05-04T00:38:33Z ERROR mavlink2rest::mavlink_vehicle] Recv error: Io(Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" })