Ublox NINA-B1 Series User manual

NINA-B1 series
Stand-alone Bluetooth low energy
modules
Getting Started
Abstract
This document describes how to set up and use the NINA-
B1
series Bluetooth low energy module with the u-
blox connectivity
software. It also provides a technical overview of the NINA-
B1
series.
www.u
-blox.com
UBX
-16009942 - R04

NINA-B1 series - Getting Started
UBX-16009942 - R04 Page 2 of 19
Document Information
Title NINA-B1 series
Subtitle Stand-alone Bluetooth low energy modules
Document type Getting Started
Document number UBX-16009942
Revision, date R04 10-Feb 2017
Disclosure restriction
This document applies to the following products:
Product name Type number u-blox connectivity software version PCN reference
NINA-B111 NINA-B111-00B-00
NINA-B111-01B-00
1.0.0
2.0.0
N/A
NINA-B112 NINA-B112-00B-00
NINA-B112-01B-00
1.0.0
2.0.0
N/A
u-blox reserves all rights to this document and the information contained herein. Products, names, logos and designs described herein may in
whole or in part be subject to intellectual property rights. Reproduction, use, modification or disclosure to third parties of this document or
any part thereof without the express permission of u-blox is strictly prohibited.
The information contained herein is provided “as is” and u-blox assumes no liability for the use of the information. No warranty, either
express or implied, is given, including but not limited, with respect to the accuracy, correctness, reliability and fitness for a particular purpose
of the information. This document may be revised by u-blox at any time. For most recent documents, visit www.u-blox.com.
Copyright © 2017, u-blox AG.
u-blox®is a registered trademark of u-blox Holding AG in the EU and other countries.
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
PCI, PCI Express, PCIe, and PCI-SIG are trademarks or registered trademarks of PCI-SIG. All other registered trademarks or trademarks
mentioned in this document are property of their respective owners.

NINA-B1 series - Getting Started
UBX-16009942 - R04 Contents
Page 3 of 19
Contents
Contents..............................................................................................................................3
1Introduction..................................................................................................................4
1.1 Key features ......................................................................................................................................... 4
1.2 Modes of operation.............................................................................................................................. 4
1.3 u-blox Low Energy Serial Port Service (SPS) ........................................................................................... 4
2Configuration ...............................................................................................................6
2.1 Basic settings ........................................................................................................................................ 6
2.2 Peers .................................................................................................................................................... 6
2.3 Client and server................................................................................................................................... 7
2.4 Bluetooth services................................................................................................................................. 7
2.5 Command mode, Data mode, and Extended data mode ...................................................................... 7
2.6 Multipoint ............................................................................................................................................ 9
2.7 Bluetooth security............................................................................................................................... 10
2.8 Low power modes .............................................................................................................................. 10
3Evaluation board........................................................................................................11
3.1 LED indications and buttons ............................................................................................................... 11
3.2 Restore default serial settings ............................................................................................................. 11
3.3 Restore factory settings ...................................................................................................................... 12
3.4 Enter the bootloader........................................................................................................................... 12
3.5 Flashing the module ........................................................................................................................... 12
4Use case examples......................................................................................................13
4.1 Connect two NINA-B1 using Bluetooth low energy............................................................................. 13
4.2 Set up GATT Server / Client on NINA-B1 ............................................................................................. 13
4.3 Setup iBeacon on NINA-B1 ................................................................................................................. 14
4.4 Setup Eddystone on NINA-B1 ............................................................................................................. 15
4.5 Change the NINA-B1 name ................................................................................................................ 15
4.6 Configure NINA-B1 over air ................................................................................................................ 15
Appendix ..........................................................................................................................17
AList of acronyms .........................................................................................................17
Related documents...........................................................................................................18
Revision history................................................................................................................18
Contact..............................................................................................................................19

