EVA SFA controller hosts “ui/” folder as static web content (except .j2 files), but you can perform a little trick on YAML and JSON files: convert them on the flow.
E.g. you have YAML file “config/test.yml” with content:
param1: 1 param2: somevalue
to get it as JSON, add “as=json” param to query string:
Continue reading ““Serve as” feature in EVA SFA”New Driver API v5 in EVA ICS 3.2.2 brings important improvement: now Physical Interface modules can support extended unit state (status + value). To test and demonstrate this feature, we’ve made PHIs for 2 popular LED controllers: Philips HUE and Nanoleaf. Everyone likes playing with LEDs, even industrial guys )
Both PHIs can be found at EVA ICS website and downloaded to Universal Controller instance.
Continue reading “Extended unit state in PHIs. Playing with LEDs”In IoT “S” stands for security
(c) one smart guy in Twitter
Weak security is a major problem of almost all modern IoT and IIoT/Industry 4.0 solutions. There’s usually nothing wrong when equipment state or shadow state is available for nodes in your configuration, as one of Industry 4.0 design principles is “Information transparency”.
However things change when we start talking about control. Allowing nodes to control each other and send action API calls is dangerous: if attacker get an access to information exchange point, he can destroy your business or even your life.
Continue reading “IoT and security”This article describes, how to install EVA ICS on Ubuntu or Debian. Actually it duplicates the information from EVA ICS installation docs, however is focused on Ubuntu with local mosquitto MQTT server, has minimal description and contains all required commands which could be just copy/pasted in console shell.
So let’s consider you have fresh Ubuntu install (I’ve used 18.04 LTS). What should be done, before we can launch EVA ICS easy-setup:
Let’s go.
Continue reading “EVA ICS on Ubuntu: copy/paste install”NixOS is a very cool Linux distribution built on top of the Nix pkg manager. It’s very reliable and easy to deploy on multiple machines, however installing 3rd party software may be tricky.
Starting from version 3.2.1, you can run EVA ICS on NixOS. This article describes how to install it.
Continue reading “Installing EVA ICS on NixOS”Primary EVA CLI tools are eva (./bin/eva) and eva-shell (./bin/eva -I or ./bin/eva-shell). Actually it’s a same program, which automatically starts itself in interactive mode (-I) when called as eva-shell and without any argument.
Interactive mode
If command “uc”, “lm” or “sfa” is called without arguments, EVA shell will launch corresponding controller sub-shell, which’s equal to calling uc-cmd, lm-cmd and sfa-cmd directly.
You can execute a pack of several commands at once, separating them with “;” symbol, just like in a system shell:
state -p sensor ; state -p unit
The next very useful trick is command repeating. In real life, there’s a lot of examples, when you mount / setup some equipment and need to check its state every second to get the moment it start working correctly. To repeat the command
in EVA shell , symbol “|” (pipe) is used
EVA ICS doesn’t use thread pools in core, number of threads is always fixed (except LM PLC macros), grows together with node configuration, and should be controlled by system administrator/integrator. Majority threads “sleep” until they get an event and don’t produce additional load.
After controller start, core launches several system threads (garbage collectors etc.), plus threads for each item:
In this blog we’ll explain how EVA ICS works, write articles with examples and real-life usage cases and discuss various general automation tips, tricks and problems.
