Knowledge Base

Reset Search



NCOS: SDK v2.0 Application Development Guide

« Go Back



NCOS SDK v2.0 Application Development Guide

Quick Links


Developer Community

Cradlepoint Knowledge Base

NCOS Python Environment

Computer Setup Instructions

NCOS Development Mode

Application Directory Structure

Application Package Anatomy

SDK Instructions Overview

NCOS Syslog for Debugging

NCM Application Deployment

Sample Application Walk Through


Cradlepoint’s NCOS device Application Framework provides the ability to add intelligence in the device. Applications written in Python can be securely downloaded to the device via Network Cloud Manager (NCM). This allows for extended device features, FOG Computing, and IoT management.

At a high level, the Cradlepoint NCOS Device Apps/SDK is a mechanism to package a collection of files – including executable files – in an archive, which can be transferred securely via NCM, hidden within a Cradlepoint device, and executed as an extension to normal firmware.

What is Supported?

For the scope of this document, NCOS Apps are limited to the non-privileged Python scripts. Supported functionality:

  • Standard TCP/UDP/SSL socket servers function on ports higher than 1024.
  • Standard TCP/UDP/SSL socket client to other devices (or the device as
  • Access to serial ports via the PySerial module, including native and USB-serial ports.
  • Ability to PING external devices.
  • UI Extensibility (i.e. Hot Spot splash page or other UI WEB pages)
  • Access to the NCOS API (aka: status and control tree data).
  • USB Memory device file access.

What is not Supported?

  • Any form of natively compiled or kernel linked code.
  • Any function requiring privileged (or root) permissions.
  • Access to shared resources (for example: no ability to issue custom AT commands to cell modems).
  • Modifications of routing or security behavior.

Supported NCOS Devices

The supported set of devices is:

  • AER – 1600/1650, 2100, 3100/3150
  • COR – IBR1100/1150, IBR900/IBR950, IBR600B/IBR650B, IBR350
  • ARC - CBA850

New NCOS products will support Python applications unless they are a special low-function, low-cost model.

Application Development

During development, an application can be directly installed into a 'DEV Mode' device. This makes it easier to debug and work through the development process. Once the application has been fully debugged and is ready for deployment, it can be installed via NCM at the group level.

SDK Toolset

Cradlepoint has a simplified SDK, written in python, which builds and creates an app package. The SDK, along with sample applications is located here.

For app development, the SDK is used to install, start, stop, uninstall, and check status of the application in a locally connected development device. The application package is the same for local debugging or for uploading to the NCM for production deployment. Application development can be done on Linux, OS X, and Windows operating systems with the same SDK.

This document is specifically written for SDK version 2.0 and above.

Developer Community

Cradlepoint has a Developer Community Portal to leverage knowledge, share, and collaborate with other developers. This forum is also actively monitored by Cradlepoint to answer questions.

Cradlepoint Knowledge Base

The existing Cradlepoint Knowledge Base also has many articles related to NCOS applications and the SDK.

NCOS Python Environment

Application are written in python. However, NCOS only contains a subset of a typical python installation on a computer. The list of python modules in the NCOS device can be obtained by installing sample app python_module_list which is included with the SDK. This application will list all of the python modules in the logs.

New python files can be added to your application but their dependencies must also adhere to the NCOS python environment. These new python files/modules can be copied to the main application directory or can be installed using pip. If pip is used, any 'egg' or 'dist' directories can be deleted as they are not required for functionality and will just use up memory unnecessarily when installed into the NCOS device.

Example pip command: pip(3) install --ignore-install --target=<path to application directory> <python module name>

note: Use pip on Windows and pip3 on Linux or OS X.

Computer Setup Instructions

The SDK and sample apps can be downloaded from Below are the setup instruction for:


  1. Install python 3.5.1 from

  2. Add Linux development libraries.

    sudo apt-get install libffi-dev
    sudo apt-get install libssl-dev
    sudo apt-get install sshpass
  3. Install python libraries.

    sudo apt-get install python3-pip
    pip3 install requests
    pip3 install pyopenssl
    pip3 install cryptography
  4. Useful tools

    PyCharm (community version is free):

Mac OS X

  1. Install python 3.5.1 from

  2. Install HomeBrew for package updates.

    /usr/bin/ruby -e "$(curl -fsSL"
  3. Install required libraries.

    brew install openssl
    brew install
  4. Install python libraries.

    pip3 install -U pip
    pip3 install requests
    pip3 install pyopenssl
    pip3 install cryptography
  5. Useful tools

    PyCharm (community version is free):


  1. Install python 3.5.1 from
  2. The SDK requires OpenSSL tools to generate digital signatures. Go here and download the 'Light' version based on your machine (i.e. Win64 or Win32). Then run the executable after it is downloaded to install.

  3. Open a terminal window and use the following commands to install python libraries.

    python -m pip install -U pip
    python -m pip install pyserial
    python -m pip install requests
    python -m pip install pyopenssl
  4. Useful tools
    1. Putty:
    2. PyCharm (community version is free):
    3. 7-zip:
    4. MarkdownPad:

SDK/Apps Directory Structure

Below is the directory structure for for the SDK and sample applications. The BOLD items are modified or created by the developer. The other files are used by the SDK or are referenced by the other files.

  • NCOS_Apps (directory)
    • app_template (directory for the application)
      • package.ini - App initialization items.
      • - The app python code. There can be multiple py files based on the app design.
      • - This is included with every sample app and should be in your app. It contains a CSClient class which is a wrapper for the TCP interface to the device config store (i.e. the NCOS JSON API trees).
      • - If included, this contains a class which can be used to generate NCOS syslogs at different levels (i.e. info, debug, error, etc.). Can be found in the common directory of the SDK.
      • - Runs on app installation. (update with app name)
      • - Script that starts an app (i.e. cppython start).
      • - Script that stops an app (i.e. cppython stop).
    • config (directory)
      • - Build system config settings (i.e. NCOS Device MAC, IP, Username, Password, etc.).
    • common
      • - This is included with every sample app and can be copied into your app directory. It contains a CSClient class which is a wrapper for the TCP.
    • tools (directory)
      • bin (directory)
        • - Used by SDK.
        • - Used by SDK.
        • pscp.exe - An executable use on Windows by the SDK.
    • sdk_setting.ini - Used by the SDK and contains the settings for building the app and connecting to the local NCOS device.
    • NCOS_SDK_V2.0_Application_Development_Guide.html
    • NCOS_APIs_for_Applications.html
    • GNU_Make_README.html

Based on the sdk_setting.ini file, the SDK will build all files located in the app_name directory into a tar.gz package that can then been installed into the device. This installation is either directly into the device (if in DEV mode) or via NCM for grouped devices.

Application Package Anatomy

A NCOS application package, which is a tar.gz archive, consists of a set of files that includes the python executable, start/stop scripts, initialization files, along with manifest and signature files. This package of files is built by the SDK base on the sdk_settings.ini. Some of these files, like the manifest and signature files, are created by the Make tool. Others are created by the application developer. Below are the example contents for a tar.gz archive created for a NCOS application.

  • app_name (directory)
    • METADATA (directory)
      • MANIFEST.json - Contains a file list along with hash signatures and other app the package initialization data.
      • SIGNATURE.DS - A signature file for the app package.
    • - The application python executable file.
    • - Another python file used by the app. There could be multiple python files depending on the application design.
    • package.ini - The package initialization data.
    • - The script run during installation.
    • - The script run when the app is started.
    • - The script run when the app is stopped


This initialization file contains information and about the application and items that affect installation and execution. This information will stored in /status/system/sdk within the NCOS config store for installed apps.

For example:

notes=Hello World Demo Application
  • [hello_world]

    This must contain the name of the application. In this example, hello_world is the application name.

  • uuid

    Every app must contain a universally unique identifier (UUID).

  • vendor

    This is the vendor name for the app.

  • notes

    Add notes to describe the app or anything else.

  • firmware_major and firmware_minor

    This is the required device firmware version for the app. Not implemented at this time.

  • restart If set to 'true', the application will be restarted if it dies or is not running. If false, the device will not attempt to restart the application. d

  • reboot If set to 'true', the application will be started following a device reboot. Otherwise, it will not be restarted.

  • version_major and version_minor

    This contains the app version. This must be incremented for any new production app used installed via NCM. It will not re-install the same version that already exist in the device.

  • auto_start

    If set to 'true', the app will automatically start after installation.

This script is executed when the application is installed in the device. Typically it will just add logs for the installation.

For example:

echo "INSTALLATION hello_world on:" >> install.log
date >> install.log

This script is executed to start the application in the device. It contains the command to start the python script and pass any arguments.

For example:

cppython start

This script is executed when the application is stopped in the device. It contains the command to stop the python script.

For example:

cppython stop

SDK Instructions Overview

The SDK includes a python file which is compatible for Windows, Linux and OS X platforms.

SDK actions are:

default (i.e. no action given): Print a help file

clean: Clean all project artifacts. Entails execution of all "-clean" make targets.

build or package: Create the app archive tar.gz file.

status: Fetch and print current app status from the locally connected device.

install: Secure copy the app archive to a locally connected device. The device must already be in SDK DEV mode via registration and licensing in NCM. Note: A 'Connection reset by peer' error will be displayed even when the application is successfully copied to the device. This occurs when the device drops the connections after the file copy is complete.

start: Start the app on the locally connected device.

stop: Stop the app on the locally connected device.

uninstall: Uninstall the app from the locally connected device.

purge: Purge all apps from the locally connected device.

uuid: This will create a new UUID for the app and write it to the package.ini file.

SDK Usage

All SDK functions are contained in the python file. While this executable is the same regardless of the workstation platform, the python command is not. Use the following python command based on your platform:

  • Linux or OS X:

  • Windows:


The command structure is:

python(3) <action>

The usage is as follows:

  1. Update the sdk_setting.ini file based on your needs.


  2. Update the UUID in the package.ini file located in the app directory.


  3. Build the application package.

    python(3) build
  4. Test connectivity with your device via the status target.

    python(3) status
        "data": {},
        "success": true
  5. Install the application on your device.

    python(3) install
    admin@'s password: 
    hspt.tar.gz                          100% 1439     1.4KB/s   00:00    
    Received disconnect from 11: Bye Bye
    lost connection
  6. Get the application execution status from your device.

    python(3) status
        "data": {
            "7042c8fd-fe7a-4846-aed1-e3f8d6a1c91c": {
                "app": {
                    "date": "2015-12-04T09:30:39.656151",
                    "name": "hspt",
                    "restart": true,
                    "uuid": "7042c8fd-fe7a-4846-aed1-e3f8d6a1c91c",
                    "vendor": "Cradlebox",
                    "version_major": 1,
                    "version_minor": 1
                "base_directory": "/var/mnt/sdk/apps/7042c8fd-fe7a-4846-aed1-e3f8d6a1c91c",
                "directory": hspt",
                "filename": "dist/tmp_znv2t",
                "state": "started",
                "summary": "Package started successfully",
                "type": "development",
                "url": "file:///var/tmp/tmpg1385l",
                "uuid": "7042c8fd-fe7a-4846-aed1-e3f8d6a1c91c"
        "success": true
  7. Uninstall the application from your device.

    python(3) uninstall
        "data": "uninstall 7042c8fd-fe7a-4846-aed1-e3f8d6a1c91c",
        "success": true

NCOS Syslog for Debugging

Application debugging is accomplished with the use of debug syslogs. However, the default logging level in the NCOS device is set to info so this will need to be changed to debug. It is also possible to send the device logs to a syslog server running on another device. For more information, see the Knowledge Base article 'Understanding Router Log Files'.

You can also view logs via CLI commands when logged into the NCOS device console. This console is available by logging into the device with Secure Shell (i.e. ssh) or by selecting the 'Device Console' from 'System > System Control > Device Options' in the device UI. The logs can be viewed or cleared with the following CLI commands:

log (displays logs in the terminal window)
log -s <text> (search for logs that contain <text> and displays them)
log -s -i <text> (search for logs that contain <text> but case insensitive)
log clear (clears the log buffer)
help log (display the log command options)

NCOS Development Mode

In order to install an application directly to the device without using NCM, the NCOS device must be placed in DEV mode. One would typically debug and test an application using DEV mode prior to using NCM for installation. DEV mode allows for quicker and easier testing and debugging. Instructions for setting up an NCOS device for DEV mode is in Knowledge Base article 'SDK Enable Developer Mode'.

NCM Application Deployment

NCM is used to securely deploy applications to devices at the group level. If an application tar.gz package is uploaded to NCM and then assigned to a NCOS device group, NCM will then securely download and install the application to the devices within the group. For security, the application files are not user accessible within NCM or devices. That is, one is not able to download the application from the device or NCM.

Sample Application Walk Through

Cradlepoint has provided several sample applications with the SDK which is located here. Any of these apps can be used as a starting point for your application. The application data structure is described here.

When using the SDK file, be sure to invoke the proper python command based on your computer OS.

  • Linux or OS X:

  • Windows:


How to Run the Hello World Sample App

  1. Download the SDK and sample apps from here.
  2. Ensure your computer has been setup. See Computer Setup Instructions.
  3. Connect the NCOS device to your computer. This can be done by connecting the LAN port of the device to the USB port of your computer via a USB to Ethernet adapter.
  4. Ensure the device is in DEV Mode. See here.
  5. Enable Debug logs in the device which is very helpful. See here
  6. Open a terminal window.
  7. Change directory to sample_apps. Depending on the version of the SDK that was downloaded, this could be 'sample_apps' or 'sdk_samples-2.1', etc.
  8. Update the sdk_settings.ini to utilize the hello_world app.


  9. Verify device connectivity via:

    $ python(3) status
  10. Create the application package

    $ python(3) build
  11. Install the application package. Note: A 'Connection reset by peer' error will be displayed even when the application is successfully copied to the device. This occurs when the device drops the connections after the file copy is complete.

    $ python(3) install
  12. Check the application status to ensure it has started.

    $ python(3) status
  13. Also check the logs in the device to ensure the application is creating 'Hello World' logs. In the device console use the 'log' command.

Published Date: 4-6-2018

This article not have what you need? Not find what you were looking for? Think this article can be improved? Please let us know at



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255