01-18-2022, 09:47 PM
@MRamone
Sorry, I managed to overlook your most recent post. I'm backed up at the moment* but I'll try to help if you get lost in the following.
I don't know any details about the Microsoft Surface Dial but I assume it supports some basic gestures such as rotate right, rotate left, press, press and hold, or such. We just need to determine what message it sends for each gesture and map them to moOde.
I covered the basics of determining the messages and mapping them in Using FLIRC and other USB input devices... but that HowTo assumed the device is already connected and recognized by the OS (and triggerhappy).
To get there using a remote Bluetooth device and the Pi's onboard Bluetooth controller, you'll have to work from the command line. If you ply your favorite search engine with a phrase like "linux connect bluetooth device from command line" you'll come across instructions using tools like hcitool and bluetoothctl, both of which are already present in moOdeOS. Some scripting may be required to tie it all together for automation but first learn the basics.
As a quick test, I enabled the triggerhappy daemon by enabling the USB Volume Knob feature in moOde and then connected a Logitech K380 Bluetooth keyboard to moOde using bluetoothctl. I found that the keyboard's predefined mute/volume up/volume down buttons worked with moOde's existing triggerhappy configuration but its previous/play-stop/next buttons did not. I'd have to follow my own HowTo above to map them.
Good luck.
Regards,
Kent
* I'm busy studying up on the FIRST Robotic Competition 2022 because I've just been asked to step in as a mentor to an local inexperienced high school team after being away from FRC for years. There's a lot to catch up on.
Sorry, I managed to overlook your most recent post. I'm backed up at the moment* but I'll try to help if you get lost in the following.
I don't know any details about the Microsoft Surface Dial but I assume it supports some basic gestures such as rotate right, rotate left, press, press and hold, or such. We just need to determine what message it sends for each gesture and map them to moOde.
I covered the basics of determining the messages and mapping them in Using FLIRC and other USB input devices... but that HowTo assumed the device is already connected and recognized by the OS (and triggerhappy).
To get there using a remote Bluetooth device and the Pi's onboard Bluetooth controller, you'll have to work from the command line. If you ply your favorite search engine with a phrase like "linux connect bluetooth device from command line" you'll come across instructions using tools like hcitool and bluetoothctl, both of which are already present in moOdeOS. Some scripting may be required to tie it all together for automation but first learn the basics.
As a quick test, I enabled the triggerhappy daemon by enabling the USB Volume Knob feature in moOde and then connected a Logitech K380 Bluetooth keyboard to moOde using bluetoothctl. I found that the keyboard's predefined mute/volume up/volume down buttons worked with moOde's existing triggerhappy configuration but its previous/play-stop/next buttons did not. I'd have to follow my own HowTo above to map them.
Good luck.
Regards,
Kent
* I'm busy studying up on the FIRST Robotic Competition 2022 because I've just been asked to step in as a mentor to an local inexperienced high school team after being away from FRC for years. There's a lot to catch up on.
