Problem DaqMx LabVIEW

Similar Questions

• DAQmx LabVIEW 7.0 Wizard problem

  Hello, I tried to search for this problem a few times, but I couldn't find a thread that matches my problem. I only started using LabVIEW yesterday so please forgive my inexperience if I do obvious errors. The problem I have is this:

  I have two computers, two LabVIEW 7.0 running on Windows 7, with a card OR-DAQmx (PCI 6221, driver version 9.3) and the other without. Without the card has MAX version 3.0.2 and the other has the latest version (4.8). So far I followed the tutorials in the 'Help' files called "Getting started with LabVIEW", using the machine without the DAQ card. In the fourth chapter he speaks of an Express VI entitled 'DAQ Assistant' which is in the range of I/O functions window. When I try to enter a block diagram VI, rather than open the wizard, it hangs on loading splash. This, I expected when the machine is not material.

  Then, I started the other machine, who owns the card installed. I opened MAX, do you have the self-test, checked the test panels and made automatic calibration. all reported ok. When I open LabVIEW, however, all functions related to hardware DAQ is missing from the palette. I tried rolling back the drivers version 7.1 and MAX to 3.0.2 in the hope that reproduce the condition on the other machine would fix it, but no luck there now I'm at square one without knowing what to do. I really need to be able to use this card with LabVIEW for my project, any help would be greatly appreciated.

  OK guys, I have now Windows XP running in a virtual machine on the computer with the installed data acquisition card. Outside the Virtual Box, I still have driver MAX 4.8 and 9.3 versions and map is available on the tree of devices to the MAX, as before. Within the VB I use LabVIEW version 7.0 and DAQmx version 8.1 (MAX 4.0.3.3003) drivers as suggested, but the map is not appear in the device tree, even if I tried refreshing several times. To create news... window has no option for a card PCI-6221, only for PXI and SCXI hardware. Clues?

• Communication problem between LabView and acquisition of data USB 6259

  I want to monitor a data USB-6259 acquisition using LabVIEW 8.6. However, when you try to create an explicit task (using the DAQ assistant) in order to acquire a signal, I get the message asked supported device found¨. I can see the USB-6259 under ¨Devices and interfaces¨ to the MAX, but when I try to import the configuration data for NOR-DAQmx 8.7.2 in MAX, I get the message ¨Can´t import file configData.nce.  File not found¨. I use NEITHER-DAQmx 8.7.2.  Any suggestions?

  Corneliu

  Hi, Corneliu,

  This question could be generated due to a corruption of database of MAX. Here is a link to restore the database to the MAX.

  http://digital.NI.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9?OpenDocument

  Just follow the steps and let me know if that solves the problem.

  A greeting.

  Jesus.

• Can I use ' I read a Scan VI "daq and driver DAQmx Labview 7.1 with a new card?

  I need to use old software in which the data is to use ' I read a Scan VI.

  I think that with labview 7.1.

  now, I work with Labview 8.5 and the new daq card that I want to use comes with NOR-DAQmx.

  is there a compatibility problem between these two.

  Please clear my doubts.

  Thanks in advance

  Renn

  It is used with 8.5 cards and as long as you install the driver traditional. It should be on your LabVIEW CD or download it from here. New cards require DAQmx and you need to rewrite your code.

• VI (s) DAQmx Labview 2012

  Hello! I have a program (under labview 2012) but I change computer and the new computer can´t labview find vi (s) of DAQmx (create channels ect...) how I can install this vi? I installed labview core, 9.7 DAQmx 2012 costume. (in my old computer, I installed labview 2010)

  Thank you

  I installed DAQmx 9.8 and the problem was solved

• NI USB box problem when Labview ends abnormally

  Hi all

  recently, I had a problem with the NI USB box used in Labview.

  I wrote a very simple program and it runs in Labview 2011. Basically, it reads data from a NI USB box and also send data back. According to my knowledge (I don't know if it's good or bad), when the Labview is arrested shortly how it is completed, the USB box should also stop working. But the thing is, when the Labview program ends abnormally, let's say I directly terminate from the windows task manager when it is running, all the ports of the box USB will hold their final statements until I restart Labview and write new values to them.

  This could be very dangerous. For example, when I use the USB box to control the power of a power supply, the Labview program crashes (which happens often), the power supply box and USB power will continue to work until I restart the program again. I tried several different types of boxes NI USB on PC and the problem still occurred. So I was wondering if there is no mechanism that prevents such problems or if I can do something programmatically to avoid it.

  I thank very you much for your help and your time.

  Best regards

  Sun

  Sun,

  Another area where you can have a misconception: LabVIEW is not control USB DAQ device. The LabVIEW program called the DAQ driver program (typically DAQmx or DAQmx Base) and pilots say the OS to send messages via the USB port of the DAQ hardware. So stop the program LV, intentionally or accidentally, does not say the data acquisition driver and the OS USB driver to put the DAQ hardware in a State course.

  If you have a configuration where the LV program can be stopped before it can send orders "Safe state" DAQ hardware, you cannot ensure the DAQ hardware stops correctly.

  There are a few screws that have been written in LV "watchdog", but even those who depend on the operation of LV execution engine.

  You should carefully rethink the entire system, make security issue, one of the main objectives at the beginning.  Most likely, you will find that you need to a separate device, hardware clock or PLC, if the software fails to stop him.  You should also consider whether you need a real-time operating system to avoid some of the problems associated with the standard desktop operating systems.

  Lynn

