Everloop

Everloop

Device Compatibility

Overview

The Everloop driver allows for:

  • Reading amount of LEDs your MATRIX device has.
  • Setting the RGBW colors for each individual LED.

Available ZeroMQ Ports

  • Base port: 20021
  • Keep-alive port: 20022
  • Error port: 20023
  • Data update port: 20024

Protocol

Base Port

This port accepts a single configuration for communicating with the Everloop driver.

  • image - the everloop configuration that's created from an EverloopImage message.

message DriverConfig {
matrix_io.malos.v1.io.EverloopImage image = 3;
}
View the defined message here.

EverloopImage

  • led - Must hold the value for each LED on your MATRIX device. Each LED is defined as one LedValue.

// Value for an led that ranges from 0 to 255 for each color
message LedValue {
uint32 red = 1;
uint32 green = 2;
uint32 blue = 3;
uint32 white = 4;
}

// The led array.
message EverloopImage {
repeated LedValue led = 1;
}
View the defined message here.

Keep-alive Port

This driver needs keep-alive messages in order to send data to your application. It's recommended to send an empty string "" because the contents of a keep-alive message are never read.

Error Port

Applications can subscribe to this port to receive driver related errors.

Data Update Port

Applications can subscribe to this port for Everloop data. The output will be a serialized message of type EverloopImage with the following information.

// The led array.
message EverloopImage {
repeated LedValue led = 1;

// Number of leds in the Everloop
int32 everloop_length = 2;
}
View the defined message here.

Contents