GOTO block - TagVisibility parameter

scoobsalamander · 2016-04-14 11:39:18

The From / Goto blocks can be used to get a signal from one task to another task if the 'TagVisibility' is set to 'global', correct?
If yes, then how is this working exactly?
If not, what is the best way to get signals from one task to another?

scoobsalamander · 2016-04-14 13:10:04

...found the answer in this Topic.

FROM/GOTO only to be used inside the .mdl file. In- and outport to be used for communication between different tasks (.mdl files)

scoobsalamander · 2016-04-14 14:02:09

...I still don't get it....feel stupid.

Test project

Edit :
Oookaaay, the names do need to correspond not the port numbers. I was actually confused by the explanation in the manual.

Manual wrote:

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.

Last edited by scoobsalamander (2016-04-14 15:31:28)

tomáš čechura · 2016-04-15 09:27:51

Hey scoobsalamander,

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:

Manual wrote:

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

Last edited by tomáš čechura (2016-04-15 09:32:55)

scoobsalamander · 2016-04-15 11:35:37

Thx, perfectly clear...

scoobsalamander · 2016-11-20 17:07:06

I have two different tasks and I'm using some signals (double) from one task into the other task by using inport and outport FB's.

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?

scoobsalamander · 2016-11-20 17:13:09

Just found out that if I remove the inport, which is connected to the PID1.pv (see image), the connection remains intact.

Last edited by scoobsalamander (2016-11-20 17:13:38)

scoobsalamander · 2016-11-20 19:07:42

Can be closed....feel very stupid again. This was all due to the fact that I have been playing around with the compile and download window.....

Expert mode is definitely not for me yet....

tomáš čechura · 2016-11-21 13:43:15

Thank you for your comments. Expert mode can be really tricky even for experts

REXYGEN Community Forum

Announcement

REXYGEN forum has been moved. This one is closed.
Head over to the new REXYGEN Community Forum at https://forum.rexygen.com.

Looking forward to meeting you there!

#1 2016-04-14 11:39:18