Virtual digital input problem

Hello,
I am trying to learn DAQ on labview. So, I made a basic digital input vi, with a virtual digital input device. For some reason I cannot get it to output anything other then zero, but when I run the daq assistant (when setting up daq assistant) the boolean values toggle between 0 and 1. But, in my VI I cannot get any input other then zero.
I have attached my VI.
Thank you
Solved!
Go to Solution.
Attachments:
ReadDigitalInputs_11-3.vi ‏46 KB

You should wire up your stop button to the Stop input on the DAQ Assistant. You are openening and closing the task each time when you do not do that. I think that is also resetting the toggling of the simulated device.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
ReadDigitalInputs_11-3.png ‏58 KB

Similar Messages

Optical digital input (S/PDIF) problem (sampling rates)

I have a huge problem with my 2009 iMac's digital input that I didn't run into on my older MacBook running the same OS (10.6.x), and it's driving me nuts!
Basically, I'm trying to record a digital feed from an ADC hooked up between my hand-built tube amps/turntable and my iMac, with the goal being the transfer of some of my LP records to 48/24 LPCM for archiving and editing. The ADC's output rate is fixed at 48000Hz and cannot be changed. My iMac, however, refuses to lock on to the device rate, instead forcing 44.1kHz in the audio/midi setup. In fact, I can't get it to do anything but 44.1kHz on anything I plug in (even my DAC's passthrough) despite the fact that I need to use 48kHz. The audio is correct for a few seconds, then forces back to the wrong rate again. No matter how many times I try, the computer insists on using the wrong sampling rate, which has rendered impossible any hope of using my iMac as an audio recorder.
I've tried setting up an aggregate device, but to no avail. Nothing I do seems to work, and since the problem is with Core Audio, any program used to catch the audio records gibberish. Is there a way to force Core Audio to use 48kHz in the terminal? It's not like the computer can't do it, as I get about 2 or 3 seconds of correct audio when changing the sampling rate manually. I just can't get it to stick!

