Scaling an IoT deployment? Join our webinar on May 28th where we dive into real-world scaling pain points and how to overcome them.

Blues Developers
What’s New
Resources
Blog
Technical articles for developers
Newsletter
The monthly Blues developer newsletter
Terminal
Connect to a Notecard in your browser
Developer Certification
Get certified on wireless connectivity with Blues
Webinars
Listing of Blues technical webinars
Blues.comNotehub.io
Shop
Docs
Button IconHelp
Notehub StatusVisit our Forum
Button IconSign In
Sign In
Sign In
Docs Home
What’s New
Resources
Blog
Technical articles for developers
Newsletter
The monthly Blues developer newsletter
Terminal
Connect to a Notecard in your browser
Developer Certification
Get certified on wireless connectivity with Blues
Webinars
Listing of Blues technical webinars
Blues.comNotehub.io
Shop
Docs
Quickstart
Cell+WiFi Quickstart
LoRaWAN Quickstart
Starnote Quickstart
Wireless for Arduino Opta Quickstart
Notecard Quickstart
IntroductionBefore You BeginConnect Your Notecard and NotecarrierSet up NotehubSet up NotecardQueue Notes to your NotecardSend Notes from Notecard to NotehubView Notes on NotehubSend Notes from Notehub to NotecardNext Steps
Notecard LoRa Quickstart
Cygnet Quickstart
Swan Quickstart
Mojo Quickstart
Sparrow Quickstart
homechevron_rightDocschevron_rightQuickstartchevron_rightNotecard Quickstart

Notecard Quickstart: Notecard and SparkFun Qwiic Cellular

Get started with a
Notecard and SparkFun Qwiic Cellular
Notecard and Notecarrier ANotecard and Notecarrier FNotecard and Notecarrier PiNotecard and Notecarrier XNotecard and SparkFun MicroMod Cellular Function BoardNotecard and SparkFun Qwiic CellularNotecard Simulator

Introduction

Watch a video of this tutorial

This tutorial should take approximately 20-30 minutes to complete.

This guide will introduce you to the Blues ecosystem, including Notecard, Notecarrier, and Notehub.

Throughout this guide, you'll issue serial requests to configure Notecard, simulate sending data from sensors to Notecard, and synchronize that data with the cloud.

By the end of this tutorial, you'll have a basic understanding of the process for building connected solutions with Blues.

Key Concepts to Know

Before you dive in, it's important to understand a few key concepts:

  • Notecard is a device-to-cloud data pump that reduces the complexity of building connected solutions with a secure, reliable cellular, Wi-Fi, or LoRa connection. It's a System-on-Module (SOM) that's ready for embedding into any project.

  • Notecarriers are development boards that help you get started quickly with Notecard. There are a variety of Notecarriers designed to fit different needs, from prototyping with a Feather-based MCU to deploying a production solution.

  • Notehub is the cloud service Notecard uses to securely send and receive data. Notehub also provides a console for fleet management and secure connectors for routing data to 3rd-party cloud applications.

  • A Note is a JSON object containing developer-provided content. A Note is the primary means of sending data to/from a Notecard.

Notecard and Notehub work together to provide bidirectional wireless communication capabilities, both outbound (from your microcontroller or single-board computer to the cloud):

animation of outbound communication from notecard to notehub to cloud

And inbound (from the cloud to your microcontroller or single-board computer):

animation of inbound communication from cloud to notehub to notecard

Before You Begin

To complete this quickstart, make sure you have access to the following:

  • Notecard and SparkFun Qwiic Cellular Kit.

  • USB-C cable for connecting the Notecarrier to your laptop or computer.

  • A browser that supports the Web Serial API, like Chrome, Microsoft Edge, or Opera.
  • If you're using a Cellular Notecard, make sure you're in a location with stable cellular coverage.
  • An internet connection that allows access to Notehub .

Connect Your Notecard and Notecarrier

The SparkFun Qwiic Cellular Kit includes a SparkFun Qwiic Cellular Notecarrier, a Notecard, and two u.FL cables for cellular and GPS (each with one side connected to the Notecarrier and one to the Notecard).

You'll also need an SMA-compatible antenna to connect to a cellular network, and an SMA passive GPS antenna if you want to use the GPS/GNSS capabilities of the Notecard. We've included pictures of common antennas here, but SparkFun has a number of great options to choose from.

note

If your SparkFun Qwiic Notecarrier came with a Notecard pre-installed, you can skip directly to connecting a cellular antenna in step six!

