Deployment & Installation Workflow

All new installations vary in complexity. This guide provides insight from an installer and programmer perspective, outlining the general workflows when setting up Pyaura systems.

• 1. Collect Information Discuss with the client to determine exact system requirements. Cover details such as video, lighting, sound, microphones, audio sources, curtain/shade control, coloured lighting effects, timed playback, and power shutdown. Clarify preferences for password-protected touch panels, zone floor maps and complete system user training sessions. Determine if the setup will use internal wireless VLAN or a standalone system, and obtain the IP address list from the IT administrator.
• 2. System Schematics & Quoting Once information is gathered, put together the schematic layout of the system. This is the stage where pricing can be finalized, the functionality list compiled, and a mock-up presentation prepared to show the client what to expect before moving forward with purchasing and installation.
• 3. Hardware Setup & Controller Boot Assuming all devices are installed and wired, set up the Pyaura system controller. Insert a micro SD card containing the pre-configured Pyaura OS image matching your specific hardware unit (e.g., matching the N95 image requirement). Power up the controller with a connected monitor, keyboard, mouse, and a direct LAN cable plugged into a network switch or router. *(Note: Do not use the controller's built-in Wi-Fi for initial configuration; use a direct LAN connection).*
• 4. Map Out Network Devices If the system utilizes multiple IP addresses, map out all network devices. The device ODS list in Pyaura acts as a central repository for this information and is used by Pyaura to process and send data across networked hardware. Ensure all external equipment is configured on the correct network ranges and that any eco modes (such as network power-saving sleep) are disabled.
• 5. Terminal Ping Tests If you are confident all IP addresses are matching, start by doing ping tests in the terminal. This is a crucial step to make sure all devices are seen on the Pyaura controller device. Go through all devices on the network until they are all recognized.
• 6. Device & Project Configuration This is where Pyaura expertise starts to show. Device and project sheets need to be appropriately filled out to match the devices, which will vary greatly for each setup. For example, if a DSP is deployed with many audio zones, it will need to be created separately and compiled in the actual DSP unit, then correctly mapped with Pyaura logic. Vision systems will similarly depend entirely on the hardware being used.
• 7. Configure Pyaura License Configure your Pyaura license. Note that edit mode will function without a license, but running Pyaura as a background service and enabling auto power-up requires a valid license. *(Refer to the licensing section for acquisition details).*
• 8. Develop Graphical User Interfaces (GUI) Once configuration data matches all devices and a valid license is active, design the GUI pages. Establish background maps, button polygon formations, and graphical preferences. Client feedback at this stage is vital to ensure the control layouts match their expectations and avoid costly revisions later.
• 9. System Testing & Validation With all configurations complete and changes approved, thoroughly test every function. Allow the client to test controls, observe responses, and verify audio quality to ensure there are no mistakes.
• 10. Lock Down Touch Panels Secure each touch panel by locking out settings that unauthorized users should not access. For Android touch panels, Fully Kiosk Browser is recommended for this purpose (see the Tech page for details).
• 11. Backup & Final Service Activation Once everyone is satisfied with system performance, create a full backup of the micro SD card. For critical operations, keeping a ready-to-plug-in spare controller next to the active unit is strongly advised. Activate the Pyaura service, then perform a final power-down and power-up test to confirm all components—including touch panels and wireless connectivity—reconnect automatically.

Click here for more about training.