IN100 NanoBeacon
Overview
The IN100 is InPlay’s first NanoBeacon SoC — a Bluetooth 5.3 chip that requires zero firmware development. Instead of writing and compiling code, you configure the device through InPlay’s NanoBeacon Config Tool desktop application. The BLE advertising protocol is implemented directly in hardware circuitry, which means the IN100 broadcasts immediately after configuration with no compiler, no RTOS, and no application code.
This makes the IN100 fundamentally different from every other BLE SoC on the market. It is designed for applications where cost, size, and simplicity matter more than programmability: asset tags, smart labels, active RFID replacements, and wireless sensor beacons.
Quick Specifications
| Specification | Details |
|---|---|
| Manufacturer | InPlay |
| SoC | IN100 |
| Bluetooth | BLE 5.3 |
| Programming | Programming-free (NanoBeacon Config Tool) |
| Package (DFN8) | 2.5 × 2.5 × 0.8 mm |
| Package (WLCSP) | 2.0 × 1.1 × 0.35 mm |
| Operating Voltage | 1.1V to 3.6V |
| Power Consumption | < 1 µW (advertising mode) |
| Sensor Interfaces | I2C, ADC, GPIO, 1-wire |
Key Features
- No firmware development required — configure via desktop GUI, flash, and go
- Bluetooth 5.3 with iBeacon, Eddystone, and custom beacon format support
- World’s smallest BLE SoC in WLCSP package (2.0 × 1.1 mm)
- Ultra-low power — sub-microwatt advertising enables 10+ year battery life on a coin cell
- Wide voltage range (1.1V–3.6V) — compatible with coin cells, printed batteries, and energy harvesting
- No external crystal required — integrated oscillator reduces BOM to as few as 3 external components
- Built-in temperature sensor and VCC measurement
- Sensor interfaces — I2C, ADC, GPIO, 1-wire for connecting external sensors
- Host Controller API — optional UART interface for MCU-driven dynamic configuration
How the IN100 Differs from Traditional BLE SoCs
| Traditional BLE SoC (nRF52, ESP32, CC2340, etc.) | IN100 NanoBeacon | |
|---|---|---|
| Development | Write firmware in C, compile, flash | Configure via GUI tool, flash |
| RTOS | Zephyr, FreeRTOS, or bare-metal | None required |
| Toolchain | GCC, IDE, SDK, debugger | NanoBeacon Config Tool only |
| Time to first advertisement | Hours to days | Minutes |
| BOM complexity | 10–20+ external components | 3 external components typical |
| Programmability | Full application logic | Advertising configuration only |
| Bidirectional communication | Yes (GATT connections) | No (broadcast only) |
| Unit cost at volume | $1.50–$4.00 | ~$1.00 target |
The IN100 is not a general-purpose MCU. It cannot run application logic, establish GATT connections, or perform complex computations. It excels at one thing: broadcasting BLE advertisements with sensor data at the lowest possible cost and power.
Getting Started with Hubble
Prerequisites
Before you begin, ensure you have:
- IN100 development board (or SparkFun NanoBeacon Board)
- IN100 programmer board (included with InPlay eval kit)
- USB-A to Micro-USB cable
- NanoBeacon Config Tool installed (macOS, Windows, Linux)
- Hubble Network account
Configure and Flash
Unlike other boards in the Hubble ecosystem, the IN100 does not use west build or any compiler toolchain. Configuration is done entirely through the NanoBeacon Config Tool:
- Connect the programmer board to your PC via USB
- Connect the IN100 dev board to the programmer board
- Open the NanoBeacon Config Tool
- Configure your advertising parameters (interval, payload, sensor data)
- Click Run in RAM to test, or Burn/Program to write permanently
Verify Broadcast
After configuration, verify the IN100 is advertising using a BLE scanner app:
- Open nRF Connect (iOS/Android) or LightBlue on your smartphone
- Scan for nearby BLE devices
- Look for your configured device name (e.g. “IN100”)
- Tap the device to inspect the advertising payload
You should see your configured data including device name, VCC measurement, and temperature reading in the manufacturer-specific data field.
Advertising Payload
The IN100 supports standard BLE advertising formats:
- iBeacon — UUID, Major, Minor values for proximity detection
- Eddystone — URL, UID, and TLM frame types
- Custom — manufacturer-specific data with sensor readings
Built-in data sources that can be included in the advertising payload without external hardware:
- Internal temperature sensor (convertible to °C)
- VCC voltage measurement (convertible to V)
- GPIO state (digital input)
- ADC readings (from external analog sensors)
- I2C sensor data (from connected I2C devices)
Power Considerations
The IN100 is designed for multi-year operation on the smallest batteries:
- Advertising power: < 1 µW at typical intervals
- Target battery life: 10+ years on a CR2032 coin cell at 1-second advertising interval
- Printed battery compatible: 1.1V minimum operating voltage enables paper-thin battery designs for smart labels
- No sleep mode management required — the hardware handles all power state transitions automatically
Development Boards
InPlay IN100 Evaluation Kit
- Includes programmer board and IN100 dev board
- Direct connection to NanoBeacon Config Tool
- Available from InPlay
SparkFun NanoBeacon Board - IN100
- Qwiic connector for easy I2C sensor integration
- 12mm coin cell holder (CR1225)
- Male headers pre-soldered
- Available from SparkFun
Troubleshooting
Device not detected by Config Tool
- Ensure the programmer board is connected via USB (not the dev board directly)
- Verify the dev board is properly seated on the programmer board
- Check that the Chip Enable jumper (P1) is in the correct position
No BLE advertisement visible
- Verify configuration was written successfully (check Config Tool status)
- Ensure a power source is connected (USB via programmer, or coin cell on SparkFun board)
- Move your phone closer — default TX power may be low
- Try a different BLE scanner app
Sensor data not appearing in payload
- Verify the sensor is connected to the correct interface (I2C address, ADC pin, GPIO pin)
- Check Config Tool sensor configuration matches your wiring
- Ensure the sensor’s operating voltage is within the IN100’s supply range
Resources
Official Documentation
Community
- NanoBeacon GitHub — examples, Host Controller API, sensor guides
- SparkFun NanoBeacon Board
- Hackster.io Getting Started Project