Test Tab for waveform graph and pass button

[nyborn]

Hi Ayman:

Thank you for great help. I know you are very nice person. I hope you can still help me a little bit out.

The timeout error, I already tried using soft front panel to make sure the NI 5112 got the correct signal. They are all with no problem. The channel no and DAQ:1 are also correct. In fact, what cause the timeout error in this niScope EX Multi Record.vi? Are there any timeout parameter to set? I could not find any in the file.

Is there any sample I can look at for moving tab, testing beep that decribe I can hear the beep sound physically and then show the light that the program hear the beep sound? Is there any kind of files. I am very appreciate your great help.

[nyborn]

Hi Ayman:

How are you? I have heard from you. Are you really busy? May you send me some message?

[nyborn]

Hi Ayman:

How are you? I have heard from you. Are you really busy? May you send me some message? I would like to ask you.

[psisterhen]

If you are using the niScope EX Multi Record.vi example, there may be a few things you need to change for your application.  This example configures (by default) two records and an analog edge reference trigger.  To acquire two records, the device must see at least two reference triggers (one for each record).  In this example, the device will trigger when the voltage input on channel 0 crosses 0V in the positive direction.  When you try to fetch these records, you pass in a timeout.  This timeout tells the driver how long you are willing to wait for the record to be acquired.  It is likely that you are not getting two triggers, so one or both records are not being finished.  Then, when you try to fetch, it waits the default 5 seconds, then returns a timeout error because the records were never acquired (because the triggers were never received).

It appears that you are expecting the examples to work perfectly for your application.  I suggest that you take a step back, figure out what you are trying to acquire, how fast the device needs to sample, how many samples you want per record, how many records you want, and how you want to trigger the device.  The help documents installed with NI-SCOPE are an excellent resource to learn about the capabilities of your 5112 and the NI-SCOPE driver software.  After you review these, the NI-SCOPE examples can show you how to accomplish many different types of acquisitions, but you probably have to adjust several parameters to make them work in your application.

As far as the beep goes, it seems like your device under test is making a sound, and you want your LabVIEW application to hear this sound and change the display.  LabVIEW cannot "hear" an external beep.  (The Beep.vi allows LabVIEW to make your system beep, not detect a beep from an external device.)  To detect this sound, you will need an external sensor (a microphone), some sort of DAQ, Digitizer, or DSA device to digitize the signal and bring it into your computer, and some analysis software to recognize the beep.  You can accomplish all of this with LabVIEW and National Instruments measurement hardware, but it's a much more involved task than you probably imagine.

[nyborn]

Hi Psisterhen:

Thanks for your replying. I follow your instruction. I found I could not get the waveform as I expected in "niScope EX Multi Record.vi" file. I could get it in SFP. Attached is my graph that show the waveform I can get in SFP. Let me tell you my setting. Vertical: +/- 6V. Horizontal: 0.2s/div  The record lenght is in between 1000 or 10000. I could get it. But when I try to set the parameter in niScope EX Multi Record.vi,

I could not get. Attached is my graph that show my setting. Could you tell me what I did wrong and I heard I can suppose to get the waveform if I get the waveform in SFP right? Thanks for your help. I am very appreicate.

[nyborn]

Since I can not attached one more pic. i put another one here.

[psisterhen]

It looks to me like your application is working like the Soft Front Panel, but you simply don't have consistent settings between them.

In the first printout you sent (Graph.pdf), the SFP is set to a sample rate of 500 kS/s, and is acquiring 2 s worth of data.  (To see the same thing, you'll obviously need a record size of 1 M samples.)  Furthermore, the trigger level is 1.12 V.

In your application (Graph.pdf), the sample rate is 100 kS/s and the record length is 100,000.  So the settings do not match those of the SFP.  However, it looks like you would get the same data if you correct them.  Also, you have the trigger level set to 0 V, instead of 1.12 V.

In the Bark Test Graph.doc, my observation is the same.  The data looks correct, based on your parameters, but they're simply not the same settings as you used in the SFP.  In the first picture, you have a sample rate of 20 MS/s, and a record size of 10,000 samples.  So you should get a total time of 500 us.  That graph looks about right.  On the last graph, you have a sample rate of 20 MS/s and a record size of 10 M samples.  So you should expect .5 seconds worth of data.  The data on that graph looks about right, if it's supposed to match the SFP display.

So you're on the right track.  Again, I encourage you to design from a measurement perspective.  Think about the signal you want to measure: how fast it is, how powerful it is, and how long it lasts.  Use this information to determine the driver settings like sample rate, vertical range, and minimum record size.  Please review the installed documentation to make sure you understand how the device and the driver work.

[nyborn]

Hi Psisterhen:

Thanks for your guildline. I follow your guildlines to change the parameter of "NiScope EX Multi Record.vi". I got the righ waveform. Thanks.

Then, I am trying put those graph under tab control. I found out I can not just put it under tab control. I have to make voltmeter continouly reading first before display those graph. I look at the example that I attached. It is very confusing. Could you tell how to acquire the voltage continouly to the voltmeter by looking at this attached example? Can I use my exactly digram to acquire the voltage continouly after pressing enable button?

Also, I can not see how the first sample I attached can jump from reset tab to supply test tab automatically after pressing enable button. Could you tell me how? because I need to make the same thing for my application one tab to another after pressing button

Third, in your previous mail, I though about using a microphone to transfer digital signal from the beep to the computer. Do I need to get a special microphone or digitalize microphone or approicate sensor (how?). I have only CB-68LP board. After I connect the microphone or sensor, is that like you get some write digital signal from your line and then you pass this logic to the beep light (indicator) in order to make sure you can hear the beep sound? Could you tell me if I am thinking it right? Could you give me example I can look at?

Forth, I used advance --> key netvigation to move tab as beep test tab to shoct test tab after the program finish, it did not work. it also even not work for assiging F1 key on bark test tab and then F2 key on shock test tab. It will automatically changed to F2 for both of the tab. How am I suppose to do it? because I want to control it by keyboard, not mouse.  Unfortunately, it did not work. Could you tell me how to do?

By the way, I would like to ask you the meaning of how powerful the signal is. You said in the previous mail that I need to start thinking the signal in this perpective. I don't really get and understand what you mean by thinking how powerful the signal is? Could you expalin to me a little bit? I need to understand it.

[nyborn]

Hi Psisterhen:

I haven't heard from you lately, so I decide to wiite you back. I really have no way to solve this problems. I could not find anyone to ask.

The company urge me That is why I ask you. Could you please help me out. Nowsaday it is not easy to find a job. Don't  worry, I will handle

the small problems by myself. I hope you can write me back.