i4SCADA Knowledge Base

i4SCADA Version 3.8.11

Abstract

Check out the Changes and Fixed Bugs of i4SCADA 3.8.11 Version. The first i4SCADA version which brings along a large amount of improvements and bug fixes.

Changes

ID

Description

SWC0074-445

Introduce Simatic TIA *.AGL and filter support

SWC0074-458

Introduce possibility to generate TIA XML configuration by importing WEBfactory i4SCADA signals

SWC0074-529

Update latest DeltaLogic libraries in SIMATIC (studio, connector)

SWC0074-472

Add support for Beckhoff ADS 3 (TwinCAT 3)

SWC0074-484

Add async write functionality to SchedulerPro and MessengerPro

SWC0074-480

Enable possibility to automatically update / upgrade a software-based license

SWC0074-429

Update control used to host WebApps to a version supporting newer browser engines

Fixed Bugs

ID

Description

SWC0074-139

NO feedback is received when writing Signal values for HTML components, when ASYNCHRON writing mode is set

SWC0074-398

The SIMATIC TIA connector encounters an error on attempt to read an inactive / deactivated Signal

SWC0074-436

A "Signal write failed" error is triggered when trying to change the time picker of the "wf-date-time-picker" extension

SWC0074-439

The "wf-historical-data-chart" extension is continuously flickering when zooming multiple series

SWC0074-440

"Unhandled rejection TypeError: Cannot read property 'isLoading' of undefined" is triggered when adding two identical series under "Series Configuration" of the "wf-historical-data-chart" extension

SWC0074-453

The value set for the Transparency property is not applied at run time, for the "wf-historical-data-chart" extension

SWC0074-520

The runtime "wf-historical-data-chart" displays no data if more than one Signal is set at design time and an error is triggered

SWC0074-531

VChannel write speed gets delayed when Incresing timeout for Async writes

SWC0074-87

ModalDialog parameter transfer error on wf-value-display

SWC0074-427

Studio crashes when deleting items from a group

SWC0074-462

Scheduler Pro _The Time stamp is not correctly displayed for Events

SWC0074-240

The TestCenter always uses the first entry of the Server List

SWC0074-433

SNMP Connector Error is triggered each time changes at level of the connector occur

SWC0074-441

Click and hold issue for the wf-historical-data chart extension

SWC0074-442

Deleting last series in the wf-historical-dta-chart extension leads to issues

SWC0074-443

When activating the Axis property "Usage of integer values", for the wf-historical-data-chart extension, the axis scaling is hidden

SWC0074-477

The columns in SchedulerPro are not variable in width

SWC0074-482

Labels aren't formatted as configured, for the wf-historical-data-chart component

New Configuration Settings

Relevance

Setting

Description

Server

WritingWithImmediatelyWCSAcknowledge

Used in combination with the Asynchron Signals writing mode. Depending on the setting value, the Asynchron mode will return a feedback and a result code, for the writing operation:

  • False - The server always returns a result code "0", regardless if the write operation was successful or if it failed

  • True - The server returns a feedback and a result code, for the write operations. The following Server Result Codes and messages can be delivered: Succeeded (0), WriteFailed (-1073479674), WriteExpired (-300) and WriteFaulted (-301)

This setting can be found under this path: "C:\Program Files (x86)\i4SCADA\Server\ServerSvc.exe.config".

Tip

For more details, please also visit the dedicated article here.

WritingStateTimeout

Even if the Asynchron (with result code) mode does not block the server, during the write operation, the server waits until the write is finished.

On slow devices, the write operation might encounter timeouts, hence, it is recommended that the „WritingStateTimeout“ setting is properly configured. By default, the timeout value is set to 500 milliseconds, but it can be increased or decreased, as desired.

This setting can be found under this path: "C:\Program Files (x86)\i4SCADA\Server\ServerSvc.exe.config".

Tip

For more details, please also visit the dedicated article here.

WritingStateTimeoutCheckInterval

Sets the time interval (measured in milliseconds) that the server waits before a write request expires and the timeout error is triggered. The default value is 100 milliseconds.

This setting can be found under this path: "C:\Program Files (x86)\i4SCADA\Server\ServerSvc.exe.config".

SnmpReadDataTimeoutSeconds

Sets the time interval (measured in milliseconds) that the server waits for the SNMP to read / write a request that needs to be executed. The default value is 10 milliseconds.

By default, these settings are commented, therefore the default value is considered. To increase or decrease the default value, the user needs to uncomment the settings, before updating the value.

These settings can be found under this path: "C:\Program Files (x86)\i4SCADA\Server\ServerSvc.exe.config".

SnmpWriteDataTimeoutSeconds

Studio

GetDependenciesOnDeleteSignalsClassicCommandTimeOut

On attempt to delete a signal, the system performs a check, looking for signal(s) associated dependencies (e.g. translations, alarm conditions, alarms, logs, etc).

Signals having alarm conditions or log conditions associated, cannot be deleted, until those dependencies are also removed. If there are other type of dependencies, the Signal Dependencies dialog will ask the user to confirm the deletion of the signal and all the corresponding dependencies. If the delete operation is finally approved, an attempt to delete the signal and all the corresponding dependencies is initiated.

Therefore, the Signal deletion can be a long running operation. Most of the errors, encountered when deleting signals, are caused by time-outs of the queries executed against the database.

Studio exposes some of the properties, involved when such queries are run against the database, so besides these three settings, there are more available.

Tip

For more details, please visit the dedicated troubleshooting article here.

DeleteSignalsBulkClassicCommandTimeOut

DeleteAllSignalsOfGroupClassicCommandTimeOut