Learning Forum

[spiritual122899]

Hi Ansys Community,

I am a Test Engineer from mainland China, and I have encountered an issue with SCADE Suite during my testing process. Specifically, this issue occurs when opening a textual expression written in a certain way, which causes some values in the model to be replaced by null, resulting in a check failure.

Steps to Reproduce the Issue:

1. Create Operator1(Input1: bool; Input2: bool) which returns (Output1: bool) and implements the functionality Output1 = Input1 or Input2.
2. Create Operator2() which returns (Output1: bool). Inside Operator2, use a textual expression to call Operator1(true, false) and directly connect it to Output1.
3. Perform a check on Operator2—it passes successfully, then save and close the SCADE project.
4. Reopen the project in SCADE. During the opening process, SCADE will display the message:
      "Expression calls fixed in project : Operator2.xscade (1)"
5. When performing the check again on Operator2, an error is displayed:
       "Illegal Empty Parameter at _L1 = Operator1(_null, _null)"
   This issue is only observed when using value directly as an input to the callee in the expression.

Expected Behavior:

Since I have made no modifications to the model, I expect that simply performing a check on Operator2 should not trigger any errors, and the check should pass successfully without any issues.

Actual Behavior:

After reopening the model, checking Operator2 results in the error "Illegal Empty Parameter at _L1 = Operator1(_null, _null)". The values passed into Operator1 should not be null under normal circumstances.

Environment:

• SCADE Suite Version: 2023R1
• Operating System: Windows 10 Enterprise 22H2

Background:

This issue was discovered while using SCADE Suite in a minimal example that I created to reproduce the problem. The issue occurs under very basic conditions, meaning that it can be triggered by a very simple test project, as described above. I am happy to provide the .etp and .xscade files for further investigation.

I would appreciate any help or information regarding whether this issue is already known and if there is any existing workaround or fix available.

Thank you for your time and support!

[Benjamin Descorps]

Hello,

This is a limitation of SCADE 2023 R1 with use of textual expression. Literal values used in operator call within textual expression are incorrectly managed.

In 2023 R1, the solution is to rather use the graphical form:

The limitation has been removed since SCADE 2023 R2.

Benjamin