The syntax
> ::MY_CIN_BLOCK.UNACK := FALSE;
>
using 2 semi-colons is correct. If it were in a different compound then it
would be
:COMP:MY_CIN_BLOCK.UNACK := FALSE;
My understanding is that if you use these type of "soft" connections (or
what are known as IP connections) then you are causing broadcast messages to
go over your nodebus. I always avoid using IP connections where possible.
Also, putting a WAIT statement inside the loop of your IND block will reduce
the frequency of execution and the number of broadcast messages.
Regards,
Dan
BP Amoco Refinery
Bulwer Island, Australia
> ----------
> From: Guoqiang Lu[SMTP:[EMAIL PROTECTED]]
> Reply To: Foxboro DCS Mail List
> Sent: Saturday, 15 January 2000 7:37
> To: <
> Subject: external reference in HLBL (was Re: FT CP40 failed)
>
> Thanks all for all the info.
>
> Foxboro rep mentioned that in most cases "green dead" CPs are caused by
> nodebus traffic jams. I am going through the configuration to see if any
> improvement can be done. We have about 13 IND blocks with endless loops
> basically setting and clearing the alarm bit of CIN blocks (these blocks
> in turn light up the annunciator panel). There is one assignment in the
> IND block with the form:
>
> ::MY_CIN_BLOCK.UNACK := FALSE;
>
> The block CIN block "MY_CIN_BLOCK" is in the same compound as the IND
> block. So my question is, shouldn't the above assignment have only ONE
> leading colon? In the B0193AV manual, it says that the leading colon
> "Begins an external reference to a block, compound or block parameter, or
> shared variable. ". Does the word "external" here mean " external to the
> IND block" or external to the station where the IND resides? What I am
> trying to determine is whether the above assignment generates nodebus
> traffic.
>
> Guoqiang Lu
>
> P.S. I am running IA 4.3. Image: V4.2.4 CP40 12-19-97, OM V4.2.4 T1, IPC
> 41.2 9/07/94, etc.........
>
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to [EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
