The new-generation EVA ICS v4 “internal alpha” is going to be released in May 2022. The “internal alpha” version will be available to our Enterprise customers only and will have very limited support of hardware equipment / logic, plus no replication between v4 and v4 nodes yet. However, it will be able to fully host UI apps and replicate data from v3 secondaries.
The goal is to:
test v4 core in production
replace heavy-loaded v3 SFA controllers
If you are the existing customer and want to try EVA ICS v4 internal alpha, please read the conditions:
I was given by one of our team members of the link to the article, where the joined team of engineers from 3 USA universities reviewed industrial and home automation systems, including EVA ICS. First of all, I must say I am proud and impressed that our platform becomes more and more popular in IoT world, second – I am happy EVA ICS shown the best results in tests, third – I would like to ask the article authors to review EVA ICS 3.3.x, which has got, in comparison to 3.2.x, more improved asynchronous core, which gives huge speed and memory advantages.
However, it was mentioned, EVA ICS has no policy-based actions, which is incorrect, and let me explain how to use them in the real production:
Web-based SCADA interfaces require more different approach, than regular web sites.
Why web SCADA?
Cons: web interfaces are unstable. Sometimes seriously unstable.
In this article we will give some tips about it, no matter which web interface is built for EVA ICS or any other IoT/IIoT platform.
EVA ICS version 3 has become the most successful industrial IoT product of our company. It already has dozens of setups we support directly and I hope even more setups we don’t.
But the version 3 has a problem: because of the rapid numbers of customers and features growth, it’s internal architecture was changed several times almost from scratch, lots of stuff already became obsolete and too complicated for beginners.
Here are the plans for the EVA ICS codename “nextgen” (next generation):
Installing EVA ICS on a production machine without the Internet connection is tricky is pretty easy, but Python virtual environment should be manually prepared. Another option is to mirror pypi.org repository, but it requires about 120GB of disk space and isn’t recommended, unless used for another company needs.
In this article we will explain how to install EVA ICS on Debian / Ubuntu machine in the offline mode.
When we started development of EVA ICS, asynchronous programming just started to be popular. EVA ICS 3 core is thread-based. It works pretty well, doesn’t produce too much memory/CPU load, but it can work even better.
Let me introduce atasker library. This is free, open source Python library, which will solve many problems as in EVA ICS core, as in any other similar project.
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 )