New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backend with Realtime Database #17

charithccmc opened this Issue Jan 23, 2018 · 1 comment


None yet
2 participants

charithccmc commented Jan 23, 2018

Drones use their radio link to communicate with their ground stations and controllers. Those radio links can communicate for a limited range. When a drone fly automatically through way points it may go away from radio link. Then ground station unable to monitor that drone any more. We want a system to monitor automatically flying drones using long range communication network “LORA” . Its mandatory to uniquely identifying each drone, for that we want to bind unique key to each drone. The final product should be a separate unit which can externally mound on any kind of drone.

Currently we have a system consisting with seperate devices to mount on drones and web system to monitor their locations. That device send data like location, timestamp, and nodeid with AES encryption. This is an one way communication system which sends messages only from drones to the DroLa web System. For further developments we are seeking to improve the system as follows.

We want a new platform to send messages in more general way instead of current fixed message format. Then we can introduce this system to other tracking solutions also. We want to design a bidirectional communication protocol and implement it including message passers for both Lora Node side and web server side.

Current system is running on web sockets, drone locations are collected by Lora receivers and send them to the web server through a web socket server. we want to move to a realtime database instead of using web-sockets.

Required Knowledge: C++, Node Js, Python and ReactJs


This comment has been minimized.

VibhorCodecianGupta commented Oct 1, 2018

@charithccmc would love to contribute to this issue, but I think #30 already does this in entirety. Would that PR be reviewed and merged? In that case, it'd be futile to redo all that work :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment