i4scada Version 3.9.0
Check out the Changes and Fixed Bugs of thei4scada 3.9.0 Version. The i4scada version brings along a large number of improvements and bug fixes.
Changes
ID | Description |
---|---|
I4SCAD-996 | Integrate the SQL Server Express 2022 in the i4scada Setup 3.9 TipThe i4scada setup comes with an integrated SQL Server Express 2022 which replaces the SQL Server Express 2016 version. However, the SQL Server Express 2016 version is still compatible with the new setup. |
I4SCAD-1008 | Implement the latest SIMATIC Driver for i4scada TipThe SIMATIC connector as well as the OPC UA and BACnet connectors have been upgraded to .NET Framework 4.8. The WTS has been dropped in the i4scada 3.9 version and it was replaced with Nlog. The ACCON-AGLink Module was upgraded to version 6.0.0.0. |
I4SCAD-1005 | The advanced logging of the MessengerPro add-on has been improved around the email sending |
I4SCAD-994 | Improve the responsiveness when an alarm or a batch of alarms gets acknowledged, especially when the alarm horn is been playing |
I4SCAD-744 | Upgrade MessengerPro to .NET Framework 4.8 |
I4SCAD-330 | Optimize the OPC UA browsing and import processes |
Fixed bugs
ID | Description |
---|---|
I4SCAD-1047 | i4Studio crashes when browsing BACnet networks with around 600+ devices |
I4SCAD-1046 | i4Studio crashes when trying to save more than 100.000 BACnet signals to the database |
I4SCAD-1001 | The Alarm viewer header and text should be aligned to the left |
I4SCAD-1000 | Alarm API does not sort the elements in a stable way when sorted by start date and there are the same dates |
I4SCAD-999 | The Alarm viewer table rows are not correctly displayed if multiple extensions are available on the same page |
I4SCAD-985 | Alarm delay/SuppressionDuration causes problems and the Alarm Manager no longer starts |
I4SCAD-750 | Configuration of the OPC UA connector gets lost |
I4SCAD-1051 | Performance issue when using distributed i4scada environment - clients show different status |
I4SCAD-730 | Security token expires after one minute on the Smart Editor visualizations |
I4SCAD-671 | The loading time of the Alarm Viewer list is slow |
I4SCAD-613 | IIS Worker Process consumes up to 100% of the CPU |
I4SCAD-578 | When creating a new project using the Visual Studio application some files are missing |
Known limitations
If you are a MessengerPro user, make sure that you are aware of the known limitations.
Since the 30th of May 2022, Google no longer supports the use of third-party applications or devices that ask you to sign in to your Google Account using only your username and password. Therefore, delivering email notifications using the MessengerPro add-on from POP3 and SMTP email servers using only username and password authentication is no longer possible.
New Configuration Settings
Relevance | Setting | Description |
---|---|---|
Server | AlarmNotificationManagerService | To improve the Alarm Viewer performance, advanced caching was introduced in the AlarmNotificationManagerService to avoid polling the entire database each 1000ms. The render performance was improved at the level of the Webservices as well. <endpoint address="net.pipe://localhost/Scada/AlarmNotificationManagerService" binding="netNamedPipeBinding" bindingConfiguration="LargeBufferNamedPipe" name="NamedPipeEndpoint" contract="Scada.AlarmManager.Contracts.IAlarmNotificationManagerService" /> This setting can be found under path: C:\Program Files (x86)\i4SCADA\Server\AlarmManager |