Application Objects are simply Shared Variables with a funny name. The are subject to EXACTLY the same rules as a SV. As an experiment, you might try changing an SV in the same manner on the same AW and see if the results differ. They should not. Is there retry logic in the code, e.g., do you trap on a failed set and then retry? Regards, Alex Johnson Invensys Process Systems Invensys Systems, Inc. 10707 Haddington Houston, TX 77043 713.722.2859 (voice) 713.722.2700 (switchboard) 713.932.0222 (fax) ajohnson@xxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Lowell, Tim: Sent: Wednesday, November 17, 2004 1:44 PM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] Setting Application Objects from IND blocks We are working on a DMCplus application where we have to set the values of Application Objects, which were generated by DMCBridge, using an IND sequence block. We are noticing a great deal of latency, upwards of 1 or 2 minutes, between the time the IND sequence code runs and when the Application Object value gets set. Here is an example bit of IND HLBL code: IF value1 > value2 :APP_OBJ_CMPND:APP_OBJ.PARAM := value3; ENDIF Is this fairly typical of IND sequence code performance? Is there something special about Application Objects vs. regular CP blocks that might cause this? Is there a setting somewhere that maybe we have left at the default that governs how fast AO's can be written to? Any ideas would be appreciated. Thanks, Tim Lowell Control Systems Engineer ConocoPhillips Trainer Refinery (610) 364-8362 tim.c.lowell@xxxxxxxxxxxxxxxxxx _______________________________________________________________________ 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: http://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: http://www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave