sensoray 626 DAQ drivers

Similar Questions

• lsdaq pci daq card not found

  Help!   I have linux redhat 5 and installed the last base of nor-daq drivers 3.4.0f2.   I see my Board from national instruments pci-6070e running lspci:

  07:04.0 class ff00: National Instruments PCI-MIO-16-1

  But when I run lsdaq, I he found nothing:

  --------------------------------
  Detect of National Instruments DAQ devices
  Find the following materials:

  --------------------------------

  Any ideas?

  Andrew,

  Thanks for the notice about the DDK.

  Wanted to let you know by putting the DAQ cards in another workstation linux also runs HR, the lsdaq have found the cards.

  I maintain there is no way to know the difference between mx and mx-Base without download them both and read the help files.

  Also the word "subset of the functionality" is also misleading because you have to change all the function names.

  Jonathan

• VB6 with DAQmx compatibility with Microsoft Vista and Win7?

  Hello

  I'm trying to figure out how what are my options for running my VB6 applications that use the API C of NOR-DAQmx with Vista or Win7.

  I have certain applications that we have maintained in VB6 (with Measurement Studio 6).  I programmed the software for traditional OR-DAQ hardware originally.  I suppose that I used for about 10 years or more.  About 2 years ago or if we needed to use our software with hardware recent DaqMX I've been able to use the API C OR-DAQmx for Visual Basic 6.0.  My application really support two hardware platforms simultaneously.  The person responsible for the project wanted to have 1 single application managed the two platforms (daqmx and inheritance).  So far, it's all great.

  If anyone knows what are my options if I want to use Windows Vista or Windows 7.  We are currently running this app on Windows XP.  I'm ready to upgrade my software if necessary although I have to spend to VB.net and Measurement Studio 7.1 (I currently have).  But if we were to happen tomorrow is there any compatilibility. I read that the traditional / legacy NOR-DAQ is not supported in Vista (Win7).  I googled and found there was a beta version which seemed to weakly in support of the legacy but did not support USB devices which is what I have (6020e (inheritance), SCXI (daqmx), 6259 (daqmx).)  I've heard that Windows 7 will have a virtualization system for XP applications that do not work natively under Win7, but for some reason, I doubt that the drivers and hardware will be run this way.

  Also, should there be differences between Vista and 7? I'm an XP user and computers I support many XP so I really have no experience with Vista.  I plan to install the Windows 7 RC to try some of this stuff.

  Thank you, David

  Use of our released traditional DAQ drivers is not supported on Vista systems, even running in virtual Windows XP mode. The driver works at a lower level which can emulate a virtual mode.

  However, we have a public beta version for a traditional DAQ driver that works for Vista. You can read about this version beta here

  -Abram

• AI sample clock using to Trigger counter samples

  My basic question is: the ai\SampleClock signal is active only during the execution of a task of analog input?

  The details are:

  I have a multifunction data acquisition card series X PCIe-6321.  It is controlling an SCXI chassis and has a module SCXI-1180 and SCXI-1302, so I can control the analog inputs of the chassis but also access to the meter 4 on the map.  My application requires that I use all 4 meters to measure a frequency input signal and synchronize the samples for the analog input signals.  I created 5 tasks, 1 for AI and 1 for each counter.

  I'm using LabVIEW 8.6.1 with the latest NOR-DAQ drivers on and the operating system 64-bit Vista

  1 are there drivers or hardware restrictions that cause this solution does not work?

  2. can I use the ai\SampleClock as sample clock of entry for each task frequency?  If I do this the beginning of sampling will be synchronized?  I.e. If I each task frequency first starts, they will wait until that task to HAVE it is started before you start sampling?

  3. If this does not work, do I need to send the sample clock of the task of the AI to a line PFI (PFI1) and then use it as the special frequency sample clock input?

  I used to do option 3 when the synchronization of two cards in PXI chassis and use only the beginning of the task of the software instead of synchronization on a digital departure, given that the sample clock will control samples anyway.  I need to know if the same behavior works with the above scenario.

  Thank you

  Bob

  Prolucid Technolgies Inc.

  Hi Bob,

  I can confirm that the AI/SampleClock is available only during the execution of the task to HAVE it.  As far as other issues go:

  1. you must provide more information on what you seek to do exactly, but there is no problem with the clock of the task of analog input sampling to be used with routing counters.  I had read through the section of the X series operating manual which deals with the measures of frequency clocked at sample (see page 7-16) for more information about what really happens during this configuration to make sure that it suits your needs.

  The frequency of the signal to be measured must be at least two times faster than the sample of your task clock to HAVE.

  2. you can indeed pass the signal on all four tasks at the same time (you can check the page peripheral routes in MAX to ensure the routing restrictions).  Sampling will be synchronized four counters are started before the task to HAVE it, but counters will be armed at different times unless you configure a trigger to begin arms (see page 7-45 series X operating instructions).  I would consider using the AI/StartTrigger if you want to do.

  The effect of not to arm the counters at the same time would be a different number of periods on average on each counter for the first sample (assuming an average is enabled).  Maybe it's not a major concern, but I just wanted to point out.

  3. the itineraries are available inside the Board of directors so external routing is not necessary, you can simply specify to use the sample clock of the AI for each meter clock and roads will be done for you.  If you want to export the signal on a PFI line and new route on another line PFI, this option is also available for you, but shouldn't be necessary.

  I hope this helps you get started.  I'll make sure to take a look at Chapter 7 of the X series user manual, if you have a chance as he described how all configurations of meter of working more in detail.  If you have related questions do not hesitate to post in return.

  Best regards

  John

