Adlink daqpilot not working in subvi (DAQ/PXI-2204)

Using DAQpilot from Adlink
in Labview 2010 / windows 7
I want to do n-channels, n-scans, single shot in a while loop
The configuration is as follows: (see also attached task)
-installed device: DAQ/PXI-2204:0
-n-chs: 0-31 differential
-10.000 Hz
-30.000 scans
-scaled data in 2D array
The DAQ pilot runs once and continously in a sub vi:
It also works when I place the task in a loop.
But when I use it in a sub vi which is called from another vi in a loop it work the first cycle and the second not, third ok, fourth not. see diagram below:
following error message:
Attachments:
test_3.vi ‏67 KB
while_loop.vi ‏13 KB
tset3.zip ‏4 KB

Hello!!!
You do not need to put the "Configuration Parameters Setting" inside a loop.
These configuration are needed just one time.
If you want to change these parameters for other acquistion, you can put these steps inside a case structure and when you need to change those configurations values you've just to call the "Configuration Case" and do it before the new acquisition starts.
The acquisition need to be continuous, not the configuration.
You can found code examples on this link below:
www.ni.com/code
Hope this helps,
Regards.
Barbara Pracek
Engenharia de Aplicações
National Instruments Brasil

Similar Messages

  • Hi am trying to save Data into a write to measurement file vi using a NI PXI 1042Q with a real time mode but it is not working but when i run it with uploading it into the PXI it save in to the file

    Hi am trying to save Data into a write to measurement file vi using a NI PXI 1042Q and DAQ NI PXI-6229 with a real time mode but it is not working but when i run it without uploading it into the PXI it save in to the file please find attached my vi
    Attachments:
    PWMs.vi ‏130 KB

     other problem is that the channel DAQmx only works at real time mode not on stand alone vi using Labview 8.2 and Real time 8.2

  • Subvi does not work properly when called inside a vi

    Hello Every body
    thanks for your help. i am using a sub vi for sine signal generation. as a vi it works fine. but when i called this subvi inside another VI it gives some problems. for example timer indicator works properly.it reinitializes as well in the sub vi, but in the main VI it does not work properly. means does not count the time.in the sub vi on the fly i can change the values of frequency and amplitude in real time, but when i use as sub vi, it does not reponse as i change the values in the control arrays.similarly pause and continue works properly in the sub vi, but once again in the main VI, it does not work properly.graph indicator also work properly in the sub vi. but here once again it does not work properly in the main VI.the pause resume indicator also does not blink, when it is continue. in the subvi it blinks very well.generally why the sub vi does not work properly inside the VI?i am sending my VI and sub vis.
    any tips would be highly appreciated.
    thanks
    Regards
    Attachments:
    vi.zip ‏87 KB

    I just want to add some more details to Dan's answer. The subVI is acting exactly like you've coded it. The mistake is in understanding how subVIs work. When you call a subVI (or a function in any other language), you pass some parameters to it, the subVI does it's thing and returns values. the subVI does not accept new parameters from the calling VI until it returns to the caller and the caller runs the subVI again. In your case, you have a subVI with a while loop. You have some front panel control wired to the subVI's stop terminal. When first called, the value is false. So the subVI will keep running until the subVI's stop button becomes true but you cannot change it from main until the subVI finishes and returns so the subVI will never stop. As Dan says, the solution is pass references of front panel controls to the subVI and have the subVI monitor those references for changes and to update references to indicators on Main. You subVI does not need any front panel controls or indicators of it's own.

  • Events in SubVi not working as expected

    Hi, I am reposting this question as my previous one didn't resulted in any satisfactory conclusion.
    I have attached my Vi's which are not working as expected. If I remove ONE subVi and its associated 3 controls and two indicators, the other one works just fine, but when I add two SUB Vis, it goes messy. I am trying to learn this way, I am sure it can be done many other ways, but please help me finding out the problem doing it this way as in my final MainVi, I would like to use 8 such sub Vis. Thanks.
    Solved!
    Go to Solution.
    Attachments:
    Main.vi ‏11 KB
    SubVi.vi ‏12 KB
    SubVi_2.vi ‏15 KB

    Your main problem is DATA FLOW.  A loop cannot iterate until EVERYTHING in it has completed.  So, as you have it, you have to have both event structures execture before you can go back to look for the next event.  So if you insist on having these subVIs, they need to be in seperate loops.
    BTW, you can get away with a single subVI.  Go into the VI properties and make it reentrant (preallocated clone).  Then each call of your subVI will have its own memory space.  A lot easier to maintain that way.
    And I know you said you didn't want alternatives, but here's how you can do it all with a single event structure in your main loop.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    Main_MODTR.vi ‏10 KB

  • Timers do and communication not working on RT system on PXI chassis

    I am having problems with my application when I "Install it to a real-time target". When I run the program in debug mode everything works fine.
    I have two programs. One runs on a real-time OS on a PXI chassis Controller (Client). The other runs on my Windows 7 PC (host).
    When I run the Client application in debug mode (Run->Debug Project) everything works fine. When I run the Client application in the release mode (Run->Install Program to Real-time execution target) things do not work.
    It appears that the timers do do start. The Client application does receive communication sent from the Host application but is not able to send communication from the Client to the Host.
    I have been fighting this for a while and have tried to get help through emailing the support but have not had much luck that way. I think I need a phone call with an application engineer.

    It is not LabView. I am developing software with LabWindows\CVI. I've seemed to narrow things down a bit. When I send a message to my application on the PXI Controller it is  calling a function PostDeferredCall(...). The deferred function is never called. Not sure why it works when I am running the code in Debug Mode but not when I install it on the target. In my while loop in my RTmain() function it looks like this:
     while (!RTIsShuttingDown () && !gDone)
      /* Your code. */
      /* Sleep for some amount of time to give the desired loop rate */
      /* and to allow lower priority threads to run.                 */
      SleepUS (1000);
      ProcessSystemEvents ();
    I thought the deferred function was supposed to be called in the Main thread? Not sure where it is hanging up yet.

  • Vision EXEcutable does not work on host machine (missing subVIs)

    Hello,
    I am working on LabVIEW 10 / vision 11. I am making a VI to take a picture with USB camera and I built this application to create an executable.
    This executable works fine on my computer (which has LabVIEW installed) but does not work on other a host machines. 
    I tried to run this application on another computer with LabVIEW installed and it worked fine.
    On host machines, it keeps telling me that I have missing subVIs (only vision subVIs !!). All my other executables without vision VIs work fine...
    Do I need a license on my host machine to run my executable?
    Do you have any other idea?
    Thank you!
    Nicolas.

    On a target machine, you need the LabVIEW runtime engine and a the Vision Acquisition Software installed to run an executable. The LabVIEW runtime engine doesn't cost anything but you still need to pay for the license of Vision Acquisition Software.
    The NI VAS can be downloaded from here:
    http://joule.ni.com/nidu/cds/view/p/id/2975/lang/en
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • SubVI with while loop + event structure not working in multi tab VI

    Hello Everyone,
    I am developing an interface for the control of a prober using Labview 2012, and I am stuck with some issue.
    To start with I provide you with a simplified version of my control interface VI, and with the sub-VI used to build and manage the wafer maps.
    The VI consists of several tabs: Prober Initialization, Wafer Handling, Wafer Map, Status, Error.
    The sub-VI can:
    1/ initialize the grid to display the map (sub VI Init Grid not provided here)
    2/ import XY coordinates from a txt file (sub VI Wafer Map Import)
    3/ display the coordinates and index of the die below the cursor
    4/ and when a die position is double clicked, and the boolean "Edit Wafer Map" is true, then the user can change the state (color) of the die between On-wafer die and Selected Die
    My issue:
    If I use the sub-VI by itself, it works fine. However when I use it as a sub-VI in the tab "Wafer Map", the map does not build up and I can no further use the embedded functionalities in the sub-VI.
    I suspect the while loop + event structure of the sub-VI to be the bottleneck here.
    However I don't know which way to go, that's why I'd be glad to have some advice and help here.
    Thank you.
    Florian
    Solved!
    Go to Solution.
    Attachments:
    Control Interface.zip ‏61 KB

    Hi NitzZ,
    Thank you for your reply.
    I tried to save the VIs in LV10, please tell me if you can open them now.
    Inside he event structure there is quite some code, and since I don't want to make the main vi too bulky, I would like to keep it as a sub-VI. 
    As you can see from the sub-VI, the event structure is used for extracting cursor position and tracking the double click action. These events are linked, through a property node, to the image "Wafer Map" which is passed to the main vi through connector pane.
    All values are passed this way as well (through connector pane). Is there another way?
    Maybe "refnum", but I don't really understand how to use them...
    If I use the event structure in the main vi, the wafer map is still not working. I tried it earlier.
    To implement the multi tab front panel, I used a tab control, and a for loop + case structure. For each element of the case structure, there is a corresponding action.
    For the case where I put the code (element=2) for Wafer Map, I also control the execution of the code with a case structure activated by the button "REFRESH". Otherwise I end up with a freezing of the panel right after the start.
    I hope these comments help you understand better.
    Regards,
    Florian
    Attachments:
    Control Interface.zip ‏104 KB

  • Activity 2-4 Call a SubVI not working as demonstrat​ed

    see description..... the wires show as not connected if I add the subVI temp & vol to diagram. If not wire to SubVI, then connection to divide VI is okay.....this is not as being demonstrated, even though I've used a SubVI created by National Instruments, as stored in the Solutions directory.

    I'm assuming that this is one of the old tutorials from LabVIEW 5. I looked it up and did the activity as described and had no problems with using the Temp & Vol.vi in the solutions folder. If you delete the connection to Temp & Vol.vi, your VI should show a broken arrow because the divide function is missing a connection. If there's no broken wire, then maybe you've wired both inputs of the divide to the constant. Delete the sire from the constant, select Remove Bad Wires from the Edit menu and try again. If all else fails, attach your VI so someone can look at it.

  • Will an apication that requests the d2k-dask.dll work with a daq-mx 6036e card?

    I have an aplication in labview 6.0 that does not run because there is a missing dll file. It worked well with another daq card, under the same version of the labview. I culdn't find the dll yet. Even if I can find it, I wonder if will it work with my daq card. Any help is welcome. Thanks.

    After doing a Google search, it appears that the dsk-dask DLL is for use in communicating with ADLINK's data acquisition cards, not National Instruments' Multifunction DAQ devices. The NI PCI-6036E is compatible with NI-DAQmx 7.5 as well as Traditional NI-DAQ 7.4 drivers, so you will want to use one of those drivers to communicate with your NI PCI-6036E.
    Hope this helps!
    Michael P
    National Instruments
    Michael P
    National Instruments

  • Why is my executable VI not working with a PCI-6259?

    I have bought a PCI-6259 which has referencing trigger capability. I wrote a VI for acquiring the data and tested the VI on my PC that has the full developmental LabView 8.2.1 package installed.  The trigger is a 1 volt level that is triggered by a potentiometer ranging from 0-5 volts that I control manually. The VI works exactly how I want it to, however, now I want to use the Application Builder to create an executable to distribute the VI to the testing station PC. I then removed the PCI-6259 from the developmental PC and installed it in the testing station PC and loaded the executable VI along with the LabView 8.2.1 Run Time Engine. I open the program and it runs but I cannot get the program to trigger using the same potentiometer so it runs in an infinite loop.  I'm pretty sure everything is loaded correctly and the only difference between the two stations is that one has the full developmental LabView package and the other is an executable. Would anyone know why my executable is not working?
    Thanks,
    Matt Kostyal

    Hey Matt,
    Thanks for contacting National Instruments support.  One thing I'd like to see you try in the DAQ diagnostic utility.  I do not suspect a bad card, but it is an executable that we can try that we know was properly built.  If it doesn't work that will give us some more insight into the problem if it is truly hardware or software. 
    Let me know what you find.
    Regards,
    Kenn North
    Senior Product Manager - Search, Product Data
    http://ni.com/search

  • My excel report is not working in executable file ,however,it works well in vi

    Hi all ,
         Could any one please help me in getting the reason behind the executable file not working for excel report generation,however I can get the same function without any problem in main vi.
    I am attaching my code and executable file also ,please have a look into it and let me know where I am wrong.
    Thanks & Regards !
    sarita
    Message Edited by MindPower on 10-24-2007 01:40 AM
    Message Edited by MindPower on 10-24-2007 01:43 AM
    Attachments:
    test datalog.vi ‏264 KB
    test datalog-NEW.zip ‏1020 KB

    I can't open the vi in the moment. But by your description I think that I know the solution.
    When you build the executable you've to add dinammically the vi's from report generator that aren't in your main vi hierarchy. So, you've to open the vi's and find those that are open trough "open vi reference" and add them dinamicaly.
    And don't know if these tips are enough.
    From NI Zvezdana S.
    "When you use the Report Generation Toolkit to build a stand-alone application with the Application Builder, you must add _Word Dynamic VIs.vi from _wordsub.llb and _Excel Dynamic VIs.vi from _exclsub.llb as dynamic VIs. These two VIs contain subVIs that are called dynamically by the high-level Report Generation VIs. I believe that if you grab these VIs from the (desired office version part of the) installation CD instead of from the development machine, then everything should work. "
    Software developer
    www.mcm-electronics.com
    PS: Don't forget to rate a good anwser ; )
    Currently using Labview 2011
    PORTUGAL

  • NI-DAQmx 8.8 does not work properly after upgrade to LabVIEW 8.6

    Hi,
    I just upgraded to LabView 8.6 from version 7.1 and found out that the NI-DAQmx 8.8 drivers do not install correctly, since there is not Measurement I/O tab in the Functions palette (see attached document). The curious thing is that I can see all my NI-DAQmx devices in the MAX, and they all test correctly, i.e., they are working correctly. The sales representative for my area recommended me to uninstall , and reinstall LV8.6 and then reinstall the NI-DAQmx 8.8 drivers, but it did not work. I still do not see the Measurement I/O functions and my application says that it "cannot compile" the NI-DAQmx vi's. Thanks in advance for your help.
    Peter
    PS. Someone reported a similar problem back in 2003, but the final solution was not posted. Thanks again.
    Attachments:
    LV8.6.doc ‏116 KB

    Dear Mallori,
    Thanks for your help. You are right, I uninstalled and reinstalled LabVIEW 8.6 (update from LabVIEW 7.1) and reinstalled DAQmx 8.8. I still continue to have some problem that seem (to me) beyond compatibility issues. Here are the answers to your questions:
    1.  Before you reinstalled DAQmx 8.8, did you
    uninstall it? If not, then I  believe that the installer would see the
    driver already present and not actually make any changes.
    REPLY: No, I did not uninstall DAQmx 8.8. What do you recommend? Should I uninstall BOTH LabVIEW 8.6 and DAQmx 8.8 and then reinstall everything again? 
    2.  When you say that the VIs are not responsive,
    could you describe this a bit better? Perhaps post one of the error
    messages about compiling that you mentioned in your first post?
    REPLY: I am having a lots of "This SubVI is not executable" error messages in many of the library VI's not even mine. See the attached file.
    3.  If you open the NI Example Finder (Help»Find
    Examples) and the expand Hardware Input and Output»DAQmx»Analog
    Measurements»Voltage, are you able to run one of the example programs
    and see the correct values that you see in the Measurement and
    Automation Explorer Test Panels?
    REPLY:  I tried to runa couple of the examples for continuous voltage acquisition (internal clock) and both open with errors (see attachement).
    Thanks again for your help. I am looking forward to your recommendation.
    Regards,
    Peter
    Attachments:
    LV8.6-3.doc ‏43 KB

  • VI Search Path not working in LV2011 for VI Server Plug-ins with exe

    I have found what seems to be a problem with the search path when a LabVIEW 2011 built executable calls a Plug-in VI. 
    When the plug-in VI has subVI’s from vi.lib on its diagram the executable has to know where to find them.  Not all VI’s in vi.lib are part of the run time engine or the dll’s that may get generated as part of the build. The things you have to do to make plug-ins work for an executable are explained in several Developer Zone articles.   The article titled “How Can I Change or Set the VI Search Path for LabVIEW Executables” describes the ini file setting  viSearchPath.  When this is set to the vi.lib directory I have not encountered problems with previous versions up to and including LabVIEW 2010.
    I have come across an example in LabVIEW 2011 where it doesn’t work.  I have attached an example (I am using LV2011 SP1).  It demonstrates the basic plug-in architecture. Everything works in the development environment.  But it doesn’t work from a built exe.  I haven’t included the actual built exe in the zip file in case that causes a problem downloading it.  If you run the build spec from the src directory project file the exe should get generated in the bld directory.  The problem appears to occur when certain VIs from the analysis library are in the Plug-in.  In the example attached, the Plug-in VI is very simple but I have placed the troublesome SubVI on the diagram.  The VI in this example where there is a problem finding it is the Butterworth Filter VI.  I have placed it on the diagram in a conditional disable structure so it is easy to enable and disable.  When enabled and you run the test Plug-in VI the error 1003 is raised, meaning a subVI cannot be found in the dynamically called VI (for example see this post).  Note that a way round this may be to incorporate the Plug-in VI into the built exe but this shouldn't be necessary.  It’s not a problem with this specific filter VI, as it occurs for other VIs I try on the diagram.  However if you place an FFT VI on the diagram there is no problem.  I suspect that one is built into the Run-Time Engine.
    I also note I am running Win7 64 bit and 32 bit LabVIEW (note the relevant viSearchPath in the ini file – you may need to change if you are on different version of Windows).  If the example is converted to LabVIEW 2010 everything works as expected for the built exe.  I tried that on a colleague’s computer running XP and 2010 but I am pretty sure in still also works on Win 7.
    Things I am suspicious of are that the analysis VI’s are part of a LabVIEW library (lvlib)  and perhaps something has changed there?  I understand there is a problem with OOP in LabVIEW 2011.  Perhaps it is related to that as that seems to be an issue in 2011 (see this Discussion Forum post).  Perhaps it is related to OS version?
    I also tried generating a Source Distribution to extract out all the vi.lib VI’s and place them directly in the Plug-in directory.  That didn’t help.
    Interested in whether anyone else reproduces this behaviour.  In any case something is different in 2011.
    Attachments:
    LV 2011 test Plug-in.zip ‏42 KB

    I found some more out about this issue working with my local NI rep here in Australia.  Apparently something has changed in the compiler between LabVIEW 2010 and 2011.  Using the viSearchPath token in the ini file, as described in various Developer Zone articles, now guarantees that the Plug-in will not work.  The only way to make it work appears to be to create a Source Distribution.  I noted in my original post that I had already tried this and it would not work.  It turns out that having the viSearchPath token in the ini file when using a Source Distribution causes the error 1003 to occur.  When the token is taken out of the ini file the Plug-in (containing an analysis VI) with a Source Distribution works - in the simple example I posted.
    Well I then found its a bit more complicated than this.  It all worked for the simple example I posted.  Recall we found the error when there was an analysis VI in the Plug-in VI.  In our actual application (which is a large one) that calls Plug-ins - we still got the error 1003.  By trial and error I found a workaround.  There are certain Build Spec settings for the calling exe that I set and found worked.  On the Additional Exclusions page I found that I had to make sure that I left unchecked "Modify Project Library File after removing unused members".  I've always had trouble understanding the need for this setting.  In the Build Spec Help on that page it notes that the build will take longer.  In most builds you remove polymorphic VI instances, remove unused members of Project libraries and also Modify the project library file after removing the instances (this is a sub setting of the previous).  This makes the exe smaller in size and a quicker build time. Obviously modifying the project library caused a problem.  In the big application exe calling Plug-in, I probably have the same analysis VI on the diagram (I haven't actually checked and also whether it is the same polymorphic instance) and in the simple example I posted I definitely did not have VI in the calling exe example - so there may be some clue there.  I should try putting the same analysis VI on the calling exe diagram in the simple example to see what happens but I'm running out of energy on this one :-(
    So none of this gives me much confidence and I wish I could get a better explanation from NI regarding this behaviour to be sure I am not going to encounter a different problem for different calling exe and Plug-ins.  I was advised that a CAR would be issued.  Perhaps this is now expected behaviour for 2011 but it would helpful if some definitive explanation could be given about what has changed from LV2010.  And an update of Developer Zone articles on the subject would be helpful.

  • False/True Case is not working. Please Help!

    Dear all,
    I attached my block diagram, one attachment refers to true case and the other refers to false case.
    My program runs like this: when i run the vi , after homing the motor (there is home.vi), DAQ is collecting the values in the while loop, and according to the DAQ's value, motor should run the False/True case but it does not
    As a result: true/false case is not working which is located at the outside of the loop(bottom side of the block diagram)
    When i put the the True/false inside the Loop(DAQ's loop) , then it is working. But this brings lots of problem, two of them is: 
    1-) When the DAQ values goes below to "50" then it turns to true case again,
    2-) The false case has stop.vi which cause to motor stop every iteration of the loop.
    So that is why i put True/False case out of the loop but now it is not working at all.
    Please answer, waiting response.
    Thank you,
    Have a nice day,
    Kind Regards.
    Attachments:
    OutloopTrueMode.pdf ‏432 KB
    OutofLoopNotWorking.pdf ‏443 KB

    Salander wrote:
    Dear GerdW,
    Thank you for reply, You can see my answers written with red.
    "As long as the case structure is located outside the loop it will not be called before the loop stops. THINK DATAFLOW!"
    - The case structure need to run same time with the loop, because as you can see from the attachments the case structure is also integrated with DAQ values.. loop is continuous till i press the stop button.  So what i understand that this case structure will not work because loop is continuous?? Cant we upgrade the vi. or do smthg that it can be able to work same time with the loop??
    Kind Regards.
    You have to place the case structure inside the while loop ( Any significance is there on placing the case outside the loop? ).
    Salander wrote:
    Dear GerdW,
    Btw. it would be much more useful to attach real pictures or, even better, the VI...
    Because most of the people dont have my "motor controller's labview drivers"  I attached as a PDF file which is very popular.
    Not Really * .png file ( vi snippet ) is much more popular here in Discussion Forum
    The best solution is the one you find it by yourself

  • IEEE USB not working

    I using LV9.0 and was using and ICS USB_IEEE converter. The ICS USB work of awhile then would lock up. So I thought I would switch to an NI USB-IEEE. I reintalled the newest NI 488 drivers then reboot. The NI-IEEE would work with Automation explore but it will not work using labiew or and LV .exe. I tried to remake a simple IEEE write -read VI and it still doesn't work. Error (0). I then unistalled ICS completely and installed the NI-488 drivers again and still does't work.Any ideas?
    Solved!
    Go to Solution.

    Hi Andy, 
    How extensively did you test the functionality in Measurement and Automation Explorer? Are you able to send/receive signals or collect data from your device by implementing tasks in MAX? If it works in Measurement and Automation Explorer, then it is likely that the GPIB IEEE is functional in connecting your device to the software. How are you calling to this device in LabVIEW? Receiving no functionality in LabVIEW but fine functionality in MAX does not indicate a problem with the cable. Please post more information regarding your set-up, what device you are connecting to as well as your LabVIEW program. 
    Regards,
    Jackie
    DAQ Product Marketing Engineer
    National Instruments

Maybe you are looking for

  • What does the 'Dual' in Dual-Link DVI Adapter refer to?

    We purchased a 'Mini Display Port to Dual-Link DVI Adapter thinking it meant we could split the output to two monitors such as the Matrox TripleHead2Go or Matrox DualHead2Go. Having received it, we are unable to determine the advantage of using this

  • How to get the First day in a Week in a Fiscal Year

    Hi guys, I have a Requirement to calculate the First day in  a Week  in a Fiscal year . The FM GET*FIRST_DATE and all are for Calender year. Is there any FM to calculate the First in a Week in a Fiscal year. For eg. They will give 200826. In this 26

  • Error on every startup - after installing LR 5

    Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches. It then quits - restarts - and shows the message again - how do I get rid of that error? OS: M

  • Asynchronous web service call from Redwood

    Hi Everyone, Build version M33.104. We have a scenario where we have to call an asynchronous web service. From the documentation i understand that the Redwood job will be in status Running until the web service completes. How does the call back work

  • Lens correction crop / full format

    Hi, Does the lens correction consider the crop factor of the camera? I mean the vignetting correction should be softener on a 1,6 crop/40d as on a fullformat/5d For my sigma 10-20, the only profile is canon@sigma 10-20, but no clue for which body. wb