Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Welcome to the ROBOTC Driver Suite Github repository.

What is this?

The Driver Suite is a collection of drivers for LEGO and 3rd party sensors for both NXT and EV3. These drivers offer access to additional functionality, which is left unexposed if you use the standard built-in ROBOTC drivers.

This repository contains a regularly updated work in progress of the migration of (almost) all drivers a new, more easy to use and uniform API.

How to install it?

If you're keen to try out these bleeding edge drivers, navigate to [this page] howtopage and follow the instructions. Simply substitute the repository in that text with this current one.

You can simply [download as zip] masterzip and expand on your system, somewhere.

If you're a more advanced user, I would advise you to use something like [Git] gitsite or the more user friendly UI based [SourceTree] [sourcetreesite]

The new API

So what is so special about this new API? It's a complete rethink of how the drivers handle sensor data. All data (or as much as possible), is contained within a sensor specific struct. For example, the struct that contains I2C data looks as follows:

typedef struct
  ubyte request[17];
  ubyte requestLen;
  ubyte reply[17];
  ubyte replyLen;
  ubyte address;
  tSensors port;
  TSensorTypes type;
} tI2CData, *tI2CDataPtr;

Global variables have been eliminated as much as possible, making the drivers less prone to weird behavioural issues, if multitasking is used.

A sensor specific struct will look more like this. This is the one for the HiTechnic Angle Sensor:

typedef struct
  tI2CData I2CData;
  int angle;
  int accumlatedAngle;
  short rpm;
  ubyte _cmd;
  bool smux;
  tMUXSensor smuxport;

As you can see, the sensor's struct contains an I2CData struct as well, to keep all the data specific to that sensor in one place.

These functions below may not pertain to all drivers, but if the sensor offers this functionality, it will be accessible through that specific function. It relies heavily on ROBOTC's function overloading to allow multiple functions with the same name to exist, but taking different arguments.

// Setup the sensor's port and struct
bool initSensor(tTIRPtr tirPtr, tSensors port)

// Populate the struct with data
bool readSensor(tTIRPtr tirPtr)

// Reset the sensor
bool resetSensor(tTIRPtr tirPtr)

// Set the offset for a sensor
bool sensorSetOffset(tHTMCPtr htmcPtr);

// Start calibration - not all sensors have a "stop" command
bool sensorCalibrate(tHTMCPtr htmcPtr);

// Stop calibration - not always required
bool sensorStopCalibrate(tHTMCPtr htmcPtr);

// Configure a sensor for a new mode
bool configSensor(tHTEOPDPtr hteopdPtr);

If you're interested in seeing an actual example of this, take a look at the [HiTechnic Angle Sensor example program] htangleexample.


If you want to contribute, simply [clone] clonehelp this repo, start tinkering with the files and submit a pull request. I encourage you to read through the examples that I have created and migrate some of the others. You can see the current status of the drivers in the [Excel sheet] status_sheet. Modifications to this file will not be accepted. If you want to start working on a driver, simply submit it as an [issue] issuelink. That will prevent multiple people working on the same drivers. There is not much point in duplicating effort.

Please note: I do reserve the right to modify submitted code as I see fit, to keep it aligned with the rest of the Suite.

A word of advice: keep your commits small, this will make merging MUCH easier for me. Contributors will be mentioned in a THANKYOU file, of course!


ROBOTC 4.x Driver Suite for NXT and EV3






No releases published


No packages published