Re: [foxboro] omset
- From: "Lowell, Timothy" <Timothy.Lowell@xxxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 22 Jul 2013 17:36:13 -0500
I always recall the rule of thumb in the bad old nodebus days being no more
than 3 calls in a row to a CP without putting a sleep statement in the script
or WAIT in the HLBL code. The MESH and CP270 might be able to handle more,
though.
Tim Lowell
Maverick Technologies | 210-439-5914 (cell)
On Jul 22, 2013, at 5:28 PM, "Schouten, Frits JF"
<Frits.Schouten@xxxxxxxxxxxxxxxxxx> wrote:
> Dear all,
> I have an issue with omset/omsetimp.
> It is not always setting/reseting bits or writing values to a CP.
>
> What I'm really asking is: Are omset/omsetimp 100% reliable?
> Today we lost 10 hours production because of an omsetimp command that didn't
> reach the CP.
>
> Regards,
> Frits Schouten
> Principal Engineer
> Process Computing Department
> Aukland: +64 +9 375 8111 ext 5261
> Waiuku: +64 +9 236 5911 ext 5261
> Mobile: 021 963894
> Email:
> Frits.Schouten@xxxxxxxxxxxxxxxxxx<mailto:Frits.Schouten@xxxxxxxxxxxxxxxxxx>
>
>
> ________________________________
>
>
> NOTICE - This message and any attached files may contain information that is
> confidential, legally privileged or proprietary. It is 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 recipient, be
> advised that you have received this message in error. Any dissemination,
> copying, use or re-transmission of this message or attachment, or the
> disclosure of any information therein, is strictly forbidden. BlueScope Steel
> Limited does not represent or guarantee that this message or attachment is
> free of errors, virus or interference.
>
> If you have received this message in error please notify the sender
> immediately and delete the message. Any views expressed in this email are not
> necessarily the views of BlueScope Steel Limited.
>
>
>
> _______________________________________________________________________
> 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
Other related posts:
