Page 1
® Helios IP Automation IP Intercom Configuration Manual Version 2.10 www.2n.cz ...
Page 2
The 2N TELEKOMUNIKACE a.s. is the holder of the ISO 9001:2009 certificate. All development, production and distribution processes of the company are managed by this standard and guarantee a high quality, technical level and professional aspect of all our products.
Warning Always abide by this information to prevent damage to the device. Caution Important information for system functionality. Useful information for quick and efficient functionality. Note Routines or advice for efficient use of the device. ® TELEKOMUNIKACE a.s., www.2n.cz...
® outputs, most of which can be configured like standard Helios IP switches (refer ® to the Switches subsection). You can make use of all of these 2N Helios IP Automation inputs and outputs in variable combinations. ® Helios IP Automation...
Page 6
It holds true in general that an action is always tied with a selected event and is executed when a selected condition is met. The condition is optional and if none is ® selected, the action is executed whenever the assigned event occurs. 2N Helios IP Automation defines a number of events, actions and conditions to be further set.
Page 7
Move your mouse cursor to the red mark to display the Help to find the error. If all the required blocks have been configured correctly (there is a green mark on ® every row), Helios IP Automation will be enabled. If there is a red mark, the ® Helios IP Automation function will be disabled.
Page 8
Refer to the following subsections for more variables with specific functions. The Upper/Lower case is not be respected in the variable names. Caution You cannot use the variables in the block relation defining parameters, i.e. Event, Condition, etc. ® TELEKOMUNIKACE a.s., www.2n.cz...
3. Events ® Helios IP Automation defines the following event types: KeyPressed – key pressed KeyReleased - key released DtmfPressed – DTMF code received in call DtmfEntered – DTMF-received in call numeric code detected CodeEntered – numeric code entered CardEntered –...
Page 10
1 2 3 4 5 6 7 8 9 * # for numeric keypad buttons , .., %999 for quick dial buttons any for any button (default value). Separate the values with a comma while defining more keys than one. ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 11
Variables Key – the recorded received DTMF code which was the last to generate the event. The DTMF is stored in the Key parameter format. Example Event generated upon detection of DTMF code #: Event.KeyPressed: Key=# ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 12
0 – tones are not suppressed 1 – tones are suppressed (default value). Variables Code – the received numeric code which was the last to generate this event. Example Event generated by entering code 12345* on a keypad: ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 13
ID (for RFID card reader models only). Parameters ® Card – define the RFID card ID; refer to the Card Reader subsection in the 2N Helios IP Configuration Manual Valid values: valid – any valid card (included in the intercom card list) invalid –...
Page 14
– digital input 1 on card reader cr_input2 – digital input 2 on card reader. ® There may be different lists of valid values for different 2N Helios IP models; refer to the Available Digital Inputs and Outputs subsection.
Page 15
Define this event to delay the response to the other event by a defined time interval, or execute the response several times. ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 16
Name – define a unique HTTP command identifier including alphabetical characters and digits. Variables The HttpTrigger event is always generated by the HTTP command which can carry a list of user parameters as included in the URI command. http://ip_address/enu/trigger/id?param1=value1¶m2=value2 ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 17
The MulticastTrigger event is generated whenever a mass command including the list of user parameters (Params parameter, MulticastRequest action) is received. Each of the parameters has a user-defined unique name and is available as a variable of the same name in the MulticastTrigger block. ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 18
– define time to start the event. Time is entered in hh:mm format. To limit validity of this event for some days only, use the condition Condition.ProfileState at the started action and specify requested days in the used time profile. ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 19
1 – start of the motion 0 – end of the motion The parameter is optional, the default value is Variables This block does not define any specific variables. Example Event generated at the start of the motion Event.MotionDetected: State=1 ® TELEKOMUNIKACE a.s., www.2n.cz...
4. Actions ® Helios IP Automation – defines the following types of actions: ActivateSwitch – switch activation SetOutput – digital output state setting BeginCall – outgoing call setup AnswerCall – incoming call answer EndCall – call termination SendHttpRequest – HTTP command sending SendMulticastRequest –...
Page 21
– LED 2 indicator led3 – LED 3 indicator. ® There may be different lists of valid values for different 2N Helios IP models; refer to the Available Digital Inputs and Outputs subsection. Level – define the required output level. This parameter is optional.
Page 22
Event – define the event to launch the action. Condition – define the condition to be met to execute the action. This parameter is optional. Example Answer a call if the event defined on row 2 arises: Action.AnswerCall: Event=2 ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 23
Password – define password in the case if authorization is required by HTTP server. This parameter is optional. Example Send an HTTP command to the device with the IP address 192.168.1.1 if the event defined on row 2 arises: Action.SendHttpRequest: uri= http://192.168.1.1/message ; Event=2 ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 24
Send the opendoor command to all devices with the properly set Event.MulticastTrigger block in the network if the event defined on row 2 arises: Action.SendMulticastRequest: Command=opendoor; Event=2 Action.PlayUserSound PlayUserSound block defines the user sound playing action. ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 25
– the source of audio is the call The parameter is optional, the default value is Example Start audio stream sending via channel 1 to address 239.0.0.1:10000 if the event defined on row 2 arises: Action.StartMulticastSend: Channel=1; Address=239.0.0.1; Port=1000; Event=2 ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 26
6 – maximum level. The parameter is optional, the default value is Example Start audio stream receiving on multicast IP address 239.0.0.1:10000 via channel 1 if the event defined on row 2 arises: Action.StartMulticastRecv: Channel=1; Address=239.0.0.1; Port=10000; Event=2 ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 27
The parameter is optional, the default value is internal ® Id – define the video signal channel. The parameter is available with the 2N Helios IP Video Kit model only and applicable only if the Type parameter is set to internal Valid values: 1 –...
Page 28
Automation settings. Parameters Event – define the event to launch this action. Condition – define the condition to be met for the action to be executed. This parameter is optional. ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 29
2 arises Action.SendEmail: User=5; Event=2 Action.SetOnvifVirtualInput SetOnvifVirtualInput block defines action for sending the change of the level of virtual input by the ONVIF protocol. ONVIF Device Manager (vesion 2.2.250) can be used for test. ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 30
Internal – internal camera External – external camera. The parameter is optional, the default value is Auto Example Uploads a picture from the camera to the FTP server if the event defined on row 2 arises ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 31
The auto provisioning parameters are configured in the System / Auto Provisioning menu. Parameters Event – define the event to launch this action. Condition – define the condition to be met for the action to be executed. This parameter is optional. ® TELEKOMUNIKACE a.s., www.2n.cz...
5. Conditions ® Helios IP Automation defines the following types of conditions: ProfileState – time profile state CallState – current call state InputState – digital input state LogicalAnd – logical AND of conditions LogicalOr – logical OR of conditions LogicalNot –...
Page 33
– digital input 1 on card reader cr_input2 – digital input 2 on card reader. ® There may be different lists of valid values for different 2N Helios IP models; refer to the Available Digital Inputs and Outputs subsection.
Page 34
Example The condition is met if conditions 1, 2 or 3 are met: Condition.LogicalOr: Condition=1, 2, 3 Condition.LogicalNot LogicalNot block defines the condition to be met in case another defined condition is not met. ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 35
Example The condition is always met: Condition.True Condition.False False block defines the condition not to be met any time. Parameters There are no parameters in the False block. Example The condition is always not met. Condition.False ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 36
The ® FlipFlopD output can be used as a condition for action control in rather complex 2N Helios IP Automation applications. It is a simulation of a D-type flip-flop circuit.
® Helios IP Verso ® SIP Speaker ® 2N Helios IP Vario Outputs relay1 – relay output on basic unit relay2 – relay output on additional switch (if installed) cr_relay1 – relay output 1 on card reader (if installed) cr_relay2 – relay output 2 on card reader (if installed) redled –...
Page 38
– tamper switch (if installed) cr_input1 – digit input 1 on card reader (if installed) cr_input2 – digital input 2 on card reader (if installed) ® 2N Helios IP Audio/Video Kit Outputs relay1 – relay output output1 – digital output 1 output2 –...
Page 39
® 2N Helios IP Verso Basic Unit Outputs output1 - digital output relay1 - relay output Inputs input1 – digital input on basic unit I/0 Module T h e i n p u t s o u t p u t s...
Page 40
Inputs input1 – vstup LED IN tamper – tamper switch (if installed) ® 2N SIP Speaker Outputs relay1 – relay output Inputs Unavailable It is possible to use Event.KeyPressed: Key=%1 for events generated at LOGIC IN input ® TELEKOMUNIKACE a.s., www.2n.cz...
Call the selected telephone number whenever the tamper switch gets disconnected (device opened). Block diagram The rising edge on the tamper input (1: Event.InputChanged) initiates calling to the defined telephone number (2: Action.BeginCall). Intercom settings 1: Event.InputChanged: Input=tamper 2: Action.BeginCall: Number=1111; Event=1 ® TELEKOMUNIKACE a.s., www.2n.cz...
(2: Condition.CodeEntered) on the numeric keypad. If another code is entered (3: Condition.CodeEntered), the condition will be invalid. Intercom settings 1: Event.InputChanged: Input=tamper; Edge=rising 2: Event.CodeEntered: Code=164575 3: Event.CodeEntered: Code=111 4: Condition.FlipFlopRS: SetEvent=3; ResetEvent=2; ResetValue=1 5: Action.BeginCall: Number=1111; Event=1; Condition=4 ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 43
Whenever the door opens, the rising edge on Input1 signal (1: Event.InputChanged) calls the defined telephone number (4: Action.BeginCall) with a 120s delay (2: Event.Delay).The call is only executed if the door remains open for more than 120 s (3: Condition.InputState). ® TELEKOMUNIKACE a.s., www.2n.cz...
Page 44
(2: Event.Delay). These two blocks define the period (250 ms) and duty cycle of the signal or the LED shining period (125 ms). These two events are tied with the on-switching (4: Action.SetOutput) and off-switching (5: Action.SetOutput) actions. The LED switch-on action is conditioned by the active call (3: Condition.CallState). ® TELEKOMUNIKACE a.s., www.2n.cz...
Need help?
Do you have a question about the Helios IP Automation and is the answer not in the manual?
Questions and answers