Maks, The GDEV USERL1 & USERL2 parameters have no affect on the block algorithm and are available strictly as data stores for an application... Another interesting parameter along the same line is the OWNER parameter (on GDEVs and many other blocks). OWNER is a 32 character string with "test and set" capabilities when used with sequence logic. If an attempt is made to write a non-blank string (i.e. the sequence block name) to OWNER that doesn't match the value already there, a system error 18 (OP_ERR) is generated. Use TO_SYS_ERROR SBX logic in the sequence block to trap the error 18. If no error is generated, the sequence block is the new "owner" of the target block. If multiple sequence blocks attempt to write to the OWNER parameter simultaneously, only one will be successful with no error 18! The OWNER parameter and the ACTIVE parameter (i.e. ACTIVATE XXX WHEN ALREADY GOTO YYY) of sequence blocks are the only two parameters in IA with "test and set" capability... Regards, Doug Lloyd DGL Controls -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Maks Wilde Sent: Monday, January 21, 2008 4:06 PM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] GDEV USERL1 Input Dear List, Is there any more information available on the GDEV USERL1 input than that provided in FoxDoc? I am trying to understand some old sequence code, and why this input is used. Does setting the value of USERL1 affect the GDEV block in any way, shape or form? We do not have Batch Plant Management or similar. FoxDoc description: USERL1 User Long 1 is a long integer input that can be used for application-specific purposes associated with the device that the GDEV block controls. Applications such as Batch Plant Management can use USERL1 when they own the block. Thanks! Maks Wilde -- Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system. _______________________________________________________________________ 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