oscillscope project

[Ray.R]

Oops here is the last one in LV8.2

[Ray.R]

Here is the previous example in LV8.2

R

[kmous]

Hi Ray ,
when i run the Vi , i connot stop it using stop acquire or stop at the top!! it always freeze up and i have to stop it using end task in ctrl+alt+del !
should i select my signals before I run it ? you have select bottom at the top !! what does this do ? i think i have to select the signals i want to acquire and then push select  and then  acquire right ? this is how i understood from the  block diagram !!
Thank you

[Ray.R]

---

kmous wrote:
Hi Ray ,
when i run the Vi , i connot stop it using stop acquire or stop at the top!! it always freeze up and i have to stop it using end task in ctrl+alt+del !
should i select my signals before I run it ? you have select bottom at the top !! what does this do ? i think i have to select the signals i want to acquire and then push select  and then  acquire right ? this is how i understood from the  block diagram !!
Thank you

---

Humm.  I'm not using my regular PC, and don't have LV installed on this PC.

I may have created a deadlock condition with the stop buttons...  I tried to minimize the code change... 😞 There should be events to handle the button press, but if it is in the middle of getting waveforms, you do have to click stop acquire before it can handle the event.  The top loop has probably exited and killed the queue by then...  Did I wire a status on the boolean to stop the bottom loop?  if not, you need to place a cluster "unbundle by name" to the error cluster then OR it with whatever boolean goes to the stop loop conditional terminal.

You can select which channels at any time until you click acquire waveform.  You need to click on select channels after you do your selections in the array.  So, yes, you described it well.

I will check later today this post to see how it is going.

R

[kmous]

Hi Joe,
If I run the code under highlight execution,  the bottom (consumer) loop won't execute acquire signal case since its waiting on the Dequeue Element vi. When i run the code, the bottom loop is initialized to idle state. The moment I hit Acquire signals, the bottom loop's state changes to acquire but it's still waiting to dequeue an element before it can execute the acquire case. I Think the case structure needs all the inputs before it can execute a case.

I heard of something caslled state machine i can use but i dunno what that is.!!

[Ray.R]

I wish I had Labview installed over here to look a the code.  😞

The description you provided did put a light on what is going on.  So a small change to the dequeue architecture may do the trick.

Try this:  Move the dequeue portion of the code into the "idle" state.  Acually, the bottom loop is a state machine.  You will need to put a shift register for each of the queued elements (qty 3). There is already one for the state selection.  So add one for the string (? i think)  and the third one is the run/stop boolean that you can pass to a shift register and wire to the OR gate that I mentionned in my previous post.

All dequeues will be done in the idle state.  That means that the next state after the acquire data now has to be idle state.  I think it was already..  I think all states would now have to point to this one, except fot the stop / exit state.

Change the code and post a screen capture of the block diagram. 

R

[Ray.R]

How did it go?

Have you tried my last suggestions?

R

[kmous]

Hi Ray , I am sorry i was off for 3 days , my nephew was so sick and  i had to stay with him all nights at the hospital......For the VI , well my deadline is over but i got 10 more days to work on. Hope this will be enough!!
The VI is not acquiring any thing , i push run , i select my signals ,  i push select and then start acquire does not do any thing the VI freezez up and i connot stop it.

[Ray.R]

I was away myself and had limited access to the internet and no access to Labview.

I'll have a look at the code this morning.

R

[Ray.R]

I made some changes and added a status window.  It is useful for debugging and you may wish to leave it there.

The purpose of the status window is to let you know when an error occurs and it stops the loop, thereby giving you the impression that nothing works.  You may want to display the Abort Execution button while developping / debugging your application.  That one can be removed once it is ready to be deployed.

I also created a state for the stop button to force the exit of the program if it is pressed.

R