キャンセル
次の結果を表示 
次の代わりに検索 
もしかして: 

通知

1.PNG

为什么右边这三个子循环不使用释放通知函数?这样不会占用内存吗?

Translated to English:Why does not it set "release notifier" functions on the three right Loops? Will the three "obtain notifier" functions occupy amounts of RAM?

0 件の賞賛
メッセージ1/7
3,943件の閲覧回数

Do all three slave loops get the same data?

 

Do a comparison on the constants where the notifiers are named.  My guess is that the they aren't all named the same even though it looks like they are all named "Data".  Perhaps one or more have some hidden characters in them.

 

Attach your VI so we can poke at it.

0 件の賞賛
メッセージ2/7
3,932件の閲覧回数

No, they don't get same data. But the source should be same.

0 件の賞賛
メッセージ3/7
3,923件の閲覧回数

Your VI works okay for me.

 

All 3 loops are getting the same sine wave data.  All the loops end properly when the Release Notifier is executed.

 

So where are you having problems?

0 件の賞賛
メッセージ4/7
3,910件の閲覧回数

Oh...I had heard that while a "obtain notifier" function is set, then that must end with a "release notifier" function. Will it master in my VI?

0 件の賞賛
メッセージ5/7
3,900件の閲覧回数

@Burning wrote:

Oh...I had heard that while a "obtain notifier" function is set, then that must end with a "release notifier" function. Will it master in my VI?


"Will it master in my VI?"

 

I don't understand this question.

 

The Release Notifier on the first loop has the force destroy input set to True.  If you read the help on Release Notifier, you'll see that it forces the destruction of all notifiers and it is not necessary to individually destroy each instance of the notifier reference.

0 件の賞賛
メッセージ6/7
3,884件の閲覧回数

So that is! Thanks a lot! I should have looked up the context help before. 

(Actually, I am not good at English. "Will it master..." means that whether the lack of "release notifier" functions is a suitable for LabVIEW programing.)

0 件の賞賛
メッセージ7/7
3,872件の閲覧回数