Difference between revisions of "Customizing a POP Kiosk"

From CLIO

 
Line 6: Line 6:
== Configuring the Raspberry Pi at Boot ==
== Configuring the Raspberry Pi at Boot ==
The Raspberry Pi computer uses the <code>boot</code> partition to configure the computer system at each boot<ref>https://www.raspberrypi.com/documentation/computers/config_txt.html</ref> .  You can edit these files by inserting the kiosk's SD card into a Windows or Mac computer and navigating to the <code>boot</code> drive that is automatically mounted.  
The Raspberry Pi computer uses the <code>boot</code> partition to configure the computer system at each boot<ref>https://www.raspberrypi.com/documentation/computers/config_txt.html</ref> .  You can edit these files by inserting the kiosk's SD card into a Windows or Mac computer and navigating to the <code>boot</code> drive that is automatically mounted.  
{{ExternalResource|[https://www.raspberrypi.com/documentation/computers/config_txt.html Raspberry Pi Documentation – The Config.txt File]}}


=== Enabling 64-Bit Processing ===
=== Enabling 64-Bit Processing ===

Latest revision as of 18:19, 2 March 2023

Google material book.png

Overview

The POP Kiosk comes with default settings that make it suitable for use as an embedded kiosk, but many of these settings are fully customizable. You can easily change the default resolution, display output, control wireless radios or change the boot logo.

Configuring the Raspberry Pi at Boot

The Raspberry Pi computer uses the boot partition to configure the computer system at each boot[1] . You can edit these files by inserting the kiosk's SD card into a Windows or Mac computer and navigating to the boot drive that is automatically mounted.


Enabling 64-Bit Processing

Open the /boot/config.txt text file in a text editor and add the line arm_64bit=1 to the end of the file. Save the file and insert the SD card back into the Raspberry Pi.

Note

Enabling Bluetooth

Open the /boot/config.txt text file in a text editor and search for the line dtoverlay=disable-bt. Add a hash mark # to the beginning of the line so it reads #dtoverlay=disable-bt. Save the file and insert the SD card back into the Raspberry Pi.

Changing Resolution

Open the /boot/config.txt text file in a text editor and search for the lines framebuffer_width=800 and framebuffer_height=480. These values can be changed to better reflect the pixel dimensions of the display you are using. Save the file and insert the SD card back into the Raspberry Pi.

Rotating the Touchscreen Display

Open the /boot/config.txt text file in a text editor and search for the lines lcd_rotate=0 or lcd_rotate=2 . A value of 0 uses the displays default orientation, while a value of 2 rotates the display by 180°. It is not easy to rotate the display and the touchscreen by 90° or 270°. Save the file and insert the SD card back into the Raspberry Pi.

Note

Enabling Wi-Fi

Open the /boot/config.txt text file in a text editor and search for the line dtoverlay=disable-wifi . Add a hash mark # to the beginning of the line so it reads #dtoverlay=disable-wifi. Save the file and insert the SD card back into the Raspberry Pi.

Connecting to a Wireless Network

Open the /boot/wpa_supplicant.conf file in a text editor. If it doesn't exist, create a new text file in the boot directory named wpa_supplicant.conf. It is common for Operating Systems to hide file extension, so you many need to verify this file is named wpa_supplicant.conf and not wpa_supplicant.conf.txt. This file needs to be formatted very specifically, according to Raspberry Pi specifications.

country=US # Your 2-digit country code
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
network={
    ssid="YOUR_NETWORK_NAME"
    psk="YOUR_PASSWORD"
    key_mgmt=WPA-PSK
}

You can easily change the boot logo that is displayed while the kiosk is starting by replacing the /boot/splash.png image file. The file you replace it with must be a PNG file with the name splash.png.

Controlling the GPIO

The /boot/config.txt file can be used to control the GPIO pins and enable technologies needed for GPIO communication.

Resources

Documentation
Installation Look and Feel
Interaction Modes Developing Activity Types
Creating an Interactive Framework
Integrating CLIO Contribute