Link Search Menu Expand Document

List of Virtual Raptor Drivers

Jan 1 2022 at 12:00 AM

  1. Overview
  2. Certified Drivers
  3. Generic Drivers
  4. Experimental Drivers
  5. Discontinued Drivers

Overview

This page lists the drivers that can be deployed directly from the V-Raptor™’s management interface or through the management API.

Certified Drivers

Drivers in this category have been developed and certified by IoT.nxt® for very specific protocols and hardware. While they may have a certain degree of customisation, they have been designed with specific devices in mind.

Driver nameCommunication protocolReadiness
HTTP
Beta
HTTP
Release
HTTP
Release
TCP
Release
HTTP
Beta
HTTP
Beta
HTTP
UDP
Release
HTTP
Beta
CoAP
Release
MQTT
Release
NetCool
TCP
Beta
HTTP
Websocket
Release
HTTP
Release
HTTP
Beta
TCP
Release
HTTP
Beta
HTTP
Release

Generic Drivers

The following integrations are not limited to specific devices, but instead rely on configuration and/or external integrators. They can be adapted to suite a variety of use cases.

Driver nameCommunication protocolReadiness
Generic Device Interface
HTTP
MQTT
Beta
Generic DLMS Telemetry Interface
TCP
Beta
Generic HTTPS Telemetry Interface
HTTP
Release
Generic Modbus Interface
TCP
Beta
Generic MQTT Telemetry Interface
TCP
Release
Generic SNMP Telemetry Interface
TCP
Beta

Experimental Drivers

The following drivers are available for use but have not been certified by IoT.nxt.

NOTE
Users will need to configure the V-Raptor to pull packages from the Prototype repositories to access these drivers.
Driver nameCommunication protocolReadiness
CoAP
Prototype
HTTP
Prototype
HTTP
Prototype
HTTP
Prototype
HTTP
Prototype

Discontinued Drivers

The following drivers are currently end-of-life and are no longer being maintained1.

Driver nameCommunication protocolReadiness
MQTT
Beta
IoTSpot Booking System
HTTP
Release
Remote Asset Manager
HTTP
Beta
Site Asset Manager
TCP
Beta
Telematic Intelligent Monitor
TCP
Beta
Xemote Wireless Sensor Gateway
HTTP
Release

RELEASE

BETA

PROTOTYPE

  1. IoT.nxt may re-activate drivers if new use cases become available