This release note describes the u-connectXpress v3.0.0 for NINA-B31 series.
1.2 Supported hardware
Ordering codes for the modules upgradeable to u-connectXpress v3.0.0
Product name Ordering code Type number Software version
NINA-B311 NINA-B311-00B NINA-B311-00B-00 V1.0.0
NINA-B312 NINA-B312-00B NINA-B312-00B-00 V1.0.0
NINA-B311 NINA-B311-01B NINA-B311-01B-00 V2.0.0
NINA-B312 NINA-B312-01B NINA-B312-01B-00 V2.0.0
NINA-B316 NINA-B316-01B NINA-B316-01B-00 V2.0.0
UBX- 20031086 u-connectXpress v3.0.0 for NINA-B31 series 1/4
C1-Public
It is possible to update all NINA-B3 series modules to u-connectXpress v3.0.0. See the
NINA-B3 System Integration manual [5] for information about the software update procedure.
NOTE: Updating to v3.0.0 will restore settings to default configuration.
The software package is available for download from NINA-B31 u-connectXpress software.
1.4 Updated documentation
[1] NINA-B3 data sheet, UBX-17052099
[2] u-connectXpress AT commands manual, UBX-14044127
[3] u-connectXpress user guide, UBX-16024251
1.5 References
[4] Implementing Bluetooth mesh with u-connectXpress software, UBX-19025268
[5] NINA-B3 system integration manual, UBX-17056748
1.6 Released software tools
The s-center version 5.0.0 or later is recommended for evaluation of u-connectXpress v3.0.0.
The s-center application is available for download from s-center evaluation software
.
2 New features
u-connectXpress v3.0.0 for NINA-B3 series has all the features of previous software releases,
plus improvements and new features such as the major ones which are described below. For
more information about using these features, see the u-connectXpress software User Guide [3]
and the u-connectXpress AT commands manual [2].
2.1 Multiple central support
Incoming connections from up to 6 centrals (for example mobile phones) can be accepted and
handled simultaneously in peripheral role and 4 centrals in combined central/peripheral role.
For more information and example of configuration see u-connectXpress User Guide [3].
2.2 Bluetooth Mesh
For more information about detailed support see [5].
Please note, this feature has experimental status and is not yet recommended for production.
2.3 Connection status information
It is now possible to read out all active connections and detailed information about each
connection, such as connection interval, slave latency, supervision timeout, MTU size, PDU
payload length, role, and more. For further details, see the AT command AT+UBTLELIST and
AT+UBTLESTAT.
UBX- 20031086 u-connectXpress v3.0.0 for NINA-B31 series 2/4
C1-Public
2.4 Improved PHY handling
Automatic switching of connections between 1 Mbps/2 Mbps and coded phy. Useful when a
device is non-stationary, that is, moving. A connection will adapt phy according to the existing
radio conditions and prevent transmitted data from stalling.
For further details, see the AT command AT+UBTLCFG and parameters 27, 28. More
information and examples can also be found in the u-connectXpress user guide [3].
2.5 Changeable MAC address
It is now possible to change the factory programmed MAC address to a customer defined one.
For further details, see the AT command AT+UMLA.
2.6 Secondary UART
The AT command AT+UDCP has been extended for opening and configuring a secondary UART
interface. This can be used, for example, to connect a u-blox cellular or positioning module, as
well as to separate AT command communication and data streams.
For more information and examples of configuration, see the u-connectXpress user guide [3].
3 Notes and limitations
3.1 Solved limitations
Description Reference
LE secure connections with security mode 4 incorrectly outputs event +UUBTUPD and
accepts AT+UBTUPE.
☞ Note: Event +UUBTUPD is replaced with +UUBTUC. Where both AT+UBTUPE and
AT+UBTUC can be used for acceptance. For more information and a configuration
example, see the u-connectXpress user guide [3].
Incoming connection from remote default peer (+UDDRP) is rejected. On device A, set
device B as default peer, and connect from device B to device A using UDCP or default
peer configuration. The connection is refused.
Wrong frame size reported in the EDM Connect Event. In EDM mode, when a central node
connects to a remote peripheral device, the wrong frame size is reported in the EDM
Connect Event, (0x0011). To get the correct size, use the Resend Connect Events
(0x0056) command.
It is not possible to switch to EDM mode on peripheral after establishing a BLE
connection in AT mode. No data can be transferred.
AT&W and AT+CPWROFF are required even when provisioning using a smartphone.
The mesh stack will assert if it finds unexpected meta data in its region of the flash. This
will result in eternal reboots when the mesh stack is initialized. In these instances, the
only solution is to re-flash the device with u-connectScript Mesh software and execute
AT+UBTMCLR. When the flash has been cleared, the u-connectXpress Mesh Software
can be re-flashed.
Advertising output power for Bluetooth Mesh is fixed at 0 dBm and cannot be adjusted.
The module will reset when trying to provision or configure without a configured mesh
module.
AT+UFACTORY does not clean the flash used by mesh. A separate AT+UBTMCLR is
needed after the factory reset.
UCS_DEV-676
UCS_DEV-208
UCS_DEV-185
UCS_DEV-175
UCS_DEV-496
UCS_DEV-516
UBX- 20031086 u-connectXpress v3.0.0 for NINA-B31 series 3/4
C1-Public
Description Reference
Rapid sending of two GET messages crashes the node. Sending two GET messages in
rapid succession before an answer is received (e.g. AT+UBTMPUB=0,0,8201,00) crashes
the node.
When using security mode 3 “display only” (AT+UBTSM=3) and the device trying to bond
enters the wrong pin code, then the man-in-the-middle (MITM) protection not guaranteed
status code, instead of authentication/pairing failed status code, is received.
When connected to a module over EDM and a remote peer disconnects, normally an EDM
disconnect event is received. However, if the module has a default remote peer and starts
in EDM mode, then we do not get any disconnect event.
When a GATT server has more than one client and gets a write long event, the connection
handle is 0 even though it should be different.
Connection event not received when UART enabled after being disabled. UCS_DEV-849
User passkey entry +UBTUPE, entering 1234 (pairing will succeed) should be equivalent
to 001234 (pairing will fail).
+UUBTUPD does not always show 6 digits UCS_DEV-814
Error received when checking RSSI value on an incoming connection from a mobile phone. UCS_DEV-581
UCS_DEV-456
UCS_DEV-1073
UCS_DEV-1057
UCS_DEV-952
UCS_DEV-815
3.2 Known limitations
Description Reference
Possible SPS data loss when L2CAP fragments are small (3 bytes) UCS_DEV-909
UBX- 20031086 u-connectXpress v3.0.0 for NINA-B31 series 4/4
C1-Public
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.