]]>]]>Expert mode is definitely not for me yet....
This method is working for only one signal for the other three identical signals it is not. There I have on the outport the value 0.
Is it possible that there is something corrupt and how do I solve this? Are there things were I should pay more attention when using the inport and outport for sending signals from one task to another one?
thank you for your question. You are completely right - From / Goto tags can be only used within one .mdl file.
About renumbering ports and connections:
The numbers of ports must be unique in the given hierarchy level, in case of manual modification of the port number the other ports are re-numbered automatically. Be aware that after re-numbering in an already connected subsystem the inputs (or outputs) in the upper hierarchy level are re-ordered, which results in probably unintended change in signal mapping!
The important information is that this issue is about subsystem inputs / outputs. See screenshots for explanation:
If you change portnumber at sine_wave Outport in SubSystem to for example "3", the signals of SubSystem are re-mapped according to port numbering. This will result in unexpected change.
Your modified project files:
Inport-test.zip
Regards, Tomas
]]>Edit :
Oookaaay, the names do need to correspond not the port numbers. I was actually confused by the explanation in the manual.
The numbers of ports must be unique in the given hierarchy level, in case of manual modification of the port number the other ports are re-numbered automatically. Be aware that after re-numbering in an already connected subsystem the inputs (or outputs) in the upper hierarchy level are re-ordered, which results in probably unintended change in signal mapping!
If I swapped the port numbers around the mapping didn't change. All signals stayed connected with the name of the port and not with the port number.
FROM/GOTO only to be used inside the .mdl file. In- and outport to be used for communication between different tasks (.mdl files)
]]>