diff --git a/README.md b/README.md index d4648636b8..a13e5b3681 100644 --- a/README.md +++ b/README.md @@ -21,7 +21,7 @@ There is also a Scada-LTS users community so if you have a problem feel free to For the developers we are preparing a complete code documentation that will contain all the REST API interfaces described with example usage. To do that we use Open API specification in version 3 that is compatible with most of the modern API tools like Swagger or Postman. Documentation file can be found in [Scada-LTS/doc](https://github.com/SCADA-LTS/Scada-LTS/tree/develop/doc/RESTAPI) directory. -To take your first steps inside Scada-LTS we suggest to get acquainted with video tutorials on YouTube or with [ScadaBR instructions](https://sourceforge.net/p/scadabr/wiki/Manual%20ScadaBR%20English%200%20Summary/). +To take your first steps inside Scada-LTS we suggest to get acquainted with video tutorials on YouTube [Scada-LTS Youtube](https://www.youtube.com/@ScadaLTS). Follow the [Release Section](https://github.com/SCADA-LTS/Scada-LTS/releases) to be up to date with the latest features and see the specific version changelogs. We follow the [Semantic Versioning Guidelines](http://semver.org/) to organize changes in our application. diff --git a/WebContent/WEB-INF/dox/de/cronPatterns.htm b/WebContent/WEB-INF/dox/de/cronPatterns.htm index 1ff7e89e2c..3569b86e2b 100644 --- a/WebContent/WEB-INF/dox/de/cronPatterns.htm +++ b/WebContent/WEB-INF/dox/de/cronPatterns.htm @@ -18,7 +18,7 @@ -->

Les modèles Cron proviennent de l'outil "cron" (de "chronologique") des systèmes UNIX. Ces modèles peuvent paraître ésotériques au premier abord, ce sont en fait des moyens simples, puissants et élégants de définir un ensemble de paramètres de planification d'évènements.

-

Les modèles Cron de ScadaBr sont régis par Quartz, une bibliothèque de planification basée sur Java. Plus d'informations sur le site:

+

Les modèles Cron de Scada-LTS sont régis par Quartz, une bibliothèque de planification basée sur Java. Plus d'informations sur le site:

CronTriggers Tutorial

CronTriggers Generator

Example configuration: 1 */15 * * * ? = At second :01, every 15 minutes starting at minute :00, of every hour

\ No newline at end of file diff --git a/WebContent/WEB-INF/dox/de/datetimeFormats.htm b/WebContent/WEB-INF/dox/de/datetimeFormats.htm index d2d63d8dfa..b6f45d6b05 100644 --- a/WebContent/WEB-INF/dox/de/datetimeFormats.htm +++ b/WebContent/WEB-INF/dox/de/datetimeFormats.htm @@ -19,6 +19,6 @@

Les formats Date/heure sont utilisés afin de déterminer comment afficher et interpréter les dates, convertir leurs représentations internes at le texte affiché. Les dates peuvent être affichées dans des formats différents,selon le contexte et la sémantique des données. Les mêmes normes peuvent être utilisées pour afficher une valeur ou saisir une valeur.

-

Dans ScadaBr le format est implémenté par la classe Java SimpleDateFormat, vous pouvez obtenir les détails de cette classe dans le lien "http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html".

+

Dans Scada-LTS le format est implémenté par la classe Java SimpleDateFormat, vous pouvez obtenir les détails de cette classe dans le lien "http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html".

Le formatage peut dépendre de la localisation par défaut de votre VM Java.

\ No newline at end of file diff --git a/WebContent/WEB-INF/dox/de/directQuerying.htm b/WebContent/WEB-INF/dox/de/directQuerying.htm index a770da08ea..e50c957b62 100644 --- a/WebContent/WEB-INF/dox/de/directQuerying.htm +++ b/WebContent/WEB-INF/dox/de/directQuerying.htm @@ -16,11 +16,11 @@ You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. --> -

ScadaBR provides the ability to directly access the system's database for both querying and updating. This facility is provided primarily for troubleshooting or system repair. It is not appropriate for regular use due to the risk of data corruption.

+

Scada-LTS provides the ability to directly access the system's database for both querying and updating. This facility is provided primarily for troubleshooting or system repair. It is not appropriate for regular use due to the risk of data corruption.

Only valid individual SQL statements may be submitted. Do not end your statements with ';' characters.

Available tables

-

The following is a list of all tables in the ScadaBR database:

+

The following is a list of all tables in the Scada-LTS database:

Sons des alarmes

-

ScadaBR peut émettre des sons lorsque les alarmes sont actives . Par défaut, les sons d'alarme sont joués pour les alarmes de sécurité, urgentes, critiques et sécurité des personnes (mais pas pour les alarmes d'information), mais les sons de chaque type d'alarme peuvent être contrôlés individuellement. Pour activer des sons d'alarme particulier, les fichiers mp3 doivent être stockés aux endroits suivants:

