SMB triger input in LabView program

Hello!
I have PXI-8187 controller instaled in PXI-1031 and two PXI-4071 digital multimeters. I want to trigger mesurement with external trigger. One way is to used AUX port on DMM, another can be TRIG input on PXI 8187 CPU unit. Is possible to use this trigger input in LabView 7.1? How - example?
Best regards!

See the reply to this question here:
http://forums.ni.com/ni/board/message?board.id=270​&message.id=1558#M1558
Thanks!
Molly K.
Web Support & Operations Manager
National Instruments

Similar Messages

  • How to use SMB trigger input on PXI-8187 in LabView

    Hello!
    I have PXI-8187 controller instaled in PXI-1031 and two PXI-4071 digital multimeters. I want to trigger mesurement with external trigger. One way is to used AUX port on DMM, another can be TRIG input on PXI 8187 CPU unit. Is possible to use this possibility in LabView 7? How?
    Best regards!

    There are multiple reasons why this is not a supported feature for triggering under Windows and why NI does not recommend using the controller's SMB connector for this purpose. National Instruments has hardware that was designed specifically for extremely accurate clock generation, synchronization, and triggering between PXI chassis (PXI-665x) and other recommended alternatives listed below.
    Non-deterministic propagation delays
    1. The controller's SMB input is not guaranteed to have a defined propagation delay to the backplane. This means the SMB trigger on the Windows PXI controller is useless for customers that want deterministic triggering. Unlike our PXI-665x boards which have a maintained API and precise triggering properties, the PXI controller's SMB connector and routing circuitry is intended for Watchdog use under LabVIEW RT and isn't designed for this use case. A trigger propagating through the SMB circuitry and going to the backplane, or vice-versa, could have a great deal of variance in the propagation delay which makes gathering useful triggers impossible. This propagation delay is not something National Instruments specs.
    An excellent available workaround: Use the measurement hardware's trigger inputs
    2. The triggering inputs on our measurement hardware (that customers likely have in their system) can route triggering signals to the PXI backplane (usually through PFI lines) with deterministic results. This functionality is fully supported in most of our APIs and will be maintained between generations of devices.
    NOT backward or forward compatible
    3. The SMB input is NOT guaranteed to be compatible between different versions of our PXI controllers under Windows. The hardware properties along with an excellent workaround are the reason we do not support doing routing of triggers through the SMB connector on our PXI family of embedded controllers under Windows. If you are still interested in the beta software despite the shortcomings, visit www.ni.com/support and submit an e-mail request.
    Adam Ullrich
    PXI/VXI Product Support Engineer
    National Instruments

  • Does LabView program behave differentl​y under Traditiona​l Chinese version from regular English version. The program reads in numbers and characters from input files.

    Does LabView program behave differently under Traditional Chinese version from regular English version. The program reads in numbers and characters from input files.

    Hope this helps,
    Ankita

  • How do I use directional PDA buttons in LabVIEW programs?

    Hi all,
    I've been assigned to get a LabVIEW program to work on a Palm PDA with LabVIEW 7.0 and palm PDA module 7.0.  I am basically totally new to LabVIEW, and my possibly very simple problem is, the PC program requires input from a serially connected number pad for the 8, 4, 5, 6, and 2 keys which are used as four directions (8, 4, 6, and 2) and an enter (5). 
    I am trying to rewrite the input vi to use the directional buttons and middle enter button on the PDA itself but am having trouble figuring out what to use.  I am using a PDA simulator because of the PALM OS5 we own.  The input demo vi example provided will not build for PDA because of size so I am unsure of how to approach this.  Another thing is, we have LabVIEW and PDA module for pocket PC 8.0, and a Dell Axim PDA on order.  From what I understand off of this website, the latest PDA module has example button vi's.  I would still like to figure out the way to do this on 7.0 so I can have a better understanding of LabVIEW.  Eventually the program's endgoal is to be used on a PDA and inputting with a bluetooth keyboard, but we are going step by step right now.
    I guess my biggest questions are, how do I assign the directional buttons on the PDA in my program, and will this differ greatly when we switch to 8.0 and pocketPC.
    Oh and I did try to look at the example asteroid.vi but from looking at the input subvi, still couldn't figure out how they assigned the buttons.
    Thanks,
    Stephen

    I can't help with any specifics (no access to the PDA module at the moment and I didn't use the buttons anyway), but I would like to say that it probably would make a big difference if you used LV 8. 7.0 was the first version of the PDA module and was extemely limited and problematic (it didn't even have a tab control). 7.1 was somewhat better and I understand that 8 is even better (although still very limited and buggy).
    I also remember reading about several differences between Palm and PocketPC and I think you will generally be better off with the PocketPC as it's related to windows and will probably support more stuff.
    Try to take over the world!

  • How do I make a labVIEW program for a linear CCD camera?

    Hi, I'm pretty new at LabVIEW and I'm having a hard time figuring out how to connect my linear CCD image sensor (Toshiba TCD1304AP) with my computer. I know I need a DAQ device, what would work best for this particular CCD? After I got that connected, I need to create a LabVIEW program that displays the light detected by my CCD. Does anyone have a similar program or template I can use as a model? Any help would be appreciated. Thanks.

    Hello,
    I'm not sure the type of signal that is generated as an input to a DAQ device. This could either be an analog or digital input. The signal type will determine how you make your program in LabVIEW. You will also need to correlate the signal level to the light detected. That will be determined by your sensor. I don't have any programs or templates for this, but if you look at the basic analog or digital input examples, you might get a good starting point for DAQ device programming.
    -Zach
    Certified LabVIEW Developer

  • Is SilverLight compulsory for running a Labview program?

    Hi,
    I am using a computer on which Silverlight isn't installed (the microprocessor doesn't have SSE instructions so I am not able to install it). While installing Labview 11 I got a message saying SilverLight isn't installed. I will test my labview program tomorrow (recording analog inputs with a Labjack U6 unit (usb connexion)).
    Could anyone tell me if in this particular use of Labview (recording analog inputs + savind data to a file) SilverLight is compulsory? 
    If needed, here is the computer :
    http://robosavvy.com/store/product_info.php?currency=EUR&cPath=39&products_id=1704
    Thansk a lot
    User
    Solved!
    Go to Solution.

    What OS version are you using on this? 512MB for anything better but XP Embedded sounds really very short!
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Labview Program will hang between 33% and 50% of the time.

    I have a problem with a Labview program I made. I have two programs that do the same thing. One is in flat sequence form and the other is in state machine form.
    As explained in the link below, I would like to make use of a microcontroller to make wiring connections for automating a measurement process. A separate current source and volt meter will be used.
    https://forums.ni.com/t5/LabVIEW/Sequence-a-good-idea/td-p/2601333
    I have since made some simple test programs which I have attached. The problem is when executing, the labview program will hang, but not every time the program is execute.
    For example: Hall 1.2.vi will work properly twice with the third time it is executed it will hang. If you abort and try again, it will again run twice with no problems with the third hanging. This one is in flat sequence format (was in a flat sequence, but merged the windows because I thought that was the cause). From what I can tell, the program will hang when calling Keithley 6517 Single Read.vi. Both connected Keithley devices are connected to the computer via GPIB at 16 and 27. The way I verified if it was this vi causing it or contributing to it was that I removed it and the program never hung. I find it very strange that it will hang exactly on the third attempt every time.
    Hall 1.3 simple.vi will work the first time and hang the second time. So it works 50% of the time. This one is in State Machine format. This one will hang at the case titled "Measure 1" which contains the Keithley 6517 Single Read.vi.
    I've used the highlight execution button and watched the program run. Oddly, it doesn't hang when using this button. So I tried adding delays/wait in different places to no avail.
    What could be causing this? As a side note, I say the program hangs for two reason. The main one is the program doesn't finish running so the run arrow is still black. The second thing is that if you notice at the end of the labview program, I have a block there that turns the current source off which doesn't happen when it hangs. I have to manually turn it off and then hit the abort program button to stop labview.
    Solved!
    Go to Solution.
    Attachments:
    Hall 1.2.vi ‏42 KB
    Hall 1.3 simple.vi ‏81 KB

    altenbach wrote:
    SaintsFan wrote:
    Also, I've tried placing wait/delays at various places with no improvement of the problem. My next thought is to just remove all the vi calls and have everything in one program.
    How did you place the waits?
    Why would placing everything in one program fix the problem. That makes no sense! What is your reasoning?
    In the case of hall1.3, I placed a wait in the Measurement cases and CS On cases and there was no affect. In the hall 1.2 when the blocks were broken up similar to the state machine cases where each sequence window was identical to the cases, I placed a wait or delay in each window with no effect on the hanging.
    My reasoning for placing everything in one program is the same as my reasoning for figuring delays would help, since the time of execution would be altered. If the execution time is faster and if the timing is the problem then I figured that the problem would happen more frequently or even every time.
    Somehow I get the feeling this is not the case. The reason being the interval in which it succeeds or hangs is constant. I believe somewhere, a value is getting set. The 6517 Read vi runs fine if I run this vi by itself no matter how many or how fast I run it. Also, the same goes for both 1.2 and 1.3 if I remove the 6517 read vi they run fine no matter how fast or how many times I run them. 
    Somehow after the current source is set to operate and triggers labview will hang on a set interval when calling 6517 read vi.
    Separately they work, together there is a problem. I tried placing a delay between these two by connecting the error out of the trigger vi to the error in of the delay block and the error out of the delay block to the error in terminal of the 6517 config block. I've also tried delays between other blocks connected the same way. From what I understand, a called vi can't execute until all inputs are present. Is this the correct way to wire the delays?

  • Connecting hardware(c​onnected to myDAQ) to my labview program

    Hi,
    I have a labview program that will send an email (Gmail) when you click the " Button " in the program but 
    i need to modify it so that when i press a switch button at my hardware(connected to myDAQ)  the email will be sent ; meaning to replace the " Button " with my hardware 's switch button.
    Consulted with my lecturer and she says something like inputing logic 1 into the mydaq/labview to run the process.
    I have attached my program below.
    Any help is greatly appreciated!
    *I'm using NI LabVIEW 2013 SP1 (32-bit)
    P.S : i know this is the 2nd thread i created but i'm not sure how to close that one(i have already selected a solution) 
    Attachments:
    Basic Sending email program.vi ‏341 KB

    In order to use your signal input instead of your button, you need to read in the signal as a boolean. Digital inputs are already in the form of booleans (just like how your digital outs are set up), but if you are pulling in the trigger through your analog inputs, you'll just have to add some threshold logic to convert from an analog value to a boolean.
    If you have digital inputs, just set it up the same way you have that DAQ Assistant in there already reading in analog inputs and wire the boolean trigger to the same case structure as your button.
    Your teacher probably means channel 1 is your trigger input when she says "logic 1". This just means if you're pulling in multiple channels, that you use channel 1 as your trigger (which is actually the second channel becauce indices in LabVIEW are base zero).
    Actually, after thinking about it, maybe your teacher is pointing out that you need to add logic to read in a value of 1 as True? This makes me think you're reading an analog input as your trigger and you need to use logic so that a value of 1 is True.
    James
    LabVIEW Professional 2014

  • How to document LabVIEW program?

    Is there any guidance for how to document a LabVIEW
    program?

    The LabView Style Guide has a chapter on documentation. Click here.
    Here are some of the things I try to do on every VI.
    Create VI Help info: on the VI's File menu, select VI Properties >> Category >> Documentation, then add you help info into the VI Description. That's what will be shown when the user shows the context help (Ctrl-H).
    Front Panel:
    Create help info for each control: right-click on the control, then select Description and Tip. The Description will be shown when the user shows the context help. The Tip will be shown (as a Tool Tip) when the user moves the mouse pointer over the control, even if context help is not shown.
    Make control Labels descriptive. Numeric, Numeric 2, Boolean, etc. are not descriptive enough to be helpful to the user.
    Use the control captions if needed.
    Use the text tool to add free labels to the front panel if needed.
    Diagram:
    Show the label for each structure (while loop, for loop, case, sequence, etc.). Not just a free label: right-click on the border of the structure and select Visible Items >> Label. This way the label is attached to the structure and will move with the structure as you're editing the diagram. Make the label descriptive. For loops, summarize what you're doing. For while loop, state when the loop will stop. For For loops, if auto-index is used, state which input will set the number of loops. For cases, describe the criteria for selecting a case.
    Within a case or sequence structure, use the text tool to add a free label inside each case or sequence frame to summarize what happens there.
    Show labels for all control terminals. Some controls may not have their labels displayed on the front panel (e.g. buttons with their boolean text shown), but always display the label on the diagram.
    Liberally use free labels to add more comments.
    VI History:
    Use it! On any VI window, from the Tools menu (the tools palette), select Options, the select Revision History from the pull-down listbox. Select Prompt for comment when VI is saved. Whenever the VI is saved, add a brief but meaningful comment about what was changed. This history is available under the VI Properties >> Category >> Revision History >> Show Current Revision History (or by pressing Ctrl-Y). It can be very helpful in debugging a program that stopped working after you made a bunch of changes.
    Icons:
    Create helpful (not just artistic) icons. I typically just use text to show an abbreviated VI name. Graphical icons can be helpful if it's clear to the user what the graphics mean. But I like text. I put my creativity into the program, not into a tiny picture trying to describe the VIs function to the user.
    I'm glad you asked the question. The more work you put into your documentation now, the easier it will be for you or anyone else to use and maintain your programs.

  • Labview programing problem

    Hi, i have problem with my labview programing which in associate with cRio-9025
    which also doing the data acquisition of temperature.
    below is my programing, pls help me to check on it, see error 
    did i made.
    Apprecite it, thanks
    Attachments:
    asas.png ‏435 KB

    Hi, as Apok has mentioned, if you click on the run arrow it will come up with a list of errors and some explanation.
    on a quick look though;
    you have an error on the TDMS file open block - the operation constant is shown with a otted line (and seems to be spelt incorrectly).
    only one input of the build array in the timed loop is connected
    the TDMS file out isn't wired in the case statement (TRUE case) in your while loop
    not necessarily an error, but the shift register storing erros isn't wired up in the input to the loop so will only pass through an error on the last iteration
    It's also not an error, but bad practise to use flat sequence structures to control program flow - you're better off using data flow to manage things if possible. You could leave the first flat sequence in place to initialise variables, wire the error cluster line to both loops and remove the other two flat sequences.
    Regards
    Paul
    Regards
    Paul
    CLD running LabVIEW 2012 32 & 64 bit on Windows 7 64 bit OS.

  • Password for labview program

    Hi all,
    I am developing a labview program for a high
    power microwave device. The final program will
    be running stand alone on a pc attached to the
    microwave device in a laboratory. To ensure
    safety, I am wondering if I can set up a password
    to the labview program at start up so only
    authorised people can use it? Or if there is
    other way to do that. Any comment will be
    greatly appreciated.
    Thanks.
    Regards
    Hank
    Sent via Deja.com
    http://www.deja.com/

    In article <[email protected]>,
    [email protected] wrote:
    > Hi all,
    >
    > I am developing a labview program for a high
    > power microwave device. The final program will
    > be running stand alone on a pc attached to the
    > microwave device in a laboratory. To ensure
    > safety, I am wondering if I can set up a password
    > to the labview program at start up so only
    > authorised people can use it? Or if there is
    > other way to do that. Any comment will be
    > greatly appreciated.
    >
    > Thanks.
    >
    > Regards
    >
    > Hank
    >
    > Sent via Deja.com
    > http://www.deja.com/
    I am pretty sure that you can do that by using a case loop outside of
    your main program. You can set it up so that user(s) will have to
    enter a string (which would be password) before he/she can get to the
    front panel of the main program.
    Within this vi, you can have an array of strings such that users can be
    given different passwords (or level of authority) for more security.
    After the user enters the password, you can compare the user input by
    using equal function in the comparison palette (make sure the password
    list is case sensitive or stuff like that or you'll have to convert all
    the user input string to either upper or lower case if you want to save
    some trouble). If the result of comparison is true, then they can get
    into the main program, or else the program will quit.
    You can also put in looping structure to make it more fancy such that
    each user can be given say 3 chances to enter the correct password...
    If you want to go really fancy, you could also try to put in a data
    file that stores all the passwords in binary format (requires a little
    conversion, of course) in a directory of the target machine that you
    know exist (say WINDOWS or WINNT), and include the data file as part of
    your instalation disk content, point the installation destination to
    that directory. In your password program, find the target machine
    operating system and then look for the file from there.
    Hope it helps. If you have any questions, please e-mail me at
    [email protected], and I'll try to e-mail you a copy of my code.
    Sent via Deja.com
    http://www.deja.com/

  • How to add PCI 7340 and UMI in my labview program from functions palette or how?

    Am using PCI 7340 and UMI7764 for motion control of a stepper motor.
    How to add the functions for PCI and UMI in my labVIEW program and how
    do I use these further? I need to control the direction of stepper
    motor rotation based on the pressure applied which we calculate as
    either clock.anti clockwise. So which function palette should I use for
    that.
    We use a darlington pair driver unit. ? The output
    from UMI are from the individual axis control whereas the driver input
    is through a serial bus. So what kind of cable should we use to connect
    the UMI with this and how do we connect this or should we use any other
    driver unit? Please explain in detail.
     Thank you

    Thank you I ll see to it

  • How do I get audio output from a labview program

    We are modifying an existing labview program that reads data from a BNC-2140 DSA and displays as a graph. We want to be able to stream audio in audible range instead of a graphical display. Is there a VI available that can create audio? If not, how can I go about creating one?
    Thank you

    Hey Lost-
    There is a wonderful document on our external website that groups our knowledge on using sound with LabVIEW.
    Under the LabVIEW Resource Library (http://zone.ni.com/libraries/) choose -> LabVIEW -> Advanced Programming Techniques -> Using Sound.
    This page lists over 5 examples for playing sounds with LabVIEW through WAV, MP3, and other formats. Streaming audio might be tough, depending on your processor. It might be hard to translate your input into a format LabVIEW can play. I am not sure what sound format that input data you refer to would be. This will be a good starting point. Also, I have heard of a Microsoft ActiveX control, DirectShow, that might help you. I have not worked with this guy, but I would check into it at Microsoft's site -> www.msdn.
    microsoft.com.
    Post again if you have follow-up questions.
    ben schulte
    national instruments

  • Comment out some sections of Labview programs during debuging

    In other programming such as VC or VB, we can always comment out some sections of our program so that the commented section are not executed during debuging. Is there any way to comment out some sections of Labview program during debugging?

    YanWong wrote:
    You can use a case structure to surround the section of the program you do not want to execute and then wire a false constant into the input so the case will never execute.
    Also remember that doing this will only work if the code you "commenting" out must be executable. A broken run arrow will still be there after you put it in the Case Structure. If you are trying to comment out some broken code, you're out of luck, at least now.
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • Convert Agilent 34972A command to labview program

    Hi,
    I'm using labview to remote control Agilent 34972A. 
    i need to read from one channel at a higher frequency,and write the result in a file. I think the following command would do that, but I couldn't make it work in labview program.
    CONF:RES  70000,1(@101)
    ROUTCAN(@101)
    TRIG:COUN 1000
    INIT
    FETC
    I attached the program that I'm using right now to get data from different channels with lower frequency.
    Thanks.
    Attachments:
    VI.jpg ‏190 KB

    It was suggested at http://forums.ni.com/t5/Signal-Conditioning/readin​g-from-one-channel-without-mechanical-opening-and-​... that you use the monitor function but I guess you didn't read that or bother to try.

Maybe you are looking for