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
{{ message }}
This repository was archived by the owner on Aug 27, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: faq/faq.md
+40-21Lines changed: 40 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,12 +116,12 @@ Follow the steps mentioned here: [How to Fix NGINX 413 Request Entity Too Large
116
116
Yes, the **Hardware Button** feature enables to control Photobooth through hardware buttons connected to Raspberry GPIO pins . This works for directly connected screens and as well for WLAN connected screen (i.e. iPad). Configuration takes place in the admin settings - Hardware Button section.
117
117
118
118
The Hardware Button functionality supports two separate modes of operation (select via admin panel):
119
-
-**Button Mode**: Distinct hardware buttons can be connected to distinct GPIOs. Each button will trigger a separate functionality (i.e. take photo).
120
-
-**Rotary Mode**: A rotary encoder connected to GPIOs will drive the input on the screen. This enables to use the rotary to scroll through the Photobooth UI buttons, and click to select actions.
119
+
-**Buttons**: Distinct hardware buttons can be connected to distinct GPIOs. Each button will trigger a separate functionality (i.e. take photo).
120
+
-**Rotary Encoder**: A rotary encoder connected to GPIOs will drive the input on the screen. This enables to use the rotary to scroll through the Photobooth UI buttons, and click to select actions.
121
121
122
-
Modes can not be combined.
122
+
Both buttons and rotary encoder controls can be combined.
123
123
124
-
In any mode, Photobooth will watch GPIOs for a PIN_DOWN event - so the hardware button needs to pull the GPIO to ground, for to trigger. This requires the GPIOs to be configured in PULLUP mode - always.
124
+
Photobooth will watch GPIOs for a PIN_DOWN event - so the hardware button needs to pull the GPIO to ground, for to trigger. This requires the GPIOs to be configured in PULLUP mode - always.
125
125
126
126
Troubleshooting / Debugging:
127
127
@@ -135,7 +135,7 @@ Troubleshooting / Debugging:
135
135
- GPIOs may not be configured as PULLUP. The configuration for this is done in fie `/boot/config.txt` by adding the GPIO numbers in use as follows - you **must reboot** the Raspberry Pi in order to activate changes in this setting.
136
136
137
137
```
138
-
gpio=16,20,21,26=pu
138
+
gpio=16,17,20,21,22,26,27=pu
139
139
```
140
140
141
141
- For the Shutdown button to work, `www-data` needs to have the necessary sudo permissions. This is done by the `install-raspian.sh` script or can be manually added as
As of Photobooth v3, hardware button support is fully integrated into Photobooth. Therefore the `button.py` script has been removed from the distribution. In case you are using this script and for continued backward compatibility please do not activate the Remote Buzzer Hardware Button feature in the admin GUI. Please note that continued backward compatibility is not guaranteed and in case of issues please switch to the integrated functionality.
150
150
151
151
152
-
***************
153
-
**Button Mode**
154
-
***************
155
-
The server supports up to three connected hardware buttons for the following functionalities:
152
+
******************
153
+
**Button Support**
154
+
******************
155
+
The server supports up to four connected hardware buttons for the following functionalities:
156
156
157
157
1)**Picture Button**
158
158
@@ -183,24 +183,43 @@ Note:
183
183
- Hold the button for a defined time to initiate the shut down (defaults to 5 seconds). This can be adjusted in the admin settings.
184
184
- The shutdown button will only trigger if there is currently no action in progress in Photobooth (picture, collage).
185
185
186
+
4)**Print Button**
187
+
188
+
- Defaults to GPIO26
189
+
- This button will initiate a print of the current picture either from the results screen or the gallery.
190
+
191
+
186
192
After any button is triggered, all hardware button remain disabled until the action (picture / collage) completed. Once completed, the hardware buttons re-arms / are active again.
187
193
188
-
***************
189
-
**Rotary Mode**
190
-
***************
191
-
In rotary mode a rotary encoder (i.e. [KY-040](https://sensorkit.en.joy-it.net/index.php?title=KY-040_Rotary_encoder)) is connected to the GPIOs. Turning the rotary left / right will navigate through the currently visible set of buttons on the screen. Button press on the rotary will activate the currently highlighted button in Photobooth.
194
+
The wiring layout is
195
+
196
+
```
197
+
Button Raspberry
198
+
199
+
Picture --- GPIO 21
200
+
Collage --- GPIO 20
201
+
Shutdown --- GPIO 16
202
+
Print --- GPIO 26
203
+
All --- GND
204
+
```
205
+
206
+
207
+
******************
208
+
**Rotary Encoder**
209
+
******************
210
+
A rotary encoder (i.e. [KY-040](https://sensorkit.en.joy-it.net/index.php?title=KY-040_Rotary_encoder)) is connected to the GPIOs. Turning the rotary left / right will navigate through the currently visible set of buttons on the screen. Button press on the rotary will activate the currently highlighted button in Photobooth.
192
211
193
212
The wiring layout is
194
213
195
214
```
196
-
Button Rotary Encoder
197
-
ModeRaspberry Mode
215
+
Rotary
216
+
Encoder Raspberry
198
217
199
-
Picture --- GPIO 21 --- DT
200
-
Collage --- GPIO 20 --- CLK
201
-
Shutdown --- GPIO 16 --- SW
202
-
3V3 --- +
203
-
GND --- GND
218
+
CLK --- GPIO 27
219
+
DT --- GPIO 17
220
+
BTN --- GPIO 22
221
+
+ --- 3V3
222
+
GND --- GND
204
223
```
205
224
206
225
Known limitations:
@@ -215,7 +234,7 @@ Other Remote Trigger (experimental)
215
234
**************
216
235
The trigger server controls and coordinates sending commands via socket.io to the photobooth client. Next to a hardware button, any socket.io client can connect to the trigger server over the network, and send a trigger command. This gives full flexibility to integrate other backend systems for trigger signals.
217
236
218
-
- Channel: `photobooth-socket`
237
+
- Channel: `photobooth-socket`
219
238
- Commands: `start-picture`, `start-collage`
220
239
- Response: `completed` will be emitted to the client, once photobooth finished the task
Copy file name to clipboardExpand all lines: resources/lang/en.json
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -372,14 +372,14 @@
372
372
"manual:remotebuzzer:remotebuzzer_collagebutton": "For COLLAGE connect the hardware button to GPIO20. Pull GPIO to ground for to trigger. If enabled, long-press on PICTURE button will not trigger collage.",
373
373
"manual:remotebuzzer:remotebuzzer_collagetime": "If PICTURE button pressed less than seconds here, a picture is triggered. If pressed more seconds than here, a collage is triggered. Only works if collage is enabled in the admin settings and the collage button is disbaled.",
374
374
"manual:remotebuzzer:remotebuzzer_enable_standalonegallery": "Controls whether the rotary encoder is active on the standalone gallery view.",
375
-
"manual:remotebuzzer:remotebuzzer_enabled": "This feature enables hardware button support through Raspberry GPIO pins. IMPORTANT: For WLAN connected screens you must make sure to configure the IP address of the Photobooth web server in the section \"General\", for this feature to work properly.",
376
375
"manual:remotebuzzer:remotebuzzer_logfile": "In Dev-Mode server debugging information will be written to the logfile, located in the <code>tmp</code> folder and defaults to <code>io_server.log</code>.",
377
376
"manual:remotebuzzer:remotebuzzer_picturebutton": "For PICTURE connect the hardware button to GPIO21. Pull GPIO to ground for to trigger. Long-press will trigger COLLAGE, if enabled and Collage hardware button is disabled.",
378
377
"manual:remotebuzzer:remotebuzzer_port": "Server TCP Port - example 14711.",
379
378
"manual:remotebuzzer:remotebuzzer_printbutton": "For PRINT connect the hardware button to GPIO26. Pull GPIO to ground for to trigger.",
380
379
"manual:remotebuzzer:remotebuzzer_shutdownbutton": "For SHUTDOWN connect the hardware button to GPIO16. Pull GPIO to ground for to trigger. Hold 5 sec (default) to trigger.",
381
380
"manual:remotebuzzer:remotebuzzer_shutdownholdtime": "Seconds to hold button until system shutdown will be initiated. Setting to Zero (0) means immediate shutdown without waiting time.",
382
-
"manual:remotebuzzer:remotebuzzer_userotary": "Switch to Rotary Encoder mode for to navigate the screen. Needs a rotary encoder switch connected to the GPIOs - see FAQ for details",
381
+
"manual:remotebuzzer:remotebuzzer_usebuttons": "This feature enables hardware button support through Raspberry GPIO pins - see FAQ for details. IMPORTANT: For WLAN connected screens you must make sure to configure the IP address of the Photobooth web server in the section \"General\", for this feature to work properly.",
382
+
"manual:remotebuzzer:remotebuzzer_userotary": "Enable Rotary Encoder support for to navigate the screen. Needs a rotary encoder switch connected to the GPIOs - see FAQ for details. IMPORTANT: For WLAN connected screens you must make sure to configure the IP address of the Photobooth web server in the section \"General\", for this feature to work properly.",
383
383
"manual:reset:reset_button": "Will execute config reset. If you like to also reset images and / or the mail address database make sure you first activate those settings and save (!) the config, then perform the config reset itself.",
384
384
"manual:reset:reset_remove_config": "If enabled, personal config gets removed on reset.",
385
385
"manual:reset:reset_remove_images": "If enabled, all images gets removed on reset.",
0 commit comments