You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have written a simple C++ command line app which connects to a pair of "bare" (no iPad) Simionic G1000 units. It maps the inputs to calculator code presets stored in a config file, and send the command to MSFS. Source is here https://github.com/GregWoods/MSFS_BluetoothLE_Bridge
The Simionic units use a very simple protocol. Once the client software is connected, each button press or rotary encoder input, sends a single byte to the connected client.
It struck that that would be a great protocol for home brewed peripherals. The Raspberry Pi Pico has BLE support built in. It would save a lot of wiring, especially for rigs that need to be disassembled regularly.
Whilst my C++ command line app works, it could be:
More robust
Have a nicer UI than a command line app and a txt config file
Work with XPlane
In other words, a BLE connected device sounds like a perfect addition to MobiFlight-Connector, and the Pico firmware.
I'd like some feedback from the contributors and community on whether BLE connected input devices are a good idea? And if so, are there any reasons not to use the Simionic "one-byte per input event" protocol?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have written a simple C++ command line app which connects to a pair of "bare" (no iPad) Simionic G1000 units. It maps the inputs to calculator code presets stored in a config file, and send the command to MSFS. Source is here https://github.com/GregWoods/MSFS_BluetoothLE_Bridge
The Simionic units use a very simple protocol. Once the client software is connected, each button press or rotary encoder input, sends a single byte to the connected client.
It struck that that would be a great protocol for home brewed peripherals. The Raspberry Pi Pico has BLE support built in. It would save a lot of wiring, especially for rigs that need to be disassembled regularly.
Whilst my C++ command line app works, it could be:
In other words, a BLE connected device sounds like a perfect addition to MobiFlight-Connector, and the Pico firmware.
I'd like some feedback from the contributors and community on whether BLE connected input devices are a good idea? And if so, are there any reasons not to use the Simionic "one-byte per input event" protocol?
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions