BL600 Series Bluetooth Module
Learn more and compare with similar parts on the family page.

Development kit for BL600-ST module

Specifications

Antenna Options
SMA Connector
Antenna Type
External
BLE Services
Any that can be implemented with smartBASIC
Bluetooth Version
v4.0 Single Mode
Chipset (Wireless)
Nordic nRF51822
Compliance
FCC, ISED, EU, MIC
Connector
USB Pluggable
Data Rate
1 Mbps (over the air)
Development Kit Contents
Development Board
Frequency Range (Max)
2480 MHz
Frequency Range (Min)
2402 MHz
Logical Interfaces
USB, GPIO, SPI, I2C, ADC, Serial
Memory
16 kb for applications
OS/Software
Nordic SDK, smartBASIC
Product Type
Development Kit
Protocols
Any that can be implemented using smartBASIC
Range
Up to 100 m
Software
UwTerminalX terminal software
System Architecture
Hostless
Technology
Bluetooth 4.0, Single Mode (BLE), Peripheral Mode
Transmit Power (Max)
+4 dBm
Weight
.035 oz (< 1g)
Wireless Specification
Bluetooth Version 4.0 Peripheral Mode

Documentation

Name Part Type Last Updated
Product Brief - BL600.pdf DVK-BL600-ST Product Brief 09/05/2024
Datasheet - BL600 DVK-BL600-ST Datasheet 09/05/2024

Buy Now

Distributor Part In Stock Region Buy
Avnet DVK-BL600-ST 0 North America Buy Now
Future Electronics DVK-BL600-ST 0 North America Buy Now
Mouser DVK-BL600-ST 0 North America Buy Now


FAQ

Where can I download UwTerminal as referenced in the BT900 or BL600 User Guides?

The BT900 and BL600 documents refer to the UwTerminal utility which was the primary utility when these documents were written. This utility is still available in the firmware zip files when they are downloaded from the BT900 Product Page or BL600 Product Page .

However, UwTerminalX is the new improved version of UwTerminal offering additional features not available in predecessor UwTerminal. We recommend working with UwTerminalX as it will support all the features mentioned in the BT900 documentation and offer the additional features, such as access to online Xcompilers.

The latest release of UwTerminalX can be downloaded from our GitHub Repository: UwTerminalX/releases


 

What could be causing additional power draw when in standby doze state?

There are several functions within an application that can increase current consumption above the measurement indicated in the Datasheet for standby doze, low power mode.

  • Timers
  • GPIOs held in an asserted state
  • LEDs
  • Nested functions - which keep the module from entering the standby doze state
  • UART (when open)

 

How can I connect a Bluetooth Low Energy Device to a PC?

Bluetooth Low Energy uses Services as opposed to the set of standardized profiles that exists for Classic Bluetooth. While some Bluetooth Low Energy services have been standardized by the Bluetooth SIG, the development of custom services is allowed to meet custom application requirements.
 
Because Bluetooth Low Energy uses a completely different protocol than Classic Bluetooth and supports custom services, Bluetooth Low Energy devices cannot connect to a computer through the typical Bluetooth configuration of a computer. Therefore, connecting to a PC requires writing and running a Bluetooth Low Energy Central Role/Client application to collect the data sent from the Bluetooth Low Energy peripheral modules. Application development for PCs and Mobile devices is outside the scope of our support. Alternatively, a BL654 USB dongle could be used as a BLE Central Role device, to collect the BLE data and pass it to the PC over a COM Port. However, you would still need an application to view and process the data received over that COM Port.
 
We generally recommend customers who are new to Bluetooth Low Energy obtain a copy of Getting Started with Bluetooth Low Energy to help them understand the Bluetooth Low Energy protocol and the GATT table. There are also many resources available online which explain this. 

When Bluetooth Low Energy was first introduced and we launched our BL6xx product line (predecessors to the BL65x series) we produced the BL600 and BL620 smartBASIC Application Walkthrough document, which provides an overview of how Bluetooth Low Energy works and how a GATT table is constructed. 

Online Xcompiler is not accessible is there a way to Xcompile a smartBASIC Application locally when using UwTerminalX?

If you are having issues using the Online Xcompilers it could be related to security settings in your system which may be blocking access to the Online Xcompilers. If you are not able to resolve this it is possible to Xcompile locally by following the steps below:

  1. Disable (uncheck) the Online XCompilers on the Config Tab in UwTerminalX as shown below:
  2. Locate the Xcomp_mmmmm_xxxx_xxxx.exe file in the firmware zip folder (downloaded from module's Product Page) for the version of firmware loaded to the module.
    Note: the Xcomp version MUST match the firmware version loaded to the module or the application will not compile.
    mmmmm = module
    xxxx_xxxx =Xcomp version
  3. Copy or Move the Xcomp_mmmmm_xxxx_xxxx.exe to the same folder the smartBASIC application is stored in as shown below:

You should now be able to Xcompile the application using UwTerminalX by right-clicking in the terminal and selecting one of the Xcompile options :

  • Xcompile
  • Xcompile+Load
  • Xcompile+Load+Run

Select the application from the folder where the Xcomp file is located. UwTerminalX will now look for the local Xcompiler in the application folder.