Power Core RP v2 - Manual Install
This chapter describes the recommended workflow to manually configure a system from scratch.
Overview
For customers who purchase Power Core RP v2 with an unlocked configuration, or customers using Beta releases they may choose to configure the Power Core RP v2 manually.
Your Lawo Project Engineer will provide you with a zipped release file that will contain the correct version of ON-AIR Designer, VisTool, as well as the Power Core and VisTool configuration files.
It is recommended that customers have some previous familiarity with using ON-AIR Designer and VisTool.
Release File Structure
Each release file will contain the following files:
- docs/readme.txt - If there are any special instructions for this release, they will be contained in this file
- docs/releaseNotes.txt - Release Notes for the current version detailing any changes, fixes, or new features, as well as known issues
- software/onair-designer-8.x.x.x.exe - The current version of ON-AIR Designer that should be used with this release.
- software/vistoolmk2-8.x.x.x-x64.exe - The current version of VisTool MK2 that should be used with this release.
- templateFiles/Emberdefault.ini - A sample file that can be used to set the Bookmark URLs
- templateFiles/Emberhosts.ini - A sample file that is used to define the EmBER+ connections from VisTool
- templateFiles/RPv2_default_labels.xml - A sample file with a default set of user labels for all Inputs and Buses
- RPv2.db3 - The ON-AIR Designer database file for customers using a Power Core Rev3 WITH the Ravenna Plus addOn license
- RPv2-rev3.db3 - The ON-AIR Designer database for customers using a Power Core Rev3 without the Ravenna Ravenna Plus addOn license
- RPv2-rev2.db3 - The ON-AIR Designer database for customers using a Power Core Rev1 or Power Core Rev2 unit
- RPv2-Local.vistool - The VisTool file that should be used for a local user (located with the MC2 console)
- RPv2-Remote.vistool - The VisTool file that should be used for a remote user (located on-site with the Power Core)
The files in the release folder should be extracted to a common directory, such as C:\Lawo\Configurations\RPv2. This way, there is no need to update the VisTool Session configurations each time a new release is available.