• SCXI-1102/SCXI-1303 undetected in SCXI-1000 chassis

  I use an installer with the SCXI-1303 module in an SCXI-1102 module in a chassis SCXI-1000 measures voltage and thermocouple.

  Until recently, everything worked well. but now it seems that I am unable to communicate with the interface. I've tried two different computers and hardware is not detected in MAX. The power light and fan on the SCXI-1000 chassis light again, it just seems to be no acknowledgement of the connection to the computer.

  A few more specific error codes:

  * When I double-click on the DAQ Assistant, in the block diagram window and click on 'Test' one of my entries, I received the following error message:
  "88705 error: the specified device is not present or is not active in the system."

  * I also got the error code "error-89130: not available in NOR-DAQmx device" in Control Panel test DAQ Assistant

  * During the closure of the DAQ Assistant test Panel, I see the error "error-89130: device not available for routing.

  * To the MAX, if I try to 'test' the chassis or the module, I've seen errors either saying that the device is not detected, or that the device must be reset or is being restored, or the traditional DAQ drivers must be reset (I tried the reset suggestions without result)

  At this point, I wonder if the Commission or the cable is pulled. Unfortunately, I don't have an other 68-pin cables to test at the moment.

  Thanks in advance...

  Thanks guys, I was able to solve the problem. To all those who might find this,

  * I noticed in the Windows Device Manager that two PCI devices have been listed as being not installed correctly.

  * After trying to update the drivers, I couldn't start the computer; got BSOD after the BIOS loading.

  * Some research led me to go out two PCI cards that I was not using, and I moved also to reinstall my data acquisition on an another slot card to force material.

  * Starts up, load drivers automatically and I'm gone.

  Doesn't explain not why it did not work in the other computer, but in the words of Spinal Tap, the authorities have said it was better left unresolved at this point.

