On DNP3 points there is the 'Disable Alarm Reporting' pick action next to 'Disable Alarms' which tells the outstation to stop generating events for that point. Our operators have on occasion gotten those two actions mixed up and accidentally disabled alarm reporting when they wanted to disable alarms. I looked into removing 'Disable Alarm Reporting' as part of their permissions but found it's tied with the Disable Alarm permission.   Is there a way to prevent operators from disabling alarm reporting while retaining their access to disabling alarms? ... View more

Hi,   Are there any configuration fields on a SCADAPack E Direct Outstation object which apply to the following settings on an RTU config: LED Power Always On VLOOP Output Select   Both settings are located under General -> Controller Settings in E-Series Configurator.   Whenever we generate a config file from ClearSCADA, those settings are not set the way we want. So I'm wondering is there a way we can set those without having to manually attach a .rtu add-on file to every affected outstation?   Thanks in advance. ... View more

So when you read the firmware stats for a SCADAPack E-Series RTU, you get a numerical firmware revision (integer system point 50001) and a firmware description (string system point 50736). Past some firmware release, it looks like to me that TRSS started bundling the RTU firmware releases with the ClearSCADA releases but I'm not 100% sure on that.   I can see that on some of our older SCADAPacks on firmware 8.05 where the firmware description simply says 'SCADAPack E Firmware 8.05.x'. If I then go to one of our newer SCADAPacks on firmware 8.12, the firmware description says 'SCADAPack E Firmware 2014 R1.0', which seems to indicate a connection to a particular ClearSCADA release? Similarly, a SCADAPack on 8.15 says 'SCADAPack E Firmware 2017 R2.2'.   Just for my curiosity, my questions are: If an E-Series firmware does indeed correspond to a particular ClearSCADA release, is there a reference document somewhere that details this? Why does the firmware have a subversion for its Revision number (e.g. R2.2) if ClearSCADA versions don't abide by this. There is no ClearSCADA 2017 R2.2 for example.   Thanks. ... View more

Hi,   We have a single pump template that caters to two different types of VSD's that both talk via the built-in SCADAPack Modbus Scanner. The only difference between those two types of VSD's is the Modbus mapping is different. This difference is currently accounted for via a template parameter, i.e. you set this parameter in the site instance to 0 and it will use a certain Modbus map, while setting the parameter to 1 will use a different Modbus map. This allows the single template to cater for both VSD configurations.   The issue is if maintenance crews change the VSD out on-site from one type to another, then we have to be engaged just to toggle that one parameter. Is there a way to expose template parameters somehow so that it can be changed by an operator from a mimic? Such as through scripting and/or logic? ... View more