Hi,
Are there any configuration fields on a SCADAPack E Direct Outstation object which apply to the following settings on an RTU config:
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.
Solved! Go to Solution.
Unless this has changed in a recent version of ClearSCADA / GeoSCADA Expert, then the answer is no.
The workaround to this is to upgrade all of your SCADAPack E series RTUs to the new 57x rPAC units 😉 hehehe just kidding.
The workaround is to use E-configurator to generate a .RTU configuration which includes the appropriate setting that you want for the LED and VLOOP. Then to open the .RTU in a text editor and search for the bit that means what you want.
Remove everything else and add this .rtu as a prepend file against your ClearSCADA E-Series object.
This way when you generate the config it will get added first, the outstation config doesn't overwrite it, and it gets pushed into the RTU... a bit of a headache, but it works.
You could raise this with your local Schneider Tech Support. There is already a PDEV against this I believe, it just needs more votes.
Hi guys, these fields will be available in the next major release, they have already been implemented.
Unless this has changed in a recent version of ClearSCADA / GeoSCADA Expert, then the answer is no.
The workaround to this is to upgrade all of your SCADAPack E series RTUs to the new 57x rPAC units 😉 hehehe just kidding.
The workaround is to use E-configurator to generate a .RTU configuration which includes the appropriate setting that you want for the LED and VLOOP. Then to open the .RTU in a text editor and search for the bit that means what you want.
Remove everything else and add this .rtu as a prepend file against your ClearSCADA E-Series object.
This way when you generate the config it will get added first, the outstation config doesn't overwrite it, and it gets pushed into the RTU... a bit of a headache, but it works.
You could raise this with your local Schneider Tech Support. There is already a PDEV against this I believe, it just needs more votes.
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
Hi guys, these fields will be available in the next major release, they have already been implemented.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!