Similar Questions

• Problem with traditional DAQ passage to DAQmx using NOR-6534

  I'm moving the traditional following of DAQ code to DAQmx:

  

  This code is used to send data to program a FPGA using a PCI OR-6534 DIO.  This code works like a charm, but when I try to write the equivalent code using DAQmx (in LV 8.6 as well) it does not work.  I don't get any errors, but the FPGA do not program.

  The General procedure is as follows:

  The value of all the lines on the Port exit 0

  Set up the mode of transfer to low Active

  Write the data in the buffer

  Send the data using the internal clock of 10 MHz of the 6534 (6533 is no longer used, but the code was never updated)

  Wait until the output is made

  Disable the task

  In DAQmx I configured as such:

  

  Any ideas on what has changed in DAQmx or what I am doing wrong?

  Looking at your code traditional DAQ once more, he is actually setting up handshaking vs just a straight sample clock.  The Config VI Mode with the "clock polarity" setting is not a sample generated at a certain rate clock, but instead, it's a protocol handshaking attack or the trailing edge.  TDAQ had much more flexibility with what DAQmx and some handshaking protocols are not transferable to DAQmx completely.

  So when you say the configuration of your device in TDAQ bass Active transfer mode, I don't see what is happening in the code TDAQ.  It's really a negotiation protocol of unknown polarity (given that you use a control and I don't see the default value in the public Service).

  You can try to determine which protocol handshake TDAQ you use first, then determine if there is an equivalent for DAQmx.  The three modes that cannot be transferred are level ACK, tip, or long pulse modes.  These have ACK leading REQ, which is not possible for DAQmx to manage.  You can read more in the user guide for the 6534 and starting on page 3 and 4 are the comparison of the different modes of handshake.

  Then move forward options are do not migrate or to download a beta driver TDAQ, if you perform the migration for the purposes of the compatibility of the OS.

  Hope this helps, let me know what other spawn of this.  Thank you.

• Why do my pci-6052e configured as traditional daq and daqmx in MAX?

  I have an old computer of three year with 1 GB of RAM and a 3.00 GHz running Windows Server 2003.  It has already been used for experiments of movement control and has a 7333 motion control card and a PCI-6052E.  Now all I want to do is sample data of a pressure sensor and a flow meter using the PCI-6052E, but for some reason, this card is configured in MAX as a DAQmx device and a traditional DAQ (Leagcy) deivce.  Unfortunately, when I write the LabVIEW 8.2 VI, the only available data acquisition tools are DAQmx and Max my two instruments are installed in traditional DAQ.

  If there is only one card PCI-6052E in the computer, why MAX card PCI-6052E called dev3 DAQmx and a card PCI-6052E dev1 in traditional DAQ?  How can I fix?

  Cpesko,

  I am happy here, you have a few things working under Windows Server 2003.  We do not however have any software under this OS except what is listed here.

  DAQmx and TDAQ are 2 different drivers and this is the behavior expected that devices that support both would be present in the title of each driver.

• Traditional DAQ against DAQmx Counter

  I'm trying to convert an existing legacy application written in LabVIEW LabVIEW 2012 6. I have a problem with a traditional Daq counter. Specicically the VI "event or time meter Config.vi. In the attached VI, you can see that 1 meter is configured to count the cycles of an internal signal, not a PIN counter SOURCE signal. This configuration generates an integer for each cycle of the internal signal: every 10 microseconds in this case. I can't find a way to replicate this feature in DAQmx. I use a DAQCard-6062E (PCMCIA Slot) card in a Dell D620 Laptop. I tried to attach a fully functional VI, but get the error 'the content of the attachment does not match the type of file.' to fix this I had to fix a JPG image. I've included comments in VI to clarify things. Any help appreciated. Thank you.

  In DAQmx you can achieve the same result by setting the terminal entrance for a task of edge to the time base County internal 100 kHz:

  

  The 100 kHz Timebase is considered to be a "Advanced terminal" (don't get started me on the topic) so see in the dropdown menu, you must right-click on the control / constant and select the appropriate name of I/O filtering option.

  Best regards

• How can I configure a PFI to high on a 6602 traditional DAQ board

  Dear all,

  I'm using LabVIEW 8.5 on 32-bit Windows XP with a data NEITHER the 6602 acquisition Committee. In the past, I used DAQmx but for compatibility with older software, I need to do a few simple things using traditional DAQ, which I never used. Specifically, I want to make a simple VI which affects 5 PFI high when the user presses a button and then low when they press a second time. How do I put 5 PFI for output and then write faithful to her?

  Thank you

  Ed

  Dear all,

  Apparently its also simple to use digital writing line VI. However, the non-obvious thing is the width of the Board 6602 32 port is not the default value 8. Buried in the LabVIEW help files is a list of widths of physical port to fall on. As the cave of bats. In the picture as an attachment to the super simple VI, I did the 16 designated PFI 16. Good to know.

  Best,

  Ed

• NOR-traditional DAQ will work with a USB-6008?

  Hi guys,.

  I have ordered a USB-6008 and I would use it with the NOR-DAQ traditional 7.4.4 instead of MX. Is this supported?

  Thank you

  Jim

  LV 8.6

  LV 8.01

  LV 7.1

  TS 4.1

  Jim,

  No, traditional DAQ isn't USB compatible, 6008.

  You can use DAQmx base instead, but I wouldn't recommend it.

  hope this helps,

  Norbert

• Determine the number of channels selected for traditional DAQ

  The blocks 'DAQmx task' and "Traditional DAQ Channel" look pretty similar (see attachments). The DAQmx block ist an individual selection of channels and I am able to determine the number of selected channels.

  Now I am trying to determine the number of selected channels to a traditional DAQ, but the property DAQmx block does not work here. I already tried the trad to some form of blocks. Range of data acquisition, but failed.

  Any idea?

  

  In traditional DAQ, there are several ways of specifying the list of channels. Assuming that your picture shows how you use your channel list is just a string of delimited by commas. Wire a constant to a string array node worksheet and specify "comma" as the separator and the number of columns must tell you the number of channels.

  Ben

• Difficult to see the details for the traditional DAQ functions

  I'm migrating a Tradtional DAQ to DAQmx applications and manage to LV 8.6 to see 'details' for traditional data acquisition functions.  I looked to the traditional manual online user DAQ & a few other pubs and impossible to find a good explanation, parameters of entry and exit to functions.  Can someone help me?

  Thank you... PacMan

  In talking with Kent Lau, an applications engineer at NOR, told me I was missing the file nidaq.chm for a reason any.  Even after trying it from reinstalling drivers traditional DAQ of Q4, 2008 software distribution, it is still missing.  So, I installed an older version of the driver on a computer that has never had LabVIEW, then copied the file nidaq.chm in the folder 8.6\Help of LabVIEW & was able to then see the traditional DAQ work details.  Thanks Kent!

• Tradition DAQ installed but not available

  Hello

  I have a system that had LabVIEW executable v6.0.2 running with 6.9.3f3 NOR-DAQ with a PCI-6052E.  I have now installed LabVIEW 2009 with NOR-7.4.4 traditional DAQ OR DAQmx 8.9.5 on this system.  My 6052E appears in MAX under NOR-DAQmx and NOR-DAQ traditional (old) devices, but under the legacy, the button 'Test panels... '. "is grayed out and if I get the properties of this device, tab 'System' of later dialogue has the resources box in gray gray as well as 'Test resources' and 'Run Test panels' buttons.  I tried to reset the device under DAQmx, but it does not help.  I ran a self-test of the 6052E by right-clicking on the device under DAQmx and happening.

  Another problem I noticed is when I try to run any traditional LabVIEW DAQ example, I get the following error repeatedly: "load error"C:\Program NIUninstaller Instruments\LabVIEW 2009\vi.lib\Daq\lvdaq.dll".  A dynamic link library (DLL) initialization failed. "This happens for each traditional DAQ VI who is trying to load.

  Examples of LabVIEW DAQmx load and run fine.

  This looks like a corrupted installation of NOR-DAQ (Legacy).  My goal is to get my code that runs under the latest NOR-DAQ (Legacy) and then transition to DAQmx. What is the best way to proceed is this new OR-DAQ (Legacy) to run?

  Thank you

  Greg

  You have fixed the problem by repairing the NOR-DAQ 7.4.4 (legacy) install via Windows ' Add / Remove programs.

  Greg

• Is there a DAQmx function to duplicate the traditional DAQ "Index.vi channel".

  I've been converting an old app using traditional DAQ to DAQmx.  It's a complicated piece of code and makes installation of all available channel group config, then the user selects the specific ways to acquire data on.  It uses the "Index.vi channel" to achieve this.  Is it possible to replicate this feature in DAQmx, or will I have to rewrite the whole mess?  Thank you.

  Thank you aNltaB.  I was able to implement a task with the necessary channels for each thing that I did and circumvent the need to configure all channels and then indexing them.  I didn't know how it was all rooted in the program, but make the separate tasks seems to work well.  As far as I am concerned, this issue is resolved.

• Traditional DAQ in multiple versions of the CVI

  I need to support some older programs in our manufacturing space. These programs are written in a few different versions of the CVI, but they also use traditional DAQ. I can't get multiple versions of the CVI to work with Tradtional DAQ.

  I installed CVI 8.1 and then installed the TDAQ. I was able to open one of my projects that was compiled previously in this environment, and everything seems to work properly. I then installed CVI 9.0. Initially, he couldn't find the header for the TDAQ files, then I pointed to the 8.1 CVI include the folder. The project has managed to compile, but it does not link. I was looking for a library to be added to the project, but I couldn't find an obvious tdaq.lib.

  Should what file I add to get this link?

  Note: We need to build in the same environment due to validation rules. If I build a program in the same environment, just to do a small test to make sure that my little change does not adversely affect anything. If I build in a more recent environment, then I need to run a complete verification throughout the application process, which is a tedious process. Management does not like to take the line down for a day or two, while I validate the application of 'new '.

  OK, so I can understand that you now TDAQ installed in CVI9 and not present in cvi8.

  If so, copy the following files from dossier\sous-folder to the corresponding CVI8 one CVI9:

  \bin\ all the files dataacq.* and easyio.*

  EasyIO.lib and \extlib\ dataacq.lib

  \include\ dataacq.h; EasyIO.h; nidaqcns.h; nidaqerr.h; olderror.h; regdefs.h

• No driver error when you include traditional DAQ in the Kit of Distribution CVI 9.0

  I have a legacy code (CVI 6.0) that I wanted to update recently.  The main reason was the ability to add the device drivers for the distribution kit.  When I installed the software on a new machine, I had a driver number error when you make a call to CounterStart.  In the past that error means that I had not included support CVI when I installed traditional DAQ.  Since that it has been installed as part of a kit of distribution that I do not see what elements have been installed.  I guess that since it was listed in the framework if a distribution of CVI kit that support the CVI is automatically.  How can I get rid of not the pilot error?

  Thank you

  CP

  Hello

  Unfortuantely, there is no way to have included in a CVI tDaq generate setup with the support of the CVI.  R & D is aware of the issue.  For now, the solution is to modify the installation of tDaq and add support for the CVI.

  For more information, please see this KB.

• Determine the number of traditional DAQ hardware using Labview.

  Hello

  Anyone can answer the question:

  Regarding materials traditional DAQ, for example the DMM OR-4060, how

  can I programmatically determine the number of device which can be seen in MAX?

  With the help of Labview 8.5, I looked into the following function libraries:

  NOR-DMM

  VISA

  NOR-ModInst

  None of the libraries above seem to provide access the number of traditional DAQ hardware

  property, which is automatically assigned.

  Background:

  I have a 18 PXI chassis containing 2 DMM, in housing 3 and 14.

  The DMM may be a mixture of type OR-4060 or NOR-4070.

  The system is controlled by a Teststand sequence employing IVI - DMM

  steps.

  When you set the IVI logical name step, I am referring to IVI device defined Sessions

  Max - rutime determined.

  Labview VISA functions using I can determine the model, i.e. 4060 or 4070.

  Because the DMM just locate into the slots 3 or 14, then the devices NOR-4070

  are accessible using the following descriptors of resources: PXI1Slot3 or

  PXISlot14.

  (The 4070 is compatible DAQmX.)

  So for devices OR-4070, I can predefine 2 Sessions of IVI device, knowing

  It will be sufficient for all occasions, when I run my Teststand sequence, which will be

  determine what device session to use at run time.

  But I'm stuck for the NOR-4060.

  At the Session of the device, I have to give a descriptor of resource the following

  format: DAQ::x (where x is the device number)

  I could create device 18 sessions each reference to a different DAQ::x, but to select

  the good pair during execution, I would need to programmatically determine the device

  number, i.e. the value of x.

  Where my question.

  The closest I came to a solution was an entry of the Knowledge Base that said that the

  Assigned device number would be the same as the slot number, providing the

  Number of the device had not previously configured manually.

  Unfortunately, our device numbers have been changed manually and maybe in the future.

  All popular solutions.

  Gary.

  Hi Gary,.

  Good afternoon and I hope that your well today.

  Thanks for your post and I want to help you solve your problems.

  I don't think there is just a function that you can use to identify and collect information on all cards with your. For traditional DAQ devices in particular I suggest using the Information.vi of DAQ devices get.

  If you look at this link,

  SAL posted an example VI entitled, find dev trad.vi.

  You can get information such as serial number, Dev name and the Base address.

  The assistance of the respective drivers to collect information you could generate an array of strings with the information that you need all the slots.

  Please let me know if this is useful at all,

• Labview2009 and NOR-traditional DAQ

  Hello friends NOR!

  I am running LV2009 on a machine with win7 32 bit with a DAQ PCI-MIO-16-1 card.  We have a program for the calibration of pressure transducers, but he wrote with the NOR-DAQ traditional.  I plan on writing a new program to make the calibrations, but until then, I would use the old.

  I see that some DAQ hardware can support two pilots, including the device that I mentioned above (http://download.ni.com/support/softlib//multifunction_daq/nidaqmx/7.4/readme.html). I also found the location to download the traditional NOR-DAQ driver for 32 bit Win7 (http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A). Based on the information I have at the moment, it seems that it will work.

  However, I remember seeing something that says that if I install a different driver, the current will be replaced (I can't find the original source).  I also met this warning: "NOR recommend not to install NOR-DAQmx on the same machine that the driver beta OR-DAQ traditional (old). (http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A)

  I'm not interested in screwing up this machine because I'm not the only person who uses it.  I don't have enough experience NOR the appeal without checking first with those who do it here on the forum.

  Thanks for the help.

  Darren

  You have a deployment problem.

  my strong recommendation would be not to change the drivers on the computer that works and develop your code of replacement to new hardware.

  Yes, you might get away with developing a new solution on a working machine but it's almost garunteed to cause some conflict somewhere with a driver.  Unless you know what everyone does with a system that works AND you really understand NOR drivers and what changes exactly where and in what version you ask some "educational" by developing a functional system necessary.

• Synchronize two E-card with traditional DAQ series

  Hello

  I have a PCI-6052E and a PCI-6071E and I have a Matlab program that interacts with traditional hardware DAQ driver cards.

  It is possible to synchronize the two cards use RTSI or something? If so, what should I do in matlab to achieve?

  I'm a bit confused, because I don't know if this is only possible using DAQmx.

  Thank you!

  Hi zlyhere,

  Using DAQmx would definitely be the best choice.

  In terms of using C vs the Data Acquisition Toolbox for The MathWorks Inc. Matlab® Software, I would recommend the Toolbox for ease of use.  The MathWorks develops the Toolbox, so they must have documents on how the maps can be synchronized.

  If you find that you need more features, you can fall back to C.  Documentation is available at

  "" "" Start menu"all programs" National Instruments "NOR-DAQ" support textual Code ' using NOR-DAQmx C reference

  MATLAB® is a registered trademark of The MathWorks, Inc.

  See you soon!