Picture of SparkFun Qwiic Cellular Notecarrier, Notecard, Cellular antenna & GPS antenna

  1. Remove the screw from the mounting receptacle on the SparkFun Qwiic Cellular Notecarrier, and rotate the u.FL cables away from the M.2 socket.

    Image of mounting receptacle on Notecarrier

  2. Place the Notecard into the M.2 slot on the Notecarrier. Once inserted, press gently until the Notecard is inserted and the screw receptacle hole is completely visible.

    Image of notecard plugged into Receptacle

  3. Re-insert the screw into the mounting receptacle and tighten to secure the Notecard to the Notecarrier. Be sure to not overtighten the screw.

    Image of Notecard affixed to Notecarrier

  4. Secure the free end of the u.FL cable connected to the socket labeled LTE on the Notecarrier to the MAIN socket on the Notecard.

    Image of MAIN u.FL cable

  5. Secure the free end of the u.FL cable connected to the socket labeled GPS on the Notecarrier to the GPS socket on the Notecard.

    Image of GPS u.FL cable

  6. Attach your cellular antenna to the SMA connector labeled LTE on the SparkFun Qwiic Cellular Notecarrier and screw to tighten.

    Image of cellular antenna and LTE SMA connection

  7. If using, attach a passive GPS antenna to the SMA connector labeled GPS on the SparkFun Qwiic Cellular Notecarrier and screw to tighten.

    Image of GPS antenna and GPS SMA connection

Now you're ready connect to the Notecard over USB and continue with the Quickstart!

Power Up the Notecard and Notecarrier

Connect a USB-C cable from the Sparkfun Qwiic Cellular's USB port to your computer's USB port.

note

If you're using Notecard WiFi you have one additional step: complete our guide to connecting to a Wi-Fi Access Point, as you'll need a network connection to complete the rest of this tutorial.

Connect to the Notecard

With your Notecard connected your next step is to communicate with the Notecard over USB. To do so, first locate the panel on the right-hand side of your browser window, which we call the In-Browser Terminal.

Within the In-Browser Terminal, click the USB Notecard button. A browser prompt will appear asking for permission to connect to a USB serial device:

Browser prompt for connecting serial

  • If you're on a Mac, select either Notecard (cu.usbmodemNOTE1) or Notecard (tty.usbmodemNOTE1).

  • On Windows, the option will show up as USB Serial Device (COMx).

  • On Linux the option will show up as Notecard (ttyACM0).

Having trouble connecting?
  • Try using a different micro USB cable. Some micro USB cables are only capable of transferring power, not data.

  • If Linux is your operating system, try adding your user to the dialout group. Run the command sudo usermod -aG dialout $USER and restart your computer for the change to take effect (as logging out and back in may not be enough).

Prefer to use the Notecard CLI instead?
  • Visit the Notecard CLI Guide for installation instructions.

  • Once installed, use the notecard -play command to begin interactive request mode.

  • Copy each request from this guide into your CLI console to run it against your connected Notecard.

Validate Serial Connection

Now you're ready to send your first JSON request to the Notecard! All requests and responses to/from the Notecard are in JSON format and are structured with the command as the value of a req key. Additional arguments are written as additional key-value pairs. For example, {"req":"card.version"} or {"req":"hub.set", "mode":"continuous"}.

The first request you'll send invokes the card.version API, which returns metadata about your Notecard.

Copy and paste the following request into the In-Browser Terminal (click the TRY IT button below).

Hit Enter and you'll see a response similar to the example output.

>
{"req":"card.version"}
{
 "version": "notecard-5.3.1",
 "device": "dev:000000000000000",
 "name": "Blues Wireless Notecard",
 "sku": "NOTE-NBGL-500",
 "board": "1.11",
 "cell": true,
 "gps": true,
 "api": 5,
 "body": {
  "org": "Blues Wireless",
  "product": "Notecard",
  "target": "r5",
  "version": "notecard-5.3.1",
  "ver_major": 5,
  "ver_minor": 3,
  "ver_patch": 1,
  "ver_build": 371,
  "built": "Sep  5 2023 12:21:30"
 }
}

Well done! You have properly set up, configured, and validated your hardware. Next, you'll configure your Notecard to communicate with Notehub.

Set up Notehub

Notehub is a secure proxy cloud service that communicates with Notecard, provides tooling for managing fleets of devices, allows you to perform over-the-air Notecard and host MCU firmware updates, and makes it easy for you to route data to your own cloud applications.

In this section, you'll set up a Notehub Project and create your first ProductUID. A ProductUID is the unique identifier you will use to associate a Notecard with a Notehub Project, and ensure that data from Notecard ends up in the right location.