+

Scada-LTS peut émettre des sons lorsque les alarmes sont actives . Par défaut, les sons d'alarme sont joués pour les alarmes de sécurité, urgentes, critiques et sécurité des personnes (mais pas pour les alarmes d'information), mais les sons de chaque type d'alarme peuvent être contrôlés individuellement. Pour activer des sons d'alarme particulier, les fichiers mp3 doivent être stockés aux endroits suivants:

- Note: Une liaison de point peut être confiqurée de telle sorte que des boucles infinies peuvent apparaître. ScadaBR détectera le problème,le terminera et + Note: Une liaison de point peut être confiqurée de telle sorte que des boucles infinies peuvent apparaître. Scada-LTS détectera le problème,le terminera et informera l'utilisateur.

@@ -45,7 +45,7 @@

Liste des liaisons de point

Configurer une liaison de point

- L'Export ID est la valeur utilisée pour identifier une liaison dans les différentes instances de ScadaBR. Il est utilisé dans le menu + L'Export ID est la valeur utilisée pour identifier une liaison dans les différentes instances de Scada-LTS. Il est utilisé dans le menu Import/Export. Cette valeur, unique est générée aléatoirement, mais elle peut être définie par l'utilisateur pour être plus explicite.

diff --git a/WebContent/WEB-INF/dox/de/pop3PP.htm b/WebContent/WEB-INF/dox/de/pop3PP.htm index de36ac0fdd..0cb45c3b5b 100644 --- a/WebContent/WEB-INF/dox/de/pop3PP.htm +++ b/WebContent/WEB-INF/dox/de/pop3PP.htm @@ -16,7 +16,7 @@ You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. --> -

The Data type is the ScadaBR representation of the value. Received data is automatically converted to the required data type. The Value RegEx determines where in the email content to find the point value. See the "Regular Expressions" documentation for more information. Note that only the first instance of the expression found in the content is used.

+

The Data type is the Scada-LTS representation of the value. Received data is automatically converted to the required data type. The Value RegEx determines where in the email content to find the point value. See the "Regular Expressions" documentation for more information. Note that only the first instance of the expression found in the content is used.

The Ignore if missing checkbox indicates whether missing values in email content should be considered error conditions. If unchecked and the value is not found in the content, a data source exception event will be raised. If checked, the event is suppressed, and the point is not updated.

diff --git a/WebContent/WEB-INF/dox/de/regex.htm b/WebContent/WEB-INF/dox/de/regex.htm index 0a45029aa1..6c6c27b570 100644 --- a/WebContent/WEB-INF/dox/de/regex.htm +++ b/WebContent/WEB-INF/dox/de/regex.htm @@ -25,7 +25,7 @@

