I've fired up my trusty FoxDoc CD and the answer is that the VALUE parameter
of a REAL data block is an OUTPUT.
The table describes it as a Data Variable, but the key to knowing that it is
an output is the fact that it is tied to RO1. RO1 is the range array for the
"first" block output.
Name Description Type Accessibility Default Units/Range
VALUE variable value real con/set 0.0 RO1
So, the answer is that you cannot "write" to these blocks. You can only set
them.
However, if you use an optimized set and you don't have to update them very
often, I'd say that you can use them without worrying too much.
You have a choice of setval calls. The setval and set_confirm calls allow
you to add the compound name to the IMPORT table. Other calls allow you to
get the PSAP address and use it.
The biggest concern with the IMPORT flag is that you might fill the IMPORT
table. There is one entry in it for each new compound name or SV name. Use
show_params to check how full it is. See Chapter 9 of B0193ND - System
Administration Guide for 50 Series Systems (Solaris 2.x) covers the
reconfiguration that you might require.
There are no other external issues with the ones that require you to acquire
and retain the station address.
The 'set' calls in general have to be used cautiously to ensure that you do
not saturate the target station's input buffers.
Hope this helps.
Regards,
Alex Johnson
The Foxboro Company
10707 Haddington
Houston, TX 77043
713.722.2859 (v)
713.722.2700 (sb)
713.932.0222 (f)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Schouten, Frits JF [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, June 15, 2000 6:05 PM
To: 'Foxboro DCS Mail List'
Subject: RE: OM-List question.
Thank you for your reply Alex,
but I still don't get it.
I'm reading in the REAL Variable Block description (FOXDOC) that
VALUE is con/set for accessibility.
One thing I noticed was that when I do an omget of C:B.TYPE on a
real data block I'm getting (i)151 returned while the block description
tells me, I should get (i)153?
It's a pity that I have to use (M)AIN blocks for all occasions where
(write)lists are involved. I suppose I'll have to get rid of the lists
then.....
Cheers,
Frits.
> -----Original Message-----
> From: Johnson,Alex [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 16, 2000 4:11 AM
> To: Foxboro DCS Mail List
> Subject: RE: OM-List question.
>
> I just have a moment, but...
>
> Get a copy of the document that describes the parameters of the
blocks.
>
> Only those parameters in the INPUT list which are marked as
connectable can
> be connected to with a Write list.
>
> All OUTPUT parameters are not connectable for write. The block
"owns" them
> and you may not write to the parameter.
>
>
> The table is confusing if you don't know this, but it basically
works as
> follows:
>
> 1) All parameters can be "gotten" (one-shot get: getval family
of
> calls)
> 2) Parameters marked settable can be set (one-shot set: setval
family
> of calls) under the proper circumstances (inputs if nothing is
connected to
> it; some outputs - if the block mode is appropriate, e.g. .OUT and
MA set to
> Manual)
> 3) All parameters marked as connectable have a "value record"
and can
> be connected for Read (read lists)
> 4) INPUT parameters marked as connectable can be connected for
write
> (write lists) under the proper circumstances (no one else is
connected)
> 5) OUTPUT parameters marked as connectable can NEVER be
connected for
> write.
>
>
> I hope this helps.
>
>
> Regards,
>
> Alex Johnson
> The Foxboro Company
> 10707 Haddington
> Houston, TX 77043
> 713.722.2859 (v)
> 713.722.2700 (sb)
> 713.932.0222 (f)
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
>
> -----Original Message-----
> From: Schouten, Frits JF [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, June 14, 2000 5:52 PM
> To: 'Foxboro DCS Mail List'
> Subject: RE: OM-List question.
>
> I just found a CAR related to this problem. (CAR 8843. No
action
> planned. CAR Closed)
> The C:B.Variables are of the type OUTPUT, hence the om-error
-3.
>
> The only question I have for FOXBORO is: WHY IS IT OF THE
TYPE
> OUTPUT???
>
> > -----Original Message-----
> > From: Schouten, Frits JF
> > Sent: Thursday, June 15, 2000 9:53 AM
> > To: 'Foxboro DCS Mail List'
> > Subject: OM-List question.
> >
> > Hello peeps,
> >
> > I've run into a problem with OM-lists.
> >
> > I'm in the process of replacing Global Variables with
> Compound:Block.Variables.
> > Up till now that has not been a problem. OM-lists were not
> involved so far.
> >
> > The 'C' program I'm now changing is using OM lists to
exchange
> data between Global Variables and the Program.
> >
> > Problem is that, when writing to the list, I'm getting an
OM-error
> -3 returned /* Write attempt to secured variable */ on the
C:B:Variable.
> > Just for the test I changed the list point to a real input
on a
> CALC block and that goes fine.
> >
> > In 'Select' I have no problems changing the C:B:Variables.
> > I can write to the C:B.Variables from a 'C' program using
> 'set_confirm' with no problems at all.
> > I can read/write C:B.Variables using 'omget' and 'omset'
from a
> vt100 again with no problems.
> >
> > Any ideas of what I'm doing wrong regarding C:B.Variables
in an
> OM-list?
> >
> > Regards,
> >
> > Frits Schouten
> > BHP-NZSteel
> >
> >
> >
> EOM
>
> NOTICE - This message contains information intended only for
the use
> of the addressee named above. It may also be confidential and/or
> privileged. If you are not the intended recipient of this message
you are
> hereby notified that you must not disseminate, copy or take any
action in>
> reliance on it. If you have received this message in error please
notify
> [EMAIL PROTECTED]
>
>
>
-----------------------------------------------------------------------
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]
