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
Guides & Tutorials
Collecting Sensor Data
Routing Data to Cloud
Building Edge ML Applications
Best Practices for Production-Ready Projects
Twilio SMS Guide
Fleet Admin Guide
Using the Notehub API
Notecard Guides
Guide Listing
Asset Tracking
Attention Pin Guide
Connecting to a Wi-Fi Access Point
Debugging with the FTDI Debug Cable
Diagnosing Cellular Connectivity Issues
Diagnosing GPS Issues
Encrypting and Decrypting Data with the Notecard
Feather MCU Low Power Management
Minimizing Latency
Notecard Communication Without a Library
Recovering a Bricked Notecard
Remote Command and Control
Sending and Receiving Large Binary Objects
Serial-Over-I2C Protocol
Understanding Environment Variables
Understanding Notecard Penalty Boxes
Types of Penalty BoxesInsufficient Power SupplyNetwork Registration FailureInability to Connect to NotehubInability to Acquire GPS Satellite Fix
Updating ESP32 Host Firmware
Using External SIM Cards
Using JSONata to Transform JSON
homechevron_rightDocschevron_rightGuides & Tutorialschevron_rightNotecard Guideschevron_rightUnderstanding Notecard Penalty Boxes

Understanding the Notecard Penalty Boxes

If you have a Notecard that is no longer communicating with Notehub or is repeatedly unable to connect to a cellular network, the Notecard may have been placed in a figurative "penalty box".

note

If lack of a reliable cellular connection is the reason your Notecard is not functional, you can get help troubleshooting your connection in this guide on Diagnosing Cellular Connectivity.

What is a Penalty Box?

A penalty box is a state in which the Notecard is isolated and not allowed to even attempt a connection to a cellular network. Repeating a network connection failure multiple times can unnecessarily drain an attached battery. Therefore, the penalty box is set up to preserve battery life while also occasionally "opening up" and allowing the Notecard to attempt a new connection at certain intervals.

If you have enabled the capture of trace logs on a Notecard, you may see log events that refer to the penalty box, such as:

{"text":"penalty: entering penalty box: connect delayed (89 min remaining): can't open session to notehub: socket open PPP: ppp connection timeout? {service}{extended-service-failure}"}

{"text":"penalty: removed from penalty box: penalty period expired"}

In this guide we will look at the reasons why a Notecard may be placed in a penalty box and under which conditions a Notecard may be removed from a penalty box.

note

The failure of a Notecard to sync with Notehub does not necessarily mean it is in a penalty box. It could also be due the use of an invalid ProductUID or incorrect Notehub host name. These can be diagnosed in the response to a hub.sync.status command. For example:

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

{"alert":true,"status":"connect delayed (60 min remaining): can't open session to discovery service: socket: cannot find host: blah.notefile.net {service}{host-unreachable} {service}{extended-service-failure}","time":1638397092,"completed":24}

Types of Penalty Boxes

There are four types of penalty boxes that a Notecard may enter after repeated failures:

  1. Insufficient Power Supply
  2. Network Registration Failure
  3. Inability to Connect to Notehub
  4. Inability to Acquire GPS Satellite Fix

Each penalty box is explained below including commands on how to manually remove a Notecard from a penalty box (when available).

Insufficient Power Supply

If the Notecard reboots due to insufficient current supply while the modem is trying to register the Notecard on a cellular network, it will enter a penalty box. If the reboot is due to a card.restart, card.restore, or a DFU-induced restart, the Notecard will not enter a penalty box.

The length of time the Notecard is in the penalty box is 1/2 of the outbound sync interval or 120 minutes (whichever is greater). For each subsequent failure during modem registration, the penalty box interval grows by 120 minutes, up to a maximum of three days.

The Notecard will be released from the penalty box upon a successful registration on a cellular network, or if the host issues any of the following:

  1. A hub.sync request with the allow:true parameter.
  2. A card.wireless.penalty request with the reset:true parameter.
  3. A hub.log request with the sync:true parameter.
  4. Any change sent in a hub.set request.

Network Registration Failure

If the cellular modem on the Notecard cannot register with a network within 120 seconds (or within 15 minutes if using NB-IoT), the Notecard will enter a network registration penalty box.

