User's Manual
Table Of Contents
- FCC and ISED (IC) statements
- 1. Introduction
- 2. Installing the option
- 3. Installing online devices
- 4. Online settings in the client
- 5. Issuing a ZigBee configuration card
- 6. System operation
- 7. Commissioning
- 8. Power loss and hardware failure
- 9. Redundancy and recovery
- Appendix A: Online devices
- Appendix B: Mounting of gateway and router
- Appendix C: Example configurations
- Appendix D: Web interface for gateway
- Appendix E: Reset of gateway
- Appendix F: Gateway boot-up
- Appendix G: More about how the gateway finds the server
- Appendix H: Firmware upgrade
12
ASSA ABLOY Hospitality
66 3081 004-23
1.4 Router
A router acts either as a repeater for range extension, or as a parent for endnodes.
It will also act as a buffer for messages sent to endnodes connected to the router.
Routers are externally powered.
The router can have either five routers or 15 endnodes connected as direct
descendants.
There can be a maximum of five hops down the gateway; i.e. gateway – router
– router – router – router – endnode. This limits the physical coverage of a
PAN. Important: Even though it is possible to have five hops, it is
recommended to have maximum three hops, i.e. gateway - router -
router - endnode. The link quality index (LQI) should be at least 30%.
See section 1.11 for more information about the LQI.
See Appendix A for more information about the router, including a detailed picture.
See Appendix B for preferred way of mounting the router.
See Appendix C for configuration examples.
1.5 Endnode
An endnode is built into each lock. It is optimized for low power consumption.
The parent router will act as a buffer for commands from the server. A command
sent from the server to a lock will be sent from the gateway to the lock’s parent
router. The command will be sent through the routers that may be located between
the gateway and the lock’s parent router. Any message sent from the lock will be
passed on to the server through the parent router, any intermediate routers and the
gateway. Messages from the lock are sent instantly. The total number of endnodes is
virtually unlimited.
1.6 Lock
The locks are the destination for commands and the source of events.
1.7 Permit joining/Forbid joining
In order to prevent nodes from joining randomly, 'permit joining' can for each PAN
only be made at one router or its 'parent gateway' at a time. When a node is to be
joined to the PAN, 'permit joining' must be made at the router or gateway that shall
be its parent. When the node has joined, 'forbid joining' should be made at the
parent. 'Forbid joining' will automatically be made on the parent after 15 minutes
in case it is forgotten. Note: It is only possible to make 'permit joining' at one RT
per PAN at a time. If you make 'permit joining' at one RT and then at another RT
in the same PAN, the first RT will automatically make 'forbid joining'.