• CUWB v5.0
CUWB USB Driver

Overview

This guide assumes that Ubuntu 22.04 or 24.04 is installed on the Host PC or the other PC that will be interacting with USB enabled series 300 devices.

Installation

Host PC Requirements

  • OS: Ubuntu 22.04 Jammy or Ubuntu 24.04 Noble
  • CPU: 64-bit, 2.5GHz, dual-core or better
  • WAN: Must be able to reach ppa.cuwb.io via port 4431
  • RAM: 8 GB or more
  • HD: 32 GB or more

1. Only required for online installation.

Online Installation

Follow the instructions below for CUWB USB Driver installation. When prompted in the “CUWB Applications Selection”, ensure that CUWB USB Driver is selected for installation.

  1. Follow best practices and review the install.sh script.
  2. bash <(wget -qO- https://cuwb.io/docs/v5.0/assets/install.sh)
  3. Paste into an Ubuntu 22.04/24.04 terminal and press Enter

Offline Installation

The CUWB USB Driver can be installed on Host PCs that do not have PPA access.

For instructions on how to obtain the DEB package, see Current Downloads Available for Software Packages. After downloading the package, transfer the DEB to a USB drive or other transfer method to the Host PC. After transferring the file, navigate to the file location, and type the command below into a terminal window to install the package:

sudo apt install ./cuwb-usb-interface_<version>_amd64.deb

Getting Started

The PT301 communicates over USB to the local PC. The CUWB Manager Package speaks Ethernet, not USB. The CUWB USB Driver allows for making USB devices (PT301, etc.) operate on the CUWBNet as an Ethernet based UWB device. It is required that for every PT301 device on the computer, there’s an instance of the CUWB USB Driver running. That can be achieved either by launching the clients manually for every device, or by running the CUWB USB Driver.

Setup

Plug in the PT301(s) that are going to be used as wired devices on the CUWBNet.

For PT301s, determine which USB interfaces(s) belong to the devices(s):

> ls /dev/ttyUSB*
/dev/ttyUSB0 /dev/ttyUSB1

Here in our example we have two PT301s connected to the local PC.

Determine which network interface you would like the PT301 to attach to:

> ifconfig
enps4s0   Link encap:Ethernet  HWaddr 1c:6f:65:d3:38:b1
          inet addr: 10.132.39.0  Bcast: 10.132.255.255  Mask: 255.255.0.0
          inet6 addr: fe80::1e6f::65ff::fed3:38b1/64  Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU: 1500 Metric: 1
          RX packets: 464430022 errors: 0 dropped: 0 overruns: 0 frame: 0
          TX packets: 4816244 errors: 0 dropped: 0 overuns: 0 carrier: 0
          collisions: 0 txqueuelen: 1000
          RX bytes: 118178068277 (118.1 GB) TX bytes: 854053251 (854.0 MB)

Or if using the PT301 on the same PC that is running CUWB Manager Package, lo is allowed:

> ifconfig
lo        Link encap: Local Loopback
          inet addr: 127.0.0.1 Mask: 255.0.0.0
          inet6 addr: ::1/128 Scope: Host
          UP LOOPBACK RUNNING MTU: 65536 Metric: 1
          RX packets: 8780339 errors: 0 dropped: 0 overruns: 0 frame: 0
          TX packets: 8780339 errors: 0 dropped: 0 overruns: 0 carrier: 0
          collisions: 0 txqueuelen: 1
          RX bytes: 1187951355 (1.1 GB) TX bytes: 1187951355 (1.1 GB)

Running the CUWB USB Driver

Run the CUWB USB Driver Client:

> cuwb-usb-interface-client /dev/ttyUSB0 lo

Alternatively, the CUWB USB Driver Daemon will dynamically attach ttyACM and ttyUSB devices to the selected interface:

> sudo cuwb-usb-interface-daemon lo

Stopping the CUWB USB Driver

The driver can be stopped by using ctrl+c.

Revision

Version Date Change Description
v5.0.1 2025-11-14 Updating Host PC Requirements
v5.0.0 2025-10-31 Initial Preliminary Release

APPENDIX A : License Terms and Conditions


APPENDIX B : Software License Attributions