ICAW Display Issue

108 views
Skip to first unread message

Eileen Suszek

unread,
Oct 17, 2011, 1:29:57 PM10/17/11
to IADS, Monica.d...@nasa.gov
An “Iads.ICAWiadsICAWControl” was selected from the ActiveX Controls
tab on the IADS Display Builder to display 1553 messages when an
Integrated Caution Advisory Warning (ICAW) fault value is detected.
The ICAW display was setup using an ICAW input file according to the
directions available from the IADS v5.3.2 on-line help.

When the ICAW display was distributed in real-time, the following
pairs of messages scrolled on the IADS Compute Data Server (CDS) for
every parameter listed in the ICAW input file: “Unable to locate
parameter = RSXXXX under stream = (null) will use stream = XX_X02STRM
Unable to locate parameter XX_X02STRM:DECOM_STATUS in Iads control
database.”
The “X’s” are merely placeholders so we don’t need to list the real
parameter names.

We are using a Wyle OMEGA front end and have theLT4IADS (low stream
time), HT4IADS (high stream time) and DS4IADS (decom status) defined
in the iadsConfig file according to the IADS Output Module
descriptions for the first stream as documented in the IADS on-line
help, however, we do not have stream names associated with a parameter
name DECOM_STATUS for every stream. No ICAW messages will be
displayed. We are using the OMEGA simulator for the data source.
We read a discussion under the IADS Google Group that there was an
option to turn off “Use decom status protection” under the ICAW
property sheet, however, it was not an option under IADS v5.3.2.

Would you explain why we are receiving the pairs of messages on the
IADS CDS for every parameter listed in the ICAW input file? Is there
a workaround available or another IadsICAW.dll version that might run
with the Wyle OMEGA front end and IADS v5.3.2?

Adam Chant

unread,
Oct 17, 2011, 2:13:12 PM10/17/11
to ia...@googlegroups.com, Monica.d...@nasa.gov
The Iads.ICAWiadsICAWControl had limited support for the Omega Wyle system
in IADS version 5.3.2.
"Decom Status Protection" was not available for the Wyle system at that
time. While ICAWs should still display, without decom status protection, it
would also display false ICAWs during lost of TM Sync.
The message says that a stream was assigned to individual parameters and if
the simulator was sending out values that would signal an ICAW it should
display active ICAWs. If no ICAWs were being displayed then verify that the
simulator was producing values for those parameters that could correlate to
known ICAW values.
IADS version 5.3.2 is an obslete version of the softare and the solution to
having decom status protection for use with the Wyle system would be to
upgrade to the IADS version 7.x.

Adam Chant
Symvionics, Inc.
IADS Application Engineer
(661) 273-7003 x 210

--
You received this message because you are subscribed to the Google Groups
"IADS" group.
To post to this group, send email to ia...@googlegroups.com.
To unsubscribe from this group, send email to
iads+uns...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/iads?hl=en.

joy....@gmail.com

unread,
Oct 18, 2011, 12:22:16 PM10/18/11
to ia...@googlegroups.com, Monica.d...@nasa.gov
Adam,
 
Can you please explain why the pairs of messages continue to scroll on the IADS CDS when the ICAW display is distributed in real-time for every parameter listed in the ICAW input file:  "Unable to locate parameter = RSXXXX under stream = (null) will use stream = XX_X02STRM
Unable to locate parameter XX_X02STRM:DECOM_STATUS in Iads control database?" 
Is there code embedded in the ICAW.dll that requests a parameter called DECOM_STATUS? 
No DECOM_STATUS parameter is being requested in the ICAW input file.
The ICAWS are not displaying but as you stated "The ICAW should still display without decom status protection." 
The simulator was sending out values of 0 and 1 as verified by data displayed on stripcharts.
Can you suggest a possible workaround and/or is there another version of the ICAW dll that may work with the OMEGA Wyle system?
This is a high priority for us and we'd appreciate whatever help you can provide other than upgrading to IADS v7+
Reply all
Reply to author
Forward
0 new messages