• Problem in Labview DSP

  I have a DSP problem to be realized in the labview. However, I am not very familiar with a few boxes to tools. The goal is to detact the pulse whose duration and intensity of a noisy signal in real time. Given the pulse signal, the points how to locate the failure?

  Thank you

  It seems that the signal on the great transitions is superior to most of the noise.  I think I might try looking great transitions, say > 8-10 in 2 or 3 samples.  When I find such a leap, then look at the average before and after to see if we're a real pulse or noise.

  If the width of the pulse is known or have a narrow range of values, you can also use this information to help distinguish between the signal and the noise.  The transitions very wide encompassing the negative part of the pulse are much easier to detect.

  Lynn

• Signal Express version unknown problem with Labview VI

  Hi all

  I am trying to run 2010 Labview Signal Express VI. It gives me "unknown version" problem. When I checked for Labview versions, he said 10.0f2 and Signal Express can read the version of LabView 2010. I don't understand this. 10.0f2 is not just a patch for version 10.0? I will appreciate if someone can help me with this.

  Kind regards

  Kanu

  Hi Kanu,

  I tried to write a simple VI and its importation to the Express Signal and I have not had any problems. I use 32-bit LV2010f2 and Signal Express 2010. I have attached the VI I used so that you can try it yourself. I followed the instructions of this KB to create a distribution of the source file. If you follow this KB and still can't make it work, can you please post the VI?

  Thank you

• Problem between Labview and Melanie 2602

  Hello world

  I think my question is a bit silly, but I really don't know what the problem is. I just want to read my current solar cell by changing the level of my blood to get an IV curve, which is normally pretty easy. So, I created a loop, where I increase my voltage step by step, and used a function named VI from Labview library that connects the Keithley and Labview together, "Keithley 2600 Series.lvlib: Source Level.vi. I start at 0 and increase by 0.01 volt each time. If I use execution of climax, I see clearly the value is correct, and if I go inside the SourceLevel VI, I clearly see the command string: "smub.source.levelv = 1.6," for example, if I want to put my voltage at 1.6V. The attached picture shows a part of my code.

  Despite all this, it is clear that the Keithley does not react properly. It only works v of v 1V, 2V, 3V, etc... but never the values between. My IV curves are ok to read the Isc, but no VOCS. Never happened to any of you? I would be really happy to understand what I'm doing wrong, because it seems easy enough to solve. :/

  Thank you very much!

  It is quite difficult to debug a picture of a tiny part of the code.

  But I'll take what I see.  Your constant shows a 0.01 (comma).  So I guess that you are in a country that uses a comma instead of a decimal point.  I don't see what is happening inside the code Keithly, but I'll make an assumption that he made some conversions where it is expected that the comma is a period.

  Look closely at the code Keithly and see if that explains it.  Try to set your PC to use a period for the decimal point and try to re-run your code and see if it works better.  It is possible that Keithly conversion uses a system, rather than setting using a decimal point, which is that your sentence says it's sending.

• Problem with LabVIEW

  I met a problem when using the peak detection function in LabVIEW...

  Basically, I load a waveform in VI to detect peaks using the function of Ridge detection. of the waveform, it is obvious that the first peak will happen about 10570Hz...

  Using size 3 subgroup, it detected 1 pic to 10567Hz (correct)

  When you use the size of subgroup of 4, it detected 1 pic to 10569Hz (correct)

  When you use the size of subgroup of 5, it detected 1 pic at 12737 Hz (bad)

  When you use the size of subgroup of 6, it detected 1 pic to 10588Hz (correct)

  When you use the size of subgroup of 7, it detected 1 pic to 10588Hz (correct)

  And using other different sizes of subgroup, the freq agrees with waveform... Why when you use the size of subgroup of 5, it does not give good playback? Is there a theory or a reason for this? or just a bug with the LabVIEW function?

  A VI is fixed and the default values are loaded.

  Appreciate any assistance/advice.

  
  

• PB all DLLs with in VS 2003 DAQmx labview

  Hello everyone.

  I've created a dll using the DAQmx tasks in Labview. I call it in Visual Studio C++ 2003. There are two heads, this one and the one of NIDAQmx.h. In the race, I have Visual C++ Runtime error. Can someone explain to me what is happening to have a solution?

  THX

  OK, I solved the situation, but I can't explain what happened. It was a mistake to R6030 CRT. I rebuild the dll and everything was ok.

