Lightweight SCADA device servers and integrations in Kotlin-Multiplatform
Go to file
2020-06-11 20:51:56 +03:00
.github/workflows CI setup and Readme changes 2020-06-07 21:16:19 +03:00
dataforge-control-core Some method renaming, fixes #3 2020-06-11 19:34:21 +03:00
demo Change package name to 'controllers', add some doc 2020-06-11 19:29:22 +03:00
docs Change package name to 'controllers', add some doc 2020-06-11 19:29:22 +03:00
gradle/wrapper Update wrapper 2020-06-07 21:28:23 +03:00
.gitignore Working prototype 2020-06-05 21:07:23 +03:00
build.gradle.kts Working prototype 2020-06-05 21:07:23 +03:00
gradlew Fix permissions 2020-06-07 21:32:39 +03:00
gradlew.bat Update wrapper 2020-06-07 21:28:23 +03:00
LICENSE Initial commit 2020-02-16 15:34:06 +03:00
README.md Change package name to 'controllers', add some doc 2020-06-11 19:29:22 +03:00
settings.gradle.kts Working prototype 2020-06-05 21:07:23 +03:00

JetBrains Research

DataForge-control

DataForge-control is a data acquisition framework (work in progress). It is based on DataForge, a software framework for automated data processing. This repository contains a prototype of API and simple implementation of a slow control system, including a demo.

DataForge-control uses some concepts and modules of DataForge, such as Meta (immutable tree-like structure) and MetaItem (which includes a scalar value, or a tree of values, easily convertable to/from JSON if needed).

To learn more about DataForge, please consult the following URLs:

DataForge-control is a Kotlin-multiplatform application. Asynchronous operations are implemented with kotlinx.coroutines library.

Features

Among other things, you can:

  • Describe devices and their properties.
  • Collect data from devices and execute arbitrary actions supported by a device.
  • Property values can be cached in the system and requested from devices as needed, asynchronously.
  • Connect devices to event bus via bidirectional message flows.

dataforge-control-core module packages

  • api - defines API for device management. The main class here is Device. Generally, a Device has Properties that can be read and written. Also, some Actions can optionally be applied on a device (may or may not affect properties).

  • base - contains baseline Device implementation DeviceBase and property implementation, including property asynchronous flows.

  • controllers - implements Message Controller that can be attached to the event bus, Message and Property flows.

demo module

The demo includes a simple mock device with a few properties changing as sin and cos of the current time. The device is configurable via a simple TornadoFX-based control panel. You can run a demo by executing application/run Gradle task.

The graphs are displayed using plotly.kt library.

Example view of a demo: