Closed kevdagoat closed 1 year ago
Yes, all that makes perfect sense. The difference is what level of interface that other library tries to implement and what node-mavlink is for (including the binding).
The library is not for top-level operations such as sending heartbeat periodically. If you'd like to do that you just use the setInterval()
function and send whatever you need when you need it. Done. Sending of messages is described in the docs and pretty much every example in the repository does the sending (I use mostly the udp one for playing around)
Good luck with your project!
@kevdagoat I've just completed preliminary work on the heartbeat and ftp services - maybe you'll want to check those out:
https://github.com/padcom/node-mavlink-heartbeat https://github.com/padcom/node-mavlink-ftp
Hope this helps you clean things up :)
Hi, I have a mavlink compatible gimbal that I am trying to control with typescript and without the use of an autopilot. This particular device requires the periodic mavlink heartbeat packet to be sent in order to establish and maintain communication.
I was originally using gomavlib and this library had a convenient configuration option for periodic heartbeat messages and additionally a way to manually send a heartbeat packet:
I had a look through the source of this library and the
mavlink-mappings
package however a function for even sending a heartbeat doesn't seem to exist, is this an issue with the auto JS definition generation script? Additionally:Hope that makes sense, thanks!