• Problem DAQmx read True False

  Hello

  I use DAQmx Write (Bool digital 1Line 1 point) to send a Boolean sample to a digital output channel.  I want to be able to tell if the signal is strong or weak, so I use DAQmx Read (Bool digital 1Line 1 point) to take up the task as input and then plug a light at the end of data.  The problem is the light lights up when I pass False to the VI DAQmx writing and does not shine when I pass the value true to the writing DAQmx VI.  Shouldn't the DAQMx Read VI be output Boolean even as input to the VI DAQmx writing?  In others, should I not get a true reading VI DAQmx if I pass a real in the DAQmx writing VI and even for a case of false?

  See code attached for simplified example of what I'm trying to do.

  Thank you

  Jason

  Which would make sense if the channel is configured as an open collector output.  This would mean that the line is retrieved when you write a REAL low and left floating when you write a FAKE.

• Problem DAQmx Base Examples

  Who what to compile the Mac DAQmx Base examples?

  I get a lot of errors. See annex.

  Hi Ben_01880,

  It is a known issue with Mac OSX and DAQmx Base. It happens when OS x starts in the 64-bit kernel instead of the 32-bit kernel which requires DAQmx Base. Here is a workaround in the DAQmx Base Help file:

  "Xcode 3.2 or later by default to 64-bit (x86_64) architecture at the call of the GCC on 32-bit OSX 10.6 If the 64-bit system hardware." This will result in errors during compilation. To resolve these errors, force gcc to use the 32-bit (i386) architecture in OSX for 32-bit installations by adding "-arch i386' for flags in your Makefile:"

  "Flags =-O2-arch i386 '.

  There is also an article on Mac support site that shows how to force OS x to start the 32-bit kernel on a basis of by-boot:

  http://support.Apple.com/kb/ht3773

  Finally, there is a forum OR discussion about this problem and how people were able to solve it. I link you to it because it's a good resource:

  http://forums.NI.com/T5/Multifunction-DAQ/NIDAQmxbase-compatibility-with-Mac-OS-X-10-6/m-p/1433896#M...

  I hope this helps, let us know if you still have problems!

• Problem of LabVIEW addons

  When opening an existing project, I was asked to find the control named "Telnet Session.ctl". The labview tries to load from "\addons\internet\telnet\telnet.llb\Telnet Session.ctl", but could not find. What should I do? I also see this box during the process.

  Why do you need it? If the VI is not broken, it does not use the Toolbox. If it is broken, then do the search but I don't think that there is a version of 2013. The old version also need a license so you will also need to that track down the original draft if in fact you need the functions of telnet. A missing ctl in a project is not a problem if any of the screws, use the.

• Problems of LabVIEW with Test Unit under lvoop

  Hello

  I try now provided with LV2012 with a LVOOP code Unit Test infrastructure but seem to be a few problems.

  I have built a unit test for a base class in the attached draft who is the source of class (it is another class in the project as it is an example of a method for recovering, but it is not used in the unit test). My problem is that I get results that fail for one of my tests, when I think they have to work.

  Basically, the unit test is configured as follows

  Case 1) test the VI without installation VI and ensure proper operation default values

  Case 2) test VI by setting specific values in the test in VI of disassembly and also check the single release of "Source Method.vi" configuration VI

  Case 3) Test of the VI with the VI of installation using the default values and confirm them through the VI of disassembly

  When running case 2 fails and indicates that disassembly of the VI return values by default not those fed to the installation VI. I don't see why.

  As per

  

  Any suggestions?

  All the best

  David

  Hi David,

  The behavior you describe is planned. When you first call the 'Source_Method.vi' by using the 'SourceAccess Unit Test Manual.vi", the"Unit Test Manual.vi SourceAccess' creates and instance of the "Source_Method.vi". In this specific case of the VI it will boot with the default values but will then retain the values passed by the "Unit Test Manual.vi SourceAccess' until the project we closed, or specifically tell you to reset defaults. Whenever she is called by 'SourceAccess Unit Test Manual.vi' it will access this instance of it. If another instance of the "Source_Method.vi" was created by another parent it would be initialized with their default values, until crushed by the top-level VI calling. Then would he behave exactly as the instance created by the "Unit Test Manual.vi SourceAccess". Whatever your type typedef and its configuration, as long as everything is connected correctly, this should be the expected behavior when you configure things through object-oriented programming in LabVIEW.

  I hope this information is useful to your application. If you want to see a LabVIEW example that demonstrates this behavior, you should consider referring to parts of the ReferenceObject.lvproj. It is found by searching in the example finder LabVIEW object-oriented. This is accessible via

  Help > find examples.