This repository contains a system for generating AV equipment instructions for rooms at UniArts Helsinki. The system consists of two main components:
- A QR code generator that creates room-specific QR codes
- An equipment instructions viewer that displays device-specific instructions for AV equipment in each room
| File | Description |
|---|---|
qrcodegenerator.php |
Creates QR codes linked to room-specific instructions |
user_instructions.php |
Displays AV equipment instructions for a specific room |
default_devices.php |
Contains device information and multilingual instructions |
config.php |
Trail API configuration and credentials (not included, see config.example.php) |
styles.css |
Styling for both the QR generator and instructions pages |
- Multilingual Support: All content is available in Finnish, Swedish, and English
- Language-specific Logos: Displays different logo files based on the selected language
- QR Code Generation: Creates QR codes that link to room-specific instructions
- Responsive Design: Works on both desktop and mobile devices
- Device Categorization: Organizes devices by type (projectors, displays, etc.)
- API Integration: Pulls room and equipment data from the Trail API
- Navigate to the QR code generator page
- Enter a room code
- Select the desired language
- Click "Generate"
- A QR code will be created that links to the instructions for that room
- Access by either scanning a QR code or navigating directly to the URL
- Select preferred language from the language bar
- View equipment instructions specific to the room
- Contact AV support via the footer if additional help is needed
- Upload all files to your web server
- Copy
config.example.phptoconfig.phpand fill in your Trail API credentials - Create language-specific logo files
logo_fi.pnglogo_sv.pnglogo_en.png
Device images are stored and managed in Trail. The system fetches them automatically via the Trail API when displaying instructions.
Images must be uploaded to Trail and attached to the correct device item. The filename must follow this convention for the system to recognize it:
- Use the device model name as the filename
- Convert to lowercase
- Replace spaces with underscores
- Use PNG format with transparent background
Examples:
| Model name in Trail | Required filename |
|---|---|
MLC Plus 100 |
mlc_plus_100.png |
BTone analog 2 |
btone_analog_2.png |
Meeting Owl 3 |
meeting_owl_3.png |
4030C |
4030c.png |
If no matching image is found, the instructions page displays a localised "No device image" message.
Marko Myöhänen, University of the Arts Helsinki