Seeing the exact same thing here. External digital source is 48kHz, and this Mac Pro Desktop will only stay on that setting very temporarily (for about .10 or .15 seconds) then it reverts back to 44.1kHz. Even if I don't have a signal or even a Toslink cable plugged in to the input.
(I'm surprised you are getting 2 or 3 seconds of correct audio, when I'm getting about 1/10th that before it reverts back to the wrong sample rate. Maybe related to a buffer size option somewhere?)
I have tried every known option to reset or re-configure this, and even to the point of creating a new user, resetting PRAM, resetting SMC, etc. I was going to try upgrading to 10.6, thinking maybe it was a 10.5.x problem, but now I'm not sure that will help.
Had I the choice to set the setting to be 48kHz and lock it in, it should stay on that setting - (even if the chance exists that what I'm getting is not correct.)
More often than not, I know what I'm doing more than Mac OS does, and I want to force it to do what it needs to.
There really needs to be a "do it because I told you so" option for most of the Mac audio configuration system. This automatic "the hardware decided to do something for you" stuff is absolutely horrid for a system that is marketed as "Pro". A real "Pro" system would let me edit the configuration once, with the tool (text editor hopefully) of my choice, rather than attempting (and failing) to automate things.
+1 for another instance of this being "a huge problem" and "it's driving me nuts!"

How to acquire serial data on a digital input line with good performance?

Hello,
we have a performance problem with our realtime controller. Our objective is, to read a 24-bit long digital waveform from a digital input line. To do this, we supply a clock signal (236 KHz) to the PFI1 Line of our DAQ Board. On each rising edge of the clock, a new bit is set on the digital input DI0.
Our hardware which transmits the data, is triggered through a digital output from our realtime controller. On each edge on this output, the hardware starts a serial transmission of 24-Bits.
Everything works fine except the bad performance of our realtime controller. We want to acquire the 24-Bits in a 1ms timed loop. To measure performance we wrote a test program. In that, we only triggered the hardware and transfered the data to the realtime controller. The task which is doing this job, has a approx. CPU-Load of 30%, which is, in my humble opinion, very high. The task is not waiting for data or anything else! We have earlier implemented a control which is also using a 1ms timed loop. This control is sampling 2 analog input signals, 2 counters. Futhermore it's sending telegrams with CAN and doing many calculations. The strange thing is, this much huger program has a CPU-Load of 25%. Does anybody know where the problem is?
For the better understandig I attached our test-program to this text.
We're using:
PXI-8175 realtime controler
PXI-6221 Multifunction DAQ
Thanks!
Regards,
Crest!
Attachments:
dig_test.zip ‏51 KB

Hello,
First of all 30% CPU-Load is normal because the DAQmx-driver needs a lot of resources.
In your programm you should place a wait (for example with 1ms) into the while-loop which causes
lower CPU-Load.
If this is not enough you should build your vi like in the following example.
Regards,
Christian
Attachments:
Read Dig Port.vi ‏51 KB

Audigy 4 Pro digital input 16 - 24

I have a Sony MDS-JB920 minidisc deck hooked up to my Audigy 4 Pro through the external box. Works fine.
However, the Minidisc deck allows one to set both the digital input and output to either 6, 20 or 24 bit. As the Audigy 4 Pro is 24 bit, I've set the deck to 24 bit for both in and out. So far no problems. If I watch the settings panel whilst playing a minidisc however, it indicates that the signal coming from the MD deck is 6 bit, although the deck is set to supply 24 bit through the SPDIF out.
When I put the MD deck on rec mode whilst the PC is supplying audio feed, the MD deck loops it back to the SPDIF input of the Audigy and then the software does display 24 bit signal coming from the MD deck.
This is very confusing to me, does anyone have an explanation?

CMSS is an effect used for stereo sounds, to emulate surround sound for them. It has no effect on the DVDs you're playing as you're just outputting the AC3 signal so the speakers can decode it.
If you're using a digital connection, then CMSS will not have any effect for other sound either, you need to connect through multiple analog connections to get that sound. A standard digital connection (coaxial and optical SPDIF) can only pass over either a stereo PCM signal, or an encoded AC3 stream (like on your DVDs). Normal sound like music or games will only be passed over as stereo PCM, so there is no CMSS effect there.
If you can connect your amplifier through several analog connections, then you can use CMSS aswell, otherwise your amplifier might have it's own upmix option like ProLogic.
Cat

Triggering an event with a digital input

Hello all,
I'm writing my first Labview program. I used an architecture I found on the forums here, and it has been very helpful in getting me started. This architecture uses two while loops, one containing an event structure and one containing a case structure. (This is a queued state machine architecture, I believe).
Part way through the programming, we decided we needed a sensor to make sure the part was in the test fixture during the test. If the part is removed during the test, we'd like to safely stop the test. So basically, I need to monitor a digital input (on an NI-USB-6525 module) and enter the "Stop" case if the digital input turns off. I would also like to make sure this digital input is on before entering the "Start" case. I don't care if the input changes state when the test is not running, nor do I care about its state during the "Exit" case.
I'm really not sure how to add this functionality to my "stop" case. I don't even know if it's possible. I've been researching DAQmx events, but I haven't found an example or answer that aligns with my particular problem.
I've attached my code. It's incomplete right now - I still have a large number of steps to add. I wanted to get this issue figured out before I programmed any more steps. A preview of the code showing the basic architecture is shown in the picture below.
Does anyone have any ideas or suggestions for me, or questions if my problem is unclear? Also, if you see anything else in my code that will be problematic, please let me know.
Thanks in advance!
Attachments:
Main_Loop_072412.vi ‏195 KB

I should also add that I looked into event dynamic registration, but it seemed incompatible with my issue. I don't want my top loop to run only when an event triggers it - I want it to run all the time so that it can immediately respond to button presses. Also, most of the triggering I found was based on value change. I care about the actual value, not just that it changed.
I don't want to do anything that will bog the code down too much since it is important that the system respond immediately to inputs, especially to the stop or exit button presses.
I'm sure I am missing something very basic here. I'm used to ladder logic, where everything is simple and straightforward.

Digital Input Cannot Display this Video Mode Optimum Resolution 1280 x 1024 60hz.

HP Pavilion h8-1360t, Windows7 home premium 64-bit, AMD Radeon HD 7570 graphics card.
error message: Digital Input Cannot Display this Video Mode Optimum Resolution 1280 x 1024 60hz.
I get the error message as soon as Windows opens and the desktop displays. Then it goes black with that message. I've been using the computer for awhile and I had it so that when I maximized a window it would go across both screens. I have two monitors on the graphics card. Somehow I changed the settings so that a program would maximize to one monitor or the other. That is how I want it to work. Maybe I activated HydraVision. Now I have the problem when I start.
Also now when I boot to Safe Mode I get the message that there is no AMD graphics driver installed, or it is not functioning properly. I have tried to update it and the computer tells me I have the most recent version installed. I would like to uninstall it and reinstall it, but I'm a little worried I won't get it installed and be without video. Something like that happened to me once before years ago.
Could someone tell me what I should do please?
Thanks,
Jim Allen

HP support is here:
http://www8.hp.com/us/en/contact-hp/contact.html
In safe mode you should uninstall the driver, then try to boot normal again.
Then check if driver was installed by win7.
If not go go AMD website and download latest driver for your card.
V.
*** Say 'Thanks' with Kudos ***

How to force digital input sample rate?

Does anyone know how to force a Digital Input sample rate and/or tell Core Audio which conversion clock to use... internal or external? Apparently both things can be done from Pro Tools, but I don't have it. My problem is locking onto an A/D converter's 48K Toslink output. I can set 48K in 'Audio - Midi' setup and the audio is perfect, but a few seconds later Core Audio returns to the default 44.1K. I need to force it to stay at 48K, or clock on the signal rather than internal clock.

Braver,
Let me clarify a few things. First, the 6733 supports correlated digital I/O. This means that the digital operation does not have its own clock. You can correlate the digital operation with the AO clock, which will allow a digital operation up to the max AO rate. You can generate a pulse train with an onboard counter and use that as your digital clock source. Also, you can use a completely external clock source to achieve the max digital rate of 10MHz. The knowledge base, linked below, points you to a couple of examples that ship with LabVIEW. Be sure and read the documentation associated with each example.
Knowlege Base
As for
the example CDI Single Point clocked by Counter (E).vi, notice how the output of...

Pci1200 digital input output

Hi,I'm a student using labview 6.1 for the first time. I use the digital input/output lines of a pci 1200 card. I use 8 digital input lines placed in one sequence, and 7 digital output lines placed in another sequence. The VI can read the input lines but the output lines give a voltage of 0.5 Volts instead of 5 VOLTS, how can I solve this problem?

What are you writing to the digital output lines in LabVIEW? Writing a Boolean value of False to a digital line will write a TTL logic low voltage and writing a Boolean value of True to a digital line will write a TTL logic high voltage. Make sure you are writing a true Boolean value to the lines you want to output 5 V.
Also, make sure you are not loading down the digital outputs. The digital lines can source 13 mA of current. If you are connecting a small resistance load across the digital outputs, you might be loading down the digital ouputs. I hope this helps.
Regards,
Todd D.
Applications Engineer
National Instruments

Digital Inputs do not record over long time periods

I am running Signals Express 2009 with a USB-6009. I have a project that needs to record the states of 8 digital inputs over a 24 hour period. The inputs typically do not change state for long periods of time. When I run the project it does record and gather data if I stop it "soon"(I have gone as long as 30 min.) When I leave it running overnight it does not appear to record anything.

If you have not already, you should try turning off display updates in the "Operate »Update Signal Views While Running" menu item. Set this to Update None. Also, turn off "Prepare log data for viewing" under the Logging part in the Tools » Options dialog.
When I ran your project overnight, it ran out of memory. The first error it threw was "Not enough memory to complete this operation." The problem was that SignalExpress saved a great deal of data in memory for easy displaying while it's running, but this grows too big when it runs overnight. The second error was as follows:
Logging Stopped:
Logging was stopped because an error occurred with a Step in the Project.
If this error is because of a device buffer overflow, you can improve performance by turning off display updates using the "Operate »Update Signal Views While Running" menu item.
You can also change the way signals are logged by changing the Logging Options in the Tools»Options dialog.
Turning off the "Prepare log data for viewing" will greatly improve performance.
Mark E.
National Instruments
Schedule a Free 1-Hour online LabVIEW Tutorial with an NI Applications Engineer

Built-in Digital Input - Tap Tap Tap Noise

Hi Guys,
Can someone out there confirm the following as normal behaviour or
otherwise -
Using Linein software (by rogue amobia) when i select "Built-in Digital Input: Digital In" as the input source and output this to "Defaul System Output" I get a loud tap, tap, tap ..... sound (it runs constantly), I also get this in Sound Studio when I select Digital Input as the source.
I have nothing connected to the Digital input of this computer so why do I get this tapping noise???
Thanks In Advance
Lee

I've had problems connecting my computer to my cable box as well. Comcast apparently disables some of the functions on its boxes. Call your cable company. It's most likely a problem with your box, not your computer.
Good luck and if you find the problem let me know.

Digital Noise Problem on AA 1.5

Adobe Audition 1.5
Lately I have noticed that just by opening a track within Adobe Audition, that process "creates" or embeds digital noise within the song.
I have tested this problem a few times by listening to the song before opening it within Audition. Beforehand, the song plays without digital noise, and after it has been opened within Audition, the noise appears. This digital noise is hard to describe, it's short in length of time, about 1-2 seconds, and will appear at least once within whatever song is being tested.
I uninstalled and reinstalled Audition to see if this would solve the problem, but to my surprise, the exact same digital noise problem remained within the reinstalled version of program. In the past, AA 1.5 has worked okay without this problem.
It's also worth noting that when I reinstalled the program, I successfully entered my program key, and I am "not" running the program in demonstration mode.
I am planning on upgrading to Adobe Audition 3, but the upgrade uses a previous version as a platform on which to upgrade to version 3.
The concern is that this digital noise will "survive" in version 3 of the program.
Thanks for any tips or ways to eliminate the digital noise (besides reinstalling the program), even within Adobe Audition 1.5 for the time being.

The brief digital noise "replaces" or interrupts the song and does not mix together with it.
I have been saving the songs in .wav format.
I operate AA in virtual mode on Windows XP within a Mac computer, and now I have also discovered the same
digital noise on another sound program within a song on the Mac side.
I appreciate that this isn't a Mac forum, but I found a bulletin from Apple about noise issues with my current G5 computer:
http://support.apple.com/kb/TS2033?viewlocale=en_US
Perhaps this is good timing as I am preparing to buy a new Mac Pro, and this one has an Intel processor so I'll be
able to run Windows and Adobe Audition natively.
Thanks to all for the insightful comments and help.

Available Input Problems...

I am currently running logic express 7 with a motu 828MkII Firewire interface with a Behringer ADA8000 running through the interface. However the extra digital inputs that the behringer provides can be seen on the drag down input selection menu but cannot be selected as they are faded out. In garage band and the various other audio packages I use these extra inputs (shown as inputs 13-24) are available to use but they still will not work in logic, leaving me to conclude that the issue lies within logic, I have spent many hours now trying to solve this problem but have got no where. If any one has a possible solution to this problem or knows anything about it I would be very grateful if you could reply to this post.
Thanks
Jimi

Logic Express is limited to the first 12 inputs available. I think a workaround is to setup a template in GarageBand with the inputs you want and then, open that file in Logic.

X-Fi Fatal1ty Pro cannot see 5.1 Dolby Digital input via Optical link (mods, please he

X-Fi Fatalty Pro cannot see 5. Dolby Digital input via Optical link. I am pumping my Xbox360 through the Digital I/O dongle and every thing works OK using Dolby Stereo, outputing to my 5. analog speakers. However, it does NOT work when choosing Dolby Digital 5.. My SPDIF tab just says unknown input.
Please help, this is very frustrating...

Ok, for those who also wanted to know the outcome, I though I'd post.
I was told that the dongle cannot decode 5. to analog, but the Dri've Upgrade and the Console Upgrade could (at $80/$80 vs. $5).
Great.
So what I want to know is this:? what chipset or connection is Creative putting in the Dri've Upgrade and Console Upgrade? It seems to me that the card should be doing the decoding, not the type of optical port. If it's getting the signal, then what is the problem? Is is that the flexijack cannot output/input 5. at all, only stereo?
Anyway, the Digital I/O dongle is going back, the thing is useless for my purposes. While I can hear 360 games fine, DVD's on it default to 5. if they have that type of audio, and there is no way to switch it to stereo; it gives me only silence then.
And mods, nothing in my frustration is with you; you seem to be very helpful and responsi've. I just wish the rest of the company would get on the ball.

Boolean values from multiple Digital Inputs

Hi guys,
This should be really basic but I've looked around to find a solution with no succes...
I have a Digital Input device with multiple inputs.
Eg, I'm reading 0-24VDC signals from pushbuttons and limit switches.
I simply would like to be able to assign each input to a boolean variable to use throughout the code.
Example: I've setup the DAQ Assist and get the usual "Data" output. I'm guessing this produces an array of boolean signals.
How do I convert that array into an individual boolean DI signal for each input?
Or better still, is there a VI I should be using that outputs individual signals?
I've also got the same problem for Digital Outputs. I'm guessing I'll be able to apply the same principles to that problem though.
Sorry if this is obvious and thanks for the help,
Joel
Solved!
Go to Solution.

Index Array will break apart an array into individual elements.
Build Array does the reverse taking individual values and build them into an array.
I would recommend looking at the online LabVIEW tutorials
LabVIEW Introduction Course - Three Hours
LabVIEW Introduction Course - Six Hours

Joe Meek Twin Q Pre-Amp and Elite Pro SPDIF/Digital input probs

Hi. I'm wondering if anyone can help. I've just purchased a Joe Meek Twin Q Pre-Amp and I specifically bought it for a new Rode mic I've just got and it needed phantom power. I also paid a little extra for the digital 'outs', thinking I could take an optic or SPDIF out into the Elite Pro breakout box. The problem is, is that digital is not recognised at all - in Audio Codes it states it's an invalid signal. However, SPDIF is recognised saying it's a stereo signal at 48,000hz, but is only being 'heard' in my right channel.
I have tried the line out into Line In 3, and there's no problem there. Joe Meek representative said it should be working as long as the bit match is the same in both units, which as far as I know is. Am I missing something here? I'm awaiting Creative to get back as it seems to me to be a breakout-box hardware problem, but I could be missing something?
Does anyone have any experience and/or advice/info?
Thanks in advance

Well, since you're not getting response, let me see what I can do.
I think you're saying the optical connection isn't working, but the coax (SPDIF) one is working, and then you're only getting the mic signal on one channel. The second part is easy to explain, but I never remember the solution suggestions. TOSLink/SPDIF, essentially, are stereo signals, and your preamp is simply putting its channel 1 signal on one side and its channel 2 signal on the other. If you had a second mic connected to the other connector, you'd have one mic on the left channel and the other on the right channel. Basically, you need to treat it as a mono signal and then either pan it into the stereo field, or just duplicate (convert) it to stereo. I'm sure there are ways, but someone else needs to join in with some experience. I'm not sure, but it seems to me if, say, you've put the mic in the channel 1 connector, you could take the channel 1 (analog) output and patch it into the channel 2 line input, and your digital outputs would probably get you the mic signal on both sides.
On both devices, the TOSLink/SPDIF signals are, to the best of my understanding, basically the same thing in two forms. If one is working, than the other should be working too. That suggests to me either hardware brokenness in the preamp's optical out, or the Elite Pro's optical in. or a problem with the optical cable. CL's optical outs can be checked to see if they are putting out red light: if they aren't, there's a problem. That probably applies to the preamp, in this case. You can simply connect the Elite Pro's optical output to its optical input and record something from the digital input device. If that works, the cable and the digital input are probably OK, and it most likely the preamp's digital output is broken (although it could be a strange compatibility issue). If it fails, then it's most likely either a bad cable, or the Elite Pro's optical input is broken. Trying another cable, or some other piece of gear you have that outputs optical, ought to sort out which it is.
-Dave
[email protected]

Virtual digital input problem

Similar Messages

Maybe you are looking for