Private Search Engine
© 2024  Nexedi
Ivan Tyagov  |

Introduction to rPLC Presentation

Agenda

  • Nexedi
  • Industrial automation solution using open source and open hardware
 

Nexedi

 

Nexedi - Profile

Nexedi World Map
  • Largest Free Software Publisher in Europe
  • Founded in 2001 in Lille (France) - 35+ engineers worldwide
  • Enterprise Software for mission critical applications
  • Build, deploy, train and run services
  • Profitable since day 1, long term organic growth
Nexedi is probably the largest Free Software publisher with more than 10 products and 15 million lines of code. Nexedi does not depend on any investor and is a profitable company since day 1.

Nexedi - Clients

Nexedi References and Map

nexedi.com/success

Nexedi clients are mainly large companies and governments looking for scalable enterprise solutions such as ERP, CRM, DMS, data lake, big data cloud, etc.  

Nexedi - Free Software Stack

Nexedi Software Stack

stack.nexedi.com

Nexedi software is primarily developed in Python, with some parts in Javascript.

Introduction to rPLC coupler

rPLC coupler is an open source software and hardware computer device which can be controlled by any IEC-61131 compliant software.
 

Beremiz control software

We use Beremiz IDE / runtime which is a IEC-61131 complient control software to program rPLC.
 

Shape sorting machine using rPLC

A real based on conveyor belt shape sorting machine using rPLC coupler, Beremiz runtime and optical shape inspection (algorithm implemented by OpenCV2).

rPLC coupler as part of a machine

XXXX

Video shape sorting machine

Using rPLC we could create a shape sorting machine which is using internally OPC UA for process communication.
 

OPC UA

OPC UA is the default communication protocol for use with rPLC coupler.
 

5G ORS and rPLC

It is possible to use another Nexedi's product (ORS) to run inside Beremiz IDE and have one device to provide process control and full fledged 5G own network.
 

SlapOS everywhere: rPLC coupler, Beremiz IDE and Beremiz Runtime.

  • Master: ERP5 (promise definition, ordering, provisioning, accounting, billing, issue tracking)
  • Slave: buildout (promise execution, build, instantiation, configuration, monitoring)

So, we used buildout (http://docs.buildout.org/en/latest/) as the base for our service descriptor language and ERP5 to keep track of "service lifecycle" after we found out that any edge or cloud system can be made of two components: a devops and an ERP (see "SlapOS: SlapOS: A Multi-Purpose Distributed Cloud Operating System Based on an ERP Billing Model" https://ieeexplore.ieee.org/document/6009348). 

For resiliency, we based all our design on the idea that resiliency must be implemented with software and should rely on redundant infrastructure on redundant sites with redundant suppliers. However each site or hardware does not need to be redundant.

This approach was quite successful. By sticking to a very simple and minimal architecture, we could achieve with a small budget what huge community projects such as OpenStack still fail to achieve after 10 years. And we could do much more, because our architecture was more generic.

SlapOS Dashboard

 

Thank You

  • Nexedi SA
  • 147 Rue du Ballon
  • 59110 La Madeleine
  • France
  • +33629024425

For more information, please contact Jean-Paul, CEO of Nexedi (+33 629 02 44 25).