LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with consumer/producer loop.

I've attached the VI Hierarchy. 
 
I'm going to guess that he meant the entire hierarchy of code, not the picture of it. 
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 21 of 25
(641 Views)
I'm not sure what you mean by entire hierarchy of code if not a picture of it. The code is in 6.vi.
0 Kudos
Message 22 of 25
(637 Views)

Chuck,

 

We don't have the type def controls  so, we cant see if there are any coersions.  Do you see any coersion dots on any of the wires containing the type def information?


"Should be" isn't "Is" -Jay
0 Kudos
Message 23 of 25
(635 Views)

OK, looking at your latest code, the only thing that puts a TIMECHECK command into the queue is a STOP button.

 

But you immediately stop the PRODUCER loop and then RELEASE THE QUEUE.

 

The queue is therefore dead, disposed, empty, deallocated, gone, bye-bye.

 

You shouldn't release the queue until the RECEIVER is done with it. 

Message Edited by CoastalMaineBird on 04-19-2010 10:49 AM
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 24 of 25
(630 Views)
I've attached the type defs
0 Kudos
Message 25 of 25
(628 Views)