The Visionect Software Suite comprises of the Graphics Engine and rendering backends, Network Manager and Gateway, each implemented as a separate process and connected together via an IPC service. Components can be run across different physical servers in multiple instances. The Data is stored in the storage backend.

Network Manager

The Network Manager is a service for the administration of other components and distributing workload. It offers facilities to monitor performance and, if needed, upgrades client devices over-the-air. It is also the centralized point from where you are able to control the operation of the HTML rendering backend servers and access the web administration interface (and the Software Suite management api).

It is the only component that needs to be run as a single instance inside your Visionect Software Suite cluster, managing all instances the HTML rendering backend and Gateway.

Graphics Engine and rendering backends

The Graphics Engine is the key component that stores the frame-buffer and the state of each connected device. The Engine includes all the features required for an RGB image to be displayed on a connected e-paper display as well as handle all the device feedback (interactions, input).

The Graphics Engine takes the RGB image input and uses various methods of dithering to convert color into the required bit-depth, optimize it for e-paper displays and compressing it to save bandwidth.

The actual content is fed into the Engine from various rendering backends. When a client connects to the Engine for the first time, it spawns a new session or attaches to an existing session if two or more devices share a common session. The session will then access the configured backend, as configured in the Network Manager. The session will persist as long as the Engine is running, regardless if the device has intermittent connectivity.

The Graphics Engine supports multiple rendering backends which can be chosen according to your specific application requirements. Currently we support a HTML rendering backend (formerly Okular), intended for interactive and dynamic applications built with HTML, and a HTTP rendering backend which exposes direct access to the device framebuffer over HTTP (direct image uploads).

HTML rendering backend

HTML rendering backend is the default backend, meant to be used for dynamic applications. It renders HTML(5), CSS and Javascript into graphical data using the WebKit rendering engine (as used in Google Chrome and Apple Safari web browsers). The backend connects to the configured URL and loads the Web application into its WebKit session. It supports full interactivity and exposes access to device (hardware) features through Javascript extensions.

More information regarding the development can be found in App Development Guide.

The WebKit session will restart in case of problematic web applications, which cause extensive memory leaks in the WebKit session. This is done to ensure the stability of the system. After the session is restarted, it opens the default URL as configured. Developers are advised to take the possibility of the session restart into account, and not count on the browser session to exist forever.

For protection against memory leaks it is possible to set the WebKit session memory limit after which the Visionect Software Suite will restart the problematic session. Users can do it by changing Web session memory limit setting [MB] in the Visionect Software Suite (Settings -> Rendering backend). The default setting is set to 120 MB.

If you wish to force a restart of a WebKit sessions due to issues with your application, you can do that by killing it with the Restart session button in the Visionect Software Suite (Devices sub-menu).


Web session memory limit setting

HTTP push backend

The HTTP backend takes whatever graphical data you provide to the backend and pushes it directly into the frame-buffer. You can use the provided RESTful API to upload images (PNG, JPG) with a simple PUT or POST command to a target URL.


The image needs to be in the PNG, JPG or GIF format and it will not be resized in any way to conform to the target screen size. Palette should be RGB, with the alpha channel (or transparency) disabled.

The HTTP backend is not especially suited for dynamic or interactive contents (you can only push image data), but it does require a lot less resources compared to HTML rendering backend as it does not processing on it’s own. HTTP backend-based sessions will use up to ten times less RAM (20-40MB for 800x600 display).

Examples of how to send an image to a Visionect e-paper device:

  • Python
from requests import Request, Session
import base64, hmac, hashlib, time, wsgiref.handlers

host = 'localhost'
uuid = '3a003c00-0d47-3130-3830-333200000000'
apiKey = '8cdec34cb9249164'
apiSecret = 'EU/X/CHo7895FGAXvsNieU1en4UtYIaP2o9R0b6hsuQ'