NINA-B1 series - Getting Started
UBX-16009942 - R04 Introduction
Page 4 of 19
1Introduction
The NINA-B1 series is a highly integrated low energy module developed by u-blox for integration in demanding,
reliable devices, such as those needed for industrial and medical applications. The module is built around a
Bluetooth low energy chip. This document describes how to set up and use the modules.
1.1 Key features
One of the key features of the NINA-B1 series is the Wireless serial cable replacement functionality. The basic
functionality is to transfer data between the serial port and a wireless link. It is possible to configure the NINA-B1
series module to automatically setup a connection and/or accept an incoming connection using AT commands.
For a host, this means that an existing serial cable can be replaced by a wireless solution; in many cases without
the need to modify the host.
Figure 1: NINA-B1 series Bluetooth setup
1.2 Modes of operation
The NINA-B1 series can operate in the following three different modes:
•Command mode
•Data mode
•Extended Data mode
In command mode, the module is configured using AT commands. For information regarding the available AT
commands, see u-blox Short Range Modules AT Commands Manual [1],
In data mode, the module transmits data transparently between the serial UART and wireless connection(s).
The extended data mode (EDM) allows individual control of each active link. While sending and/or receiving
data, AT commands can simultaneously be sent to the module from the host. For more information about EDM,
see section 2.5 and u-blox Extended Data Mode Protocol Specification [7]).
1.3 u-blox Low Energy Serial Port Service (SPS)
In Bluetooth BR/EDR, there is a Serial Port Profile (SPP) that emulates a serial port over air. For Bluetooth Low
Energy, there is no such profile and thereby no standardized way of transferring generic data over the air.
The u-blox Low Energy Serial Port Service is a non-standard profile developed for the u-blox serial port adapter
concept. The specification is open and may be implemented in any Bluetooth Low Energy device to enable
generic data transmission.

NINA-B1 series - Getting Started
UBX-16009942 - R04 Introduction
Page 5 of 19
The serial port service is implemented on top of the Generic Attribute Profile (GATT). It contains the following
characteristics:
•FIFO for reading and writing data
•Credits to simulate the Bluetooth BR/EDR credit-based flow control
To connect, the central/client side sets up the ACL (Asynchronous Connection-Less) link and enables indications
for both the FIFO and credits characteristics. Then, the server side sends the number of credits to the client using
the credit indication, and the client writes the number of credits to the server. The credits correspond to the
number of packets the remote side may write before receiving new credits. The received credits are added to the
remaining ones (if any).
Once connected and credits have been received, data transmission starts. The client writes to the FIFO and the
server sends indications or notifications with the FIFO data.
Connections without credits are also supported. Connections without credits are faster to establish and ideal for
scenarios where a small amount of data shall be transferred.
For more information see u-blox Low Energy Serial Port Service Protocol Specification [10].

NINA-B1 series - Getting Started
UBX-16009942 - R04 Configuration
Page 6 of 19
2Configuration
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.

NINA-B1 series - Getting Started
UBX-16009942 - R04 Configuration
Page 7 of 19
2.3 Client and server
A client will initiate a connection and the server will accept an incoming connection.
Figure 2: NINA-B1 as a client connecting to the NINA-B1 server
To configure a client to automatically set up a connection to a server, configure the correct Bluetooth service and
the remote peer. The Bluetooth service controls the type of connection that is requested (see section 2.4) and
the preferred server to connect is defined by the remote peer.
•Default Remote Peer AT+UDDRP Configures server (profile and address) to connect and when to
initiate the connection. Peer is enumerated starting with id 0.
•Server Configuration AT+UDSC:Will only accept incoming connection attempts for the configured
server profile. NINA-B1 will have the SPS enabled by default.
2.4 Bluetooth services
The Generic Attributes (GATT) is used when Bluetooth LE devices exchanges data. There are two roles defined in
GATT - the client and server. For more information about GATT, see [8].
The GATT server stores data received from the GATT client. The GATT server sends responses to requests and
sends indications and notifications to the GATT client when specified events occur on the GATT server.
Official as well as user defined GATT Services can be set up with AT commands. The Serial Port Service (SPS) is a
u-blox proprietary serial cable emulation service, which is enabled by default.
2.5 Command mode, Data mode, and Extended data mode
By default, NINA-B1 will enter command mode and has to be reconfigured to start up in data mode or extended
data mode. From the data mode or extended data mode, it is possible to enter the command mode by
transmitting escape sequence to the module. By default, the escape sequence is:
1. Silence 1 second
2. +++
3. Silence 1 second
The +++ must be sent within 200 ms, which means that it is difficult or impossible to enter the
escape sequence manually using a terminal window though the characters can also be typically pasted
instead. The module leaves the command mode and enters data mode using the ATO1/ATO2 command. It
is also possible to toggle the UART DTR pin from High to Low to enter the command mode.

