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
> 
> 
> 

-----------------------------------------------------------------------
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]

Reply via email to