OPC input module unknown upon worksheet startup. No sound card installed error.

Hi all,
I am on v11.00.00 and have two problems.
1. Upon startup, I get a 'no sound card installed' error despite having already selected the sound board from the Measurement tab. I've already checked the Windows Device manager and verified that the sound card is working OK.
2. Upon loading a worksheet, I get a module unknown error - in this case an OPC Input module for a DT9837B sound and vibration measurement box. I've already installed the DAQ OEM drivers.
Can anyone tell me what's wrong?
Thanks...
 

You may need to edit the sounddrv.ini file to change the device number. 
The default file is this
[SETUP]
PlayWelcome=1
DisplayNoSoundCardMsg=0
InputDevice=0
OutputDevice=0
BitsPerSample=16
LeftVolume=50000
RightVolume=50000
SameVolume=1
Change InputDevice to =1
File is in the Public users folder (Documents and Settings\All Users on XP), in the DASYLab\11.0.0\Eng folder.
OPC and DT have nothing to do with each other. They may be conflicting, however, since both are add-on drivers. If you edit the DASYLab.ini file (same location as the SoundDrv.ini file), put a semicolon character ";" in front of the line that loads the OPCC.DLL.
If the line is missing (i.e., the DT installation obliterated it), change one of the other lines to be DLLx=Opcc.dll. That will add it back in. 
Ensure that the DT driver is loaded. Both of these are in the [EXTEND] section of the file. 
 

