-
Notifications
You must be signed in to change notification settings - Fork 320
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
BLE, TCP and UDP Support #1498
BLE, TCP and UDP Support #1498
Conversation
js/msp/MSPHelper.js
Outdated
@@ -463,22 +463,33 @@ var mspHelper = (function (gui) { | |||
console.log("Servo mix saved"); | |||
break; | |||
case MSPCodes.MSP2_INAV_LOGIC_CONDITIONS: | |||
LOGIC_CONDITIONS.flush(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Scavanger this is a great PR. But we have to change how it's done. I've left a review in the INAV repo but it ultimately goes down to:
- Leave
MSP2_INAV_LOGIC_CONDITIONS
unchanged - Add
MSP2_INAV_LOGIC_CONDITIONS_SINGLE
frame - Switch configurator to use
MSP2_INAV_LOGIC_CONDITIONS_SINGLE
And then, in one of future releases we can remove support for MSP2_INAV_LOGIC_CONDITIONS
completely.
What do you think?
Yeah, this is the cleaner way. |
@Scavanger yes, we'd like for Configurator 5 to support INAV 4. So it should indeed check for supported message. |
@Scavanger could you please add a small doc here or in the firmware repo on how to use it? It would be awesome to have at least a short explanation of what's going on |
Tried this feature using this board, https://www.adafruit.com/product/2821, Worked, thanks! I only had to change my baud rate to 57600. |
Adds support for wireless connections.
Bluetooth Low Energy:
Hardware:
For CC2541 based modules a small hack in iNav is necessary: iNavFlight/inav#7931
See also: iNavFlight/inav#7783
TCP and UDP
See discussion here: #1436
I have written a firmware for ESP8266 modules that allows easy configuration via a web interface.
It checks MSP frames for errors and wraps an MSP frame in one UDP/TCP packet.
UDP runs very smoothly, TCP is a bit laggy.
https://github.com/Scavanger/MSPWifiBridge
But any device that forwards the data of a UART one-to-one to TCP/UDP should work the same way.
if #1447/iNavFlight/inav#7812 is merged, this PR/iNavFlight/inav#7931 may needs a rebase.