The length of time the Notecard is in the penalty box is extended by each subsequent network registration failure, by a minimum of 15 minutes. For each failure the previous delay is multiplied by 1.25 + 15 minutes, up to a maximum of 3 days. For example, the first set of retry intervals (in minutes) are: 15, 34, 58, 86, 123, 169, 227, and 298.

note

As of Notecard firmware v5.3.1, if the Notecard is connected over USB, three short 3-8 minute retries will occur before it is placed into a network registration failure penalty box.

The Notecard will be released from the penalty box upon a successful registration on a cellular network, or if the host issues any of the following:

  1. A hub.sync request with the allow:true parameter.
  2. A card.wireless.penalty request with the reset:true parameter.
  3. A hub.log request with the sync:true parameter.
  4. Any change sent in a hub.set request.

Overriding Network Registration Penalty Box Settings

warning

The misuse of this feature may result in the cellular carrier preventing the Notecard from future connections because it's effectively "spamming" the network. The cellular carrier may blacklist devices that it thinks are attempting to connect too frequently.

The default settings that determine the duration of the Network Registration Penalty Box are calculated based on the number of consecutive registration failures and can be overridden at runtime by using the card.wireless.penalty API:

{
   "req":  "card.wireless.penalty",
   "set":  true,
   "rate": <PenaltyMultiplierRate(float)>,
   "add":  <PenaltyAddMins>,
   "max":  <PenaltyMaxMins>,
   "min":  <PenaltyMinMins>
}
note

If overriding the default settings with this API request, all of the above fields MUST be specified.

When using this API request, the first retry interval is PenaltyMinMins. For each successive failure, the prior delay is multiplied by PenaltyMultiplierRate plus another PenaltyAddMins is added, up to a maximum of PenaltyMaxMins.

For example, by sending the following request, the retry intervals would be 5, 20, 50, 110, 230, 470, and 720 minutes:

{"req":"card.wireless.penalty","set":true,"rate":2.0,"add":10,"max":720,"min":5}

Likewise, the default settings for a Network Registration Penalty Box can be also overridden with the environment variable _wireless_penalty:

_wireless_penalty = <PenaltyMultiplierRate(float)>,<PenaltyAddMins>,<PenaltyMinMins>,<PenaltyMaxMins>

Inability to Connect to Notehub

If the cellular modem can successfully register with the network, but is unable to connect to Notehub, the Notecard may be placed in a "Notehub connection failure" penalty box.

The Notecard will enter this penalty box if connection failures to Notehub happen more than 3 consecutive times (if the Notecard is battery-powered) or 6 consecutive times (if the Notecard is USB/line-powered). The Notecard will remain in the penalty box for 1/2 of the configured outbound sync interval or 60 minutes, whichever is greater. Note that this penalty box will only come into play if there are no other network registration or power-related errors.

The Notecard will be released from the penalty box upon a successful connection to Notehub, or if the host issues any of the following:

  1. A hub.sync request with the allow:true parameter.
  2. A card.wireless.penalty request with the reset:true parameter.
  3. A hub.log request with the sync:true parameter.
  4. Any change sent in a hub.set request.

Inability to Acquire GPS Satellite Fix

If the Notecard is configured to acquire its location via GNSS (GPS) but is unable to make a position fix, it may be placed in a penalty box (provided all of the following conditions are met):

  1. The device is in motion (as determined by the on-board accelerometer).
  2. At least one GPS satellite is visible.
  3. A GPS position fix is NOT made within 15 minutes.
note

If the GPS is not able to track any satellites at all, it is powered off after 90 seconds of searching and not placed in a penalty box (or it will be removed from the penalty box if it was already in one).

The length of time the Notecard is in the penalty box is 30 minutes multiplied by the number of consecutive GPS position fix failures (up to a maximum of 12 hours). This maximum duration of 12 hours would be reached after approximately 5 days of continuous GPS position fix failures.

The Notecard will be released from the penalty box if either:

  1. The GPS makes a valid position fix.
  2. The GPS is unable to track any satellites for 90 seconds.

Additional Resources

  • Capture Trace Logs
  • card.wireless.penalty API
  • Notecard Error and Status Codes
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