Octant & XE826 Installation Guide

Hardware connection

Product	Host connection	Field interfaces
Octant	External USB host connection	2 × CAN FD · 4 × RS-485 · 2 × RS-232
XE826	Internal USB host connection	2 × CAN FD · 4 × RS-485 · 2 × RS-232

Connect the host
Use the matching USB cable for Octant. Install and secure XE826 with the host powered down, then attach its matching internal USB harness.
Match the field connections
Follow the product and harness labels for each target device. Connect CAN, RS-485 and RS-232 equipment to the corresponding interface.
Match communication settings
Use the same CAN arbitration rate, data rate and FD/BRS settings as the peer. For serial devices, match baud rate, data bits, parity and stop bits.

Windows

Install the driver first
Download and fully extract the matching package below. In its Windows folder, run Xilume_Octant_XE826_Windows_Driver_V7.1.9.0.exe.
Connect and verify the device
Connect the device after installation. In Device Manager, under Ports, check for two CAN FD COM endpoints and six serial COM ports. Windows assigns the COM numbers.
Open CAN FD software
Select the corresponding CAN channel in Xilume CAN FD Control Center, match the bus settings and connect. TraceBox Analyzer Pro provides capture and diagnostic reporting.

CAN FD COM endpoints carry the Xilume CAN command protocol. Use CAN FD Control Center or an application that implements this protocol to exchange frames.

Linux

The package requires Linux 5.4 or later on x86-64 or aarch64, with DKMS, a compiler toolchain and headers matching the running kernel.

Fully extract the driver package and open a terminal in its Linux folder.

chmod +x install.sh uninstall.sh verify.sh
sudo ./install.sh

Reconnect the device after installation, then run the verification script.

./verify.sh

Use the CAN interface names reported by the check. The operating system does not guarantee the names can0 and can1.

The six serial channels are available at /dev/xilume/serial1 through /dev/xilume/serial6.

If installation requests a reboot or cannot find kernel headers

If Secure Boot causes the installer to request local key enrollment, follow its reboot and enrollment steps, then rerun installation. Custom kernels require matching headers from the system supplier; use uname -r to identify the running version.

First CAN connection

This example uses a correctly wired test bus and assumes the verification script reports can0. Substitute the actual interface name and match the peer’s bit rate.

Classical CAN · 500 kbit/s

sudo ip link set can0 down
sudo ip link set can0 type can bitrate 500000
sudo ip link set can0 up
ip -details -statistics link show can0

With your distribution’s can-utils installed, display received frames in a terminal.

candump can0

CAN FD · 500 kbit/s + 5 Mbit/s

Confirm the peer supports and uses these CAN FD rates before switching to this configuration.

sudo ip link set can0 down
sudo ip link set can0 type can bitrate 500000 dbitrate 5000000 fd on
sudo ip link set can0 up

Higher data rates depend on the transceiver, wiring, termination and peer configuration. The 8 Mbit/s specification refers to the CAN FD data phase.

Serial channels

On Windows, use the six COM ports labeled Serial. On Linux, use the six serial paths. Match each application channel to its physical connector before connecting the target equipment.

Item	Setting
Interfaces	4 × RS-485 · 2 × RS-232
Application settings	Match baud rate, data bits, parity and stop bits to the peer
Channel mapping	Use the device labels and driver verification output

Interface compatibility

Platform	Current driver and interfaces
Windows	7.1.9.0 · two CAN FD COM endpoints and six serial COM ports
Linux	1.2.3 · 2 SocketCAN interfaces + 6 serial channels
CAN protocol	Classical CAN data frames, CAN FD data frames and BRS

The current CAN text protocol does not represent RTR remote frames or distinguish extended frames with numeric IDs at or below 0x7FF from standard frames. Check these conditions when selecting an application protocol or developing an interface.

Connection checks

Observation	Check
Device not detected	Check the USB host path, power and connection. On Linux, use `lsusb` to inspect USB recognition.
USB detected, no CAN interface	Run `./verify.sh` from the package’s Linux folder and retain the output and kernel version.
Channel present, no reception	Check CANH/CANL, end-of-bus termination, signal reference, bit rates and frame modes.
Channel names change after reboot	Use the verification output to remap interfaces instead of assuming can0/can1 or fixed COM numbers.

Related downloads

Download driver package ↓CAN FD Control Center →TraceBox Analyzer Pro · EN →Product information →

This guide follows the README, installer and verification script distributed in the current driver package. See Software & Drivers for release versions.