Home
Open Source project for Supervisory Control and Data Acquisiton system. It is an Web-based, multi-platform solution to build your own SCADA environment.
Works on:
-
IMPORTANT
If you decide to use docker in production, you need to configure volumes to permanently store data: https://docs.docker.com/storage/volumes/
The easiest way to start with Scada-LTS is to launch the docker environment that is described inside docker-compose.yml.zip file. You need to have a Docker engine installed on your machine. Then you can download that file, unzip and in directory where you save that file you can type:
docker-compose upThat command will start "database" and "scadalts" docker containers and then you can access the application at the following address from your browser: localhost:8080/Scada-LTS. Default user: admin/admin.
-
IMPORTANT NOTE!
Sometimes "scadalts" docker container is loaded faster than the "database" so you can see that the application is not available. To fix that problem you can start them manually in following order:docker-compose up database docker-compose up scadalts
That script download the latest stable version of Scada-LTS from our official Docker Hub repository. More details how to configure the application can be found in our docker tutorial.
-
Important note!
To download the latest version, use thelatesttag in yourscadalts/scadaltsimage name. You can also download thenightlyversion of Scada-LTS that is build from the pre-release workflow. It may not be stable but you can test the latest changes by your own.
There is also another image repository for develop versions of the Scada-LTS. Following repository contains only images for specific feature branches.
You can download the latest Scada-LTS application *.war package from release page. Step by step instruction how to do in on Linux was described here.
To start using the Scada-LTS application we suggest to use ScadaBR tutorial that is available on SourceForge. Most features are very similar to that which was presented there. Some of them may not be available or could be changed. This application has many HELP messages included so user can just read them when something is not obvious.
Are you new to the Scada-LTS? 👶🏻 You want to know how to use this application? No problem we have just created a basic tutorial scenario where you can follow the steps to create a fully functional Scada system. "Home Scenario" will introduce you to basic business objects and show you relations within objects inside this app. If you do not want to create everything from scratch there is attached "Zip" file with ready configuration that you can just import into your app.
If you have any question about Scada-LTS feel free to ask on StackOverflow forum with Scada-LTS tag or on our GitHub Discussions.
We have a community that has developed and implemented ScadaBR and for sure will try to help you if you have any issue or questions. We will try to solve your problems and suggest the best solutions.
Video tutorials with example Scada-LTS configuration will be available on our YouTube channel.
We try to publish also the short summary video with latest changes. Of course not every issue can be described there. If you want to be up to date with latest changes please subscribe our channel.
We have also some articles that was about latest changes in the code and project. That articles can be found here on Grzesiekb profile. There you can find some explanations how specific features works.
First time to our project? You want to start adding some awesome stuff? Firstly you have to deal with installation all required libraries and dependencies. To make it easier we prepared step-by-step tutorial. Then if your application will have been built successfully you can start developing a new features. For people who do not know what to do at the beginning we prepared instructions for two most popular Java IDE.
ScadaBR code was not well documented and the most important information was described at CERTI ScadaBR page and as comments inside code. To make it easier to maintain that project by other developers we started to preparing README.md files that explains how specific feature has been implemented (eg. System Settings in Vue.js) and how to use prepared interfaces. Some functions are described with JavaDoc or JavaScriptDoc but most of them are not so that could be a difficulty to start development.
One rule to rule them all!
To keep our project clean we introduced some rules that should be obey. They are described in following sections:
Our team tries to provide the best user experience while you are using this application. This application is still under development but it main business core is ready to be deployed. We are fixing the bugs and we are trying to implement a new User Interface that will be intuitive, fast and reliable.