Re: [foxboro] DEP block error code : Summary

  • From: "Windle, John" <jwindle@xxxxxxxxxxx>
  • To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
  • Date: Wed, 24 Mar 2004 08:10:30 -0500

I keep the following in my PDA.

Sequence Errors

24xx  - ACTIVE parameter set error
21xx  - runtime data conversion
        error
2101  - bool->integer or real
2102  - integer->bool
2103  - array write error
2116  - array read error
23xx  - Violation of HLBL semantics
2301  - data type error
2302  - bool data type error
2303  - no bool data permitted
2304  - only integer permitted
2305  - incompatible operands
2306  - incompatible operands
2307  - no bool permitted
2308  - no real permitted in ORD
2309  - timer val  not treated as real
2310  - array index out of bounds
2311  - array index not long
2312  - out of bounds
2313  - out of bounds
2314  - string expected
2315  - subset expr not long
2316  - subset expr not long
2317  - input parm not writable

3xxx  - Serious, normally caught
        by the compiler
3     - attempt to set a secured
        parameter
9     - cannot convert to boolean
10    - cannot convert to string
11    - cannot convert to integer
12    - cannot convert to real
13    - too large a real for integer
15    - parameter not settable
16    - too much data
18    - locked access
19    - to character conversion err
23    - to packed bool conversion
25    - target too small

Object Manager Returns
-2    - bad data type
-1    - Getval error
-3    - setconfirm (sink secured)
-9    - malloc problems
-12   - illegal FPN
-13   - not all data returned
-41   - IPC error
-43   - remote comms error
-45   - variable not found

John Windle
Foxboro

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Sascha Wildner
Sent: Tuesday, March 23, 2004 8:05 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] DEP block error code : Summary


Omprakash wrote:

> Just a reminder that many/most of the runtime error codes are
> documented in the /opt/fox/bin/tools/oma.exe program.  Fire up
> oma and ask for the error code meaning at the "COMMAND:" prompt.
> The required syntax is "y" followed by the error code number.
> Think of it as "why am I getting this error".

Appendix A of FoxDoc Document B0193AV (Integrated Control Configurator) =

also explains all the error codes.

--
Sascha Wildner
erpicon Software Development GmbH
Neusser Str. 724-726
50737 K=F6ln
Germany

Phone: +49 221 9746069
Fax:   +49 221 9746099
eMail: swildner@xxxxxxxxxx


=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
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: