![PESA RCP-GPIO Скачать руководство пользователя страница 24](http://html1.mh-extra.com/html/pesa/rcp-gpio/rcp-gpio_manual_1531770024.webp)
Operations
Section 3
RCP-GPIO
10/96
P/N 81905903860
page 3.5
OP ERAT ION
3
Given a configuration that has the source VTR 1 associated to data key
#3, when input #3 is activated on the panel, VTR 1 is taken to the destina-
tion controlled by the panel. The output associated with the source VTR1
becomes active.
If the same source is used more than once on a panel (i.e. assigned to
more than one data key) and is used for GPIO panel output activation, the
user will need to OR the switch closures together. The panel does not
guarantee which output will activate when the source is switched to the
panels destination.
The data key list only needs the first 32 data keys configured. Keys 33-
72 need not be configured.
11.Salvo key and soft keys are not used by this configuration. They do
not need to be configured on the panel.
Configuring Actions to be Taken on Different Destinations
The RCP-GPIO panel may be configured to initiate switches on different
destinations. Doing so has some limitations in that each input event must
go to two separate inputs. In addition, the use of the general purpose
outputs is limited as the panel only provides tally for one destination at any
one time.
1. Enter a panel name. This is an optional name for your benefit that
allows you to identify the function of the panel.
2. Enter the address for which the panel is coded. This address is coded
on the DIP switch on the back of the panel.
3. Enter a requester code. Usually this is the same as the panel address.
Requester codes are used when locks and protects need to be shared
among a number of panels.
4. Enter the lock priority. Since this panel performs no lock actions, a
value of 0 (super user) is adequate.
5. Enter the status level. This is the level of control that is of most inter-
est to the panel. It is the level of control that will determine the tally
that activates the GPIO panel outputs.
3.4 Panel Configuration Continued:
Configuring All Actions to be Taken on a Single Destination Cont: