Markus Zolliker e0b2747821 central point for status codes
Put status code definitions into frappy.datatypes.StatusType.
frappy.datatypes is anyway imported in servers and clients,
so this is a better place than frappy.modules.

Change-Id: I81dfc8a066f598fbd20854ed1a13b937b7facc8c
Reviewed-on: https://forge.frm2.tum.de/review/c/secop/frappy/+/30703
Tested-by: Jenkins Automated Tests <pedersen+jenkins@frm2.tum.de>
Reviewed-by: Markus Zolliker <markus.zolliker@psi.ch>
2023-03-16 14:42:42 +01:00
2023-02-21 17:44:57 +01:00
2022-11-09 16:29:29 +01:00
2023-03-16 14:42:42 +01:00
2023-03-16 08:47:45 +01:00
2022-11-09 16:29:29 +01:00
2022-11-09 16:29:29 +01:00
2023-03-14 14:24:11 +01:00
2023-01-24 10:56:39 +01:00
2022-11-08 17:44:58 +01:00
2023-02-21 16:47:01 +01:00
2023-03-14 08:20:03 +01:00
2023-03-08 15:59:30 +01:00
2022-11-09 16:29:29 +01:00
2023-01-18 16:24:30 +01:00
2023-03-03 14:38:23 +01:00
2022-11-09 16:29:29 +01:00

Frappy: Framework for programming secnodes in Python

Frappy is a Pyhthon-framework for writing SECoP servers (called SECNodes or Nodes) and Clients. It comes with its own Graphical client and a collection of example Nodes. It is able to use TCP and Serial connections.

To get started, look at the provided demo, the provided examples, or have a look at the INTRODUCTION section.

Main development is done here and a readonly GitHub-mirror for easier access is available here.

Requirements

See requirements.txt.

Demo

Use the following command after installing the dependencies:

$ make demo

Documentation

See here for documentation of Frappy

Description
PSI local frappy repo, probably ahead of git/gerrit at MLZ
Readme 11 MiB
Languages
Python 99.9%