Logic Profiles take up a position within the channel count of the Altus. For example, if the Altus instance is licensed with 12 channels, each instance of a logic profile loaded will take one of the channels. So one PDM control profile loaded will allow 11 audio profiles to be loaded. To define a Logic Profile, select the Logic menu item under Profile Manager heading (7-1A). With the new page, select the appropriate predefined profile (7-1B) for your application.
With Logic Profiles, there are 3 predefined profiles (7-1B).
GPIO - 5 Buttons that will interface with a GPIO port assigned to a matching channel number.
User Buttons (Livewire Control Protocol) - 10 Buttons that can interact with a LWCP controller, Pathfinder for example.
PDM - 5 Buttons that mimic the control interface of a 25/7 PDM along with a display for delay time status.
Figure 7-1 - Logic Profiles
GPIO
The GPIO configuration is composed of 4 items.
Figure 7-2 - GPIO Logic Profile
Module name - The name of the profile so it can be found in the drop down list of each channel.
Channel - The Livewire channel for GPIO logic. Typically a channel number is assigned to a GPIO port and this is the number to be used for this property.
Mode - Two different options, Snake or Module. Snake would likely be the typical use case.
Snake - Like the term audio snake, the 5 buttons will interact with the 5 GPIOs of a port. Pressing of a button will create a GPO change where a GPI trigger at the port will cause the button to illuminate.
Module - Interaction with consoles logic as a GPIO port does (effectively the opposite of Snake). So button presses will trigger GPI activity that a console module could respond to and likewise console logic activity that triggers a GPO on a port would likewise trigger the button to illuminate.
GPIO# - A name field for the button to label the button. Best to label it as “Eject” and not “Button 2”. Note that a blank text box will hide the button from the user interface. Say you want to give the user a single button that will trigger the door to unlock but don’t wish to give the user control of the other pins on the GPIO port, blank out the text of all the other instances ans the user interface will produce a single button.
Single GPIO button example
User Buttons (Livewire Control Protocol)
The User Buttons configuration is composed of 3 items.
Figure 7-3 - User Buttons Logic Profile
Module name - The name of the profile so it can be found in the drop down list of each channel.
User Mode ID - The ID (up to 16) is used to identify the buttons by the LWCP controller.
Text - A text field to label the button. Note that a blank text box will hide the button from the user interface.
A controller like Pathfinder can dynamically change the Text field and define the colors for when the button is in the ON state and when the button is in the OFF state. Default colors are grey for off and blue for on.
Default colors for User Buttons
PDM
The PDM configuration is composed of 3 items.
Figure 7-4 - PDM Logic Profile
Module name - The name of the profile so it can be found in the drop down list of each channel.
IP - The IP address of the PDM product which is to be controlled.
Port - The port for control. The default value of 5443 for PDM products, but if it were changed, you can match them here.