You might take a look at using AMI or one of the 3rd party packages that
does this.


Regards,

Alex Johnson
10707 Haddington
Houston, TX 77063
713.722.2859(v)
713.722.2700(sb)
713.932.0222(f)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 


        -----Original Message-----
        From:   Stan Brown [SMTP:[EMAIL PROTECTED]]
        Sent:   Wednesday, December 27, 2000 11:10 AM
        To:     [EMAIL PROTECTED]
        Subject:        Alarm printout format(s)?

                We are having a really hard time keeping all the serila
alarm/event
                printers on various control systems throught the mill
maintained/fed.

                As a result I have embarked upon a project to replace these
with some
                old PC's. Part of this project will be to parse these alarm
prinouts,
                and insert teh results inot a database, that will be
searchable via a
                web interface. 

                What I need, at the moment, is an education on the format of
the alarm
                printouts generted by our IA systems. 

                It appears that each alarm causes 2 lines to be printed on
the printer,
                it also appears that these are of at leats 2 differnt
formats. System
                alarms, which start with the time/datestamp, and non-system
alarms that
                start with the compund:block. Is this correct? Could anyone
explain, in
                gory detail these 2 formats?

                Also, are they a fixed format, or are the configurable? If
they are
                configurabel, where is the magic config file stored?

                We are at version 6.1 if it matters (I hope it doesn't, as
this would
                imply problems at some future time, when we upgrade).

                Any information at all, would be greatly appreciated

        -- 
        Stan Brown     [EMAIL PROTECTED]
843-745-3154
        Charleston SC.
        -- 
        Windows 98: n.
                useless extension to a minor patch release for 32-bit
extensions and
                a graphical shell for a 16-bit patch to an 8-bit operating
system
                originally coded for a 4-bit microprocessor, written by a
2-bit 
                company that can't stand for 1 bit of competition.
        -
        (c) 2000 Stan Brown.  Redistribution via the Microsoft Network is
prohibited.

        
-----------------------------------------------------------------------
        This list is neither sponsored nor endorsed by the Foxboro Company.
All 
        postings from this list are the work of list subscribers and no
warranty 
        is made or implied as to the accuracy of any information
disseminated 
        through this medium. By subscribing to this list you agree to hold
the 
        list sponsor(s) blameless for any and all mishaps which might occur
due to 
        your application of information received from this mailing list.

        To be removed from this list, send mail to 
        [EMAIL PROTECTED] 
        with "unsubscribe foxboro" in the Subject. Or, send any mail to
        [EMAIL PROTECTED]

-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Reply via email to