• PCI-6251 vs PCIe-6351

  Hi all

  In another thread here somehwere I spoke getting the smaller possible buffers to reduce latency when reading and writing to the acquisition of card data in a loop.  The "10% rule" came (i.e. setting the buffer size of e/s to 10% of the sampling rate of 100ms per buffer) and although it seems to work on most systems, on some systems, well I can do much better than this, reliable: I can do full Visual Studio 2010 then builds in this loop , using a few sizes of buffers of 20ms, without a single negative overflow error.  It's all about a card PCI-6251.

  I decided to see if I could do better with a PCIe-6351 surfboard, hoping all latency issues could be mitigated by the PCI express bus.  Unfortunately, things are much worse.  On the same system where using 20ms puts in buffer (at 100 kHz sampling) was the test of the bullets; for example I couldn't fail any load I put on the CPU (a quad core Xeon hyperthreading), using the same code with the PCIe-6351 could not even past the start of my loop of I/O without meeting many overflow errors.  I increased the sizes of buffer to 100ms (as recommended by the basic rule), but still have occasional overflow errors, even with virtually no load on the PC.

  Another question, I noticed during the transition to the 6351 that surprised me was synchronization; another application considerably depends on the sync input and output buffers. It worked well on the 6251, taking into account delays caused by the buffering.  The same code fails on the 6351; not with a code error, but tampons are not synchronized.  I did a thorough analysis of this yet (I put emphasis on the first problem above), but it seems that the IO can be synchronized by a partial buffer; in any case, the behavior is quite different, questioning reports cards of the same physical buffer size in each case, using DAQmxGetBufOutputOnbrdBufSize.

  I'm not sure what my question is, except, "huh?"  The biggest difference that I could find on the sheets, is that the 6351 has several DMA channels, which could only help (although I don't think I need more than what's on the 6251).  If someone could shed some light on that, I'm all ears.

  (It was all done using the 9.3.5 drivers supplied with the PCIe-6351;) I don't have the time to go through the pain and suffering that is updated to the NOR-DAQ drivers yet - my company has limited bandwidth and, let's face it, 1.3 GB for a simple driver update is ridiculous, not to mention the time it takes actually install.)

  Hi, JSA,.

  Take a look at your other thread, my first suggestion is to disable the regeneration on your output task.  In c#, use the following text:

  myTask.Stream.WriteRegenerationMode = WriteRegenerationMode.DoNotAllowRegeneration;

  WARNING 200015 can only come when you use regeneration, and it occurs when you copy data on the same portion in the output buffer that the device is being read.  It does not necessarily indicate that an overflow would occur with disabled regeneration.  If you have enabled the regeneration (which is the default) then the unit will try to keep its edge FIFO (8191 samples) filled with data that is currently in the output buffer, so you could get the additional data transferred to the device before you have a chance to replace the previous buffer.

  In addition, you mentioned that "i/o can be out of sync by a partial buffer."  While I don't have too much to go here, I wouldn't be surprised if regeneration disabling fixed this problem as well.  If you transfer a partial buffer of data to the device, and then write the new data, your output waveform may appear out of sync with where you expected it to be.  It is best to simply disable the regeneration, in which case the output buffer is treated as a FIFO, and not a circular buffer, so you're never more than expected.

  Once you disable the regeneration, you will no longer receive WARNING 200015 and I believe that potentially you will not see the synchronization problem.  If the loop of Scripture cannot meet the generation, you will now see 200290 error, which is a mistake of underflow true (i.e. no data is present in the FIFO shipped on time the sample clock is received).  If you encounter some errors-200290 rates and sizes of memory buffer that you think are unreasonable, please do after return and I will be happy to take a look at your code to see if what you see is logical.

  Best regards

• Screw worked in LabVIEW 2009 but do not work in LabVIEW 2010

  The screws were initially written in BT 7.1 but then compiled in 2009 LV, and saves. These screws worked well on the Windows XP machine.

  Unfortunately, the XP machine was crushed and I try to run these screws in LV 2010, with windows 7, 32 bit.

  I installed the traditional DAQ drivers (latest version, 7.5) alongwith DAQmx (version 9.8).

  We use these VI to control valves of depression, using PCI-6503.

  To begin we first use a VI that reset the valves and the PCI card. The name of the first vi is: portconfig.vi this port and port config vi uses write screws I see error 10401 port config vi, when I run, step by step (i.e., sequence 1). However, the VI work but do not do any actual work.

  The second VI which depends on the first VI and therefore the second VI also does not work. on this VI, we have buttons (representing the valve) and when you click on them, the valves must close or open, but nothing happens in LV2010. the same screws worked in LV2009!

  Card PCI-6503 is defined under devices and interfaces in MAX. It is not defined under DAQ devices. When I test PCI-6503, it works.

  I enclose the two screws (there is in QuadMain.llb). I don't know how to get the real VI of your hard drive...

  first open portconfig.vi

  then open Control Panel.vi

  There are global variables used in the Panel.vi control, there are listed in the Global.VI Valve, which is located in globals. LLB second attachment).

  I really appreciate if someone can convert these screws for LV 2010.

  
  

