Clarification on Adapter Usage in SimpleFB

[rudoc]

Dear 4diac developers and community,

I'm exploring the use of adapters in SimpleFB within 4diac-IDE and have encountered an architectural question regarding event activation.
I understand that the normal use case for a SimpleFB is REQ → ALG → CNF. However, adapters are available within the SimpleFB, yet the control flow mechanics aren't immediately apparent compared to other FB types, especially since SimpleFB lacks an ECC and contains only algorithms.
My specific questions are:

1. What is the intended mechanism for triggering adapter output events from within a SimpleFB instance, if any?
2. Should adapter events be implicitly triggered when algorithms finish execution, or is an explicit association required?
3. If no internal triggering mechanism exists, what are the recommended design patterns for utilizing adapters in SimpleFB?

Any clarification on the design philosophy and practical implementation would be greatly appreciated.
Thank you for your time and expertise.

[azoitl]

The simple FB will be in the upcoming 3rd edition of IEC 61499 Part 1. 4diac IDE does not have all editing capabilities necessary for editing simple FB types. What is missing, and on our roadmap, is an edit feature for the simple states. Simple states is the IEC 61499-1 approach for assigning algorithms and events to input events. The IEC 61499 syntax is similar to the one for actions in basic FBs. You can already do that in XML and for normal input and output events we will also generate the correct code. I expect that the code generation for adapter output events will also be correct. What I'm not sure is if we have adapter input events correctly considered. We will test that as soon as we have the editing capabilities.

[rudoc]

Dear @azoitl !
Thank you for the clarification.
I actually tried modifying the XML as described:

			<ECAction Algorithm="REQ" Output="CNF"/>
			<ECAction Output="PLUG1.CNF"/>
			<ECAction Output="SOCKET1.REQ"/>

The resulting code works correctly. I am wondering whether this method aligns with the design philosophy of SimpleFB.

[azoitl]

Dear @rudoc!
Yes this is exactly what is expected how simple FBs would work for such a scenario.

For reacting to an adapter event the XML syntax would be:

<ECState Name="SOCKET1.CNF">
    <ECAction Algorithm="REQ" Output="CNF"/>
</ECState>

[rudoc]

Thank you for your guidance. Although adapter events are not directly available, with your input I was able to develop working code after XML export. I consider the topic fully covered. I appreciate your efforts in explaining this.

[azoitl]

happy to help