Redundancies in RingCast - WaveNet

Redundancy through transmission media

If you use second-generation Ethernet router nodes (=RN2), the router nodes first use the Ethernet connection and then the wireless connection as backup.

If the WaveNet Manager detects when calculating the RingCast that several RouterNodes reach each other wirelessly at the same time (in the example "Initiator", 1, 2, 3, 4, 5 or 4a, 4b and 4c), it assigns exactly one target partner to each RouterNode within this "radio cloud".

Router node

1. Transmission medium in RingCast

2. Transmission medium
(backup) in RingCast

RN2.ER.IO (Ethernet and radio)

Ethernet

Radio (868 MHz)

RN.CR.IO (RS-485 and Radio)

Radio (868 MHz)

RN.R.IO (Radio)

Radio (868 MHz)

NOTE

notice

Transmission range

The range of the radio connection is up to 30 m (depending on the building structure).

If the Ethernet RouterNode does not reach its target partner via the Ethernet connection after five seconds with a RingCast, it attempts to reach the target partner via the wireless connection. Since the RouterNode is physically unable to address its target partners in a wireless connection, all RouterNodes within range receive the data packet. Subsequently, all RouterNodes that have received the data packet check whether the condition Actual target partner is fulfilled. If the condition is not fulfilled, the router nodes that are not target partners of the sending RouterNode discard the packet again.

If the RouterNode does not reach its target partner via the wireless connection, the RingCast is interrupted at this point.

Redundancy through branching

Regardless of the transmission medium, it is possible for the WaveNet Manager to establish multiple connections between two RouterNodes when calculating the RingCast. If one of these connections fails or is disturbed, then the RingCast can partially continue to run over the intact connections. The data packet with the same input counter reading as the input counter reading stored in the initiator arrives at the initiator again and the RingCast is recognised as completed.

Redundancy of the power supply

NOTE

notice

Interruption of the RingCast due to power failure

Power in buildings may fail. If RouterNodes are not supplied with power, you cannot forward your data packets and the RingCast is interrupted.

  1. Use an uninterruptible power supply (UPS) to protect the RouterNodes from a power failure.

Redundancy through events in LSM

NOTE

notice

Event management only in LSM Business

This chapter describes how to use the Event Manager. The Event Manager is only available in LSM Business/Professional.

Various influences can (temporarily) interfere with radio transmission (see Radio network and Signal quality). If interference occurs during a broadcast, not all LockNodes and therefore not all locking devices may be reached.

You can add an additional transmission using the LSM. Since you can also forward input events to the LSM when a connection to the LSM is established (see RouterNode: Digital output), you can also react to them in the LSM (Network - Event manager). In the window I/O configuration activate the checkbox Yes.

This additional broadcast requires the following:

  • Initiator and central output router are the same device
  • Only Ethernet RouterNodes are involved in RingCast

If you use a central output router and forward its input acknowledgement to LSM, you can also cancel the additional transmission (in LSM, cancel the timer as a response). To do this, connect the output of the input acknowledgement (e.g. 1) to a free input (e.g. 2).

The event in LSM is processed in three parts.

  1. WaveNet input starts a timer event.
  2. Timer event starts after event expires and starts reaction.
  3. Reaction sends the RingCast command to all specified locking devices.

Repeating the broadcast

  1. LSM open.
  1. Via Network select the entry Event manager.
  2. The window Network event manager opens.
  4. In the area Reactions click the button New.
  5. The window New reaction opens.
  7. Enter a name and a description.
  8. In the dropdown menu Type select the entry Network task.
  9. Click on the button Configure reaction.
  10. The window Task opens.
  12. Enter a name and a description.
  13. In the dropdown menu Type select the command that your RingCast transmits.
  14. In the area Locks/network nodes click the button Edit.
  15. The window Administration opens.
  17. Mark all locking devices that are controlled by the RingCast.
  18. Click on the button ← Add.
  19. Click on the OK button.
  20. The Administration window closes.
  21. Click on the OK button.
  22. The window Task closes.
  23. Click on the OK button.
  24. The New reaction window closes.
  25. The reaction is listed in the area Reactions.

