The ACTTOC feature should work regardless of whether or not the DSR_RB parameter is connected. DSR_RB is only needed if logic downstream of the GDEV (i.e. PLB) might change the actual field drive state which the limit switches should be compared against. Regards, Doug Lloyd DGL Controls -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Pirie, Sandra M Sent: Wednesday, April 19, 2006 9:11 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] ACTTOC in GDEV blocks Thanks Dirk, The GDEV block has a TOC and dev limits configured, but no DSR_RB (=3D = 0). Regards, Sandra. -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Pauwels, Dirk - RSM Sent: 19 April 2006 12:54 To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] ACTTOC in GDEV blocks If you have a TOC and dev limits and DSR_RB =3D3D 1 then you should = always get the ACTTOC. Rgds, Dirk -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Pirie, Sandra M Sent: woensdag 19 april 2006 13:28 To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] ACTTOC in GDEV blocks Hi List, One example of a GDEV block for an ROV calculates the ACTTOC (actual travel time) whilst another doesn't. Is it because the DSR_RB is not connected? How can I get the ACTTOC calculation to work? Thanks, Sandra. =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