Zebra Technologies QL+ Manuale Utente
![Zebra Technologies](https://files.manualsbrain.com/attachments/a78f49d565a2596a8b31f4240e25fed2998da2a0/common/fit/150/50/2656e56263d759e2c7910989c000585d7bce0fb5d50f1f63705e38675fa7/brand_logo.gif)
32
QL Series User Guide
Bluetooth™ Networking Overview
In order to exchange data, two Bluetooth enabled devices
must establish a connection. Bluetooth software is always
running in the background, ready to respond to connection re-
quests. One device (known as the master or the client) must
request a connection with another. The second device (the
slave or the server) then accepts or rejects the connection. A
Bluetooth enabled QL Series printer will normally act as a
slave, but in theory any Bluetooth device can be either a mas-
ter or a slave. This miniature network is sometimes referred to
as a “piconet” and can consist of several Bluetooth enabled
devices.
running in the background, ready to respond to connection re-
quests. One device (known as the master or the client) must
request a connection with another. The second device (the
slave or the server) then accepts or rejects the connection. A
Bluetooth enabled QL Series printer will normally act as a
slave, but in theory any Bluetooth device can be either a mas-
ter or a slave. This miniature network is sometimes referred to
as a “piconet” and can consist of several Bluetooth enabled
devices.
For the most part, communications using the Bluetooth pro-
tocol are initiated and processed without any operator inter-
vention, much like the IrDA system described previously.
vention, much like the IrDA system described previously.
Each Bluetooth enabled QL Series printer is identified by a
unique Bluetooth Device Address (BDA) loaded into its Quick-
Link module when manufactured.
Link module when manufactured.