NINA-B1 series - Getting Started
UBX-16009942 - R04 Configuration
Page 8 of 19
Figure 3: Operational modes
In data mode, the data transmitted on the UART to the module will be transmitted (and broadcasted for all
connections), over air, to all wireless connections. Data received from the wireless connections may be
interleaved upon reception and it may be difficult or impossible to figure out from which remote device the data
is received. This "multipoint strategy" is called as Wireless Multidrop. It is suitable mainly for master/slave polled
protocols such as Modbus and point-to-point communication.
Figure 4: Data mode
The extended data mode is a simple protocol for the UART, which enables transmission of data to one specific
remote device and also informs the remote device from where the data is received. It is also possible to execute
AT commands as part of the extended data mode protocol. Hence, it is not necessary to enter the command
mode from the extended data mode.

NINA-B1 series - Getting Started
UBX-16009942 - R04 Configuration
Page 9 of 19
Figure 5: Extended data mode
No extended data mode protocol data is available over the air. Only "raw" data is transmitted in the same
way as in the data mode over air. Hence, it is possible for one side to be configured for extended data
mode and the other side for the standard data mode.
Figure 6: Data mode and extended data mode
2.6 Multipoint
It is possible to configure a module to support up to 8 parallel Bluetooth connections. These connections can be
to 1 central and 7 peripherals in a multirole configuration. The AT+UBTCFG command is used to set the
maximum number of Bluetooth connections.
In data mode, data is transmitted over air to all the connected devices and the data received from remote
devices is interleaved.
Figure 7: Wireless Multidrop
In extended data mode, it is possible to transmit data to a specific remote device and to know from which
remote device data is received (see u-blox Extended Data Mode Protocol Specification [7]).

NINA-B1 series - Getting Started
UBX-16009942 - R04 Configuration
Page 10 of 19
Figure 8: Multidrop in extended data mode
2.7 Bluetooth security
There are five different security modes that support all kinds of use cases regarding the pairing procedure.
All security modes use encryption. The encryption algorithm is a 128-bit cipher called E0.
Security mode 1 and 2 are implemented to keep the same or similar behavior as for previous versions of u-blox
Bluetooth products.
Secure Simple Pairing (SSP) was introduced in Bluetooth 2.1 to improve security and simplify the pairing process.
SSP uses a form of public key cryptography and the just works, numeric comparison, passkey entry and out of
band authentication mechanisms.
•Just works: No user interaction is needed, except that the user may need to confirm the pairing process.
The method is typically used by devices with very limited IO capabilities.
•Numeric comparison: A 6-digit numeric code is displayed on each device where the user compares the
numbers to ensure they are identical.
•Passkey Entry: Either a 6-digit numeric code is displayed on one device that the user enters on the other
device, or the same 6-digit numbers are entered on both devices.
Use the security mode 1 (Bluetooth 2.1 auto accept security) AT+UBTSM=1 to start with. It is highly
recommended to analyze the security and if appropriate, use a more secured solution, for example security
mode 2 (Bluetooth 2.1 Just Works) AT+UBTSM=2.
2.8 Low power modes
The Standby mode is one of the power saving modes in NINA-B1 module that essentially powers down the
module but keeps the system RAM and allows incoming connection to the module. The Sleep mode is the
deepest power saving mode of NINA-B1 modules, but does not allow any connection to wake up the module.
The low power modes in NINA-B1 are set using the AT&D command.
2.8.1 Standby mode
The standby mode in NINA-B1 that is enabled with AT&D3, is used to disable the UART. The radio is still active
and the UART can be activated again either on a logical 0 to logical 1 signal transition on the DTR line, or by an
incoming Bluetooth connection establishment.
For more information about Standby mode, see NINA-B1 series Data Sheet [2].
2.8.2 Sleep mode
The sleep mode in NINA-B1 that is enabled with the command AT&D4, will upon a logical 0 to logical 1 on signal
transition of the DTR line, completely shuts off the module. Upon a logical 1 to logical 0 signal transition on the
DTR line, the module is started again. This is the lowest power mode, and NINA-B1 will not be able to keep or
make any connection in this mode.
For more information about Sleep mode, see the NINA-B1 series Data Sheet [2].