• Find the strength of output voltage

  My VI generates a graph displays the output voltage of two 250 lbf (http://search.digikey.com/us/en/products/FC2311-0000-0250-L/MSP6952-ND/809398) to load data sheet (http://www.meas-spec.com/downloads/FC23.pdf) cells. I am trying to determine how much force is applied to the my output voltage load cell. So basically how to convert the output of a tension force (Newtons). Thank you.

  Sheet indicates that the nominal power is 100 mV at load full scale and 0 at no charge.  If you neglect the mini-maxi offset of zero and span min - max variation, you have 250 lbf/100 mV.  Then multiply by the conversion factor appropriate in newtons.  To account for the offset and gain variations, you might use a linear correction by solving the equation of a line (y = m * x + b) at two points, one with and without load near full scale.

  Some DAQ drivers put the scale included.

  Lynn

• Missing virtual channels PXI-4070 DMM

  
  

  Problem has been resolved in office. Cannot create global to the DMM virtual channels as the DMM uses the pilot DMM and global virtual channels are a method of the DAQmx and traditional DAQ drivers.

  LeeM
  NIUK

• PCI-6013 error 10007

  I'm troubleshooting some old software made by my company card PCI-6013. The software was written using the old traditional NOR-DAQ drivers and the user gets error code 10007 HAVE control.

  This software worked before when using LabVIEW 7.1(.1?), but the hard drive failed and the client did not have the 7.1 discs to reinstall. They have upgraded to 2009 and installed the traditional drivers of NOR-DAQ 7.4.4. The unit withdrew to the MAX, but when they run the program they get the error code 10007:

  A canal, the port or the meter is out of reach for the configuration of the device, or the combination of the channels is not allowed; or the scan order should be reversed (last)

  I'm trying to go through the code looking for all the parameters that may be beyond the control of the program that could be the cause. I'm not very familiar with NOR-traditional DAQ and I was wondering if there are some things I should look for or if there is a compatibility issue with LV 2009 and this card.

  And insight would be greatly appreciated.

  Thank you

  Check to see if this will help

• definitions

  National has a knowledge base or Web page w definitions?

  One of the many that I have questions is:

  What is considered a "Shared Library"?  to create an exe file?  Are daq drivers?  How will I know if I've used one?  What happens if low levels in a Subvi multiples and I used the vi call?  I use one and don't even know it.

  What is a 'library of packed project "?

  What is meant by 'typedefs '?

  etc. etc...

  Hello Mark

  You can consult the glossary referred to in the help file for Labview. There you will find many terms definations.

• 6501 units are not interchangeable?

  I have a program that uses the dll nicalu to moitor entries on a NOR-DAQ 6501 States.  It seems that if I install the NOR-DAQ drivers with a particular switch attached, the dll never recognizes another unit of 6501.  I have uninstalled/reinstalled the NOR-DAQ drivers and the only 6501 device that works is the one that is connected to the origin.

  I wiped another PC and loaded the drivers with another unit of 6501 and this 6501 unit works, but again, no 6501 unit only works with this computer.

  6501 units are somehow related to the hardware configuration?

  The main objective of this exercise is to the image of a hard drive with the NOR-DAQ drivers loaded to install on each PC using a 6501.  Right now the image restored PC only work with the 6501 that was used on the original PC and they have their own NO-DAQ 6501 units which do not work unless the player is cleared and the operating system is recharged, then installs it to NOR-DAQ drivers.

  Although 6501 are linked to a PC, I do not understand why uninstall and then reinstall the software OR-DAQ and the drivers do not work contrary to wipe the hard drive and then installing the NOR-DAQ software and drivers?

  Hi Dustin_IDI,

  NOR-DAQmx devices have names which are assigned to the first time they are connected on the PC, such as 'Dev1' and 'PXI1Slot5 '. For devices USB, these names are associated with the serial number of the device, so NEITHER-DAQmx will see the second USB-6501 as "Dev2', the third as"Dev3", etc..

  If you uninstall / reinstall OR DAQmx, the database maps between names and serial numbers is preserved, which explains why you get different results when you uninstall / reinstall OR-DAQmx, compared to when you wipe the hard drive and reinstall everything.

  If you open Explorer Measurement & Automation, you can use it to remove the old device and rename the new device to have the name of your application expects. Another approach is to modify your application to find the names of the installed devices, as described in How I can get all devices on my Machine DAQmx name programmatically?

  Brad

• App builder includes library dll

  I am trying to build an exe application in LV6i. I have problems with a couple of dll, which is ours and the other a library NIDAQ dll, lvdaq.dll.

  App builder includes support files and wants to put them in the data directory.  I want that they in a common space, because other applications use.

  If I leave them in place, the build fails (probably due to a source/destinationclash).

  If I move the source location, the App Builder won't find them unless I'm recording with them. I can't change the field of generator of the app it here to point where I want to.

  If I register with the location of the 'source', I modify the destination location for what I want and the build succeeds, but the program cannot find the dll files and does not start correctly. I have manually pointing them at startup.

  I am doing something stupid? (my head spinning) I'm very happy for App Builder just ignore them and install them manually on the target computer.

  It works fine when running in the environment of development (base) of the screw.

  Malcolm

  Malcolm Bebb wrote:

  I am trying to build an exe application in LV6i. I have problems with a couple of dll, which is ours and the other a library NIDAQ dll, lvdaq.dll.

  App builder includes support files and wants to put them in the data directory.  I want that they in a common space, because other applications use.

  If I leave them in place, the build fails (probably due to a source/destinationclash).

  If I move the source location, the App Builder won't find them unless I'm recording with them. I can't change the field of generator of the app it here to point where I want to.

  If I register with the location of the 'source', I modify the destination location for what I want and the build succeeds, but the program cannot find the dll files and does not start correctly. I have manually pointing them at startup.

  I am doing something stupid? (my head spinning) I'm very happy for App Builder just ignore them and install them manually on the target computer.

  It works fine when running in the environment of development (base) of the screw.

  Malcolm

  If you want Builder app for ignoring them you prefer to copy in the path system or Windows and delete all other copies on your development computer. You will ignore the DLLs located in one of these locations by Builder app as being provided by the system.

  Of course, in order to start your application on another system, need to ensure that these DLLs are installed. They can either go to the Windows directory or system referred to above, or if you put them somewhere else you must make sure to add this directory to the PATH environment variable. LabVIEW will simply Windows for the DLL, and if it isn't in the Windows directory or system (or the directory of the current application) or in a directory path variables windows won't be able to find it.

  I would not mess with lvdaq.dll. It is necessary to LabVIEW for hardware access DAQ and access the system will install the NOR-DAQ drivers.

  Rolf Kalbermatter

• Satellite A100-626 with Win7 - cannot install Bluetooth

  Hello

  I have a Toshiba Satellite A100-626 and I recently installed Windows 7. I was able to install all the drivers except bluetooth!

  There is no bluetooth device in the Device Manager... There is no unknown device is... When I try to install Bluetooth Stack, I get an error message saying, plug in and press OK.

  I don't know what to do... Can anyone help? In XP bluetooth worked well and I have used so many times...

  Help, please.

  Prior to installing the BT software, you must activate the BT module.
  The principle is the same as for the earlier operating system: turn on the WLAN antenna and use the FN + F8 key combination.

  The question is: can you use FN + F8 key combination to activate the BT?

• Strange behavior USB Flash Drive Satellite A100-626

  Hello

  I did install Windows Vista Business Edition on my Satellite A100-626 (PSAA9) following the instructions provided in the Web page of drivers.

  So far, everything works as expected, except for one little (or no) question.

  When I ask Vista to 'Remove hardware safely' my USB Flash drive, a Popup appears telling me to remove it. So far, so good :D

  The only thing is that the flash player is not put out as could be expected and and yellow question mark appears in Device Manager.

  Opening of the question mark can read what follows:

  "Windows cannot use this hardware device because it has been developed to remove safely, but it has not been removed from the computer. (Code 47) To resolve this issue, disconnect the device from your computer and plug it in again. »

  Following the instructions above, the light turns off, lol...

  Someone else met this strange behavior? If so, any solution?

  I tried a few USB flashes that run well on XP and they both do the same thing.

  Thank you, Nuno!

  Hi Nuno

  It's very strange. I have the Satellite A100-504 (comes with Windows XP Home edition). Last week, I installed Vista and all the stuff followed Toshiba document instructions facilities. I use the mouse wireless, external HDD USB web cam. With the help of these external devices together I never noticed a similar behavior.

  You have the same situation with all the USB ports?