Abstract Advance website ( is a rich pool of information. Product information, technical documents...

u-blox

Copyright © 2015 u-blox AG of 49

ODIN-W2 00B AT COMMANDS MANUAL

Abstract

Description of standard and proprietary AT commands used with u-blox short rangemodules.

22.3 x 14.8 x 3.3 mm

Advance

Info

rmat

ion

u-blox


Document Information

Title ODIN-W2 series

Subtitle Short range stand alone modules

Document type AT Commands Manual

Document number UBX-14044127

Revision and date R08, 20-Sep-2015

Document status Advance Information

Document statusexplanation

Objective Specification Document contains target values. Revised and supplementary data will be published later.

Advance Information Document contains data based on early testing. Revised and supplementary data will be publishedlater.

Early Production Information Document contains data from product verification. Revised and supplementary data may be publishedlater.

Production Information Document contains the final product specification.

This document applies to the following products:

Name Type number Firmware version PCN / IN

ODIN-W260 ODIN-W260-00B 1.0.0-beta.4 UBX-15022446

ODIN-W262 ODIN-W262-00B 1.0.0-beta.4 UBX-15022446

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 besubject to intellectual property rights. Reproduction, use, modification or disclosure to third parties of this document or any part thereof without the express permission ofu-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 byu-blox at any time. For most recent documents, visit .www.u-blox.com

Copyright © 2015, u-blox AG.

u-blox® is a registered trademark of u-blox Holding AG in the EU and other countries.

Advance

Info

rmat

ion

http://www.u-blox.com/

u-blox


1 Contents

1 Contents2 Preface

2.1 u-blox technical documentation2.2 How to use this manual2.3 Questions2.4 Technical support

3 AT command settings3.1 Definitions

4 General operation4.1 Start up4.2 AT-Command types4.3 Data Types

5 General5.1 AT Attention Command5.2 Manufacturer identification +CGMI5.3 Model identification +CGMM5.4 Firmware version identification +CGMR5.5 Serial number +CGSN5.6 Manufacturer identification +GMI5.7 Model identification +GMM5.8 Firmware version identification +GMR5.9 Serial number +GSN5.10 Identification information I5.11 Set greeting text +CSGT

6 System6.1 Store current configuration &W6.2 Set to default configuration Z6.3 Set to factory defined configuration +UFACTORY6.4 Circuit 108/2 (DTR) behavior &D6.5 DSR Overide &S6.6 ATE Echo On/Off6.7 Escape Character S26.8 Command Line Termination Character S36.9 Response Formatting Character S46.10 Backspace Character S56.11 Firmware update Over AT command (FOAT) +UFWUPD6.12 Module switch off +CPWROFF6.13 Module Start Mode +UMSM6.14 Local Address +UMLA6.15 System Status +UMSTAT6.16 RS232 Settings +UMRS

7 Data Mode Commands7.1 Enter Data Mode O7.2 Connect Peer +UDCP7.3 Close Peer Connection +UDCPC7.4 Default Remote Peer +UDDRP7.5 Server Configuration +UDSC7.6 Watchdog Settings +UDWS7.7 Configuration +UDCFG7.8 Unsolicited response codes

8 Bluetooth Commands8.1 Discoverability Mode +UBTDM8.2 Connectability Mode +UBTCM8.3 Pairing Mode +UBTPM8.4 Security Mode +UBTSM8.5 User Confirmation +UBTUC8.6 User Passkey Entry +UBTUPE8.7 Name Discovery +UBTND8.8 Inquiry (Classic) +UBTI8.9 Discovery (Low Energy) +UBTD8.10 Bond +UBTB8.11 Un-bond +UBTUB8.12 Read Bonded Devices +UBTBD8.13 Local Name +UBTLN8.14 Local COD +UBTLC8.15 Master Slave Role +UBTMSR8.16 Master Slave Role Policy +UBTMSP8.17 Get RSSI +UBTRSS

Advance

Info

rmat

ion

u-blox


8.18 Get Link Quality +UBTLQ8.19 Bluetooth Low Energy Role +UBTLE8.20 Low Energy Advertise Data +UBTAD8.21 Low Energy Scan Response Data +UBTSD8.22 Service Search +UBTSS8.23 Watchdog Settings +UBTWS8.24 Bluetooth Configuration +UBTCFG8.25 Bluetooth Low Energy Configuration +UBTLECFG8.26 Unsolicited Result Codes

9 Wi-Fi9.1 Wi-Fi Station Configuration +UWSC9.2 Wi-Fi Station Configuration Action +UWSCA9.3 Wi-Fi Active Station Configuration List +UWASCL9.4 Scan +UWSCAN9.5 Channel List +UWCL9.6 Wi-Fi Watchdog Settings +UWWS9.7 Wi-Fi Station Status +UWSSTAT9.8 Unsolicited response codes

10 Network10.1 Network Host Name +UNHN10.2 Network Status +UNSTAT10.3 Unsolicitated Result Codes

11 Related documents12 Revision History13 Contact

13.1 u-blox Offices

Advance

Info

rmat

ion

u-blox


2 Preface

2.1 u-blox technical documentation

As part of our commitment to customer support, u-blox maintains an extensive volume of technical documentation for our products. Inaddition to our product-specific technical data sheets, the following manuals are available to assist u-blox customers in product design anddevelopment.

AT Commands Manual: This document provides the description of the AT commands supported by the u-blox short rangemodules.System Integration Manual: This document provides the description of u-blox short ramge modules system from the hardwareand the software point of view, it provides hardware design guidelines for the optimal integration of the short range modules in theapplication device and it provides information on how to set up production and final product tests on application devices integratingthe short range modules.Application Note: These documents provide guidelines and information on specific hardware and/or software topics on u-bloxshort range modules. See for a list of Application Notes related to your short range Module.Related documents

2.2 How to use this manualThe ODIN-W2 AT Commands Manual provides the necessary information to successfully design and configure the u-blox short rangemodules.

This manual has a modular structure. It is not necessary to read it from the beginning to the end.

The following symbols are used to highlight important information within the manual:

2.3 QuestionsIf you have any questions about u-blox short range Integration:

Read this manual carefully.Contact our information service on the homepage http://www.u-blox.com/

2.4 Technical support

2.4.1 Worldwide Web

Our website ( ) is a rich pool of information. Product information, technical documents can be accessed 24h a day.http://www.u-blox.com/

2.4.2 By E-mail

Contact the closest Technical Support office by email. Use our service pool email addresses rather than any personal email address of ourstaff. This makes sure that your request is processed as soon as possible. You will find the contact details at the end of the document.

2.4.3 Helpful information when contacting technical support

When contacting Technical Support, have the following information ready:

Module type (e.g. ODIN-W260) and firmware version.Module configuration, the configuration can be read using s-center, the u-blox Short Range Radio Toolbox.Clear description of your question or the problem.A short description of the application.Your complete contact details.

An info box points out key information pertaining to module integration and performance.

A warning box indicates actions that could negatively impact or damage the module.

Advance

Info

rmat

ion



u-blox


3 AT command settingsu-blox short range modules provide at least one physical serial interface for configuration and data transport. At the module power on themodule enter the command mode. For more details on command mode see the Chapter 1.1.For module and terminal connection and settings see the corresponding Evaluation Kit User Guide.

3.1 Definitions

In this document the following naming conventions are used:

DCE (Data Communications Equipment): u-blox short range moduleDTE (Data Terminal Equipment) or TE (Terminal Equipment): terminal that issues the command to the module

The terms DCE and DTE are used in the serial interface context.

The DCE interface can operate in these modes:

Command mode: the DCE waits for AT command instructions. The DCE interprets all the characters received as commands toexecute. The DCE may send responses back to the DTE indicating the outcome of the command or further information withouthaving received any commands by the DTE (e.g. unsolicited response code - URC).Data mode: the DCE transfers data after having sent the ATO command; all the characters sent to the DCE are intended to betransmitted to the remote party. Any further characters received over the serial link are deemed to be from the remote party, andany characters sent are transmitted to the remote party.Extended data mode: Binary mode, see the "ODIN-W2 Extended Data Mode Specification" document

It is possible to switch from data mode to command mode in the following ways:

with the escape sequence: for more details see Escape Character S2via a DTR ON to OFF transition: for more details see Circuit 108/2 (DTR) behavior &D

To switch back to data mode or Extended data mode from command mode the command is used. Note that the moduleEnter Data Mode Ostartup mode is set using the command.Module Start Mode +UMSM

3.1.1 Command description

The AT commands configure and enable the short range module functionality according to 3GPP normative and u-blox specifications. TheAT commands are issued to the module via a hyper terminal through a command line and are described in the following sections. A generaldescription of each command is provided including the functionalities, the correct syntax to be provided by the TE/DTE, the allowedresponses and an example.The command description defines each named parameter with its type, its range (valid / acceptable values), the default value (whenavailable) and the factory default setting (when applicable).

3.1.2 Command line

The AT commands are typically issued to the modules using a command line with the following generic syntax:"AT"<command_name><string><S3_character>Where:

"AT": prefix to be set at the beginning of each command line<command_name>: command name string; it can have a "+" character as prefix<string>: string consisting of the value parameters following the syntax provided in this manualThe following rules are used when describing the command syntax:

<...>: the name in angle brackets is a parameter. The brackets themselves do not appear in the command line[...]: the square brackets represent the optional parameters of a command or an optional part of the DCE information textresponse. Brackets themselves do not appear in the command line. When a parameter is not given, the value will be set tothe default value provided in the command description

<S3_character>: command line termination character; it can be set with ATS3 command; the factory default termination characteris <CR>

The serial interface driver does not allow a new command until the previous one has been terminated by "OK" or by an error message.

In this document <CR><LF> are intentionally omitted int the command syntax, see and Command line Information text responses for more details.and result codes

The command line is not case sensitive.

Advance

Info

rmat

ion

u-blox


3.1.3 Default values

If the command has optional parameters, and the default values are not otherwise specified, the default values are assumed as follows:• For parameters of type Number, the default value is 0• For parameters of type String, the default value is an empty string

3.1.4 Information text responses and result codes

The response format is as follows:

Information text responses: <S3_character><S4_character><text><S3_character><S4_character>Result codes: <S3_character><S4_character><verbose code><S3_character><S4_character>

where

<S3_character> is the command line termination character; it can be set with S3 command<S4_character> is the linefeed character; it can be set with S4 command

If the command line is successfully processed and the commands correctly executed, in verbose response format the string "OK" is sent asfinal result code.

Intermediate outputs as well as descriptive outputs of a command are formatted as information text responses;if more than one string has to be printed out (see for example command description), additional command line terminationScan +UWSCANand linefeed characters may be inserted for sake of readability.

If the command is not accepted by the DCE an error result code will be displayed. The error result has the format:

<S3_character><S4_character>ERROR<S3_character><S4_character>

3.1.5 S-parameters

The S-parameters, as specified in ITU-T recommendation V250, constitute a group of commands that begin with the string "ATS". They aregenerally indicated as S registers and are used to configure the way the module operates. Their syntax is:ATS<parameter_number>?ATS<parameter_number>=<value>The number following the "ATS" is the referenced S parameter.u-blox short range modules support the following set of S-parameters (<parameter_number>):

2: escape character setting (for more details see the )S23: command line termination character setting (for more details see the )S34: response formatting character setting (for more details see the )S45: command line editing character setting (for more details see the )S5

Advance

Info

rmat

ion

u-blox


4 General operation

4.1 Start up

Start up mode can be set with the command.+UMSM

4.2 AT-Command types

4.2.1 Set command

A set command configures the preferred settings for the specified command. The set command is the only way to set the preferred settingsin the DCE. Parameters set with a set command will be used immediately and the parameters can be stored to the start up database using

.&W

4.2.2 Read command

A read command provides the current setting of the command parameters. It is used to find out the current command configuration.

4.2.3 Status command

A status command provides current operating status of the module.

4.2.4 Action command

An action command forces the DCE to print information text or execute a specific action for the command.

4.2.5 Configuration Action command

Some configuration commands require that the configuration is reset, stored, activated or deactivated using a corresponding configurationaction command. For ODIN-W2 00B this only applies to the Wi-Fi Station Configuration command.

4.2.6 Unsolicited Result Code (URC)

An unsolicited result code is a string message (provided by the DCE) that is not triggered as a information text response to a previous ATcommand and can be output, when enabled, at any time to inform the DTE of a specific event or status change. The URC can have thesame name of the command that enables it or can be enabled by another command.

4.3 Data Types

The definition of each command specifies the data types used for values associated with the command. There are four different data types:

StringIntegerByte_ArrayIPv4_AddrMAC_AddrBd_AddrList

These are described below:

4.3.1 String

A string shall consist of a sequence of displayable characters from the ISO 8859-1 (8-bit ASCII) character set, except for characters "\", """and characters below 32 (space). A string constant shall be delimited by two double-quote (""") characters, e.g. "Donald Duck". If thedouble-quote character (""") is to be used within a string, e.g. "My friend "Bono" is a singer", they have to be represented as "\22". If theback-slash character ("\") is to be used within a string constant, it has to be represented as "\5C". An empty string is represented by twoadjacent delimiters, "".

4.3.2 Integer

An integer value consists of a sequence of characters all in the range {0..9} plus a possible minus ('-') sign for negative values. Numericconstants are expressed in decimal format only.

Some set commands requires a reboot before it's used. Store with and reset with .&W +CPWROFF

Advance

Info

rmat

ion

u-blox


4.3.3 Enumerator

An enumerator value is actually an integer, where all its possible values are specified in each case. Only the defined values are acceptedfor the command in question.

4.3.4 Byte_Array

A Byte_Array consists of a sequence of characters expressed in two digit hexadecimal in the ranges {0..9}, {a..f} and {A..F}. Thehexadecimal values are grouped together without delimiters, an example of Byte_Array (three values) is "800000" (Bit 23 is set), excludingthe double quote characters.

4.3.5 IPv4_Addr

An IPv4_Addr is a special text string in dotted decimal notation form (i.e. four numbers in range 0-255 separated by periods). An example IPaddress is "192.168.0.1", excluding the double-quote characters.

4.3.6 IPv6_Addr

An IPv6_Addr is a special text string represented as eight groups of four hexadecimal digits, each group representing 16 bits (two octets).The groups are separated by colons (:). An example of an IPv6 address is "2001:0db8:85a3:0000:0000:8a2e:0370:7334", excluding thedouble-quote characters.

4.3.7 MAC_Addr

A MAC_Addr is a Byte_Array of fixed length (6 values). An example MAC_Addr is "01A0F7101C08", excluding the double-quotecharacters.

4.3.8 Bd_Addr

A Bd_Addr is a MAC_Addr followed an optional address type, 'r' for random address and 'p' for public address. If the address type isomitted it will default to public. An example Bd_Addr is "01A0F7101C08p", excluding the double-quote characters.

4.3.9 List

A List is a comma (,) separated list of items, where items can be any of the other data types. Example: channel list is a list of integers,"1,6,11", excluding the double-quote characters.

5 General

5.1 AT Attention Command

Syntax Description

AT Attention command determining the presence of a DCE, i.e. the serial port adapter.

Responses Description

OK Successful response

ERROR Error response

5.2 Manufacturer identification +CGMI

AT Command Description

AT+CGMI Text string identifying the manufacturer.


<manufacturer>

OK

Successful read response.

Parameters Type Value

manufacturer string u-blox

Advance

Info

rmat

ion

u-blox


5.3 Model identification +CGMM


AT+CGMM Text string identifying the model identification.


<model>

OK


Parameters Type

model string

5.4 Firmware version identification +CGMR


AT+CGMR Returns a text string identifying the firmware version of the module.


<version>

OK


Parameters Type

version string

5.5 Serial number +CGSN


AT+CGSN Returns the product serial number (MCU UID).


<serial_number>

OK


Parameters Type

serial_number string

5.6 Manufacturer identification +GMI


AT+GMI Text string identifying the manufacturer.


< >manufacturer

OK



manufacturer string u-blox

Advance

Info

rmat

ion

u-blox


5.7 Model identification +GMM


AT+GMM Text string identifying the model identification.


<model>

OK


Parameters Type

model string

5.8 Firmware version identification +GMR


AT+GMR Returns a text string identifying the firmware version of the module.


<version>

OK


Parameters Type

version string

5.9 Serial number +GSN


AT+GSN Returns a text string with the module serial number.


<serial_number>

OK


Parameters Type

serial_number string

5.10 Identification information I


ATI<value> Reads the identification information

Parameters Type Description

value Enumerator 9: Complete firmware version information


<ApplicationVersion>,<UniqueIdentifier>

OK


Parameters Type

Advance

Info

rmat

ion

u-blox


ApplicationVersion string

UniqueIdentifier string

5.11 Set greeting text +CSGT


AT+CSGT=<mode>[,<text>] Set the greeting text

Configures and activates/deactivates the greeting text. The greeting text configuration's change will beapplied at the subsequent boot. If active, the greeting text is shown at boot once, on any AT interface, ifthe module start up mode is set to command mode.

AT+CSGT? Read the greeting text


mode Enumerator 0: turn off the greeting text 1 (factory default): turn on the greeting text

text String factory default: "+STARTUP"

Max string length is 49


+CSGT:<mode>,<text>

OK


OK Successful write response.

Setting is stored to start up database with &W command.

Advance

Info

rmat

ion

u-blox


6 System

6.1 Store current configuration &W


AT&W[<value>] Commits all settings to be stored in start up database. The parameters are written to non volatile memory when +CP is issued.WROFF


value Enumerator 0: Only valid value


OK Successful response.

6.2 Set to default configuration Z

ATCommand

Description

ATZ[<value>] Resets all settings to the last stored configuration. All settings committed with the AT&W will be cleared. The applicationwill use the restored values after a reboot.


value Enumerator 0: Only valid value



6.3 Set to factory defined configuration +UFACTORY


AT+UFACTORY Reset to factory defined defaults. A reboot is required before the new settings will be used.



6.4 Circuit 108/2 (DTR) behavior &D


AT&D[<value>] Controls the behavior of RS232 circuit 108/2 - Data Terminal Ready (DTR) - relates to changes from ON toOFF condition during on-line data state.

Note: The DTR line is connected to the DSR pin on the module!


value Enumerator 0: DTR line is ignored1 (default and factory default value): upon an ON-to-OFF transition of circuit 108/2, the DCE enterscommand mode and issues and OK result code.2: upon an ON-to-OFF transition of circuit 108/2, the DCE performs an orderly disconnect of all radio linksand peer connections. No new connections will be established while circuit 108/2 remains OFF.


Advance

Info

rmat

ion

u-blox




6.5 DSR Overide &S


AT&S[<value>] Selects how the module will control RS232 circuit 107 - Data Set Ready (DSR).

Note: The DSR line is connected to the DTR pin on the module!


value Enumerator 0: sets DSR line to ON1 (default value and factory default value): sets the DSR line to OFF in command mode and ON when notin command mode.2: sets the DSR line to ON in data mode when at least one remote peer is connected, all other cases it'sset to off.




6.6 ATE Echo On/Off

Syntax Description

ATE[<echo_on>] This command configures whether or not the unit echoes characters received from the DTE when in CommandMode. If <echo_on> is omitted, it turns off echoing.

ATE? Read current echo setting.


echo_on integer 0: Unit does not echo characters during command mode.1 (factory default): Unit echoes characters during command mode.


echo_on

OK

Successful read response




6.7 Escape Character S2

Syntax Description

ATS2=<esc_char> Configure the escape character used to switch the unit from data mode to Command Mode.

ATS2? Read escape character


esc_char integer 0...255 (Note: The escape sequence will be the value repeated three times. I.e. "+++".)

Factory default: 43, i.e the '+' character


Advance

Info

rmat

ion

u-blox


esc_char

OK





6.8 Command Line Termination Character S3

Syntax Description

ATS3=<line_term> Write command line termination character.

This setting changes the decimal value of the character recognized by the DCE from the DTE to terminate anincoming command line. It is also generated by the DCE as part of the header, trailer, and terminator for resultcodes and information text along with the S4 parameter.

The previous value of S3 is used to determine the command line termination character for entry of the commandline containing the S3 setting command. However, the result code issued shall use the value of S3 as set duringthe processing of the command line. For example, if S3 was previously set to 13 and the command line"ATS3=30" is issued, the command line shall be terminated with a CR, character (13), but the result code issuedwill use the character with the ordinal value 30 in place of the CR.

ATS3? Read command line termination character.


line_term integer 0...127

Factory default: 13, i.e. <CR>


line_term

OK





6.9 Response Formatting Character S4

Syntax Description

ATS4=<term> Write response formatting character.

This setting changes the decimal value of the character generated by the DCE as part of the header, trailer, andterminator for result codes and information text, along with the S3 parameter.

If the value of S4 is changed in a command line, the result code issued in response to that command line will use thenew value of S4.

ATS4? Read response formatting character.


term integer 0...127

Factory default: 10, i.e <LF>


term

OK



Advance

Info

rmat

ion

u-blox




6.10 Backspace Character S5

Syntax Description

ATS5=<backspace> Write backspace character.

This setting changes the decimal value of the character recognized by the DCE as a request to delete from thecommand line the immediately preceding character.

ATS5? Read backspace character.


backspace integer 0...127

Factory default: 8


<backspace>

OK





6.11 Firmware update Over AT command (FOAT) +UFWUPD


AT+UFWUPD=<filetype>[,<baud_rate>] Force start of boot loader. The boot loader will start and be ready for an X-modem transfer atthe defined baud rate.


CCC...

OK

UFWUPD REBOOT

Successful write response.


filetype string Download type

0: firmware image update

baud_rate integer Baud rate in b/s

115200 (default)230400460800

6.12 Module switch off +CPWROFF


AT+CPWROFF Reboot the DCE. During shut-down, settings marked for storing to start up database by are written in module's&Wnon-volatile memory.


OK Successful read response.

Advance

Info

rmat

ion

u-blox


6.13 Module Start Mode +UMSM


AT+UMSM=<start_mode> Write start mode

AT+UMSM? Read start mode


start_mode Enumerator 0 (factory default): Command Mode1: Data Mode2: Extended Data Mode



+UMSM:<start_mode>

OK



6.14 Local Address +UMLA

Syntax Description

AT+UMLA=<interface_id> Read the local address of the interface id


interface_id integer 1: Bluetooth2: Wi-Fi3: Ethernet

address MAC_Addr Factory default of interface specific MAC address


+UMLA:<interface_id>,<address>

OK



6.15 System Status +UMSTAT


AT+UMSTAT Read current status of the system


+UMSTAT:<status_id>,<status_val> This is sent for every applicable status.


ERROR Error message.


status_id integer 0: <status_val> is the uptime in seconds, i.e seconds since last reboot1: <status_val> is the current status of the settings

0: Not saved, i.e there exists changes since the last store command1: Saved

Advance

Info

rmat

ion

u-blox


6.16 RS232 Settings +UMRS


AT+UMRS? This command reads current RS232 settings from the Serial Port Adapter.

AT+UMRS[=<baud_rate>[, <>[, <data_bits>[,flow_control

<stop_bits>[, <parity>[,<change_after_confirm>]]]]]]

This command applies new RS232 settings to the Serial Port Adapter. If 5, 6 or 7 data bits are selectedthe Serial Port Adapter will not change its RS232 settings until the next power cycle. If the command issuccessful, the baud rate is changed after the response. Wait 40ms from that the response is receivedbefore sending a new command to the Serial Port Adapter.


+UMRS:<baud_rate>, <data_bits>, <stop_bits>, <parity><flow_control>,

OK


OK Successful write response



baud_rate integer Recommended baud rates: 2400, 4800, 9600, 19200, 38400, 57600, 115200, 230400, 460800,921600, 1360000, 2625000, 3000000.Factory defaultvalue: 115200

flow_control enumerator 1 : CTS/RTS used for flow control(factory default)2: CTS/RTS not used.

data_bits integer Factory-programmed value: 8

stop_bits enumerator 1 (factory default): 1 stop bit2: 2 stop bits

parity enumerator 1 : no parity(factory default)2: odd parity 3: even parity

change_after_confirm enumerator 0: Do not change, it must be stored and reset before the new setting is applied1 (default): Change after OK. The DTE should wait at least 40 ms before sending a newcommand.


Any baud rate between 2400 and 5250000 are accepted by the DCE. Best effort will be used.

For EVB-W2xxU allowed baud rate is 3000000. This is a limitation for the dev. board2625000 can not be used and the highest and not for the ODIN-W2.

After the reception of the OK response for the +UMRS command, the DTE shall wait for at least 40 ms before issuing a new ATcommand; this is to guarantee a proper baudrate reconfiguration.

When operating in extended data mode, the has no direct effect. Settings must be stored in start upchange_after_confirm database and module rebooted before settings are applied.

Only 8 data bits are supportedAdvance

Info

rmat

ion

u-blox


7 Data Mode Commands

7.1 Enter Data Mode O


ATO[<mode>] Request the Serial Port Adapter to move to new mode.



ERROR Error response.


mode Enumerator 0: Command Mode1: Data Mode (default) 2: Extended Data Mode.

7.2 Connect Peer +UDCP


AT+UDCP=<url> Connect to an enabled service on a remote device.When the host connects to a service on a remote device it implicitly registers to receive the "Connection Closed"event.


+UDCP:<peer_handle>

OK

Successful response.



Note that the module startup mode is set using the command Module Start Mode +UMSM

Advance

Info

rmat

ion

u-blox


url string URL to the service on the remote peer. <scheme>://<domain>[:<port>]/[?<query_string>]

supported schemes:

spp:

<domain> specifies Bluetooth address of the remote device, port specifies RFCOMM channel<query_string> can define "bt_name", "uuid"

sps:

<domain> specifies Bluetooth address of the remote device, port is ignored.

tcp:

<domain> specifies either IPv4 or IPv6 address or domain name.<query_string> can define "local_port"

udp:

<domain> specifies either IPv4 or IPv6 address or domain name.<query_string> can define "local_port"

The following are examples of different URLs

spp:

" "spp://0012f3000001p/" "spp://0012f3000001:31/

"spp://0012f3000001p/?uuid=fa87c0d0afac11de8a390800200c9a66"

sps:" "sps://0012f3000001/

gatt:" " gatt://0012f3000001/

tcp:" "tcp://192.168.0.1:8080/"tcp://[FE80:0000:0000:0000:0202:B3FF:FE1E:8329]:8080" <local_port>"tcp://example.org:2000/?local_port=

udp:" "udp://192.168.0.1:8080/"udp://[FE80:0000:0000:0000:0202:B3FF:FE1E:8329]:8080" <local_port>"udp://example.org:2000/?local_port=

peer_handle integer The peer handle identifies the connection and is used when closing the connection.

7.3 Close Peer Connection +UDCPC


AT+UDCPC=<peer_handle> Close an existing peer connection.





peer_handle integer The peer handle identifies the connection.

7.4 Default Remote Peer +UDDRP

The default remote peer command works for classic Bluetooth, Bluetooth Low Energy (SPS), TCP and UDP. The DCE will connect to adefault remote peer either when entering Data mode or Extended data mode (either by command or at startup if defined by the Module

command).Start Mode +UMSM


The command is not supported for the Client-Peripheral and Server-Peripheral Bluetooth Low Energy configurations

Advance

Info

rmat

ion

spp://0012f3000001p/

spp://0012f3000001:31/

spp://0012f3000001:31/

sps://0012f3000001/

gatt://0012f3000001/

tcp://192.168.0.1:8080/

tcp://example.org:2000/?local_port=

udp://192.168.0.1:8080/

udp://example.org:2000/?local_port=

u-blox


AT+UDDRP[=<peer_id>] This command reads the default remote peer (peer id).

AT+UDDRP=<peer_id>,<url>, <connect_scheme> This command writes the default remote peer (peer id).


+UDDRP:<peer_id>,<url>,<connect_scheme>

OK





peer_id integer The peer ID can be 0 - 6.

url string URL to the service on the remote peer. See for more details and examples of validConnect Peer +UDCPURLs.

connect_scheme integer This parameter is a bit field. At least one bit needs to be set. Bit 0 is the least significant bit. Each bit isdefined as follows:

Bit 0: Reserved, do not use.Bit 1: Always connected, always try to be connected to the default remote peer when in data mode.Bit 2: External connect, try to connect to default remote peer on external signal. The external signal isimplementation specific, e.g. some Serial Port Adapters might have a button. Note that the externalsignal/button must not be pressed more than 1 second and the device needs to be in Data mode.

Setting is stored to start up database with command.&W

7.5 Server Configuration +UDSC

Syntax Description

AT+UDSC=<id>,<type>[,<option1>[,<option2>]] Write server configuration

AT+UDSC[=<id>] Read server configuration


id Integer 0 - 6, the server id to configure

type Integer 0: Server disabled1: TCP2: UDP3: SPP4: DUN5: UUID6: SPS

option1 Integer orString

For TCP and UDP <option1> specifies the listening port. Valid values are 1 - 65535.

For SPP, DUN and UUID <option1> specifies the service name. The service name can be max 15characters. If an empty string is provided the default service name is used ("SPP", "DUN", "UUID").

option2 EnumeratororByte_Array

For UDP <option2> specifies the behavior on incoming data.

0 (default): No connect. This will trigger an +UUDPC URC immediately (with broadcast as remote_ipand 0 as remote port), but this will not cause any new +UUDPC when data is received so it will not bepossible to extract the source of the data. This is typically used together with data mode.1: Auto connect.This will spawn a new peer and a trigger a +UUDPC URC so the host can respond tothe sender. Further incoming data from the same source will be received on the newly created peer.The originally created server will still be active to listen for new data. This is typically used togetherwith Extended data mode.

For UUID <option2> specifies the 128bit UUID identifier.


+UDSC:<id>,<type>[,<option1>[,<option2>]]

OK


Advance

Info

rmat

ion

http://confluence/display/PRODMULT/ODIN-W26+AT+Commands+Manual#ODIN-W26ATCommandsManual-ConnectPeer+UDCP

u-blox





7.6 Watchdog Settings +UDWS


AT+UDWS[=<type>] Read current watchdog settings.

AT+UDWS=<type>,<value> Write watchdog parameters.


+UDWS:<type>,<value>

OK





type enumerator 0: write timeout: <value> is time in milliseconds before DCE disconnects if a write isn't acknowledged.

0: Disabled > 0: Timeout in milliseconds (factory default value: 10000 ms)

1: inactivity timeout: <value> is time in milliseconds before DCE disconnects if no activity is detected.

0 (factory default): Disabled > 0: Timeout in milliseconds


7.7 Configuration +UDCFG


AT+UDCFG[=<param_tag>] Read peer configuration.

AT+UDCFG=<param_tag>,<param_val> Write peer configuration


+UDCFG:<param_tag>,<param_val> Sent for each applicable param_tag.




param_tag Enumerator 0: Keep remote peer in Command mode

0: Disconnect peers when entering Command mode1 (default): Keep connections when entering Command mode


Before an active server can be changed, it must first be disabled.

A DCE reboot is required before any Bluetooth related server configuration will take effect.

The data watchdog functionality is only active in data or extended data mode. Furthermore, the power mode must also be set toonline or sleep mode.

Advance

Info

rmat

ion

u-blox


7.8 Unsolicited response codes

7.8.1 Peer Connected +UUDPC

URC Description

+UUDPC:<peer_handle>,<type>,<profile>,<address>,<frame_size> A Bluetooth peer hasbeen connected.

+UUDPC:<peer_handle>,<type>,<protocol>,<local_address>,<local_port>,<remote_address>,<remote_port> An IP peer has beenconnected


peer_handle integer The peer handle identifies the connection.

type integer 1: Bluetooth2: IPv43: IPv6

profile enumerator 1: SPP2: DUN3: UUID4: SPS

protocol enumerator 0: TCP1: UDP

address Bd_Addr Bluetooth address

local_address IPv4_Addr or IPv6_Addr Local IP address associated to the peer

local_port integer Local port associated to the peer

remote_address IPv4_Addr or IPv6_Addr Remote IP address associated to the peer

remote_port integer Remote port associated to the peer

7.8.2 Peer Disconnected +UUDPD

URC Description

+UUDPD:<peer_handle> A connection to a remote peer has been disconnected.


peer_handle integer The connection handle identifies the connection.

This URC is not sent for connections initiated with the command.Connect Peer +UDCP

This URC is not sent for connections terminated with the commandClose Peer Connection +UDCPC

Advance

Info

rmat

ion

u-blox


8 Bluetooth Commands

8.1 Discoverability Mode +UBTDM


AT+UBTDM? Reads the GAP discoverability mode.

AT+ DM=<discoverability_mode>UBT Writes the GAP discoverability mode.


+ DM:<discoverability_mode>UBT

OK





discoverability_mode enumerator 1: GAP non-discoverable mode 2: GAP limited discoverable mode3 : GAP general discoverable mode(factory default)


8.2 Connectability Mode +UBTCM


AT+ CM?UBT Reads the GAP connectability mode.

AT+ CM=<connectability_mode>UBT Writes the GAP connectability mode.


+UBTCM:<connectability_mode>

OK





connectablilty_mode enumerator 1: GAP non-connectable mode 2 : GAP connectable mode (factory default)


8.3 Pairing Mode +UBTPM


AT+ PM?UBT Reads the pairing mode.

AT+ PM=<pairing_mode>UBT Writes the pairing mode.


+ PM:<pairing_mode>UBT

OK


Advance

Info

rmat

ion

u-blox





pairing_mode enumerator 1: GAP non-pairing mode 2 : GAP pairing mode (factory default)


8.4 Security Mode +UBTSM

The security modes are described more in detail in the document.ODIN-W2 Bluetooth Security


AT+ SM?UBT Reads the security mode.

AT+ SM=<security_mode>UBT [,<security_mode_BT2.0>[,<fixed_pin>]] Writes the security mode.


+ SM:<security_mode>,<security_mode_BT2.0>UBT

OK





security_mode enumerator 1 (factory default): Security Disabled. Should not be used in real life application.- Auto accept (No man-in-the-middle attack protection, encryption enabled)

2: Security Enabled - Just Works - Auto accept (no man-in-the-middle attack protection, encryption enabled) This security mode is intended for pairing in safe environments. When this mode is set,pairability (see ) is automatically disabled. In data mode, pairing can be enabled for 60+UBTPMseconds by pressing the "External Connect" button for at least 5 seconds. When the module ispairable, the LED will blink. If the mode is changed from Just Works to another, pairability mustbe enabled again using the command. +UBTPM

3: Security Enabled - Display Only* - Service level authentication and encryption enabled. User should be presented a passkey. This security mode is used when the device has a display that can present a 6-digit value thatthe user shall enter on the remote device.

4: Security Enabled - Display Yes/No* - Service level authentication and encryption enabled. User should compare two values. This security mode is used when the device has a display that can present a 6-digit value thatthe user shall verify with yes or no to the remote device's presented value. Invalid for Bluetooth Low Energy.

5: Security Enabled - Keyboard Only* - Service level authentication and encryption enabled. User should enter a passkey. This security mode is used when the device only has a keyboard where the user can enter a6-digit value that is presented on the remote device.

* For security modes 3, 4 and 5 the DCE must be in Command or Extended Data mode to beable to do bonding because user interaction might be required.

security_mode_BT2.0 integer 0 : Disabled, (factory default) no pairing is allowed with Bluetooth 2.0 devices.1: Enabled. Pairing is allowed with Bluetooth 2.0 devices using the fixed_pin.

fixed_pin string The BT 2.0 fixed_pin is a string of one to sixteen alphanumerical characters. It is recommended to use a pin code of at least eight characters of mixed type, e.g. "12w35tg7". Factory default is "0".


Advance

Info

rmat

ion

u-blox


8.5 User Confirmation +UBTUC


AT+UBTUC=<bd_addr>,<yes_no> The user confirmation is used together with security mode "display yes/no" to respond on a userconfirmation request (+UUBTUC). The command should only be used after +UUBTUC has beenreceived.





bd_addr Bd_Addr The remote Bluetooth Device address

yes_no enumerator 0: No. The remote and local values are different or the user cancels. 1: Yes. The remote and local values are the same.

8.6 User Passkey Entry +UBTUPE


AT+UBTUPE=<bd_addr>,<ok_cancel>[,<passkey>] The user passkey entry is used together with security mode "keyboard only" torespond on a user passkey entry request (+UUBTUPE). The command shouldonly be used after +UUBTUPE has been received.






ok_cancel enumerator 0: Cancel. 1: Ok.

passkey integer This is an integer in the range of [0..999999]. If ok_cancel is Cancel, this can be omitted.

8.7 Name Discovery +UBTND

This command uses different syntaxes for Bluetooth classic devices and Bluetooth Low Energy dual mode devices. The mode parameter isused to distinguish between Bluetooth Low Energy and Bluetooth classic in dual mode radios.


AT+ ND=<bd_addr>[,<mode>[UBT ,<timeout>]] Retrieves the device name of a remote device given its Bluetooth device address.


+ ND:<device_name>UBT

OK

Successful response



device_name string Local name of remote device of maximum 240 characters (8-bit ASCII).

bd_addr Bd_Addr Bluetooth device address of the device from which to retrieve the name.

In security_mode 1, no Bluetooth 2.0 pairing is required.

Advance

Info

rmat

ion

u-blox


timeout integer Timeout measured in milliseconds, only applicable for BT Classic Time Range: 10 ms - 40 s

Default: 5s

mode integer 0 (default): Bluetooth classic 1: Bluetooth Low Energy

8.8 Inquiry (Classic) +UBTI


AT+UBTI[=<inquiry_type>[,<inquiry_length>]] Performs an inquiry procedure to find any discoverable devices in the vicinity.


+UBTI:<bd_addr>,<rssi>,<cod>,<device_name> This response is sent for every found device.




bd_addr Bd_Addr Bluetooth device address of a found device.

cod Byte_Array See Read Local COD command.

inquiry_type enumerator 1 (default): General extended inquiry2: Limited extended inquiry

inquiry_length integer Timeout measured in milliseconds Time Range: 10 ms - 40 s, default 5000 ms

device_name string Name of discovered device.

rssi integer Received signal strength in dBm

8.9 Discovery (Low Energy) +UBTD


AT+ =<discovery_type>[,<mode>[,<inquiry_length>UBTD[]]]

Performs an inquiry procedure to find any discoverable devices in thevicinity.


+ :UBTD <bd_addr>,<rssi>,<device_name>,<data_type>,<data>

This response is sent for every found device, if no name is found,<device_name> is an empty string. If <mode> is set to Active, both Scanresponses and Advertises will be shown.




bd_addr Bd_Addr Bluetooth device address of a found device.

discovery_type enumerator 1: All, display all found devices, each device will only be displayed once2 (default): General inquiry, display devices in General discoverablitiy mode, each device will only bedisplayed once.3: Limited inquiry, display devices in Limited discoverability mode, each device will only be displayedonce4: All with no filter, display all found device. Devices can be displayed multiple times.

mode enumerator 1 : Active (default)2: Passive, no scan response data will be received

Name of discovered devices is only returned by devices supporting Bluetooth 2.1 or later.

Advance

Info

rmat

ion

u-blox


discovery_length integer Timeout measured in milliseconds Time Range: 10 ms - 40 s, default 5000 ms

device_name string Name of discovered device.


data_type enumerator 1: Scan response data2: Advertise data

data Byte_Array Complete advertise / scan response data received from remote device

8.10 Bond +UBTB


AT+UBTB=<bd_addr>[,<mode>] Performs a GAP bond procedure with another Bluetooth device. During the bonding procedure user interaction is required. Which procedure to use is determined bythe security mode. For user interaction during bonding see and User Confirmation +UBTUC User

commands and and Passkey Entry +UBTUPE User Confirmation +UUBTUC User Passkey Entry events. Note that to be able to perform bonding the remote device must be in pairable+UUBTUPE

and connectable mode. When the bond is complete a is generatedBond Event +UUBTB



ERROR Error message


bd_addr Bd_Addr Bluetooth device address of the device to bond with.

mode integer 0 (default): Bluetooth classic1: Bluetooth Low Energy

8.11 Un-bond +UBTUB


AT+ UB=<bd_addr>UBT This command un-bonds a previously bonded device.





bd_addr Bd_Addr Bluetooth device address of the device subject to un-bond.

If address FFFFFFFFFFFF is selected all bonded devices will be removed.

8.12 Read Bonded Devices +UBTBD

The mode parameter is used to distinguish between Bluetooth Low Energy bondings and Bluetooth classic bondings in dual mode radios.


AT+UBTBD[=<mode>] Read the bonded devices.


Only works if module is configured as LE Central Role

A Bluetooth Low Energy peripheral cannot initiate Bonding

Advance

Info

rmat

ion

u-blox


+UBTBD:<bd_addr>,<device_mode> This response is sent for every found device.




mode integer This parameter is only used for Bluetooth Low Energy and dual mode radios

0: Bluetooth Classic1: Bluetooth Low Energy2 (default): Bluetooth Classic and Low Energy

bd_addr Bd_Addr Bluetooth device address of the device from which to retrieve the name.

device_mode boolean 0: Device is in Classic mode. 1: Device is in Low Energy mode.

8.13 Local Name +UBTLN


AT+ LN?UBT Reads the local Bluetooth device name.

AT+ LN=<device_name>UBT Writes the local Bluetooth device name.


+ LN:<device_name>UBT

OK





device_name string Max 31 characters. The default name is "Bluetooth Device".


8.14 Local COD +UBTLC


AT+ LC?UBT Reads the Local Class Of Device code.

AT+ LC=<cod>UBT Writes the Local Class Of Device code.


+ LC:<cod>UBT

OK




Parameters Type ValueAdvance

Info

rmat

ion

u-blox


cod Byte_Array Valid values for this parameter are specified in the Bluetooth Assigned Numbers Document, www.bluetoot. The parameter has been divided into three segments, a service class segment, a major deviceh.com

class segment and a minor device class segment (bits 2-7).

Extract from the Bluetooth Assigned Numbers Document:

Service class (bit mask, bits 13-23): Bit 16: Positioning (Location identification) Bit 17: Networking (LAN, Ad hoc, etc) Bit 18: Rendering (Printing, Speaker, etc) Bit 19: Capturing (Scanner, Microphone, etc) Bit 20: Object Transfer (v-Inbox, v-Folder, etc) Bit 21: Audio (Speaker, Microphone, Headset service, etc) Bit 22: Telephony (Cordless telephony, Modem, Headset service) Bit 23: Information (WEB-server, WAP-server, etc)

Major device class (number, bits 12-8): 00000: Miscellaneous 00001: Computer (desktop, notebook, PDA, etc) 00010: Phone (cellular, cordless, modem, etc) 00011: LAN/Network Access point 00100: Audio/Video (headset, speaker, stereo, video display, VCR) 00101: Peripheral (mouse, joystick, keyboards) 00110: Imaging (printing, scanner, camera, etc) 11111: Uncategorized, specific device code not specified

For the minor device class field please refer to [1].

The default value is 0.


8.15 Master Slave Role +UBTMSR


AT+ MSR=<UBTbd_addr>

Read the local master-slave role. Returns the role of the Serial Port Adapter, master or slave, for the connection between the Serial Port Adapter andthe remote device identified by the 'bd_addr' parameter.


+ MSR:<role>UBT

OK




role enumerator 0: Slave 1: Master

bd_addr Bd_Addr Identifies a device that the Serial Port Adapter is currently communicating with.

8.16 Master Slave Role Policy +UBTMSP


AT+ MSP?UBT Reads the role policy of the device.

AT+ MSP=<role_policy>UBT Writes the role policy of the device.


+ MSP:<role_policy>UBT

OK




Advance

Info

rmat

ion

http://www.bluetooth.com

http://www.bluetooth.com

u-blox



role_policy enumerator 0: Always attempt to become master on incoming connections. 1 (factory default): Always let the connecting device select master/slave role on incoming connections.


8.17 Get RSSI +UBTRSS


AT+ RSS=<UBTbd_addr>

This request returns the current received signal strength, RSSI, for the connection between the Serial Port Adapterand the remote device identified by the 'bd_addr' parameter.


+ RSS:<rssi>UBT

OK






8.18 Get Link Quality +UBTLQ


AT+ LQ=<bdUBT_addr>

This request returns the current link quality for the connection between the Serial Port Adapter and the remotedevice identified by the <bd_addr> parameter.


+ LQ:<link_quality>UBT

OK




link_quality integer Link quality represented as a percentage value, where 100% is a perfect link without CRC errors.

Packet types are not taken into account.


8.19 Bluetooth Low Energy Role +UBTLE

Read/Write Bluetooth Low Energy role, for models supporting Bluetooth Low Energy. This command can be used to enable/disableBluetooth Low Energy for dual mode radios, and to read out the role of single mode Low Energy radios.


AT+ LE?UBT Reads the configuration status.

AT+ LE=<role>UBT Writes the configuration status.


Please note that the implementation is vendor specific and may differ for future module versions.

Advance

Info

rmat

ion

u-blox


+ LE:<role>UBT

OK





role integer 0 (factory default): Disabled1: Low Energy Central 2: Low Energy Peripheral

Setting is stored to start up database with &W command. A reset is required for the setting to take effect.

8.20 Low Energy Advertise Data +UBTAD

Command for use of custom advertise data in Low Energy. Any custom advertise data will be appended to the default mandatory flags field.Note that the Inquiry AT command AT+UBTD supports scan modes that can be used to see the complete advertising data. This is usefulwhen testing advertising configurations set with the AT+UBTAD.

By default the service UUID for the u-blox Serial Port Service is part of the advertising data and the local name is part of the scan responsedata.

There will be no check whether the same data types are used in AT+UBTAD and AT+UBTSD. It is up to the application to make sure thedata types are used in only one of the advertisement and scan response data.


AT+ AD?UBT Read custom advertise data.

AT+ AD=<data>UBT Write custom advertise data.


+ AD:<data>UBT

OK





When Bluetooth Low Energy is enabled the device can not be client and server at the same time.

Advance

Info

rmat

ion

u-blox


data Byte_Array Custom advertise data. Maximum 28 bytes.

The default value includes AD Flags, Tx power, Slave connection interval and the u-blox Serial ServiceUUID.

It is recommended to use the u-blox Serial Service UUID [2456e1b926e28f83e744f34f01e9d701] forfiltering when doing scan in smartphone apps.

The data must follow the Bluetooth Specification, see GAP section in ref[4]. Data is divided into differentconsecutive data blocks, where each block has the following structure:

Byte 0: Length of data block, N, excluding length byte.Byte 1: GAP advertisement data type, see below.Byte 2-N: Data.

Typical GAP advertisement data types:0x01 AD Flags (Mandatory for advertising data)0x02 16-bit Service UUIDs, more available0x03 16-bit Service UUIDs, complete list0x04 32-bit Service UUIDs, more available0x05 32-bit Service UUIDs, complete list0x06 128-bit Service UUIDs, more available0x07 128-bit Service UUIDs, complete list0x08 Shortened Local name0x09 Complete Local Name0x0A Tx Power in dBm0x12 Slave connection interval range0xFF Manufacturer Specific Data (The first 2 octets contain the Company Identifier Code followed byadditional manufacturer specific data)

See GAP section in ref[4] for complete list.

Example: "07FF710000112233", where "07" is the length, "FF" is the GAP advertisement data type"Manufacturer Specific Data" and "7100" is the u-blox Company Identifier written with lowest octet first and"00112233" is the application data.


8.21 Low Energy Scan Response Data +UBTSD

Command for use of custom scan response data in Low Energy. Any custom scan response data will overwrite the default scan responsedata.

Note that the local name used in the scan response data is normally set with AT+UBTLN. AT+UBTSD will override what is set withAT+UBTLN. Note that it is highly advised to run AT+UBTLN with the correct local name before any AT+UBTSD to make sure it is the samename for Classic Bluetooth, the GAP device name and the scan response data.

Note that the Inquiry AT command AT+UBTD supports scan modes that can be used to see the complete scan response data. This isuseful when testing configurations set with the AT+UBTSD command.


AT+ SD?UBT Read scan response data.

AT+ SD=<data>UBT Write scan response data.


+ SD:<data>UBT

OK





Command is only supported in LE peripheral mode.

Advance

Info

rmat

ion

u-blox


data Byte_Array Custom scan response data. Maximum 31 bytes.

The default value includes the complete local name of device.

Same format as of the AT+UBTAD command.data parameter


8.22 Service Search +UBTSS


AT+ SS=<bd_addr>,<type>[,<uuid>]UBT Search for services on a remote device.


+UBTSS:<service_name>,<rfcomm_server_chan> This response issent for every foundservice for type setto 0, 1, 2 and 3

+UBTSS:<spec_version>,<vendor_id>,<product_id>,<product_version>,<primary_service>,<vendor_id_source> This response issent for every foundservice for type setto 4

OK Successfulresponse. Note thatOK is returned also ifthe service search issuccessfullycompleted but but noservices are found.



bd_addr Bd_Addr Bluetooth device address of the device on which to search for services.

type enumerator 0: Serial Port Profile 1: Dial-Up Networking Profile 2: SPP iPhone 3: UUID (Android)4: Device Id

uuid Byte_Array 16 values

rfcomm_server_chan integer RFCOMM server channel number on which this service can be found. It is used when connectingto a profile. Range 1 to 30.

service_name string Service name.

spec_version Byte_Array This is intended to reflect the version number of the Bluetooth Device ID Profile specificationsupported by the device. The two most significant hexadecimal digits will indicate the majornumber of the Bluetooth Device ID Profile specification and the two least significant hexadecimaldigits will reflect the minor number of the specification, e.g JJMM for version JJ.MM (JJ – major

).version number, M – minor version number

vendor_id Byte_Array Uniquely identifier for the vendor of the device. Used in conjunction with required attribute 0205,VendorIDSource, which determines which organization assigned the VendorID value. Note: TheBluetooth Special Interest Group assigns Device ID Vendor ID and the USB Implementer’sForum assigns vendor IDs, either of which can be used for the VendorID value here. Deviceproviders should procure the vendor ID from the USB Implementer’s Forum or the CompanyIdentifier from the Bluetooth SIG. The VendorID ‘FFFF’ is reserved as the default VendorID whenno Device ID Service Record is present in the device.

product_id Byte_Array This is intended to distinguish between different products made by the vendor above. These IDsare managed by the vendors themselves.

Command is only supported in LE peripheral mode.

Advance

Info

rmat

ion

u-blox


product_version Byte_Array A numeric expression identifying the device release number in Binary-Coded Decimal. This is avendor-assigned field, which defines the version of the product identified by the VendorID andProductID attributes. This attribute is intended to differentiate between versions of products withidentical VendorIDs and ProductIDs. The value of the field is JJMN for version JJ.M.N (JJ – majorversion number, M – minor version number, N – sub-minor version number); e.g., version 2.1.3 isrepresented with value 0213 and version 2.0.0 is represented with a value of 0200. Whenupward-compatible changes are made to the device, it is recommended that the minor versionnumber be incremented. If incompatible changes are made to the device, it is recommended thatthe major version number be incremented.

primary_service integer 0: This is not the primary Device Id service1: This is the primary Device Id service

vendor_id_source integer Organization that assigned the VendorID attribute.

1: Bluetooth SIG2: USB Implementer’s Forum

8.23 Watchdog Settings +UBTWS


AT+UBTWS=<type>,<value> Write watchdog parameter.

AT+UBTWS[=<type>] Read watchdog parameter(s)


+UBTWS:<type>,<value> Sent for every applicable watchdog parameter




type enumerator 0: connection setup timeout: <value> is the max connection time in milliseconds (integer) before aconnection is terminated.

0 (factory default): Disabled> 0: Timeout in milliseconds, max 2147483647 ms.

1: disconnect reset: <value> defines if the DCE shall reset on dropped connection (not on actively closedconnection)

0 (factory default): disabled1: enabled


8.24 Bluetooth Configuration +UBTCFG

Configures miscellaneous Bluetooth parameters. The values are kept in volatile memory and will have immediate effect for all upcomingconnections.


AT+UBTCFG=<param_tag> Read Bluetooth configuration.

AT+UBTCFG=<param_tag>,<param_val> Write Bluetooth configuration


+UBTCFG:<param_tag>,<param_val> Sent for each applicable configuration id.



Paramtag

Defaultvalue

Minvalue

Maxvalue

Description Calculation

Advance

Info

rmat

ion

u-blox


1 1 0 7 Max number of Bluetooth Classiclinks

-

2 1 0 7 Max number of Bluetooth LE links -

3 56602

(0xDD1A)

Bit 1:2-DH1Bit 3: DM1Bit 4: DH1Bit 8:2-DH3Bit 10:DM3Bit 11: DH3Bit 12:2-DH5Bit 14:DM5Bit 15: DH5

Bitmask containing allowed packettypes. All bitmask combinations areallowed. Reserved bits will be ignored.

Bit 0: ReservedBit 1: 2-DH1Bit 2: 3-DH1 (not supported in 00b)Bit 3: DM1 (DM1 is always on no matter if thisbit is set)Bit 4: DH1Bit 5: ReservedBit 6: ReservedBit 7: ReservedBit 8: 2-DH3Bit 9: 3-DH3 (not supported in 00b)Bit 10: DM3Bit 11: DH3Bit 12: 2-DH5Bit 13: 3-DH5 (not supported in 00b)Bit 14: DM5Bit 15: DH5


8.25 Bluetooth Low Energy Configuration +UBTLECFG

Configures Bluetooth LE connection and advertising parameters. The values are kept in volatile memory and will have immediate effect forall upcoming connections (exceptions mentioned below). Max values/windows must always be greater than or equal to min values/intervals.Default values taken from BT Core Specification v 4.2.


AT+UBTLECFG=<param_tag>,<param_val> Write Bluetooth LE configuration.

AT+ UBTLECFG[=<param_tag>] Read Bluetooth LEconfiguration


+UBTLECFG: <param_tag>,<param_val>

OK

Successful read response for AT+UBTLECFG=<param_id>,<param_tag>

+UBTLECFG: <param_tag>,<param_val>

...OK

Successful read response for AT+UBTLECFG+UBTLECFG: <param_tag>,<param_val> is sent for all param_tags



Paramtag

Defaultvalue

Minvalue

Maxvalue

Description Calculation

1 1600 (1000ms)

32 16384 Advertising Interval Min (must be <= Advertising Interval Max)NOTE: parameter needs module reset to take effect

<param_val>*0.625ms

2 2000 (1250ms)

32 16384 Advertising Interval Max(must be >= Advertising Interval Min)NOTE: parameter needs module reset to take effect

<param_val>*0.625ms

3 7(ch37,38,39)

0 7 Advertising channel mapNOTE: parameter needs module reset to take effect

Bit0: channel 37Bit1: channel 38Bit2: channel 39

4 24 (30 ms) 6 3200 Connect Connection Interval Min(must be <= Connect Connection Interval Max)

<param_val>*1.25ms

5 40 (50 ms) 6 3200 Connect Connection Interval Max(must be >= Connect Connection Interval Min)

<param_val>*1.25ms

Advance

Info

rmat

ion

u-blox


6 0 0 500 Connect Latency for Number of Connection Events <param_val> ms

7 2000 100 32000 Connect Linkloss Timeout <param_val> ms

8 5000 0 65535 Connect Create Connection Timeout <param_val> ms

9 48 (30 ms) 16 16384 Connect Connection Scan Interval(must be >= Connect Scan Window)

<param_val>*0.625ms

10 48 (30 ms) 16 16384 Connect Scan Window(must be <= Connection Scan Interval

<param_val>*0.625ms

11 24 (30 ms) 6 3200 Bond Connection Interval Min(must be <= Bond Connection Interval Max)

<param_val>*1.25ms

12 40 (50 ms) 6 3200 Bond Connection Interval Max(must be >= Bond Connection Interval Min)

<param_val>*1.25ms

13 0 0 500 Bond Latency for Number of Connection Events <param_val> ms

14 2000 100 32000 Bond Linkloss Timeout <param_val> ms

15 5000 0 65535 Bond Create Connection Timeout <param_val> ms

16 48 (30 ms) 16 16384 Bond Connection Scan Interval(must be >= Bond Scan Window)

<param_val>*0.625ms

17 48 (30 ms) 16 16384 Bond Scan Window(must be <= Bond Scan Interval

<param_val>*0.625ms

18 24 (30 ms) 6 3200 Remote Name Request Connection Interval Min(must be <= Remote Name Request Connection IntervalMax)

<param_val>*1.25ms

19 40 (50 ms) 6 3200 Remote Name Request Connection Interval Max(must be >= Remote Name Request Connection IntervalMin)

<param_val>*1.25ms

20 0 0 500 Remote Name Request Latency for Number ofConnection Events

<param_val> ms

21 2000 100 32000 Remote Name Request Linkloss Timeout <param_val> ms

22 5000 0 65535 Remote Name Request Create Connection Timeout <param_val> ms

23 48 (30 ms) 16 16384 Remote Name Request Connection Scan Interval(must be >= Remote Name Request Scan Window)

<param_val>*0.625ms

24 48 (30 ms) 16 16384 Remote Name Request Scan Window(must be <= Remote Name Request Scan Interval

<param_val>*0.625ms


8.26 Unsolicited Result Codes

8.26.1 Bond Event +UUBTB


+UUBTB:<bd_addr>,<status>

This event indicates that bonding initiated with AT+UBTB is complete. The status parameter tells if thebonding did succeed or fail.

EventParameters

Type Value


status enumerator 0: bonding succeeded 1: bonding failed because of page timeout 2: bonding failed because authentication or pairing failed. This could be due to incorrect PIN/passkey. 3: bonding failed because protection against Man-In-The-Middle attack could not be guaranteed (Thegenerated link key was too weak)

Advance

Info

rmat

ion

u-blox


8.26.2 User Confirmation +UUBTUC


+UUBTUC:<bd_addr>,<numeric_value> This event is used during bonding with security mode 'Display Yes/No' to indicate that userconfirmation of a numeric value is required. If the local and remote sides numeric values areequal a positive reply with AT+UBTUC should be issued, otherwise a negative reply.

Event Parameters Type Value


numeric_value integer This is an integer in the range of [0..999999].

8.26.3 User Passkey Display +UUBTUPD


+UUBTUPD:<bd_addr>,<passkey> This event is used to indicate to the user a passkey to be entered on the remote device during abonding procedure with security mode 'Display only'. The event should not be replied on.



passkey integer This is an integer in the range of [0..999999].

8.26.4 User Passkey Entry +UUBTUPE


+UUBTUPE:<bd_addr> This event is used during bonding with security mode 'Keyboard only' to indicate that a passkey is requiredfrom the user. The event should be responded with AT+UBTUPE.



Advance

Info

rmat

ion

u-blox


9 Wi-Fi

9.1 Wi-Fi Station Configuration +UWSC

This command is used to configure up to 2 different Wi-Fi Networks. After a network is configured it must be activated (Wi-Fi Station) before it's used.Configuration Action +UWSCA

Syntax Description

AT+UWSC=<configuration_id>,<param_tag>,<param_val1>[,<param_val2>,...,<param_valn>] Set Wi-Fi station configuration.

AT+UWSC=<configuration_id>[,<param_tag>] Read Wi-Fi station configuration.


configuration_id integer Wi-Fi configuration id.

0-1

The command will generate an error if the configuration id is active. See forWi-Fi Station Configuration Action +UWSCAinstructions on how to deactivate a configuration.

Advance

Info

rmat

ion

u-blox


param_tag integer 0: <param_val1> decides if the station is active on startup.

0 : inactive (default)1: active

2: SSID - <param_val1> is the Service Set Identifier. The factory default value is an empty string ("").3: BSSID - <param_val1> is the Basic Service Set Identification (MAC_Addr of the Access Point). May beomitted. The factory default value is "000000000000".4: Reserved 5: Authentication - <param_val> is the authentication type.

1 (default): Open2: WPA/WPA2 PSK3: LEAP4: PEAP

6*: WEP Keys - <param_val1>...<param_val4> is the WEP encryption keys. A WEP key is either 5 or 13bytes and if not used it can be left empty.7: Active Key - <param_val1> is the WEP active TX key (factory default 0 means that Open authenticationwith WEP encryption is disabled). Range 1-4.8*: PSK/Passphrase - <param_val1> is the PSK (32 HEX values) or Passphrase (8-63 ascii characters asa string) for WPA and WPA29*: Password <param_val1> is the password for LEAP, PEAP and EAP-TLS10: <param_val1> is the public user name, String, max length 64. 11: <param_val1> is the public domain name, String, max length 64. 100: IPv4 Mode - <param_val1> to set the way to retreive an IP address

1: Static2 (default): Dhcp

101: <param_val> is the IPv4 address. The factory default value is 0.0.0.0. The factory default value is 0.0.0.0102: <param_val> is the subnet mask

103: <param_val> is the default gateway. The factory default value is 0.0.0.0104: <param_val> is the primary DNS server IP address. The factory default value is 0.0.0.0105: <param_val> is the secondary DNS server IP address. The factory default value is 0.0.0.0200: IPv6 Mode - <param_val1> to set the way to retreive an IP address

1 (default): Link Local IpAddress

201: <param_val> is the IPv6 link local address. If value is not set the link local address is automaticallygenerated from the interface IEEE 48 bit MAC identifier.The factory default value is ::

* = Does not support reading

To use WEP with open authentication, the WEP key index must be different from zero (0).


+UWSC:<configuration_id>,<param_tag>,<param_val1>

Sent for every applicable param_tag



The setting is stored to the start up database using the - Store command.Wi-Fi Station Configuration Action +UWSCA

9.2 Wi-Fi Station Configuration Action +UWSCA

Syntax Description

AT+UWSCA=<config_id>,<action> Execute an action for the Wi-Fi Network.


If more than one configuration has the active on startup parameter enabled, behaviour is undefined.Advance

Info

rmat

ion

u-blox


config_id integer Wi-Fi Network configuration id.

0-1

action integer 0: reset; it clears the specified profile resetting all the parameters to their factory defaults1: store; validates the configuration, calculates the PSK for WPA and WPA2 (if not already calculated) andsaves the configuration.2: load: it reads all the parameters from memory3: activate; avalidates the configuration, calculates the PSK for WPA and WPA2 (if not already calculated) and ctivates the specified profile. It will try to connect if not connected.4: deactivate; it deactivates the specified profile. Disconnects the profile if connected and may reconnect toother active network




9.3 Wi-Fi Active Station Configuration List +UWASCL

Syntax Description

AT+UWASCL List active network configurations


config_id_# integer Wi-Fi Network configuration id.

0-1


+UWASCL:<config_id_0>,...,<config_id_n>

OK

Successful response


9.4 Scan +UWSCAN

Syntax Description

AT+UWSCAN[=<ssid>] Scan the surroundings for networks. The command will return networks in the immediate surroundings, thenreturn OK or ERROR if not able to start scan. Channels scanned is given by the channel list, see +UWCL formore information irected scan will be performed.. If SSID is defined a d


ssid string The SSID name of network

channel integer The channel the network uses

bssid Mac_Addr The MAC address of the access point

op_mode integer 1 = Infrastructure 2 = Ad-hoc

rssi integer Signal strength value for the network in dBm.

authentication_suites Byte_Array 1 hexadecimal value

Bit 0 = Shared secretBit 1 = PSKBit 2 = EAPBit 3 = WPABit 4 = WPA2

Only one configuration may be active at each point in time.

Advance

Info

rmat

ion

u-blox


unicast_ciphers and Byte_Array 1 hexadecimal value

Bit 0 = WEP64Bit 1 = WEP128Bit 2 = TKIPBit 3 = AES/CCMP

group_ciphers Byte_Array 1 hexadecimal value

Bit 0 = WEP64Bit 1 = WEP128Bit 2 = TKIPBit 3 = AES/CCMP


+UWSCAN:<bssid>,<op_mode>,<ssid>,<channel>,<rssi>,<authentication_suites>,<unicast_ciphers>,<group_ciphers>

OK

Successfulread response

ERROR Errorresponse

9.5 Channel List +UWCL

Syntax Description

AT+UWCL[=channel_list] Write the wanted channel list for station mode.

Example: AT+UWCL=1,6,11

The channel list is restored to default value by passing the command without parameters: AT+UWCL

AT+UWCL? Read the wanted channel list.


channel_list list of integer Channels to use


+UWCL:<ch1>,<ch2>,...,<chN>

OK




AT+UWSCAN will return ERROR if channel list set by AT+UWCL is empty.

The actual channel list may differ from the wanted channel list. Depending on the physical location, the radio environment, andthe product version the actual channel list in use may be limited to comply with regulatory approvals.

Channel 12 and 13 will be disabled until it has been determined that the module is operating outside FCC region.Channels 120, 124, 128 will be disabled until it has been determined that the module is operating outside FCC region.Channels 149, 153, 157, 161, 165 will be disabled until it has been determined that these are allowed for the currentregion.Any DFS channel will be disabled for active use until an appropriate authoritative source has been found for clearingeach specific channel.Other limitations may also apply.Adva

nce In

form

atio

n

u-blox


9.6 Wi-Fi Watchdog Settings +UWWS


AT+UWWS=<type>,<value> Write watchdog parameters.

AT+UWWS[=<type>] Read watchdog parameter, if type is omitted, all parameters are read.


+UWWS:<type>,<value> sent for all applicable watchdog setting




type enumerator 1: disconnect reset: <value> defines if the DCE shall reset on dropped connection

0 (factory default): disabled1: enabled


9.7 Wi-Fi Station Status +UWSSTAT


AT+UWSSTAT[=<status_id>] Read current status of the Wi-Fi interface


+UWSSTAT:<status_id>,<status_val> This is sent for every applicable status.




status_id integer 0: <status_val> is the currently used SSID.1: <status_val> is the currently used BSSID.2: <status_val> is the currently used channel.3: <status_val> is the current status of the station, possible values of status_val are:

0: Disabled1: Disconnected2: Connected

6: <status_val> is the RSSI value of the current connection

9.8 Unsolicited response codes

9.8.1 Wi-Fi Link Connected +UUWLE

URC Description

+UUWLC:<connection_id>,<bssid>,<channel> Wi-Fi connection established


connection_id integer Wi-Fi Network configuration Id

bssid MAC_Addr BSSID of connected network

channel integer Connected channel

Advance

Info

rmat

ion

u-blox


9.8.2 Wi-Fi Link Disconnected +UUWLD

URC Description

+UUWLD:<connection_id>,<reason> Wi-Fi connection


connection_id integer Wi-Fi Network configuration Id

reason enumerator 0: Unknown1: Remote Close2: Out of range3: Roaming4: Security problems5: Network disabled

Advance

Info

rmat

ion

u-blox


10 Network

10.1 Network Host Name +UNHN

Syntax Description

AT+UNHN? Read current Host Name. Default: "odin-w2-xxxxxxxxxxxx", where "xxxxxxxxxxxx" is a device specificnumber.

AT+UNHN=<param_tag> Set a new host name, parameter must be a string with maximum 64 charaters





10.2 Network Status +UNSTAT

Syntax Description

AT+UNSTAT[=<interface_type>[,< ]]status_id> Show current status of network configuration id.


interface_type enumerator Network interface type.

0: Wi-Fi Station

status_id integer 0: <status_val> is the interface HW address (only shown if applicable).1: <status_val> is the current status of the network interface (Layer-3).

0: Network down1: Network up

101: <status_val> is the currently used IPv4_Addr (omitted if no IP address has been acquired).102: <status_val> is the currently used subnet mask (omitted if no IP address has been acquired).103: <status_val> is the currently used gateway (omitted if no IP address has been acquired).104: <status_val> is the current primary DNS server105: <status_val> is the current secondary DNS server

201: <status_val> is the current IPv6 link local address.


+UNSTAT=<interface_type>,<status_id>,<status_val> Sent for every applicable status



10.3 Unsolicitated Result Codes

10.3.1 Network UP +UUNU

Syntax Description

+UUNU=<interface_type> Network is up


Advance

Info

rmat

ion

u-blox


interface_type enumerator Network interface type.0: Wi-Fi Station

10.3.2 Network Down +UUND

Syntax Description

+UUND=<interface_type> Network is down


interface_type enumerator Network interface type.0: Wi-Fi Station

Advance

Info

rmat

ion

u-blox


1. 2.

11 Related documentsODIN-W2 Getting started guideODIN-W2 Extended Data Mode

Advance

Info

rmat

ion

u-blox


12 Revision History

Revision Date Name Status / Comments

R01 14-Nov-2014 pber Initial release

R02 10-Feb-2015 hreh Major update

Added ATZUpdated +UMRSUpdated Bluetooth securityUpdated/Added Wi-Fi CommandsAdded +UDCFGAdded +UBTCFGAdded +UBTBDAdded +UBTSTATChannel parameter removed from +UWSC command. Use channel list +UWCL insteadRemoved +UDNRP (Use +UBTCFG instead)Added active on startup parameter to +UNC and +UWSC

R03 31-Mar-2015 hreh Updated +UDSCRemoved +UBTSN. Functionality added to +UDSC.Added ATIChannel parameter removed from +UWSCAN command. Use channel list +UWCL instead

R04 22-Apr-2015 hreh Updated udcp (DNS resolver is now implemented)Basic IPv6 functionalilty added. Updated +UNC and +UNSTAT.

R05 2-Jun-2015 hwin Updated +UWSC, +UNC and +UNSTAT. Note: These changes are not backwardscompatible!Removed +AT&F. Functionality added to +UFACTORY.Clarified description of AT&S and AT&D

R06 3-Jul-2015 plin Updated +UBTBDAdded +UWAPCAdded +UWAPCAAdded +UWAPSTATAdded +UWAPSTALISTAdded +UUWAPUAdded +UUWAPDAdded +UUWAPSTACAdded +UUWAPSTADAdded +UETHCAAdded +UETHCAdded +CSGT

R07 Moved features not supported in 00B release to separate document

R08 20-Sep-2015 vull Added data type "list".Removed connection scheme "connect on data".Renamed a lot of factory-programmed value to factory default.General updates after review.Removed time and date from ATI9.Added unique identifier to ATI9.

Advance

Info

rmat

ion

u-blox


13 ContactFor complete contact information visit us at .www.u-blox.com

13.1 u-blox Offices

North, Central and South America HeadquartersEurope, Middle East, Africa

Asia, Australia, Pacific

u-blox America, Inc.Phone: +1 703 483 3180 E-mail: [email protected]

Regional Office West Coast:Phone: +1 408 573 3640 E-mail: [email protected]

Technical Support:Phone: +1 703 483 3185 E-mail: [email protected]

u-blox AGPhone: +41 44 722 74 44 E-mail: [email protected]: [email protected]

u-blox Singapore Pte. Ltd.Phone: +65 6734 3811E-mail: [email protected]: [email protected]

Regional Office Australia:Phone: +61 2 8448 2016E-mail: [email protected]: [email protected]

Regional Office China (Beijing):Phone: +86 10 68 133 545E-mail: [email protected]: [email protected]

Regional Office China (Chongqing):Phone: +86 23 6815 1588E-mail: [email protected]: [email protected]

Regional Office China (Shanghai):Phone: +86 21 6090 4832E-mail: [email protected]: [email protected]

Regional Office China (Shenzhen):Phone: +86 755 8627 1083E-mail: [email protected]: [email protected]

Regional Office India:Phone: +91 959 1302 450E-mail: [email protected]: [email protected]

Regional Office Japan (Osaka):Phone: +81 6 6941 3660E-mail: [email protected]: [email protected]

Regional Office Japan (Tokyo):Phone: +81 3 5775 3850E-mail: [email protected]: [email protected]

Regional Office Korea:Phone: +82 2 542 0861E-mail: [email protected]: [email protected]

Regional Office Taiwan:Phone: +886 2 2657 1090E-mail: [email protected]: [email protected]

Advance

Info

rmat

ion


Abstract Advance website ( is a rich pool of information. Product information, technical documents...

Documents

Transcript of Abstract Advance website ( is a rich pool of information. Product information, technical documents...