NINA-B1 series - Getting Started
UBX-16009942 - R04 Evaluation board
Page 11 of 19
3Evaluation board
The evaluation board for NINA-B1 is EVK-NINA-B1.
3.1 LED indications and buttons
There are two operational buttons (SW1 and SW2) and one multi LED (DS9), as shown in Figure 9.
Figure 9: EVK-NINA-B1 Evaluation board
The LED indicates what mode is currently active and what activity is currently in progress. The following color
indications are used. See EVK-NINA-B1 User Guide [3] for more information about the EVK-NINA-B1.
•Green: The current mode is data mode and no connection attempts are in progress.
•Orange: The current mode is command mode.
•Purple: A connection attempt is in progress.
•Blue: A connection is currently active.
•Blue Blinking: A connection is active and data is transmitted or received over air.
•Red Blinking: Error detected. Typically, this means buffer overflow, parity or framing error detected on
the UART.
The LED on the evaluation board is a 3-colour LED, which means that, on the module, it
corresponds to three IO pins.
3.2 Restore default serial settings
If the SW2 button is pressed during power on, the module resets the serial settings and escape sequence to the
default values.
•Default serial settings is 115.2 kbps, 8N1 and HW flow control enabled
•Default escape sequence is +++
•Default escape sequence timing is 1s silence before and after the escape sequence

NINA-B1 series - Getting Started
UBX-16009942 - R04 Evaluation board
Page 12 of 19
3.3 Restore factory settings
If both the SW1 and SW2 buttons are pressed for 10 seconds during power up, the factory settings are restored.
You can also restore to the factory settings using the AT+UFACTORY command followed by power off/on.
3.4 Enter the bootloader
To enter the bootloader, press the SW1 and SW2 buttons during a reset; this will start the module in the u-blox
bootloader. You can also enter the bootloader using the AT+UFWUPD command. The bootloader will time out
and resume the application after 10 seconds.
3.5 Flashing the module
The PC tool s-center 3.0.0 or later may be used to flash NINA-B1. Instructions on flashing the NINA-B1 can be
found in the Software section of the NINA-B1 System Integration Manual [11].
Go to the u-blox support webpage to obtain the latest available firmware.

NINA-B1 series - Getting Started
UBX-16009942 - R04 Use case examples
Page 13 of 19
4Use case examples
4.1 Connect two NINA-B1 using Bluetooth low energy
Connect two NINA-B1 modules using Bluetooth low energy Serial Port Service (SPS) that connects automatically.
To set up first NINA-B1 as a Central (Device A)
•Enable Central Role
oAT+UBTLE=1
•Default peer to Serial Port Service and always connected (use the address of Device B)
oAT+UDDRP=0,sps://112233445566,2
•Startup NINA-B1 in data mode
oAT+UMSM=1
•Store configuration
oAT&W
•Restart NINA-B1
oAT+CPWROFF
Set up second NINA-B1 as a Peripheral (Device B)
NINA-B1 has the u-blox Serial Port Service enabled by default:
•Startup in data mode
oAT+UMSM=1
•Store configuration
oAT&W
•Restart
oAT+CPWROFF
4.2 Set up GATT Server / Client on NINA-B1
The following example shows how to set up a GATT Server on one NINA-B1 and receive notifications of updated
values at a GATT Client on a second NINA-B1.
Set up a GATT Server with a pre-defined service on NINA-B1 (Device A)
•Define a Heart Rate service, a list of all available pre-defined services and its characteristics can be found
at [8] and [9]
oAT+UBTGSER=180D
+UBTGSER:30
•Add a Heart Rate measurement characteristic with notification support
oAT+UBTGCHA=2A37,10,1,1
+UBTGCHA:32,33
Use the GATT Client on NINA-B1 (Device B) to receive Heart rate measurement values:
•Enable Central Role
oAT+UBTLE=1
•Store configuration
oAT&W
•Restart
oAT+CPWROFF
•Find the other device
oAT+UBTD=4,1

