SimonsVoss WaveNet - Ringcast

WARNING
Change in the sequence of emergency functions due to malfunctions
SimonsVoss and "Made in Germany" stand for maximum safety and reliab-
ility. 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 [}178] 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 [}136] ).
Switch the corresponding input on the initiator and check:
 whether the locks react as desired (see also RouterNode: Digital input
[}77] ).
 whether the output set on the RouterNode shows the
acknowledgement by switching as desired (see also
RouterNode:
Digital output [}74] ).
Test with central output router
NOTE
Central output router in RingCast with R/CR router nodes
The central output router receives the input acknowledgement of the parti-
cipating router nodes exclusively via an Ethernet connection. The central
output router therefore ignores the status of router nodes that are not Eth-
ernet 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.
 Check the status of other router nodes (R/CR) independently of the
central output router manually (see
Test reachability (LSM) [}177]
and RouterNodes [}174] or IO Status and LockNode responsiveness
[}179] ).
The use of a central output router (see Central output router [}132] )
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:
WaveNet (Manual)
5. WaveNet Manager
137 / 210