Standalone, redundant, distributed, balanced: Sinapse – Part 1

Each project has its own needs. Every project shall use the right product to cover the requirements requested.

Too many times projects start based on a product which will be not enough to cover the new requirements that come out when the project grows.

Sinapse is not designed to cover one single scope; Sinapse is designed to scale up and cover different scenarios letting the developers add functionalities to it.

In this series of articles will be described various scenarios where Sinapse is used and can be used by customers of different areas.

The first will be the Standalone configuration scenario.

This scenario is the most common you can found in simple projects. A common example is a SCADA system controlling a process and showing information to the users.

Standalone

In the figure above it is possible to identify common entities:

  1. Field devices: PLC, ModBus devices, Cameras, readers and so on
  2. Server: a standalone machine (in general a PC) where the logical softwares runs on
  3. Client: it can be the same machine where the server runs or an external terminal where the operator interacts with the system

The basic functionalities available in Sinapse permits to a customer to deploy a system with a little development knowledge; the steps are:

  1. insert specific plugins for each device;
  2. configure each plugin with device information: IP address, port, …;
  3. connect plugins each other and insert the logic related to the process;
  4. debug, modify, update the logic using Sinapse hot update feature;
  5. that’s all.

In future articles other scenarios will be described.