Configuration; Basic Settings; Peers - u-blox NINA-B1 Series Getting Started

2 Configuration

You can configure the NINA-B1 module according to your specific requirements by using AT commands (see
u-blox Short Range Modules AT Commands Manual [1]). The easiest way to get started is to use the u-blox
s-center, which is a graphical user interface for sending the AT-commands (see s-center Product Summary [4]).
The u-blox s-center allows an easy configuration for the most common AT commands.

2.1 Basic settings

There are some basic commands for controlling the general Bluetooth behavior of the module.
•
Connectable - AT+UBTCM: Configures the connectability for incoming connections.
•
Discoverable - AT+UBTDM: Configures the visibility for remote devices making inquiries.
•
Pairable - AT+UBTPM: Configures the ability to pair (authenticate) for the remote devices.
•
Bluetooth name - AT+UBTLN: The name presented to the remote devices making inquiries or name
requests.
Once a pairing has been done with a remote device, it is recommended to disable both discoverable and pairable
mode for security reasons and performance.

2.2 Peers

A connection consists of a sender and a receiver of data. Every sender and receiver in a setup is referred to as a
peer. Thus, a peer is capable of either receiving and/or sending data.
There are two kinds of peer classes in the serial port adapter:
•
Local peer
•
Remote peer
The local peer is synonymous with the UART. In contrast to the local peer, the remote peer is another device.
Several remote peers can be defined if a multidrop scenario is needed.
A remote peer is addressed using a Uniform Resource Locator, URL. These locators are strings representing the
nodes on internet or on a local net. This is the same addressing technology used in case of a web browser. For
more information about URLs, check out http://www.rfc-base.org/txt/rfc-1738.txt.
In general, URLs are written as follows:
<scheme>:<scheme-specific-part>
Where <scheme> is the scheme or protocol used when communicating and <scheme-specific-part> is normally
the address and port number of the remote node. For example, a web server on the internet can have the
following address:
http://www.u-blox.com/
This tells the browser to use the HTTP protocol and connect to the node at address http://www.u-blox.com/. A
similar addressing scheme is used by NINA-B1 to pinpoint the remote peer. The scheme is not "http", but the
node addressing is identical.
Available schemes:
•
sps: Bluetooth low energy u-blox Serial Port Service
Syntax:
•
sps: <scheme>://bluetooth_address/
Example
•
sps://0012f3000001
A peer can be set up using either the default remote peer command AT+UDDRP or dynamically created using
the connect peer command AT+UDCP. A connection is closed using AT+UDCPC.
The Bluetooth low energy SPS service is enabled by default in NINA-B1 and it accepts incoming
connections by default.
UBX-16009942 - R04
NINA-B1 series - Getting Started
Configuration
Page 6 of 19