- Many RegEx patterns used in ScadaBR are similar. Typically the intension is to locate a particular value in some text. + Many RegEx patterns used in Scada-LTS are similar. Typically the intension is to locate a particular value in some text. As such, the pattern will consist of prefix and suffix strings that uniquely identify the value, and a group pattern that extracts the value. For example, the text to parse may look like this:

diff --git a/WebContent/WEB-INF/dox/de/reportInstances.htm b/WebContent/WEB-INF/dox/de/reportInstances.htm index bd71b77b19..2643e53f31 100644 --- a/WebContent/WEB-INF/dox/de/reportInstances.htm +++ b/WebContent/WEB-INF/dox/de/reportInstances.htm @@ -17,7 +17,7 @@ along with this program. If not, see http://www.gnu.org/licenses/. -->

Overview

-

Reports in ScadaBR have two representations: templates which define the content of a report, and instances which are the result of running a report with a given template. Simply: the report engine creates instances from templates. A template has attributes like a name, a list of points that it includes, and the date range of values it extracts. An instance will inherit its name from the template, but have its own attributes such as the time it ran, the run duration, the number of records it includes, and, of course, the data.

+

Reports in Scada-LTS have two representations: templates which define the content of a report, and instances which are the result of running a report with a given template. Simply: the report engine creates instances from templates. A template has attributes like a name, a list of points that it includes, and the date range of values it extracts. An instance will inherit its name from the template, but have its own attributes such as the time it ran, the run duration, the number of records it includes, and, of course, the data.

An instance can be considered a snapshot of the data at the time it was run. Instance attributes cannot be changed. Also, the data that the instance reports exists as long as the instance exists. (I.e. it survives the purging of the source data.) For this reason, it is important to purge report instances—especially large instances—when they are no longer needed since they can consume large amounts of storage.

Report templates—and the instances they create—belong to the user that created them. They cannot be explicitly shared within the system, but may be shared implicitly. See the "Report templates" documentation for more information.

diff --git a/WebContent/WEB-INF/dox/de/snmpPP.htm b/WebContent/WEB-INF/dox/de/snmpPP.htm index 1090e4274f..cbcf3a72df 100644 --- a/WebContent/WEB-INF/dox/de/snmpPP.htm +++ b/WebContent/WEB-INF/dox/de/snmpPP.htm @@ -16,4 +16,4 @@ You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. --> -

The OID represents either the object identifier to request on host, or to match in traps that are received. The Data type is the ScadaBR representation of the value. Received data is automatically converted to the required data type. The Binary 0 value is the value to match for a binary point to be given the value 0. The Set type is the SNMP data type to use when setting values on the host. A value of "(not settable)" indicates that the point is read-only. The Polling field determines whether to include the value in GET requests with each polling cycle, or whether values are received only via traps.

\ No newline at end of file +

The OID represents either the object identifier to request on host, or to match in traps that are received. The Data type is the Scada-LTS representation of the value. Received data is automatically converted to the required data type. The Binary 0 value is the value to match for a binary point to be given the value 0. The Set type is the SNMP data type to use when setting values on the host. A value of "(not settable)" indicates that the point is read-only. The Polling field determines whether to include the value in GET requests with each polling cycle, or whether values are received only via traps.

\ No newline at end of file diff --git a/WebContent/WEB-INF/dox/de/sqlDS.htm b/WebContent/WEB-INF/dox/de/sqlDS.htm index 44bbe963c7..92c3ea49d5 100644 --- a/WebContent/WEB-INF/dox/de/sqlDS.htm +++ b/WebContent/WEB-INF/dox/de/sqlDS.htm @@ -28,7 +28,7 @@

Configuration

The Driver class name specifies the Java class that implements the JDBC Driver interface within your JDBC driver. This value can be found in the documentation for your driver. The following is a list of driver class names for the given database, and is provided as convenience only. Note that connectivity typically requires the - installation of driver software on the ScadaBR server. If you are having problems, please consult the documentation for + installation of driver software on the Scada-LTS server. If you are having problems, please consult the documentation for your database.