Wait for timer

  1. In the area Events click the button New.
  2. The window New Event opens.
  4. Enter a name and a description.
  5. In the dropdown menu Type select the entry Time interval.
  6. Click on the button Configure event.
  7. The window Time interval event opens.
  9. Specify the time delay between RingCast start and LSM backup start.

  10. NOTE

    notice

    RingCast malfunction due to parallel transmission

    If LSM executes the reaction immediately, then the affected router nodes are already sending while the RingCast is not yet complete. This can interrupt the RingCast.

    1. Set a delay that is one minute longer than the maximum transmission time of the RingCast (see Maximum transmission time in RingCast).
  11. Click on the OK button.
  12. The window Time interval event closes.
  13. Click on the button Add.
  14. The window Administration opens.
  16. Mark the response which you have just created and which is to be triggered when the timer event expires without being interrupted.
  17. Click the button ← Add.
  18. Click on the OK button.
  19. The Administration window closes.
  20. Action is displayed in the list of actions associated with the event.
  22. Click on the OK button.
  23. The New Event window closes.
  24. Reactions receives two additional entries with the endings "Deactivate" and "Activate".

Starting the timer

  1. In the area Events click the button New.
  2. The window New Event opens.
  4. Enter a name and a description.
  5. In the dropdown menu Type select the entry Input Event.
  6. Click on the button Configure event.
  7. The window Input Event opens.
  9. In the area Select input select the input that troggers your RingCast.
  10. In the area Input changes select when your RingCast starts.
    from 0 to 1: RingCast starts when the signal is present.
    from 1 to 0: RingCast starts when the signal is no longer present.
    both: RingCast starts when the signal is present and when it is no longer present.
  11. Click on the OK button.
  12. The Input Event window closes.
  13. Click on the button Select.
  14. The window Administration opens.
  16. Mark the router that is the initiator in your RingCast (the RouterNode that gets the input first).
  17. Click on the button ← Add.
  18. The Administration window closes.
  19. RouterNode is displayed in the list of locking devices associated with the event.
  21. Click on the button Add.
  22. The window Administration opens.
  23. From the responses you created earlier, mark the one with the ending "activate".
  24. Click the button ← Add.
  25. Click on the OK button.
  26. The Administration window closes.
  27. Action is displayed in the list of actions associated with the event.
  29. Click on the OK button.
  30. The New Event window closes.
  1. LSM backup is set up.

Cancel timer event

  1. On the central output router, at least one digital output is set to Input receipt short or Input receipt static eingestellt (see RouterNode: Digital output).
  1. At the central output router, connect a free input input to a digital output with input acknowledgement (see Central output router).
  2. Via Network select the entry Event manager.
  3. The window Network event manager opens.
  4. In the area Events click the button New.
  5. The window New Event opens.
  6. Enter a name for the event, e.g. "Backup abort".
  7. In the dropdown menu Type select the entry Input Event.
  8. Click on the button Configure event.
  9. The window Input Event opens.
  10. In the Select input area, select the input to which the central output router's acknowledgement is to be created.
  11. In the area Input changes select the optionfrom 1 to 0.
  12. Click on the OK button.
  13. The window Input Event closes.
  14. Click on the button Add.
  15. The window Administration opens.
  16. From the responses created earlier, select the one with the ending "activate".
  17. Click the button ← Add.
  18. Response is
  19. Click on the OK button.
  20. window Administration closes.
  21. Action is displayed in the list of actions associated with the event.
  22. Click on the OK button.
  23. The Network event manager window closes.
  1. LSM backup is set up.

Transfer the changes to the communication node assigned to your router node (see LSM import).

For more information on setting up an event and a reaction, refer to the LSM manual.