RingCast function test - WaveNet

The RingCast has no self-test function.

WARNING

warning

Impairment or failure of protective functions due to changed conditions

The activation of the protection functions in RingCast is based on wireless connections and Ethernet connections. Wireless connections in particular can be affected by changing environmental conditions (see Radio network und Challenges in wireless networks). This also influences the activation of the protective functions in the RingCast and can jeopardise the safety of persons and property that are additionally protected by the protective functions in the RingCast, for example.

  1. Test the protective functions at least once a month (see RingCast function test).
  2. If necessary, also observe other guidelines or regulations that are relevant for your locking system (especially for escape and rescue routes and fire protection. You are solely responsible for ensuring compliance with these guidelines and regulations).

Change in the sequence of emergency functions due to malfunctions

SimonsVoss and "Made in Germany" stand for maximum safety and reliability. In individual cases, however, malfunctions of your devices cannot be ruled out. This may pose a risk to the safety of persons and property, which are additionally protected by the protective functions in the RingCast.

  1. You should test your devices at least once a month (see Device function test Shorter intervals may also be required according to other regulations concerning your overall system).
  2. Test the protective functions at least once a month (see RingCast function test).

Switch the corresponding input on the initiator and check:

Test with central output router

NOTE

notice

Central output router in RingCast with R/CR router nodes

The central output router receives the input acknowledgement of the participating router nodes exclusively via an Ethernet connection. The central output router therefore ignores the status of router nodes that are not Ethernet router nodes (.ER). If you are using the central output router and your RingCast also contains router nodes without an Ethernet interface, the central output router's input acknowledgement only means that all locking devices assigned to an Ethernet router node have received the command.

  1. Check the status of other router nodes (R/CR) independently of the central output router manually (see Test reachability (LSM) and RouterNodes or IO Status and LockNode responsiveness).

The use of a central output router (see Central output router) simplifies the test of the RingCast considerably. Switch the corresponding input at the initiator and check whether the central output router sends an input acknowledgement or switches the corresponding output. If the output does not switch, then check which RouterNodes have caused problems:

  1. WaveNet Manager opened via LSM (see Best Practice: From the LSM software)
  1. Click with the right mouse button on the RingCast entry you want to test.
  2. In the drop-down menu Select domain select the input whose RingCast you want to test.
  3. The window Edit radio domains opens.
  5. Click on the button Status.
  1. RingCast is tested.

The RingCast was able to address all locking devices.

The RingCast could not be closed. Possible causes (see also Central output router):

  • One or more RouterNodes have not received the data packet.
  • One or more RouterNodes have not reached one or more LockNodes.
  • Ethernet connection to one or more RouterNodes is interrupted. The RouterNodes could have received the data packet wirelessly, but could no longer return their input acknowledgements due to the interrupted Ethernet connection.
  1. Check the reachability of the RouterNodes mentioned (see RouterNodes und Test reachability (LSM)).
  2. Check the reachability of the LockNodes (see LockNodes und Test reachability (LSM)).
  3. Check the last responses of the LockNodes (see IO Status and LockNode responsiveness).