Similar Messages

  • Upon iTunes startup, I will get message error 4002

    After itunes startup I get the message Error 4002. How can I eliminate this

    Hi there Hockeyfan_intn,
    You may find the troubleshooting steps in the article below helpful.
    iOS: Troubleshooting Messages
    http://support.apple.com/kb/ts2755
    -Griff W. 

  • How to use both digital and analog input modules in the same worksheet - MCC USB1208LS

    Dear all,
    Hi, I am Imran. I am using MCC USB1208LS. I have created the worksheet using digital input module as below and able to execute (run).
    But when i add another analog input module in the same worksheet and executes, An error Message pops-up as in the below image
    I have connected temperature sensor sognal to the analog input of USB1208LS. When using analog input alone in the worksheet, it indiates the actual values. 
    is any black box solve? please guide me. I am attaching in images
    We already placed a purchase order for USB1208FS. Will it sort out my issues?.
    Thanking you,
    Imran Mohamed.
    Attachments:
    present worksheet digital input only.JPG ‏67 KB
    with analog input module.JPG ‏81 KB
    error menu.JPG ‏77 KB

    Hello Imran,
    the USB-1208LS is not capable of running concurrent operations such as an analog input scan and ANY digital Ins, Outs, counter reads, or analog outs.  In Dasylab, the 1208LS is scanning, and nothing else from that particular device can be requested of it while that is happening.
    Yes, using the 1208FS will resolve some of these issues.
    Please refer to the ULHELP.CHM file installed on your computer in c:\program files\measurement computing\daq for details on this issue, et al.
    also I recommend you send your MCC/DASYLab requests for support to [email protected] as MCC staff (that includes me) does not normally monitor NI's Developer Zone.

  • How do I acquire multiple signals in the NI cDAQ 9172 using 2 analog input modules?

    Hi everyone,
    Is anyone familiar with using the NI cDAQ 9172?  This is my first time using it and I am not sure what exactly I am doing wrong... Alone with a NI 9233 analog input module, it works great.  I can grab my 4 signals from each channel and go.  However, when I add another analog input module to the mix, it gets an error.  It looks like it is reading only one and not the other.  It bombs at one of the DAQ start task and read task.
    Basically, the block diagram is just a double of the one 9233 working alone.  Is there something needed for input to make the 9172 working?  Any ideas?
    Any help is much appreciated.  Thanks!!

    Hi Jud,
    Both threads are correct.  The cDAQ-9172 has a single analog input timing engine, so both of your analog input modules will need to be in a single task.  The other VI you referenced shows one analog input task (with channels added from two modules) as well as an analog output task.  Analog output has a separate timing engine from analog input, so both of those can run in parallel independent tasks.
    The beginning of this thread is a good example; a single DAQmx Create Task followed by a DAQmx Create Virtual Channel for channels from each module.  Also, Getting Started with NI-DAQmx will give you the fundamentals for data acquisition, though I don't know how many of their examples use CompactDAQ.
    Regards,
    Kyle

  • How to automatically activate a third party application upon MAC startup on OSX 10.9.5?

    I am trying to automatically activate a downloaded application upon the startup of the computer.  This particular app is one that works in the background.
    Thanks for the help

    1) Open System Preferences -> Users & Groups, then select your account.
    2) Select "Login items" and click "+" button to select application.
    3) Check out "Hide" checkbox.

  • "Chassis Temperatur​e" in Analog Input Module for FPGA (cRIO-9201​)

    I have just gotten my cRIO with a analog module (9201) and a digital output module (9472).
    When I place an Analog Input Module on my block diagram and double click it, I can choose from the following inputs:
    Channel 0 through Channel 7
    AND
    Chassis Temperature
    I have tried to find any documentation for this "Chassis Temperature" but so far without success.
    If I read this input and feed it straight to an indicator, I get values in the range of 120 to 150.. Now, without more information, this number is rather useless. Does anyone know how to transfer this data to a temperature (either in the Celcius scale or the Fahrenheit scale)?
    Thank you!
    Project Engineer
    LabVIEW 2009
    Run LabVIEW on WinXP and Vista system.
    Used LabVIEW since May 2005
    Certifications: CLD and CPI certified
    Currently employed.

    I still did not find any documentation for this "feature" but I lucked out and found the following:
    in the folder: \labview 7.1\examples\FPGA\CompactRIO\cRIO-910x\
    you should have a file called:
    cRIO-910x support files.llb
    in this there is a convert to temperature vi.
    To get the raw data as a temperature, it looks like all you have to do is divide the binary data by 4 and the answer will be in Celcius.
    Project Engineer
    LabVIEW 2009
    Run LabVIEW on WinXP and Vista system.
    Used LabVIEW since May 2005
    Certifications: CLD and CPI certified
    Currently employed.

  • Is it possible to call a java control upon server startup

    I have a java control that creates business rules for validation of files submitted by users. This control
    makes many calls to db controls and performs a lot of
    fetch operations . Is it possible to invoke this control
    upon server startup and cache the results

    In the current release(8.1), calling controls from a plain Java class is not supported. Controls can only be invoked from a any one of the following Workshop components JWS/JPD/JPFs/or another control.
    Hope this helps.
    Raj Alagumalai

  • Faulting application AcroRd32.exe, version 9.5.0.270, faulting module unknown

    We run a large Citrix Xenapp estate based on Citrix XenApp 4.5 x64  technology in a 80 server farm with Windows Server 2003 x64 O/S.
    We have recently experienced issues with thin client users using having their Adobe Reader version 9.5.0 crash whilst trying to print.
    We un-install and re-install Adove Reader and the problem goes away for a little while but comes back soon with over 45 users using each Citrix server.
    This is the Microsoft error code which is not very helpful
    Faulting application AcroRd32.exe, version 9.5.0.270, faulting module unknown, version 0.0.0.0, fault address 0x000528ef.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    The only trigger appears to be the Microsoft Patch Tuesday roundup from December.
    However rolling back these patches does not resolve the problem?
    Has anyone had a similar problem?
    Anyone got any ideas?
    Thanks   Sean   London, UK

    Hi,
    The ADMPlugin is used by Acrobat or Reader to create dialog boxes. The reason for crash could be that the ADMPlugin file is either corrupt or their is some problem with the permissions of the file.
    To resolve this issue you can fully repair Reader installation. Steps to do the same are mentioned below.
    Close any running reader process.
    Go to C:\Program Files\Adobe\Reader 9.0
    Delete Reader folder.
    Now try repairing the reader installtion from Control Panel->Add or remove Programs.
    This should resovle the issue.
    If crash occours even after repair then please share the MD5 and permissions of the ADMPlugin.apl file from C:\Program Files (x86)\Adobe\Reader 9.0\Reader\SPPlugins.

  • Will Analog Instruments ADXL330 triaxial accelerometer work with the SCXI-1531 input module?

    I have an SCXI-1001 chassis and will soon be purchasing an accelerometer input module (SCXI-1531).  I'm also investigating possible accelerometers to buy.  Does anyone know if the the Analog Instruments ADXL330 accelerometer can be made to work with the SCXI-1531?  Here is a link to the Analog Instrument's page about the device:
    http://www.analog.com/en/sensors/inertial-sensors/adxl330/products/product.html
    Thanks!

    Hello,
    The output voltage and current levels are within specification of the module, the only concern I have is interfacing between the IC chip and the BNC connections on the 1531.  If you have a way to effectively connect the pins to BNC connectors and connect that to the module, then it should work.  Are you using the module's excitation source as well? 
    Kyle A.
    National Instruments
    High Speed Digital I/O Product Support Engineer - R&D

  • How to clear class cache upon applet startup?

    Hi,
    is there any HTML-tag to force the class loader cache being cleared upon applet startup?
    When I have recompiled the applet code, I am forced to clear the cache in the java plugin console. Is there any way to automate this?
    Thanx in advance

    i know what he's talking about, you have to restart the browser to get it to reload the class files. You may be able to set your browser cache to 1MB, but I think I did that and it didnt work, and I never found a solution. If you're trying to develop your application and you're testing it and this is becoming a problem, use appletviewer to test the applet. Once you have the finished product, make sure it works on IE and Netscape.

  • CSA - Ignoring modules loading after system startup

    I'm currently running CSA 5.2 r238 with all systems in Test Mode. I keep seeing events for certain modules loading after startup, such as pdcrypt2.sys in a Citrix environment. I know these events are normal and don't care to have those events logged any more.
    The events are being generated by Rule 50, a Kernel Protection rule with a monitor action in System Hardening Module [V5.2 r238]. I've copied this rule to a custom rule module and set it to priority allow and did not check the Log option.
    I created a file set for pdcrypt2.sys as follows:
    Directories Matching: **\Program Files\Citrix\system32\drivers but not <none>
    Files matching: pdcrypt2.sys but not <none>
    I'm still seeing events generated by rule 50. I know my rule is enforced by looking at an affected host and my rule appears to process beore Rule 50. Why am I still seeing events generated by rule 50?

    Tom,
    I'm just baffled. I changed my file set, AAA - Citrix pdcrypt2.sys, to look like yours does.
    Directories matching: but not:
    Files matching: but not: pdcrypt2.sys
    The change history for rule 50, which I based my rule off of, is blank.
    The rule basically reads likes this:
    Priority Allow
    Take Precedence
    Modules load after system startup is checked
    File set contains: $AAA - Citrix pdcrypt2.sys
    Based on my understanding of the rules and the previous posts in this thread it would seem that logging for these events should be suppressed, but that is obviously not the case. Does your modified file set exist in rule 50 (or the corresponding rule in another version) or did you clone rule 50 to create your suppression filter rule?
    -Mike

  • Using NI 9214 16-Channel Thermocoup​le Input Module

    Hi,
    Now that we have the NI 9214 with NI TB-9214, 16-Channel Thermocouple Input Module with
    Terminal Block how do we go about using it?
    It was not obvious as to what or where I get the instruments drivers for this, so any direction would be good?
    Also I have the CVI sample code, ContThrmcplSamps-IntClk.prj, are there any others about?
    Thanks
    Simon

    Hi Simon,
    Minimum driver requirements for all modules can be found using the software support tool and selecting the module you are interested in, in this case C Series modules and accessories>:NI9214.
    Link to Software Support Tool: ftp://ftp.ni.com/pub/gdc/tut/crio_software_versions.htm
    The latest NI-DAQmx driver version, is as above, the NI-DAQmx 15.0.1: http://www.ni.com/download/ni-daqmx-15.0.1/5353/en/  and the latest NI CompactRIO Device Driver is the NI CompactRIO 15.0: http://www.ni.com/download/ni-rio-15.0/5363/en/
    I'd recommend having a look through the Example Finder (through LabVIEW>Help>Find Examples) in particular the "NI 9214 Getting Started.lvproj".
    You could also try http://www.ni.com/examples/ to see if there is anything suitable available. The search can be narrowed using keywords and filtering i.e. Software>LabWindows/CVI
    Hope this helps!
    Rebecca
    National Instruments Applications Engineer
     

  • Windows 7 x64 only installs the drivers for USB devices that are plugged in upon system startup

    Hi all,
    I have a most unusual problem. On my personal desktop, I can only use USB devices that are plugged in upon system startup. If I unplug a USB device and then plug it in again, the driver will not install correctly. I cannot force the device to start and I
    can't pick a driver manually. All I get is this. If I plug in a USB device and then reboot, the driver gets installed correctly and I can use it until I unplug it again. I'm pretty sure it's a Windows issue
    but I can list the hardware I have if it is needed.
    I have tried:
    Running an SFC /SCANNOW as administrator
    Uninstalling all USB controllers via device manager and letting them reinstall
    Neither worked to resolve the issue. If this was a client's computer I would probably just reinstall Windows but because this is my main work PC it'd be a huge hassle to do it, so I'd really appreciate any other ideas anyone has. If I have to reinstall I
    will. Thanks!

    Hi,
    Since the issue just happened for 4 monthes, I consider that some changes or updates may cause the issue.
    Please also try to restore the system back to the point before this issue.
    You can also try these steps:
    1.Power down your laptop or desktop
    2.Physically unplug the computer.  If it’s a laptop, remove the battery too.
    3.Leave it disconnected for three minutes
    4.Replug the desktop or reinsert the battery
    5.Power on the system
    For the reasons, you can refer to this article:
    How to fix “USB device not recognized”
    http://www.fixedbyvonnie.com/2013/10/how-to-fix-usb-device-not-recognized/#.UvtCLf7xvwo
    Kate Li
    TechNet Community Support

  • NI SPDIF Input Module

    Has anyone tried to use the NI SPDIF Input Module? I already checked the document, but still, I am having troubles making it work. It doesn't read a 48 KHz signal with a 7831R board.
    Thanks for any suggestions.

    I have two suggestions to try.
    In regards to developing your own SPDIF reader; when you only measure the pulse lengths you get the proper readings, but as you add more code to the loop the readings changes and become incorrect. This is most likely a result of the extra code slowing down the loop and causing it to not run fast enough to read each pulse. Using a regular While loop in LV FPGA, each function block you use takes up at least one FPGA clock cycle. In addition the While loop has an overhead of two FPGA clock cycles. So assuming you have a While loop with 5 consecutive functions it will take 7 clock cycles to run each iteration of the loop. If you were to use this loop to measure the pulse length it would give you a measurment with a resolution of 7 ticks, i.e. the pulse length would be 7, 14, 21, 28, etc. As you add more code to this loop the length of each iteration increases and the resolution of the pulse width decreases. In order for us to adequately measure the width of the pulses in the SPDIF signal we need to have a loop iteration time of less than 6 or 7 clock cycles (about half of the shortest pulse we want to measure). This is the reason why the original SPDIF code is set up in three different loops and the first loop that measures the pulse width is kept very simple. It also uses pipelining to further reduce the time of each iteration and we compile the FPGA for a 80 MHz clock rate to get more clock cycles per pulse. I think in your code as you add the Case structure and additional code, you are increasing the loop time above the necessary limit.
    One 'easy' solution to this problem is to use the Single Cycle Timed Loop (SCTL) instead of the While loop. This loop is processed differently by the compiler so that all of the code inside the SCTL is executed in one clock cycle. (The SCTL was not available in LV FPGA when the original SPDIF code was developed, otherwise we would have used it then.) So in the updated SPDIF code we use the SCTL and can include all of the SPDIF processing in one loop. There are some limitations on the code that can be included in a SCTL. Information about the SCTL and optimizing FPGA code can be found in this prsentation (Advanced FPGA Programming). I think if you convert your code to the SCTL (right click on the While loop and chose Replace with Timed Loop) you should be able to measure your signal correctly.
    Getting back to the SPDIF code I included on my last post. This code does work correctly on my end with a SPDIF signal coming from a Soundblaster sound card. This signal has two raw audio channels with 20-bit data per channel. The 4 AUX bits in the SPDIF packet are not used. I have logged the data to file and can load the file using the Reader VI included in my last post. To play the sound back on a regular sound card in LabVIEW I have to resample the data to 44.1 kHz and then use the upper 16-bits of the 20-bit audio signal. I'm attaching a sample file of logged data on this post that you can open and play back using Read SPDIF Data File.vi.
    Is there a chance that the audio data in your signal is formatted differently? Could it be using 5.1 or 6.1 encoding with DTS or Dolby?
    Christian Loew, CLA
    Principal Systems Engineer, National Instruments
    Please tip your answer providers with kudos.
    Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
    or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
    to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense
    Attachments:
    sampledata.zip ‏2987 KB

  • Touchscreen xorg input module

    Several touchscreen input modules (evtouch egalax etc) work fine in Ubuntu but not in Arch.
    The error is:
    (EE) module ABI major version (0) doesn't match the server's version (2)
    (EE) Failed to load module "evtouch" (module requirement mismatch, 0)
    (EE) No Input driver matching `evtouch'
    I'm not sure what direction to take here as I'm not exactly sure about ABI and I'm not sure what server it's comparing to (xorg? kernel module?)
    I've tried IgnoreABI but the system crashes so clearly there's an issue somewhere.
    Can someone point me in the right direction?
    Thanks!

    OK, I seem to have this working now.  Seems that all the touchscreen input modules that I've tried were not compatible with version 1.4 of the X server.
    evtouch 0.8.7-3 seems to work and can be gotten from a Debian package.
    http://packages.debian.org/unstable/x11 … ut-evtouch
    The only file you really need from this package is evtouch_drv.so.  Copy this file to /usr/lib/xorg/modules/input.
    Set your xorg.conf to use the evtouch driver (there are many instructions around for this)
    You may need to set up a udev rule so that your USB touchscreen has a known link and doesn't change every reboot (there are instructions around for this too.)

Maybe you are looking for