Hi Doug, Good idea! I'll start checking the P2P relations and build local copies where needed. Thanks & Rgds, Dirk "Douglas G. Lloyd" <doug@xxxxxxxxxxxxxxx> Sent by: foxboro-bounce@xxxxxxxxxxxxx 25/08/2010 17:11 Please respond to foxboro@xxxxxxxxxxxxx To <foxboro@xxxxxxxxxxxxx> cc Subject Re: [foxboro] system error in sequences Dirk, A way to minimize the problem would be to build copies of this block parameter for each external CP that requires access. Best case would be to build copies local to each CP to eliminate the one shot peer-to-peer access. Have all of the sequences in a particular CP read their own local copy. This approach should eliminate the access collisions and also cut down on network traffic. Regards, Doug Lloyd DGL Controls -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of dirk.pauwels@xxxxxxxxxx Sent: Wednesday, August 25, 2010 10:28 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] system error in sequences Hi Doug, That could well be the case, this pressure xmttr is used by a lot of ind's and calc's. In that case it'll be difficult to solve this probably, other than extending the exception to sys-error or exception to manual I guess. I'll do some more testing on it. Thanks Dirk "Douglas G. Lloyd" <doug@xxxxxxxxxxxxxxx> Sent by: foxboro-bounce@xxxxxxxxxxxxx 25/08/2010 15:30 Please respond to foxboro@xxxxxxxxxxxxx To <foxboro@xxxxxxxxxxxxx> cc Subject Re: [foxboro] system error in sequences Here's another possible reason for the intermittent sequence errors: If multiple sequences are trying to access the same parameter from different CPs, they can collide every now and then and cause an access error. This can happen with a read or a write, since even a read function appears to temporarily "secure" the parameter. It's generally not a problem if multiple sequences in the same CP access the same parameter since they really can't execute simultaneously. But, no guarantees peer-to-peer. Regards, Doug Lloyd DGL Controls _______________________________________________________________________ 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