Compiled EXE and installer w/ DAQ card?

I created a specialized data logging VI and compiled the application.  I also created an installer so I could install it on another computer.  I included runtime and DaqMX w/ the installer.  When I installed it on the other computer, in MAX I can see the daq card, but in the program all the inputs from the card show up as zeros.  Is there something I'm doing wrong?  Should I be using MAX tasks and scales instead of project tasks and scales?

Hi Zorro,
There should be no problem in using the tasks and scales that you originally saved in your project.  Do you have multiple DAQ boards in this system, such that the board you are intending to use now has a different device name in MAX?  For example, the card could now be displayed in MAX as Dev2 when you originally programmed it with a device name of Dev1.  Also, if you open up test panels within MAX for your device do you still get 0V readings on all of the input channels in question?
Regards,
Andrew W
National Instruments

Similar Messages

  • Generating a tri state waveform pattern and writing into DAQ card

    Hi,
    I am using LV8.0 and NI-6259 DAQ card.
    I want to generate a waveform pattern which initially goes to +5v and goes to 0v and then again goes to -5v
    and finally goes to 0v. 
    I have used the waveform pattern generator and have generated 4 kinds of waveform with some particular samples
    and I will be appending all the 4 waveform patterns(+5, 0, -5, 0) and the appended waveform will be written into DAQ card.
    The problem is:
        When I probe CRO at the Analog output pin of the DAQ card, the pin level will be always at +5v and sometimes
        it goes to 0 and back to +5v. But I am expecting a waveform with 3 voltage levels i.e.., +5( some 100 samples), 0v(for some 1000 samples.
        -5v(same as +5v) and 0v( 2000 samples). 
    How to get this kind of waveforms in NI-6259 DAQ(M Series) card.
    Please find the attached VI which I have created.
    Letme know the loophole in the VI and correct way of generating a tristate waveform.
    Thanx in advance, 
     Yogesh
    Attachments:
    PWM_sample.vi ‏43 KB

    Hello YogeshaYS,
    Thanks for your post!
    I see that you are wanting to output a waveform that goes from 5 to 0 to -5 and then back to 0. It looks like from your code that you want to do this in a continuous fashion? If this is so you will need a while loop to output the waveform. Take a look at one of our shipping examples that shows how to do analog output waveform. Go to Help >> Find Examples. When here go to Hardware Input and Output >>  DAQmx >> Voltage >> Cont Gen Voltage Wfm-Int Clk.vi. Your VI works great but it only does the output once so that may be why you see some interesting results on your output. Let me know if any of this information helps you with your program. I was able to run it in a continuous mode and see the voltage levels go from 5 to 0 to -5 just like you were wanting. Have a great day YogeshaYS and please reply if you have any other questions on this. 
    Cheers!
    Corby_B
    http://www.ni.com/support 

  • Which type of ADC is used in M Series, S Series and C Series DAQ Cards?

    Hi
    I want to know which type of Analog to digital converters(ADC) are used in M Series and S Series DAQ Cards. I know that DSA Cards and some C series are using Delta Sigma ADC. What about the ADC used in non delta sigma C Series modules. Why Delta sigma ADC is not used in M series and S series DAQ cards.
    Regards
    Samuel J

    Hi Samuel.
    The ADC type used is Succesive Approximation ADC. You can refer to the following links for your reference.
    http://digital.ni.com/public.nsf/websearch/32FD9AA817D0EBE68625708C005E1B26?OpenDocument
    Hope this helps.
    Thank You.

  • I need to interface SCC-TC02 with help of SC 2345 and PCI-6024E DAQ Card.please tell me the procedure and if possible send me the program

    Dear Friends,
               I need to interface SCC-TC02 with help of SC 2345 and PCI-6024E DAQ Card.But i can not understand example program.please send me the procedure to interface these three componnets and if possible send me the program.
    With Regards,
    Eswaramoorthy K V

    nce of nth triggering pulse. i need to know when the when the ist trigger occurs and when the nth trigger occurs . please tell me how to to . what i know is that event triggering has to be done with start and stop trigger. please tell me how it has to doneSuresh;
    What you will need to do is to set up a digital start and stop triggered Analog Input acquisition. Then you will need to have a counter set as event counter, having the specific number of pulses you need configured as the preset value, configured to count down, and generating a pulse after the terminal count has been reached. That counter output will be the stop trigger of the Analog Input operation. In summary, you will have the external pulse being both the digital trigger of the Analog Input operation and the source pin of the counter, and the counter output being the digital stop signal for the analog input.
    I'm attaching a Labview VI that does the start and stop analog input acquisition. You will need to include the counter part and set the stop s
    ignal to be the counter output.
    Hope this helps.
    Filipe
    Attachments:
    AI_Start-Stop_D-Trig.zip ‏25 KB

  • Pre Build EXE and Installer Set Version

    So this topic comes up relatively often so I thought I'd make a new thread showing an example of how to make it work.  The problem is developers want a way to set the version of builds programmatically.  Luckily NI added some VIs for doing this.  Too bad you can't invoke them from the Pre-Build action of a build, because that information is read before the pre-build.  Here is an idea exchange discussing it.
    But I figured I could come with some kind of work around and I have two, and neither is perfect.  Attached is a simple project.  It contains a VI that runs reading the EXE version that it is running from once it is in an EXE.  The project has three build specifications, an EXE, and two installers.  The developer can set the Major, Minor, and Fix of the EXE, but the build version is set programmatically in the Pre-Build action.  The version of the installers will also be set to the version of the EXE.
    Attempt to build the EXE and a dialog will appear asking to enter the build version that should be used.  This could be determined some other way but this was the easiest for the demo.  If the EXE, and the Installers are already the correct version, where the build is the same as the one specified, and the installers are the same version as the EXE, then the build goes on like normal.  But if the build you enter is not the same as the current, it will abort the current build, change the versions, and then tell the operator to attempt to build again.  This time no prompt is seen and the build will work like normal with the version you set earlier.
    The downside to this method is you have to tell the developer to build again, I figured I could do that programmatically so I tried.  There is a constant on the BD of Prebuild Action VI.vi, and if it is set to True it will try to invoke a new build on its own.  The problem with this method is the build the user invoked is aborted and the user sees the error.  But the second build might have worked fine, but there isn't any feedback.
    In any case this is a sorta working way of setting EXE and Installer build versions from a pre-build VI.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.
    Attachments:
    Test EXE Version.zip ‏80 KB

    Bob_Schor wrote:
    I took your idea and "simplified" it a little
    Some may want the simplified version I understand.  But for me I wanted a more robust VI, one that would work if a project had multiple build specifications of applications, or multiple installers.  Some developers may have two applications one that is normal, and another with debugging turned on and I wanted the versioning to work consistently there by grabbing the newest version and using it.  And in all my cases, if there is an installer it should be the same version as the EXE.
    As for the getting around the error I think if I had enought time I could dig into the NI VIs to get rid of the error and show the progress of the new build.  The whole build process is a bunch of VIs, that augment the right click menus in the project so the source is there it is just taking time to understand it.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Simulation PID on control and design with DAQ card how to connection

    hi guys.. i am a beginner for LabVIEW 
    i have homework design PID on simulation path and i found by google
    how to connect simulation path to DAQ card ??
    anybody can help me
    which function to connect it???

    Duplicate Post

  • Difference between simple DAQ card and FPGA based DAQ card(like PCI 7831R)

    Could any one tell me, where should i use simple DAQ card and where should i use FPGA based DAQ card ? if i can take data acquisition from simple DAQ card then why we go to the FPGA based DAQ cards(like PCI 7831R) ?

    Hello,
    The choice of card depends on the application that you develop. For example, you’d better use FPGA if you need a perfect synchronization of several acquisition chains as FPGA matrix will adapt in the way that your channels will be separated and will no use common resources. Another example of FPGA application can be acquisition of several chains of the data that demands very high sampling frequency (FPGA internal frequency can be up to 400MHz).
    When using FPGA you have to program signal acquisition “from the beginning”, I mean that there are no standard tasks as, for example, “counting edges”. But due to this you can modify standard tasks of DAQ acquisition if you need it.

  • Controling heating/cooling element with labview and usb 6008 DAQ card

    Greetings All
    I'm looking for a heating/cooling type of element that I can control with labview and my usb-6008 card. Heating/Cooling will just be for clean water and the temperture range will be from 0 C to 100 degree C.
    Thanks
    The heating and cooling elements can be seperate products. Any recommendations

    A simple kettle element will of course be sufficient for upto 100°C
    To get the temperature down you need a cooling system, what springs readily to mind of course is a refrigerator.
    Just a note of warning, water and electricity are dangerous bed fellows.
    On that note perhaps one of those vortex air units would be safer - they blow hot in one direction and cold in the other, nominally to 100°C
    see: -
    http://www.airtxinternational.com/how_vortex_tubes_work.php

  • How do I syncronize and implement MANY DAQ cards?

    I need to acquire 30 channels of analog data at 400 kHz scan rate (all 30 channels is one scan. It would be preferable to convert all 30 cahannels simultaneously and stream data to disk for long data collection times. Signal conditioning such as integrators/sample and hold is an option to reduce the simultaneous sampling requirements.

    Do you already have DAQ boards or are you looking to purchase? If you already have the DAQ boards, you can synchronize them together by sharing the clock source between them. This can either be done externally or internally with a RTSI cable.
    If you are wondering what DAQ boards to use, there are several options.
    If you can drop your scan rate all the way down to 40 kHz, you can use one NI 6071 device to scan in all 30 channels. If you must sample every channel at at 400 kHz, you will need to use multiple DAQ boards, and possible multiple systems. With the 6070E board, you can sample 3 channels at 400 kHz, though you would need ten of these boards. Another option would be to go with a simultanious sampling boards. The NI 6110 has four analog inputs with a 5
    M/samples per channel rate. You would need several of these as well.
    Once you have the DAQ boards, you can synchonize them by having them all use the same scan clock. If the boards are in the same system. You can internally connect them using a RTSI cable. (up to five devices.) This way, you do not have to externally wire the clock. Since you will probably have to use multiple systems, you will need to use external wiring to connect the clock source to the multiple systems.
    Let me know if you have any questions about this.
    Brian

  • Why does my compiled exe ask for the location of subvis when installed on another computer?

    Hello,
    I have a piece of deployable software I have developed and so I have created two build specifications to produce an .exe file and an installer.
    The build specification for the installer includes the compiled exe and all of the required SubVIs to reside in a sub directory in the install directory and when it installs on another computer the SubVIs are located in the correct place.
    However, when I install and run it on another computer, a dialog box appears prompting for the location of the SubVIs, I select the one that it is asking for and it then loads the remaining VIs and runs as normal.
    Is there something fundamentally I'm missing in the way SubVIs are called after using an installer, or is there a way to bundle them into the .exe/installer so that I don't receive the dialog box?
    Many thanks in advance,
    Sam
    Certified LabVIEW Architect, Certified TestStand Developer
    NI Days (and A&DF): 2010, 2011, 2013, 2014
    NI Week: 2012, 2014
    Knowledgeable in all things Giant Tetris and WebSockets
    Solved!
    Go to Solution.

    Yes - but on my computer, I believe the exe is finding the files from the .exe build, rather than the installer location.
    In fact, I just renamed the default build directory (where it places the installer / exe after the build and I get the same dialog - it is looking in C:\LabVIEW Builds\etc.
    rather than...
    C:\Program Files\My Software\subvidirectory
    So maybe it is the problem you suggested Yamaeda? If so - is there a solution/workaround for this?
    Certified LabVIEW Architect, Certified TestStand Developer
    NI Days (and A&DF): 2010, 2011, 2013, 2014
    NI Week: 2012, 2014
    Knowledgeable in all things Giant Tetris and WebSockets

  • How to run VI without the DAQ card connected to the labtop

    This may be a silly question but I want to have the answer and couldn't find the answer for spending time in searching in the web.
    I want to run the VI that controls the intruments in my labtop. The VI was run in a destop that has a DAQ card in the PC (a PCI card).  I know it is possible to run it without errors (without a DAQ card) in my labtop . Anyone knows how to do it? I used labview 7.1. Thanks,
    Jun

    If you are using DAQmx and if the DAQ card is supported, you can add a simulated device in MAX.

  • How SCXI modules are multiplexed into one Channel of the DAQ card?

    Hi all,
    I am Sirisha from Hyderabad.
    I am a new to NI hardware.
    take the below mentioned senario.
    Suppose i am using SCXI-1000 chassis with SCXI-1520 and 3 SCXI-1102 modules and PCI-6070E DAQ card.
    now i know that if i connect the DAQ card to the SCXI chassis through sh-6868 cable and 1349 adapter, all channels of SCXI modules are multiplxed into the 0th channel of DAQ card.
    Here i want the detailed explanation of theory of multiplexion on how all the scxi channels go to 0th channel of DAQ card
    Thanks in advance
    regards
    Preetam

    Sirisha,
    Thank you for contacting National Instruments.
    Here is a KnowledgeBase article entitled "How Are SCXI Channels Multiplexed While Having Other Inputs On The DAQ Card?"
    There is a little more specific information about multiplexed mode here.
    Michael P
    National Instruments

  • IMAQ 1408 + DAQ cards crashing when loop iteration 1

    I have a problem trying to run some code which outputs a synchronised analog and digital pattern using the PCI-DIO-32HS and PCI-6713 DAQ cards which triggers an external analog camera. The images from the camera are then read via the IMAQ 1408 frame grabbing card.
    When I run the code once, it executes successfully every time. If, however, I select 'run continuously', or alternatively place a FOR-loop around the pattern output and image collection, the computer executes the pattern once, then completely freezes the computer, requiring a hard reboot of the computer.
    I have attempted to add wait times at various points through the code, however even if I place 10s delays in the loop (the pattern takes around 1s) the computer hangs and crashes. Running the code by repeatedly clicking 'run' however works every time, with no error or crashes.
    Is there any way to extract or trace the error causing this behaviour - the issue must be with the IMAQ drivers, however I cannot see what is different between running the VI manually 10 times in a row, and running it continuously with a wait to prevent it running at full speed. Any advice for debugging this error would be much appreciated. I have attached the code with subVIs necessary to reproduce the error.
    Attachments:
    JAI_Testing.zip ‏841 KB

    Hi Fan Wu,
    You're right that you only have two counters on your USB DAQ device. If we limit the problem to only one channel, then I would recommend using the counter because it sounds like you're creating a pulse train of known parameters. Since the counters use a fast timebase (if you're using Mseries you're using an 80MHz clock), you'll get very predictable performance at 1ms of interest.
    The other way to do this (since you'll need more channels) is to use a counter to setup a timing engine. A simple pulse train with 50% duty cycle and whatever frequency you're interested in (sounds like 1kHz) can be used as your DI/O timing clock. You can then create a digital waveform with the characteristics you are interested in and write that to your buffer. With your Digital task correlated to your counter output, you can output this waveform at the rate of your counter output.
    While this is NOT the end application you are looking to write, this example has some great parallels to what you are trying to do. It illustrates creating a clock with the counter and then writing a digital waveform to correlate to that clock.
    http://zone.ni.com/devzone/cda/epd/p/id/3687
    PBear
    NI RF

  • Installing labview before DAQ card?

    Hi,
    We've just bought LabView 8.2 and a new DAQ card, PCI 6281 M series...
    What I was wondering was whether there is any order in which these need to be installed. At the moment there is no pre-existing version of LabView or DAQ Software on the computer.
    I have just read that the drivers that came with the DAQ card need to be installed before the card is inserted into the PC, but am not sure if LabView is supposed to be installed before or after the card or if it even makes any difference.
    Thanks,
    Harry

    Thanks!!

  • DC Motor Controlling with ANSI C & DAQ Card

    Hello,
    I have 2 DC motors and a sensor. I have a NI Daq Card and i have a NI Connector board. I am trying to control DC motor with based on sensor values. Based on the conditions motors should move forward or backward. I am also using motor driver, i already connected my DAQ Card to computer and Connector block and i connected my motors to motor driver and my motor driver to connector block. And i also connected my sensor to connector board.
    I gave you a HIGH LOW example which is ritten in PIC BASIC. What i am trying to learn is how i will write in ANSI C and use with DAQ card. And with which function i can read the value of the sensor? Normally if i read port in PIC Basic i will easily read the value.
    I checked the DAQ CARD ANSI - C Examples but they aren't too clear. So this i just wanna ask someone who know this.
    And to show what i exactly mean, here are some code written in PIC BASIC
    INPUT PORTB.0                          ; Light Sensor
    OUTPUT PORTB.3                     ; Left Motor Forward
    OUTPUT PORTB.4                     ; Left Motor Backward
    OUTPUT PORTB.5                     ; Right Motor Forward
    OUTPUT PORTB.6                     ; Right Motor Backward
    ; to make code easy to read we are defining symbols for our ports:
    SYMBOL             LSENSOR                 PORTB.0
    SYMBOL             LMOTORF                 PORTB.3
    SYMBOL             LMOTORB                 PORTB.4
    SYMBOL             RMOTORF                 PORTB.5
    SYMBOL             RMOTORB                 PORTB.6
    Our functions:
    TURN_RIGHT_FORWARD:
    HIGH   RMOTORF
    LOW   RMOTORB
    LOW   LMOTORB
    LOW   LMOTORF
    TURN_LEFT_FORWARD:
    HIGH   LMOTORF
    LOW   RMOTORB
    LOW   LMOTORB
    LOW   RMOTORF
    GO_STRAIGHT_FORWARD:
    HIGH   LMOTORF
    HIGH   RMOTORF
    LOW   LMOTORB
    LOW   RMOTORB
    GO_STRAIGHT_BACKWARD:
    HIGH   LMOTORB
    HIGH   RMOTORB
    LOW   LMOTORF
    LOW   RMOTORF

    Hey there,
    I noticed that you have posted here (http://forums.ni.com/ni/board/message?board.id=250&message.id=31497) and got some answers
    Might be worth sticking to that forum.
    AdamB
    Applications Engineering Team Leader | National Instruments | UK & Ireland

Maybe you are looking for