Notifier not received when other code in while loop exists

[JÞB]

First.  DO NOT run wires backwards like that one out of obtain queue! and do not wire inputs to loops on the right side!

Whatever the boolean to the AND primitive is is likely a latching boolean control

and why are you ovewriting the waveform timing info?

try something like this:

[RavensFan]

---

@belopsky wrote:

The issue I have now is that only the first time the element is enqueued does it work..the next time nothing gets enqueued...Not sure why.

Hope this snippet helps to troubleshoot

---

Then the problem is probably in your left hand loop where you are enqueuing your data.  But since the snippet shows only a very small portion of that loop, we can't guess what is going on in the parts we can't see.

[belopsky]

I probed the case where the element is being enqueued, it seems to be calling it correctly (goes True when I need it to go True) but nothing is being enqueued after the first time..

Thank you all!

[RavensFan]

If that boolean goes true, then the true case must be executing, and something must be getting enqueued.  Have you tried highlight execution?  Or put probes on your wires?

You have a value(signalling) property node in a case structure right after you DAQmx read.  But it is impossible to know what it is for because the label that shows what control that property node goes to is not visible.

Are you trying to control an event structure with that property node?  Something seems odd about that construct.

Why are you using array to cluster after the DAQmx waveform read then using Unbundle cluster?  You should just be using Index Array.

[belopsky]

Yes, that property node is controlling some voltage behavior in an event structure. 

I did put a probe on the 'queue refnum' wire from the 'Enqueue Element' inside the True case structure.

After the first element is enqueued, the Value is: 1-enqueued elements; Which then turns to 0-enqueued elements.

And no other elements get enqueued, the 'Last Update' column in the Probe Watch Monitor continues to be updated so it is being executed..

[RavensFan]

I wouldn't trust the information in a probe on a refnum for it's count on how many elements are enqueued.  If that refnum probe keeps showing it is being updated, then the Enqueue must be working.

So what aspect (besides that #-enqueued) are you using to decide that things aren't being enqueued.)

(Be sure to show the label on that property node so your code is properly documenting what boolean control it is linked to.)

[JÞB]

---

@RavensFan wrote:

Are you trying to control an event structure with that property node?  Something seems odd about that construct.

---

I Think he is looking for an honorable mention on the Rube Goldberg thread

If soethin is not equal to false it IS true So the And input goes TRUE only when "injection" is false, but you write the p-node to true on falling and rising edges of injection

Is that what you wanted?

[belopsky]

The p-node Value(Signaling) is written to true in the TRUE case but nothing is in the FALSE case..

[crossrulz]

---

Jeff·Þ·Bohrer wrote:

I Think he is looking for an honorable mention on the Rube Goldberg thread

If soethin is not equal to false it IS true So the And input goes TRUE only when "injection" is false, but you write the p-node to true on falling and rising edges of injection

Is that what you wanted?

---

Jeff, I think you missed the shift register.  So it is when the values changes that they write to the property node.

[belopsky]

crossrulz: Yes, thanks, the shift register handles the correct value assignment.

What is a good way for me to check what is being enqueued, other than a probe on the queue refnum wire?

I am looking at this example, cant see what really I am missing..just tested this example too, and it works just fine..

https://decibel.ni.com/content/docs/DOC-2431