Thresholds and Limitations

60 views
Skip to first unread message

Chris

unread,
Feb 19, 2025, 12:06:53 PMFeb 19
to IADS
Hello guys, 

I am trying something out and cannot really find a way to reach my "wished goal". Perhaps someone more experienced can assist me in my thoughts and give some inspiration :-)

Wish-scenario: 
One table which can be edited independently of the "ParametersDefaults" table which will list all limitations, not only structural but also operational such as e.g. RPMs, Temperatures etc. 

These set values will drive not only thresholds (inside the ParameterDefaults table) but also dynamic backgrounds in gauges etc (e.g. "set background color of a dial to red when the displayed value is exceeding a set limitation inside this table) or "Alarm" and "Warning" colors inside "standardgauges" e.g.

What I have tried out so far:

1) Use Dynamic Wizard to set a background color based on a "variable" limitation

Say I get a value from e.g. the "missionattributes" table to a derived parameter via the GetMissionAttribute function. Then I would like to use this value as "threshold" inside the dynamic Wizard. 

This does not seem to work. See screenshot. The argument (red box) works fine when adding a static value, but does not accept a variable (yellow highlight), the one stored inside the missionattributes table.

Display_Wizard_variable threshold.png

--> Is there a syntax-error or is this simply not possible?
--> Is there a workaround you might think of?

2) Use this approach to set the threshold of a parameter inside the Defaultsparameter table

Say I want to use that same value to set the threshold inside the Defaultsparameter. This also doesn't seem to work, or I am using the wrong syntax (see screenshot below)

Threshold_Variable.png

--> Is there a way to use variables to define thresholds?


I hope I made myself clear. I didn't find anything related to this topic in the help so far, that's why I am reaching out inside this user group :-)

Thanks in advance and regards!
Chris

Chant, Adam

unread,
Feb 19, 2025, 12:45:27 PMFeb 19
to ia...@googlegroups.com

Chris,
The majority of the columns in the ParameterDefaults Table are static in that they cannot accept variable inputs like parameters. This is also the case for a select few display Object Properties.

The Dynamics Wizard accepts one input parameter (defined in the first step of the wizard, but bypassed when a parameter is already assigned to a given property) and this is represented at ‘value’ in the tables.

There are other tables within the Configuration that may be better suited for storing values (Constants, UserInputValues); However consideration should be given to the rate at which these values need to be queried as they are throttled to no greater than 2 times as second.

It would be my recommendation to consider using the interpolate1D(), interpolate2D() and/or interpolate3D() functions to build tables of your desired inputs and then feed the resulting singular value into each Display Object Property or Dynamics Wizard. There is no restriction to then number of Derived Parameters you can create so all of the processing could be done in Derived Parameters that then feed the respective display object properties.

One advantage to using the UserInputValues Table is that it can be fed values directly from IadsInputObjects (IadsTextInput,IadsDropdown, etc.) using the OutputName Property.

 

While there have been some attempts to create localized methods for editing common properties of displays in IADS they tend to be limited to a handful of objects on a singular Analysis Window.

 


Thank you,

Adam Chant
Project Engineer, IADS

Curtiss-Wright
190 Sierra Court A-3 Palmdale, CA 93550
T: 661.273.7003 x 2210
ach...@curtisswright.com

iads-s...@curtisswright.com

 

From: ia...@googlegroups.com <ia...@googlegroups.com> On Behalf Of Chris
Sent: Wednesday, February 19, 2025 8:20 AM
To: IADS <ia...@googlegroups.com>
Subject: [IADS] Thresholds and Limitations [EXTERNAL]

 

WARNING: This message came from an external source. Please exercise caution and proper judgment when opening any attachments, clicking links or responding to this message.


 

--
You received this message because you are subscribed to the Google Groups "IADS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iads+uns...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/iads/e14e4244-1862-4248-bbb2-4a78e50ca85bn%40googlegroups.com.


This e-mail and any files transmitted with it are proprietary and intended solely for the use of the individual or entity to whom they are addressed. If you have reason to believe that you have received this e-mail in error, please notify the sender and destroy this e-mail and any attached files. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the Curtiss-Wright Corporation or any of its subsidiaries. Documents attached hereto may contain technology subject to government export regulations. Recipient is solely responsible for ensuring that any re-export, transfer or disclosure of this information is in accordance with applicable government export regulations. The recipient should check this e-mail and any attachments for the presence of viruses. Curtiss-Wright Corporation and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail.

For information about how we process personal data and monitor communications, please visit https://www.curtisswright.com/privacy-notice/default.aspx

Christian Lemke

unread,
Feb 19, 2025, 12:57:35 PMFeb 19
to ia...@googlegroups.com
Thanks Adam for your quick reply. 

Ok that is understood. If I understand you correctly, it should be possible to reach my goal by using 1d interpolation (which I also had in mind but wanted to omit at first for ease of use :-) ) and assigning those values to the dynamic wizard e.g..

I will look into that tomorrow (based in Europe) and get back to you if I encounter some specific issues. 

Many thanks and best regards 
Chris 

On 19. Feb 2025, at 18:45, 'Chant, Adam' via IADS <ia...@googlegroups.com> wrote:



<image001.png>



--> Is there a syntax-error or is this simply not possible?

--> Is there a workaround you might think of?

 

2) Use this approach to set the threshold of a parameter inside the Defaultsparameter table

 

Say I want to use that same value to set the threshold inside the Defaultsparameter. This also doesn't seem to work, or I am using the wrong syntax (see screenshot below)

<image002.png>

 

--> Is there a way to use variables to define thresholds?

 

 

I hope I made myself clear. I didn't find anything related to this topic in the help so far, that's why I am reaching out inside this user group :-)

 

Thanks in advance and regards!
Chris

--
You received this message because you are subscribed to the Google Groups "IADS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iads+uns...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/iads/e14e4244-1862-4248-bbb2-4a78e50ca85bn%40googlegroups.com.


This e-mail and any files transmitted with it are proprietary and intended solely for the use of the individual or entity to whom they are addressed. If you have reason to believe that you have received this e-mail in error, please notify the sender and destroy this e-mail and any attached files. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the Curtiss-Wright Corporation or any of its subsidiaries. Documents attached hereto may contain technology subject to government export regulations. Recipient is solely responsible for ensuring that any re-export, transfer or disclosure of this information is in accordance with applicable government export regulations. The recipient should check this e-mail and any attachments for the presence of viruses. Curtiss-Wright Corporation and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail.

For information about how we process personal data and monitor communications, please visit https://www.curtisswright.com/privacy-notice/default.aspx

--
You received this message because you are subscribed to the Google Groups "IADS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to iads+uns...@googlegroups.com.

Brian Gass

unread,
Feb 21, 2025, 12:28:00 PMFeb 21
to IADS
Chris,

I think what you want is a dynamic calculated limit compared to a parameter value. In this case a temperature. In the parameter defaults table create a parameter to calculate the limit. Then create a parameter that compares the temperature to that calculated limit. Use comparison parameter as the "value" that the fill color would trip on.

ITT = value from a source
ITT_LIM = fn(altitude, mn)
ITT_OL = ITT > ITT_LIM   <-- could be a 0/1 or T/F or whatever result you wanted

Then use ITT_OL to drive the DialFillColorProperty. In that case value is ITT_OL.

Brian

Chris

unread,
Feb 26, 2025, 11:00:32 AMFeb 26
to IADS
Thank you very much Brian for this piece of advice. It helped me to find a solution and will certainly help me in the future for other topics :-)

Regards

Reply all
Reply to author
Forward
0 new messages