NINA-B1 series - Getting Started
UBX-16009942 - R04 Use case examples
Page 14 of 19
+UBTD:112233445566p,-59,"NINA-B1 GATT Server",1,1109426C756574...
•Create an ACL connection
oAT+UBTACLC=112233445566
+UUBTACLC:0,0,112233445566p
•Use the connection handle 0from the +UUBTACLC and Discover Services
oAT+UBTGDP=0
+UBTGDP:0,1,9,1800
+UBTGDP:0,10,13,1801
+UBTGDP:0,14,22,180A
+UBTGDP:0,23,29,01D7E9014FF344E7838FE226B9E15624
+UBTGDP:0,30,65535,180D
OK
•After finding the “Heart Rate service” (180 D), use the start handle 30 and end handle 65535 from the
+UBTGDP, and Discover all characteristics of service
oAT+UBTGDCS=0,30,65535
+UBTGDCS:0,31,10,32,2A37
OK
•After finding the “Heart Rate Measurement characteristics” (2A37), use the value handle 32 from the
+UBTGDCS and end handle 65535 from the +UBTGDP, and Discover all characteristic descriptors
oAT+UBTGDCD=0,32,65535
+UBTGDCD:0,32,33,2902
OK
•After finding the “Client Characteristic Configuration descriptor” (2902), use the descriptor handle 33
from the +UBTGDCD, and subscribe to notifications of Heart Rate measurement value changes
oAT+UBTGWC=0,33,1
OK
Update and notify new value of Heart Rate measurement (Device A):
•We can now set a new value (50) and send a notification from Device A (the GATT Server)
oAT+UBTGSN=0,32,50
New value is notified to Device B:
•An event is received when the remote side (Device A) sends a notification
o+UUBTGN:0,32,50
4.3 Setup iBeacon on NINA-B1
Setup NINA-B1 to advertise Apple iBeacon packets:
This is only an example use case. Apple requires iBeacon license agreement if it is used in a product.
iBeacon is a Manufacturer-specific event, and contains an 128 bit UUID such as D9B9EC1F-3925-43D0-80A9-
1E39D4CEA95C. Note that the byte order for the AT command use the reverse byte order. Together with the
Major (2 bytes), Minor (2 bytes) and the Tx power (1 byte), it builds up the iBeacon advertise packet.
Apple recommends the Local Name in the Scan Response packet. See [5] for more information about iBeacon.
•To change advertise packet on NINA-B1 to include iBeacon:
oAT+UBTAD=1AFF4C000215EBEFD08370A247C89837E7B5634DF52400010001C5
•To change Local Name to “Bluetooth Device”:
oAT+UBTSD=1109426C7565746F6F746820446576696365

NINA-B1 series - Getting Started
UBX-16009942 - R04 Use case examples
Page 15 of 19
4.4 Setup Eddystone on NINA-B1
Setup NINA-B1 to advertise Google Eddystone packets:
This example will show how to send an URL inside the advertisement packet; by nature, the
advertisement packet is limited in size and the information is also limited.
The payload contains a short version of an URL, for example https://goo.gl/Aq18zF.The link is encoded to
save space, but most smartphones can use this information to navigate to the advertised URL. See [6] for more
information about Eddystone.
•To change advertise packet on NINA-B1 to include the Eddystone URL:
oAT+UBTAD=0303AAFE0D16AAFE10F801752D626C6F7807
•To change Local Name to “Bluetooth Device”:
oAT+UBTSD=1109426C7565746F6F746820446576696365
4.5 Change the NINA-B1 name
NINA-B1 (Device A) is a Peripheral
•Set Local Name on NINA-B1 to
oAT+UBTLN="u-blox NINA-B1"
NINA-B1 (Device B) as a Central
•Set Central Role on NINA-B1
oAT+UBTLE=1
•Store configuration
oAT&W
•Restart NINA-B1
oAT+CPWROFF
•Make a Device Discover to find Device A
oAT+UBTD
o+UBTD:112233445566p,-70,"u-blox NINA-B1",1,0F09752D626C6F78204E494E412D...
4.6 Configure NINA-B1 over air
Set up NINA-B1 (Device A) that should be configured over air
•Enable remote configuration through the SPS server
oAT+UDSF=0,1
•Enter data mode
oATO1
Set up NINA-B1 (Device B)
•Enable Central Role
oAT+UBTLE=1
•Store configuration
oAT&W
•Restart
oAT+CPWROFF
•Change escape character from default ‘+’ (ASCII 43) to ‘-‘ (ASCII 45) to make the escape sequence pass
through Device A without getting detected as an escape sequence at Device B
oATS2=45
•Find the other device (Device A)
oAT+UBTD=4,1
+UBTD:112233445566p,-59,"NINA-B1 Device A",1,1109426C756574...
•Create an SPS connection to Device A
oAT+UDCP="sps://112233445566”
•Enter data mode
oATO1

NINA-B1 series - Getting Started
UBX-16009942 - R04 Use case examples
Page 16 of 19
•Enter configuration mode by sending escape sequence of Device A. By default, the NINA-B1 escape
sequence is:
1. Silence 1 second
2. +++
3. Silence 1 second
•Device B can now send AT-commands to Device A, for example, reading the local Bluetooth address of
Device A:
oAT+UMLA=1
+UMLA:112233445566

NINA-B1 series - Getting Started
UBX-16009942 - R04 Appendix
Page 17 of 19
Appendix
AList of acronyms
Abbreviation / Term Explanation / Definition
ACL Asynchronous Connection-Less
BR Basic Rate
DSR Data Set Ready
DTR Data Terminal Ready
EDM Extended Data Mode
EDR Enhanced Data Rate
GATT Generic Attributes
HTTP Hypertext Transfer Protocol
LED Light-Emitting Diode
SPS Serial Port Service
URL Uniform Resource Locator

NINA-B1 series - Getting Started
UBX-16009942 - R04 Related documents
Page 18 of 19
Related documents
[1] u-blox Short Range Modules AT Commands Manual, Document No. UBX-14044127
[2] NINA-B1 series Data Sheet, Document No. UBX-15019243
[3] EVK-NINA-B1 User Guide, Document No. UBX-15028120
[4] s-center Product Summary, Document No. UBX-15020022
[5] https://developer.apple.com/ibeacon/
[6] https://developers.google.com/beacons/eddystone
[7] u-blox Extended Data Mode Protocol Specification, Document No. UBX-14044126
[8] https://www.bluetooth.com/specifications/gatt/services
[9] https://www.bluetooth.com/specifications/gatt/characteristics
[10] u-blox Low Energy Serial Port Service Protocol Specification, Document No. UBX-16011192
[11] NINA-B1 System Integration Manual, Document No. UBX-15026175
Revision history
Revision Date Name Comments
R01 17-Jun-2016 cmag, kgom Initial release.
R02 08-Jul-2016 cmag Added Use case for iBeacon (section 4.3) and Eddystone beacons (section 4.4).
R03 09-Sep-2016 cmag Changed the document status to Early Production Information. Added more
information about Low power modes (section 2.8).
R04 10-Feb-2017 apet, kgom Included type numbers for NINA-B1 firmware 2.0.0. Added EDM to Modes of
operation. Added use case for GATT Server / Client and Config over air. Updated
the following sections: u-blox Low Energy Serial Port Service (SPS), Bluetooth
services and Bluetooth security. Replaced Document status with Disclosure
restriction on page 2.

NINA-B1 series - Getting Started
UBX-16009942 - R04 Contact
Page 19 of 19
Contact
For complete contact information visit us at http://www.u-blox.com/.
u-blox Offices
North, Central and South America
u-blox America, Inc.
Phone: [phone]
E-mail: [e-mail]
Regional Office West Coast:
Phone: [phone]
E-mail: [e-mail]
Technical Support:
Phone: [phone]
E-mail: [e-mail]
Headquarters
Europe, Middle East, Africa
u-blox AG
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Asia, Australia, Pacific
u-blox Singapore Pte. Ltd.
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office Australia:
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office China (Beijing):
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office China (Chongqing):
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office China (Shanghai):
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office China (Shenzhen):
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office India:
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office Japan (Osaka):
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office Japan (Tokyo):
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office Korea:
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]
Regional Office Taiwan:
Phone: [phone]
E-mail: [e-mail]
Support: [e-mail]