Re: [foxboro] Displaying time left on a timer
- From: Jeff Hurt <hurtman@xxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 22 May 2007 09:20:31 -0700 (PDT)
Thanks to all of you. I appreciate the help.
Jeff Hurt
Indeck
--- mike.stewart@xxxxxxxxxxxxxx wrote:
> I do the same as Dirk. It's easier for other people
> to read the sequence
> code. Also if I am displaying the time to
> technicians, I always convert
> it to minutes.
>
> Mike
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Pauwels, Dirk
> Sent: Tuesday, May 22, 2007 11:06 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Displaying time left on a
> timer
>
> I always use the start - stop_timer command. It's
> easy afterwards for =
> =3D
> other people to read the sequence. I usually also
> reset the TIMR1V to =
> =3D
> zero when the timer is stopped. It's a habit
>
> Rgds,
>
> Dirk
>
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> =3D
> On Behalf Of Sascha Wildner
> Sent: dinsdag 22 mei 2007 16:38
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] Displaying time left on a
> timer
>
>
> Pauwels, Dirk wrote:
> > We show the TIMER.TIMR1V parameter on the screen
> when the timer is
> > activated, it's in seconds offcourse. If you need
> minutes use a calc =
> =3D
> or
> > do the math in the sequence like Mike says.
>
> Hi,
>
> related question: As TIM blocks used for countdowns
> in most of the=3D20
> cases, is there any real gain in using START_TIMER()
> and STOP_TIMER() =
> =3D
> still?
>
> I usually configure my TIM blocks like this (for the
> first timer):
>
> TIMER.TIMR1R =3D3D :TIMER.POS_V1.~
>
> ...and write (a negative value) directly to
> TIMER.TIMR1V.
>
> Regards,
>
> --=3D20
> Sascha Wildner
> erpicon Software Development GmbH
> Neusser Str. 724-726
> 50737 K=3DF6ln
> Germany
>
> Phone: +49 221 9746089
> Fax: +49 221 9746099
> eMail: swildner@xxxxxxxxxx
> =3D20
> =3D20
>
_______________________________________________________________________
> 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
> =3D20
> foxboro mailing list:
> //www.freelists.org/list/foxboro
> to subscribe: =3D
>
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
> to unsubscribe: =3D
>
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
> =3D20
> =20
> =20
>
_______________________________________________________________________
> 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
> =20
> foxboro mailing list:
> //www.freelists.org/list/foxboro
> to subscribe: =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
>
>
>
_______________________________________________________________________
> 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:
> //www.freelists.org/list/foxboro
> to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
