Archive:Fastfood Remotes: Difference between revisions

From The Munich Maker Lab's Wiki
Jump to navigation Jump to search
(Created page with "{{project |name=Fastfood Remotes |status=experimental |author=JanS, Severin |description=Remote controls for random things in the space |downl...")
 
Line 15: Line 15:
| Toggle Space Lights || Turn on red rotating light
| Toggle Space Lights || Turn on red rotating light
|-
|-
| - || -  
| Toggle Common Space Lights || -  
|-
|-
| - || Turn off red rotating light
| Toggle Lights infront of projection wall || Turn off red rotating light
|}
|}


Line 27: Line 27:
|-
|-
| - || -
| - || -
|}
=== Remote C ===
{| class=wikitable
| Traffic light Green ON || Traffic light Green OFF
|-
| Traffic light Yellow ON || Traffic light Yellow OFF
|-
| Traffic light Red ON || Traffic light Red OFF
|}
|}



Revision as of 22:57, 23 January 2016

   
Fastfood Remotes

Release status: experimental [box doku]

Description Remote controls for random things in the space
Author(s)  JanS, Severin
Download  https://github.com/munichmakerlab/fastfoodremotes

We got a few RF remote controls from a big fastfood chain. The receivers have serial outputs which output button presses as single bytes.

Button Mappings

Current functions of the buttons on the remotes:

Remote A

Toggle Space Lights Turn on red rotating light
Toggle Common Space Lights -
Toggle Lights infront of projection wall Turn off red rotating light

Remote B

MPD toggle play/pause MPD vol up
MPD next MPD vol down
- -

Remote C

Traffic light Green ON Traffic light Green OFF
Traffic light Yellow ON Traffic light Yellow OFF
Traffic light Red ON Traffic light Red OFF

Software

Severin wrote a python script that takes the button presses sent by the receiver over its serial connection, and parses them. It maps the bytes to the buttons on the remotes, and sends them to our MQTT broker.

Currently, three remotes are registered with the receiver. They are marked with stickers as A, B, and C, and their buttons are numbered from 0 to 5. The script sends the ID of the button (e.g. "B3") to mumalab/mccafe/1/buttonpress. Further actions are then defined in our "Automation Layer" (currently a Node-Red installation).

The script currently runs on the PrinterBot machine, which the receiver is connected to.