[foxboro] Tool development (was Spare I/O points)

Hi,

everyone is developing his own tool or toolkit to extract data out of
the I/A system.

Why is that?
I vote that a lot of users are not happy with FoxCAE.

Why isn't Invensys Foxboro able to recognize this gap and offer a
solution?
I don't know.

But it would help developers like you and me if we had a way to exchange
our code.
Why not working more together? I think that we had a call for action
like this sometime ago and I'm interested again.
That would require that all developers in a project accept the code
formatting rules and a lot of other stuff ...=20

more concrete

I'm working on a standardized way of extracting all Control Station
Database data into other file formats. I develop my own thing (at this
time) because I'm not happy with existing tools, they are not failsafe
enough and not able to run 24x7x365.
The project is splitted into different parts:
1. detecting changes in the Control Station database
2. extracting the Control Station database information=20
3. converting the information into different file formats (xml, txt, sql
database)=20
4. creating subsets of these information for specific tasks (data file
for visualizing the used I/O points, ...) because the amount of data
(file sizes) takes a lot of machine ressources
5. offer the data for clients or client programs on other machines

Part 1 and 2 are nearly finished. Part 3 is finished for one
xml-file-format.=20
I'm using kornshell scripts at this time.

Let's see how far this project grows.

Regards,
Andreas Weiss

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: