There's an internal thermometer on the Schneider SCADAPack 334 E-Series RTUs. I spent ages trying to find out how to access it and read the temperature on the RTU.
And then, hidden in a release note, I found it. It is an internal analogue DNP3 point with a point number of 50062.
Random, but it worked!
Showing posts with label E-Series. Show all posts
Showing posts with label E-Series. Show all posts
Monday, January 14, 2013
Thursday, October 13, 2011
SCADAPack E-Series
I've been developing some remote field RTU software for the Schneider/Control Microsystems SCADAPack 334E. This is a nifty little device that let's you program in about 6 different styles using the IEC 61131-3 protocol in a software package called ISaGRAF. I've been sticking to function blocks because it's neat and new for me and easy on the eye. There's a USB host port on the front, so I thought it'd be easy to program the device to log data to a USB key on it, right? Especially considering there's an example on the internet for it.
Well, I was wrong.
I was trying to get this example to work on my SCADAPack: http://resourcecenter.
But I went to debug via the configurator, and I came across the same debugging errors:
So I asked what I could do with the USB host port. And I was told
Apart from this though, the SCADAPacks are great little devices for field units!
Well, I was wrong.
I was trying to get this example to work on my SCADAPack: http://resourcecenter.
Further digging showed me that the dlog and
dlogcnfg weren’t installed at all in ISaGRAF. The function blocks were
there in the code I downloaded, but they had no back end to them. They
weren’t in the Library at all.
I
then went to the DVD that came with USB licence key and installed the
software on there. This one said “IEC61131-3 Programming language suite
for SCADAPack controllers”. Previously I was using a downloaded ISaGRAF
from their webpage because I started developing in demo mode. Opening the
DLog project, the dlog and dlogcnfg function blocks were there. But
then when I went to debug the program, there was no option for
“Configurator” in the debug Communication port link parameters!
I
had a bit of a head scratch, then tried importing the libraries from
the DVD version of ISaGRAF to the downloaded E-series ISaGRAF. Using the
“Libraries” program of the E-Series version, I restored from archive
all of the dlog associated C function blocks from C:\ISAWIN\LIB\SOURCE\
(the DVD version’s location). Going back into the programs in the
downloaded E-Series version, the dlog and dlogcnfg function blocks were
there!
Frustrated, I gave a quick Google which lead to this webpage: http://resourcecenter.
A program is using a C function block, which is unknown in the target. Your workbench library may not correspond to your target version.At this point, after hitting my head against the keyboard repeatedly, I decided to get a hold of tech support. Where I was able to find out:
The problem here, in a nutshell, is that the E-Series RTUs do not support the dlog functionality.Cool, well I can do logging, but it's not software controlled. It's on a timer as trend data. Not as flexible as I would have liked, and it does not save on the USB.
This functionality is native to the SCADAPack controllers, but the E-Series, which are born from entirely different firmware, do not have an implementation of dlog.
The E-Series controllers DO however have some data logging capabilities.
If you open the E-Series Configurator Reference Manual, take a look here: E-Series Technical Reference Manuals > SCADAPack E-Series Trend Sampler Technical Reference
So I asked what I could do with the USB host port. And I was told
Unfortunately the USB Host port is not currently supported by the E-Series operating system.Excellent. Not in use at all. Despite being ranted and raved over in the documentation and advertising.
It may be supported in the future, but I’m not sure when.
Apart from this though, the SCADAPacks are great little devices for field units!
Subscribe to:
Posts (Atom)