About rlao

rlao

Hi Bevan, Thanks, that's a bummer. Your alternate method of pre-pending RTU configs is something we have done a lot in the past and it's a bit of a pain to manage. I was definitely hoping for an easier way but no luck I guess. @JChamberlain, are you aware of this particular PDEV? Would I have to formally raise a support ticket or can I just ask you here to add a vote on my behalf? Cheers

rlao

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.

rlao

Hi Geoff, Yes that's the way we've always done it, but I am trying to embrace the use of template parameters. Works very well in some cases but I've also encountered shortcomings such as this. I think if there was a way to expose template parameters to the end-user rather than just have it as an engineering thing, it would be a lot easier to adopt.

rlao

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.

rlao

Thanks Jesse, probably too much complexity and trouble for our particular situation but definitely good to keep in mind for future.

rlao

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?

rlao

Thanks Steve, I got around to trying your meta-query and it helped considerably. It needed a little bit of tweaking, mainly around all the aggregate classes as they need their select statements manually modified to inner join on CDBObject (as they don't directly contain a FullName).

rlao · ‎2020-02-20

Thanks for confirming Adam. At least it sounds like I'm on the right track with how I'm approaching this and not missing something obvious. Some sort of Alarm Severity Summary table as Bevan suggested would be very helpful, although I'm not exactly sure how feasible it is to implement such a feature.

rlao · ‎2020-02-19

Hi all, Broad question, but I am undertaking some alarm rationalization work and am wondering if there is an efficient way to query what the value of all alarm severity fields are across all relevant object classes in a ClearSCADA database? The only way I know of currently is to individually query object classes like CeNetAnalog, CPointAlg, etc. one by one for all of their alarm severity fields and manually compile all the information somewhere like a spreadsheet. Quite a time-consuming process and my main concern is that it is very easy to accidentally miss alarms on object types that I'm not aware even had configurable alarms in the first place. For example, I only just learnt that CRootGroup has a WSEventSeverity field for workstation events as well as multiple aggregates that each have severity settings too. I'm just thinking could there be a way to work backwards instead and somehow start from the severity settings in Server Config and somehow grab a list of all references to that?

rlao · ‎2020-02-16

Hi Jesse, No worries, I'll shoot a formal email to support. We are already running CS2017R2 Oct 2018 patch (79.6884) so it is probably not covered by SUP-10408 .

Online Status	Offline
Date Last Visited	7 hours ago

Explore Exchange Community

About rlao

Re: Using ServerObject.Interface to read array-based properties

Re: Using ServerObject.Interface to read array-based properties

Re: Changing LED and VLOOP settings on a SCADAPack E Direct Outstation Object

Changing LED and VLOOP settings on a SCADAPack E Direct Outstation Object

Re: Set the value of a Template Parameter on an Instance via Scripting/Logic

Corresponding ClearSCADA Release Version for SCADAPack E-Series Firmware

Re: Set the value of a Template Parameter on an Instance via Scripting/Logic

Set the value of a Template Parameter on an Instance via Scripting/Logic

Re: Querying Alarm Severity settings across an entire database

Re: Querying Alarm Severity settings across an entire database

Querying Alarm Severity settings across an entire database

Re: Weird URL escape behaviour when calling TrendSpec in a WebX client

Support

FAQ

About