Hi David, long, long time ago, before I switched to FoxAPI, I programmed a 1 second delay for every 5 OM calls. I'm not sure it that was the optimum but it worked for me alright.=20 Nowadays I'm using the 'uread' and 'uwrite' API calls for those one off bunches of data I want to put/get to the control stations. It's just an array of points/values that you pass to the one API call. Nice and easy. But, like I said in one of my previous e-mails, I have had some issues with FoxAPI calls. Cheers, Frits. -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of David Johnson Sent: Wednesday, 1 June 2005 06:16 To: Foxboro@xxxxxxxxxxxxx Subject: [foxboro] Proper wait time for omget Hello all, I am planning to use /opt/fox/bin/tools/omgetimp to get several values=20 (less than 300). I know that omgetimp sends a broadcast message to the get=20 the information the first time, which can be bad if too many requests are=20 sent too fast. Speed isn't a big concern, but I don't want to wait much longer than necessary. Is 1 second between om requests sufficient, 2=20 seconds, 4 seconds, or something else? I have searched the old postings,=20 and see a lot of apocryphal information, like I can use omget for 100=20 values a minute with no problems (that I notice, on my small node, etc.) but no hard numbers that I can work from. If I can get something together,=20 I will consolidate the information and post it on the cassandra site so I=20 will never have to ask this question again. Also what's the difference (if any) between using the omget family and=20 calling up an un-optimized display the first time? Doesn't the display=20 make a broadcast call for each connection on the graphic? Thanks, David "An utterly fearless man is a far more dangerous comrade than a coward." Starbuck, Moby Dick=20 EOM=0A=0ANOTICE - This message and any attached files may contain informa= tion that is confidential and/or subject of legal privilege intended only= for use by the intended recipient. If you are not the intended recipient= or the person responsible for delivering the message to the intended rec= ipient, be advised that you have received this message in error and that = any dissemination, copying or use of this message or attachment is strict= ly forbidden, as is the disclosure of the information therein. If you hav= e received this message in error please notify the sender immediately and= delete the message. _______________________________________________________________________ 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