Create a Notehub Project

  1. Sign in or sign up for Notehub using the links below.

    Create a Notehub Account

    Already have an account? Sign in
  2. Click "Create Project" on the dashboard. In the New Project card, give your project a name and ProductUID.

    The dialog for creating a project in Notehub

    note

    The ProductUID must be globally unique. To reduce collisions, Notehub prepends a generated namespace based on your account email, for instance com.your-company.your-name:. Enter any identifier you like in the input on the right.

  3. Take note of your ProductUID. This identifier is used by Notehub to associate a Notecard to your project.

    The location of the ProductUID within a Notehub project

Set up Notecard

Now that you know how to send requests to Notecard, let's next tell Notecard about your Notehub project so it knows where to send data.

To associate Notecard with your project in Notehub you must assign the ProductUID you created to your Notecard. A Notecard can easily be moved between projects over time, but it can only belong to one project at a time

To set the ProductUID, you'll start by sending a hub.set JSON request to your Notecard. Once Notecard has finished processing your request, it will send a JSON response back to your computer to let you know that the request is complete.

An empty JSON object ({}) from Notecard indicates a successful request. If an error occurs, Notecard will return a JSON object with an err key and a string describing the error.

Copy and paste the following Notecard request, making sure to replace com.your-company.your-name:your_product with the ProductUID you created in the last step (click the TRY IT button below).

>
{"req":"hub.set", "product":"com.your-company.your-name:your_product"}
{}

The JSON object above consists of two key-value pairs. The first provides the name of the request, denoted with the key req and a value of hub.set. The second, product, is one of the arguments for the hub.set request. You can see all the arguments for this and all Notecard requests in the API Documentation.

Validate Your ProductUID and Connection

In this section, you'll validate your Notecard configuration by performing a manual sync with Notehub and then request sync status updates from Notecard.

Start a Sync

Initiate a synchronization between Notecard and Notehub with a hub.sync request, as shown below.

>
{"req":"hub.sync"}
{}

Once a sync has started, you can monitor the state of the sync by watching the status bar at the top of the In-Browser Terminal.

In-Browser Terminal sync pending

As soon as you see "Successful Notehub sync [x]s ago", the sync is complete!

In-Browser Terminal sync complete

Optional: Manually check on the state of a sync with the hub.sync.status API

You can also manually check on the state of a sync with a hub.sync.status request. When the sync is ongoing, the response will return a status field with the current progress of the sync and a requested field with the number of seconds since the sync was initiated.

Depending on the timing of your hub.sync.status requests, your responses may differ from what is displayed here:

>
{"req":"hub.sync.status"}
{
  "status": "starting communications {wait-module} {connecting}",
  "requested": 2
}
...
{
  "status": "modem now ON {modem-on}",
  "requested": 6
}
...
{
  "status": "waiting for wireless service 6 sec [+---] {cell-registration-wait}",
  "requested": 12
}

Once the sync has completed, the response to hub.sync.status includes the UNIX Epoch time of the last sync, and the number of seconds since the last completed sync.

>
{"req":"hub.sync.status"}
{
 "time": 1615585299,
 "completed": 4
}

You should now be able to return to Notehub, refresh the Devices page, and see that a device has been added to your project:

device in notehub

Sync not completing, or having trouble connecting?
  1. Check if the response to a hub.sync.status request includes "no project was found" or "can't open Notehub" errors:

    >
    {"req":"hub.sync.status"}
    {
      "status": "opening notehub: no project was found with product UID product:com.your-company.your-name:your_product {product-noexist} {notehub-open-failure}",
      "requested": 10
    }
    ...
    {
      "status": "can't open notehub: opening notehub: no project was found with product UID product:com.your-company.your-name:your_product {product-noexist} {notehub-open-failure}",
      "requested": 11
    }

    If so, you may have a typo, or may have passed a project name to your hub.set request's product instead of a ProductUID. If this is the case, send another hub.set request with the correct product, and then send a hub.sync request.

    REMINDER: The ProductUID is typically in the form of com.your-company.your-name:your_product.

  2. If your ProductUID seems correct, you may have a connectivity issue. Please consult our guide on Diagnosing Cellular Connectivity Issues.

  3. It may be helpful to view a detailed trace of the Notecard's activity during a connection attempt. To do this, type sync-trace into the In-Browser Terminal and press return to initate a sync and start logging. Once the trace is complete, click the save button in the terminal to export the log for further analysis.

  4. If you've tried these troubleshooting steps and are still having issues, please reach out on our community forum .

Why doesn't Notecard sync data immediately?

We designed Notecard to be low-power friendly by default. Notecard is extremely low power in its idle state (consuming only ~8-12µA@5V when idle) and when queuing data with note.add requests, but uses a nontrivial amount of energy when the cellular modem is on and transmitting data to and from a network.

However, Notecard is also very configurable, and you can easily set up a Notecard to synchronize data immediately. You can read more about that approach in our guide on Minimizing Latency.

You're doing great! You have now configured your Notecard and are ready to send Notes to your Notehub Project!

Queue Notes to Your Notecard

In this section, you will add Notes simulating sensor data to your Notecard.

Imagine your Notecard is connected to a Host MCU that reads temperature and humidity data from a sensor. Your sample data might look like this: {"temp":35.5,"humid":56.23}.

To do this, you will use Notecard's note.add API that includes a body argument which accepts any arbitrary JSON data.

Copy and paste the following request into the In-Browser Terminal, then press Enter to send it to your Notecard.

>
{"req":"note.add","body":{"temp":35.5,"humid":56.23}}
{"total":1}

This request will create a Note that includes your JSON body and additional metadata like creation time and location.

As with other requests, the first key-value pair of the JSON specifies the note.add request, but in this case, the argument of body contains a full JSON object of your data as the value. There are a number of other possible arguments to note.add, as listed in the documentation.

In response, Notecard returns a JSON object indicating the total number of Notes ready to sync to Notehub. You won't see your Note in Notehub just yet, because Notecard queues your Notes until it is time to sync them to the cloud.

Excellent work! You have queued your first Note to your Notecard!

Send Notes from Notecard to Notehub

In this section, you'll perform another sync to send your Note to Notehub.

As before, you can manually initiate a sync by entering the following JSON request in the In-Browser Terminal:

>
{"req":"hub.sync"}
{}

Behind the scenes, your Notecard will again search for a network connection and connect to Notehub. Once the connection is made, Notecard uploads your Note and closes the connection.

As before, you can monitor the state of the sync by watching the status bar at the top of the In-Browser Terminal, or use a hub.sync.status request.

By default, Notecard places Notes in a Notefile called data.qo. The .qo extension means that the file is an "outbound queue," or a queue that originates on Notecard and is synchronized with Notehub.

Great work! Your Note has now been transferred from Notecard to the cloud and stored in your Notehub project!

note

Notecard is a low-power device (consuming only ~8-12µA@5V when idle) and is built to be continuously powered. This is important to know because certain features of Notecard require the current time, which is established upon Notecard successfully connecting to a network upon startup.

View Notes on Notehub

In this section, you'll learn how to view and interact with your Note on Notehub.

Sign in or sign up for Notehub using the links below.

Create a Notehub Account

Already have an account? Sign in

Navigate to Notehub.io .

You will see your project dashboard:

List of projects in Notehub

Click on the tile with your Project, and the device dashboard for your Project will load. You'll see your Notecard in the Devices list.

List of devices in Notehub

Click Events in the left-side navigation. In the Events list, you should see your Note in the list with a simulated sensor reading body. Your Note will be listed in the table, along with other session and environment-specific events sent automatically by Notecard.

List of events in Notehub

It's that simple, your product and data are now online!

Send Notes from Notehub to Notecard

It's important to remember that communication between Notecard and Notehub is bi-directional, both outbound (from Notecard to the cloud, as documented above) and inbound (from the cloud to Notecard).

While not part of the quickstart, you can learn more about inbound data syncing in the Notehub Walkthrough.

Next Steps

Congratulations! You've now queued sensor data on a Notecard and sent that data to the cloud!

If you're following the Blues Quickstart, next we recommend setting up your microcontroller:

  1. Use the Notecard to Send Data
  2. Set Up Your Microcontroller
  3. Build Your First IoT App With Blues
  4. Send Data to Your Cloud

At any time, if you find yourself stuck, please reach out on the community forum .

Can we improve this page? Send us feedback
© 2025 Blues Inc.
© 2025 Blues Inc.
TermsPrivacy
Notecard Disconnected
Having trouble connecting?

Try changing your USB cable as some cables do not support transferring data. If that does not solve your problem, contact us at support@blues.com and we will get you set up with another tool to communicate with the Notecard.

Advanced Usage

The help command gives more info.

Connect a Notecard
Use USB to connect and start issuing requests from the browser.
Try Notecard Simulator
Experiment with Notecard's latest firmware on a Simulator assigned to your free Notehub account.

Don't have an account? Sign up