headers = {
   'Date': wsgiref.handlers.format_date_time(time.time()),

req = Request('PUT', 'http://%s:8081/backend/%s' % (host, uuid),
   files=[('image', ('local_image.png', open('local_image.png', 'rb'), 'image/png'))],

prepped = req.prepare()

h =, 'PUT\n\n%s\n%s\n/backend/%s' % (prepped.headers['Content-Type'], prepped.headers['Date'], uuid), hashlib.sha256)
prepped.headers['Authorization'] = '%s:%s' % (apiKey, base64.encodestring(h.digest()).strip())

s = Session()
resp = s.send(prepped)

if resp.status_code != 200:
   print 'Error: ' + resp.text

  • Node.js
var crypto = require('crypto'),
FormData = require('form-data'),
fs = require('fs'),
http = require('http'),
util = require('util');

var uuid = "3f003c12-0d47-3130-3830-3f3100000000",
host = "localhost",
apiKey = "036a8483ad55932131ba3",
apiSecret = "EDQvVRsg5thvuHlfYVdfdsafvzKfK1Pak8FEP2KiodWezQY8";

var form = new FormData();
form.append('image', fs.createReadStream('image.png'));

var headers = form.getHeaders(),
date = Date(),
path = util.format('/backend/%s', uuid);

auth = crypto.createHmac('sha256', apiSecret)
     .update(util.format('%s\n%s\n%s\n%s\n%s', 'PUT', '', headers['content-type'], date, path))

headers.Date = date;
headers.Authorization = util.format('%s:%s', apiKey, auth)

var request = http.request({
   method: 'put',
   host: host,
   port: 8081,
   path: path,
   headers: headers


request.on('response', function(res) {
   if (res.statusCode  != 200) {
      console.log('Error: ' + res.statusCode)
   res.on('data', function (chunk) {

  • PHP
$ressource = "/api/user/";
$url = "http://localhost:8081".$ressource;


$method = "GET";
$contentType= "application/json";

$date = gmstrftime("%a, %d %b %G %T %Z", time()); #date in format 'Tue, 02 Aug 2016 12:57:17 GMT'

$hash = hash_hmac("sha256", $method . "\n\n". $contentType . "\n". $date . "\n" . $ressource, $secret,  true);
$hash_b64 = base64_encode($hash);

$options = array(
    'http' => array(
        'header'  => "Content-type: ".$contentType."\r\n" .
             "Date: ".$date."\r\n" .
             "Authorization: ".$key.":".$hash_b64."\r\n",
        'method'  => $method,

$context  = stream_context_create($options);
$result = file_get_contents($url, false, $context);
if ($result === FALSE) {
    print("http fail\n");

For more information on implementation, please consult the server API documentation.


The Gateway is a virtual bridge between client devices and the Visionect Software Suite. It is possible to deploy multiple instances, providing connectivity to devices from multiple networks.

Database (storage) backends

The Storage component provides the Software Suite with data storage functionality and abstracts the underlying database. This is where the Visionect Software Suite stores all the settings and device events. Currently the Visionect Software Suite supports PostgreSQL as the database backend.

The database settings are configured in the config.json file. The valid settings are:

"Storage": {
    "Backend": "postgresql",
    "Database": "name_of_your_database",
    "Host": "hostname", // if not configured defaults to localhost
    "Port": your_db_port, // if not configured defaults to default database port
    "Username": "your_username",
    "Password": "your_pass"


In the past, both the PostgreSQL and CouchDB databases were supported. Due to the much better performance of PostgreSQL support for CouchDB was discontinued. If you are using an old version of the Visionect Software Suite (with CouchDB) and you want to upgrade it, you are required to migrate your database first.

Restarting The Services

All the core components of the Visionect Software Suite can be restarted remotely by pressing the red ‘Restart Services’ button in the Suite (under Settings).

The components of the Visionect Software Suite (engine, networkmanager, gateway, storage, admin) are run as a system deamon via the supervisord facility. You can restart the components through the Software Suite command prompt with sudo supervisorctl restart all. You can list the services (and view their status) by typing sudo supervisorctl status.

All Visionect Software Suite configuration files reside in /etc/supervisord/conf.d/.