ikarus/sps

Maintainers

Details

github.com/tasoftch/ikarus-sps

Source

Issues

Installs: 250

Dependents: 20

Suggesters: 0

Security: 0

Stars: 0

Watchers: 2

Forks: 0

Open Issues: 0

v0.8.20 2023-06-03 10:06 UTC

Requires

Requires (Dev)

BSD-3-Clause b3bb8088f6362e2bdffbc70d76db59ae4df239db

  • Thomas Abplanalp <info.woop@tasoft.ch>

This package is auto-updated.

Last update: 2024-04-03 15:19:47 UTC

README

Ikarus SPS is an attempt to run PHP on a device as independent SPS.

Installation

This reporitory is a package that can be intalled using composer:

$ composer require ikarus/sps

How Ikarus SPS works

The Ikarus SPS engine distinguish between two kinds of run modes:

  1. Cycle based engine
    This engine type defines a fixed frequency, for example 2Hz, which means, that the engine updates twice per second.
  2. Event based engine
    The event based engine waits until an event gets triggered from one of its plugins.

So it depends of your requirements, which kind of SPS engine you prefer.

General workflow

  1. There is usually one instance of a SPS Engine running on a device.
  2. Eventbased: This instance needs two kinds of plugins: listeners and triggers.
    or cyclebased: The instance needs only cycle plugins.
  3. The listener waits until something happens in the SPS to perform an action. (SPS to device)
    Example: A timer event was triggered and the listener now instructs a motor to close the door.
  4. A trigger wait until something happens on the device and informs the SPS. (Device to SPS)
    Example: An input sensor notifies that the door is closed or a timer triggers that time is up.
  5. Run the engine, now the plugins get active and the SPS runs.

Multiprocessing

PHP has an extension that allows forking a process.
This feature is used to multitask the SPS Engine.
All trigger plugins are dispatched to a separate process. Now they can wait for an event of the device, while the SPS Engine and its listeners continue working.

SPS Trigger Plugins

As described above, trigger plugins run in a separate process to avoid that the SPS Engine gets blocked because of a listener (Example: listening on a socket blocks the thread until something is available to read from the socket.)

But this has one disadvantage:

  • An SPS trigger does not share the same memory as the SPS Engine and its listeners.

This means:

  • An SPS trigger gets a copy of the environment at engine start.
    After that, everything it does (reading object properties, defining variables, etc) does not affect the SPS Engine anymore (and vice versa!)

To solve this problem, the Ikarus SPS package has dispatchable events that can be transmitted from and to SPS triggers.