COMMUNICATION INTERFACES
Bluetooth
E355/E265 USER AND BEST PRACTICES GUIDE 35
Bluetooth
The e355 Bluetooth device is BCM 43340 BT/Wi-Fi integrated chip that supports
BT 2.1+ EDR. The Bluetooth interface is enabled whenever the e355 is turned on
and not installed in a frame.
The Bluetooth device provides low power consumption and operation and is
capable of staying paired and connected while in deep sleep mode and waking up
to receive data. If the Bluetooth device is connected to/from a smart device with
either SPP/PAN profiles, it will maintain the connection and not automatically
power down.
The Bluetooth Manager (BT_MGR) application provides the user interface for
pairing to/from a smart device, connecting to/from SPP/PAN profile on the smart
device and Bluetooth link management. Being paired with a device does not mean
that the e355 and smart device are connected. To be connected, the e355 must
be linked to one of the supported profiles.
The Bluetooth Managers document has all the details need for pairing and
connecting to profile services to/from a smart device. For more information, refer
to Verix eVo Bluetooth Manager Users Guide, VPN - DOC00327.
Supported Profiles
The following profiles are supported:
Serial Port Profile (SPP)
The e355 supports SPP for both Client/Server modes. The BT_MGR application is
used to configure these profile. By default, SPP port is used for SPP Client mode
and SPP2 port is used for SPP Server mode. These ports can be used
simultaneously.
When in SPP Client Serial Mode, BT_MGR provides Bluetooth link maintenance
and reconnection logic. When in SPP Server mode, the smart device is in SPP
Client mode and must perform Bluetooth link maintenance and reconnection logic.
Apple
The e355 can connect to iOS device via iAP1/iAP2 protocol over SPP in both
Client and Server modes. The iAP1/iAP2 service is always running on the iOS
device so connecting to the device in Client mode is much easier.
Android/Windows
The e355/e265 connects to an Android/Windows device via custom PMR-MUX2
protocol over SPP in both Client and Server modes. When connecting e355 to
Android/Windows device in SPP Client mode, the SPP Server must be running on
the smart device. If the SPP service is not running on the smart device, it will pair
but not connect.
If the device is installed in a frame and then removed the e355 must be restarted
to go into Bluetooth communications mode.
To Next Page
Loading...
Need help?
General
