2N Helios IP Automation Configuration Manual
Hide thumbs
Also See for Helios IP Automation:
- Configuration manual (33 pages) ,
- Configuration manual (46 pages)
Related Manuals for 2N Helios IP Automation
Summary of Contents for 2N Helios IP Automation
- Page 1 ® Helios IP Automation Configuration Manual Version 2.5.0 www.2n.cz Firmware...
- Page 2 The product family developed by 2N TELEKOMUNIKACE a.s. includes GSM gateways, private branch exchanges (PBX), and door and lift communicators. 2N TELEKOMUNIKACE a.s. has been ranked among the Czech top companies for years and represented a symbol of stability and prosperity on the telecommunications market for almost two decades.
-
Page 3: Table Of Contents
1. 2N Helios IP Automation ..........5 Terms and Symbols ....................... 6 Symbols Used in Manual ....................6 ® Helios IP Automation Configuration ..............7 Block Parameter Settings ....................8 Use of Variables ......................10 Events ..........................11 Event.KeyPressed ......................12 Event.CodeEntered ...................... - Page 4 Condition.LogicalNot ...................... 45 Condition.True ........................ 45 Condition.False....................... 45 Condition.FlipFlopD ......................46 Condition.FlipFlopRS ..................... 47 Available Digital Inputs and Outputs................48 Examples of Use ......................50...
-
Page 5: Helios Ip Automation
® Helios IP Automation ® In this section, we describe the 2N Helios IP Automation configuration. Here is what you can find in this section: Terms and Symbols ® Helios IP Automation Configuration Description of Configurable Blocks ... -
Page 6: Terms And Symbols
Terms and Symbols 1.1 Terms and Symbols Symbols Used in Manual Safety Always abide by this information to prevent injury of persons. Warning Always abide by this information to prevent damage to the device. Caution Important information for system functionality. ... -
Page 7: Helios Ip Automation Configuration
® Helios IP Automation helps you combine the Events arising in the system (such as key pressing, RFID card use, digital input status change, etc.) with specific Actions (such as digital output activation, user sound playing, call, etc.) as necessary. -
Page 8: Block Parameter Settings
If all the required blocks have been configured correctly (there is a green mark on ® ® every row), 2N Helios IP Automation will be enabled. If there is a red mark, the 2N Helios IP Automation function will be disabled. - Page 9 2N® Helios IP Automation Configuration Most of the blocks include parameters (Event, Condition, StartEvent, e.g.) that refer to other blocks. Set these parameters to interconnect the defined blocks. Make sure that the value to be entered matches the row number in the table defining the block that is referred to.
-
Page 10: Use Of Variables
2N® Helios IP Automation Configuration Use of Variables The event block variables (parameters) help transfer additional information between blocks – send ID of the detected card via HTTP to another device, use parameters received in HTTP for setting parameters of a tied action and so on. Their values are updated whenever the event is generated. -
Page 11: Events
Events 1.3 Events ® Helios IP Automation defines the following event types: KeyPressed key pressed CodeEntered numerical code entered CardEntered RFID card entered DtmfPressed DTMF code received in call DtmfEntered DTMF-received in call numerical code detected CallStateChanged call state changed... -
Page 12: Event.keypressed
Events Event.KeyPressed The KeyPressed block defines the event generated by pressing of the defined key or any key from the defined group. Parameters Define the key or a key group. If this parameter is not completed, the event is generated upon pressing of any key (default value: any). Valid values: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, *, # for numerical keypad buttons %1, %2, .., %54 for quick dial buttons... -
Page 13: Event.codeentered
Events Event.CodeEntered The CodeEntered block defines the event generated by entering of the numerical code and confirmation with the * key (for numerical keypad models only). Parameters Code Define the numerical code. Valid values: Numerical code - 12345, e.g. SuppressTones Suppress sound signalling initiated by receiving of an invalid numerical code. -
Page 14: Event.dtmfpressed
Events Event.DtmfPressed The DtmfPressed block defines the event that is generated when the defined or any DTMF code is received from the defined group. DTMF codes are detected both in incoming and outgoing calls. Parameters Define the DTMF code (or DTMF code group). If this parameter is not completed, the event is generated whenever any DTMF code is detected (default value: Any). -
Page 15: Event.dtmfentered
Events Event.DtmfEntered The DtmfEntered block defines the event that is generated by entering of a DTMF numerical code confirmed with the * key in an incoming or outgoing call. Parameters Code Define the numerical code. Valid values: Numerical code – 12345, e.g. Variables Code Detected received numerical code which was the last to generate this event. -
Page 16: Event.cardentered
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 17: Event.callstatechanged
Events Event.CallStateChanged The CallStateChanged block defines the event generated by a call state change (call ringing, call connection, call termination, etc.) Parameters State Define the call state change. Valid values: ringing - ringing start connected – successful call connection terminated – call termination Direction Define the call direction. -
Page 18: Event.inputchanged
– 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 19: Event.delay
Events Event.Delay The Delay block defines the event generated with a defined delay after another specified event. Define this event to delay the response to the other event by a defined time interval (Delay). Parameters StartEvent Define the event that starts the delay. StopEvent Define the event that stops the delay. -
Page 20: Event.timer
Events Event.Timer The Timer block defines the event generated with a defined delay after another specified event with a defined count of repetitions. Define this event to delay the response to the other event by a defined time interval, or execute the response several times. -
Page 21: Event.httptrigger
Events Event.HttpTrigger The HttpTrigger block defines the event generated by receiving of an HTTP command from the intercom HTTP server. When the HTTP command http://ip_addr/enu/trigger/id is received, an event will be generated whose ID matches the value that follows ‘trigger/’ in the HTTP command. The intercom sends a simple reply to this request (200 OK). -
Page 22: Event.multicasttrigger
Events Event.MulticastTrigger The MulticastTrigger block defines the event generated by receiving of a command sent via SendMulticastRequest. The request is a message sent by UDP to a multicast address (235.255.255.250:4433) and can thus be received by multiple devices at the same time. The message includes the command ID (Command parameter) and additional optional parameters. - Page 23 Events processes this command will automatically include value 123 for the AAA variable. This variable can be referred to in the interconnected blocks. Example Event generated by receiving of a mass opendoor command: Event.MulticastTrigger: Command=opendoor...
-
Page 24: Event.audiolooptest
Events Event.AudioLoopTest The AudioLoopTest block defines the event generated after the loudspeaker and microphone test (Audio Loop Test) is performed. The subsequent actions are executed based on the test result. Parameters Result This parameter specifies the required test result. Valid values: any –... -
Page 25: Actions
Actions 1.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 command sending to multiple devices... -
Page 26: Action.activateswitch
Actions Action.ActivateSwitch The ActivateSwitch block defines the action necessary for activation of the intercom switch as configured in the Switch 1 – 4 tags. The activity to be performed depends fully on the particular switch settings (digital output activation, HTTP command sending, etc.). -
Page 27: Action.setoutput
– LED 1 indicator led2 – 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. -
Page 28: Action.begincall
Actions Action.BeginCall The BeginCall block defines the action necessary for establishing of an outgoing call to the defined telephone number, SIP URI or user number included in the intercom telephone directory. Parameters Event Define the event to launch the action. Condition Define the condition to be met to execute the action. -
Page 29: Action.answercall
Actions Action.AnswerCall The AnswerCall block defines the action necessary for answering of an incoming call. In case no call is coming or the incoming call is not ringing, the action will not initiate any activity. Parameters Event Define the event to launch the action. Condition Define the condition to be met to execute the action. -
Page 30: Action.endcall
Actions Action.EndCall The EndCall block defines the action necessary for termination of the currently made call. In case there is no active call via the intercom, the action will not initiate any activity. Parameters Event Define the event to launch the action. Condition Define the condition to be met to execute the action. -
Page 31: Action.sendhttprequest
Actions Action.SendHttpRequest The SendHttpRequest block defines the action necessary for sending of an HTTP command to another LAN device. The HTTP command helps you control other devices in the LAN (IP relay, recording system, another intercom, etc.). Parameters Event Define the event to launch the action. Condition Define the condition to be met to execute the action. -
Page 32: Action.sendmulticastrequest
Actions Action.SendMulticastRequest The SendMulticastRequest block defines the user command sending action to multiple devices. The sent command can be processed by the MulticastTrigger block. The command is a message sent by UDP to a multicast address (235.255.255.250:4433) and can thus be received by multiple devices at the same time. - Page 33 Actions...
-
Page 34: Action.playusersound
Actions Action.PlayUserSound The PlayUserSound block defines the user sound playing action. 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. Sound Select the user sound number (1 – 10). Example Play user sound 1: Action.PlayUserSound: Sound=1... -
Page 35: Action.startmulticastsend
Actions Action.StartMulticastSend The StartMulticastSend block defines the starting action for audio stream sending to a multicast IP address. You can control up to four independent transmission channels. The RTP/UDP protocol is used and the data are in the PCMU format. Parameters Event Define the event to launch this action. -
Page 36: Action.stopmulticastsend
Actions Action.StopMulticastSend The StopMulticastSend block defines the stopping action for audio stream sending to a multicast IP address. 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. -
Page 37: Action.startmulticastrecv
Actions Action.StartMulticastRecv The StartMulticastRecv block defines the starting action for audio stream receiving and playing. You can control up to four independent transmission channels. The RTP/UDP protocol is used and the data are in the PCMU format. Parameters Event Define the event to launch this action. Condition Define the condition to be met for the action to be executed. -
Page 38: Action.stopmulticastrecv
Actions Action.StopMulticastRecv The StopMulticastRecv block defines the stopping action for audio stream receiving to a multicast IP address. 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. -
Page 39: Action.setcamerainput
– external IP camera The parameter is optional, the default value is internal. ® 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. -
Page 40: Conditions
Conditions 1.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 condition negation FlipFlopD D-type flip-flop... -
Page 41: Condition.profilestate
Conditions Condition.ProfileState The ProfileState block defines the condition to be met in the case of active/inactive time profile. Parameters Profile Define the time profile number (1 – 20 depending on the intercom model). State Define the required profile state. This parameter is optional. Valid values: active –... -
Page 42: Condition.callstate
Conditions Condition.CallState The CallState block defines the condition to be met in the case of a defined state of the currently made call. Parameters State Define the call state. Valid values: idle – call is not being made ringing – ringing in progress connected –... -
Page 43: Condition.inputstate
– 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 44: Condition.logicaland
Conditions Condition.LogicalAnd The LogicalAnd block helps you create groups of conditions. The block is fulfilled if all the conditions in the defined group are met. Parameters Condition Define the list of conditions to be met. Separate the conditions with a comma. Example The condition is met if conditions 1, 2 and 3 are met at the same time: Condition.LogicalAnd: Condition=1, 2, 3... -
Page 45: Condition.logicalnot
Conditions Condition.LogicalNot The LogicalNot block defines the condition to be met in case another defined condition is not met. Parameters Condition Define the condition not to be met. Example The condition is met in case condition 1 is not met: Condition.LogicalNot: Condition=1 Condition.True The True block defines the condition to be met each time. -
Page 46: Condition.flipflopd
The FlipFlopD output can be used as a condition for control of actions in rather complex ® Helios IP Automation applications. It is a simulation of a D-type flip-flop circuit. Parameters ClockEvent Define the event at which the current state of the condition is to be recorded. -
Page 47: Condition.flipfloprs
0 at the rise of defined events. The FlipFlopRS output can be used as a condition for ® control of actions in rather complex 2N Helios IP Automation applications. It is a simulation of an RS-type flip-flop circuit. Parameters SetEvent Define the event to set the condition into the ‘met’... -
Page 48: Available Digital Inputs And Outputs
Available Digital Inputs and Outputs 1.6 Available Digital Inputs and Outputs ® In this section, the digital inputs and outputs available on each 2N Helios IP model are described. 2N Helios IP Vario Outputs relay1 – relay output on basic unit relay2 –... - Page 49 2N Helios IP Uni Outputs relay1 – relay output on basic unit Inputs Not available. 2N Helios IP Audio/Video Kit Outputs relay1 – relay output output1 – digital output 1 output2 – digital output 2 led1 – LED 1 control output led2 –...
-
Page 50: Examples Of Use
Examples of Use 1.7 Examples of Use Calling to Dispatching Office in Case of Unauthorised Door Opening Specification Call the selected telephone number whenever the tamper switch is 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). - Page 51 Examples of Use Calling to Dispatching Office in Case of Unauthorised Door Opening with Service Code Blocking Option Specification Call the selected telephone number whenever the tamper switch is disconnected (device opened). Enable blocking and re-enable numerical code alarm entered from the intercom keypad.
- Page 52 Examples of Use Door Opening by RFID Card Specification Activate the door contact switch by entering the proper RFID card. Block diagram Entering an RFID card with the defined ID (1: Event.CardEntered) activates switch 1 (2: Action.ActivateSwitch). Event (1) Action (2) CardEntered ActivateSwitch Card=0*0000...
- Page 53 Examples of Use Alarm (Dispatching Office Call) Caused by Over 2-Min Long Door Opening Specification Call the dispatching office in case the door remains open for more than 2 minutes. It is supposed in the example that the door opening signalling contact is connected to Input1.
- Page 54 Examples of Use LED Flashing during Call / Electric Door Lock Opening Specification Enable LED flashing during an active call. Block diagram Enable LED flashing by a combination of the periodic timer (1: Event.Timer) and delay (2: Event.Delay). These two blocks define the period (250ms) and duty cycle of the signal or the LED shining period (125ms).
- Page 55 2N TELEKOMUNIKACE a.s. Modřanská 621, 143 01 Praha 4, Česká Republika Tel.: +420 261 301 111, Fax: +420 261 301 999 E-mail: obchod@2n.cz Web: 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