Rob,
read very carefully what John is saying.
The TIME kept by a CALC block is very stable.
What I read between the lines is: use the TIM statement to record/store the beginning 
and or end of an event and use the difference as the lapse time.
Looks neater in the code too, but that's more of a personal opinion.

Cheers,
Frits.
BHP-NZSteel

-----Original Message-----
From: Johnson, Alex [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 02, 2001 9:51 AM
To: Foxboro DCS Mail List
Subject: RE: Block Scan Time


I hit the button too quickly.

The time kept by the Station Block and by the CALC block are both stable.

The CALC will give you seconds since midnight. The Station Block provides
year, month, day, hour, and minute (but not second if I remember properly).

I suspect that your best bet is to use the CALC block.


Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 


        -----Original Message-----
        From:   Burnham, Rob C. [SMTP:[EMAIL PROTECTED]]
        Sent:   Thursday, February 01, 2001 2:32 PM
        To:     'Foxboro List'
        Subject:        Block Scan Time

        Can a blocks scan time be used
        to accurately count? I am trying to
        to count elapsed seconds of overflow
        on a tank, the scan time for the block
        is 1 second and I increment a memory
        register by one on each scan.
        Is this accurate?

        Rob Burnham
        P. H. Glatfelter Co.
        920 727-2426


        
-----------------------------------------------------------------------
        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]

EOM 

NOTICE - This message contains information intended only for the use of the addressee 
named above.  It may also be confidential and/or privileged.  If you are not the 
intended recipient of this message you are hereby notified that you must not 
disseminate, copy or take any action in reliance on it.  If you have received this 
message in error please notify [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