Those options work with array indexes.
Set your array index to the first element you want to copy and then do the "start Selection".
Set the index to one more than the last element you want to select. and do end selection.
Data operations copy data.
If "show Selection" is enabled you will see the selected data.
It will copy to the clipboard and you can paste it into another LV control if you want.
Ben
I don't have the Xilinx IP Datasheet.
I don't know what the Xilinx IP Node is. The Functions pallet has a Xilinx IP with a bunch of blocks in a sub-menu.
The particular block that I am trying to use is the Xilinx RAM-based Shift Register v12.0.
Thank you, you totally enlightened me out.
My Host -- PC. My Remote -- PXI running LabVIEW RT on PharLap OS. The two machines each have a NIC dedictated to the Network Stream traffic, and are connected by a standard Cat5 Ethernet cable.
While my "needs" are for four independent Network Streams, I could easily add more. If you follow my suggestion and write a "tiny" test routine, putting in the Network Streams you are trying to set up, and attach your Test VI, we could (probably) point out ways you could "make it work". If you have the same URL on multiple Streams, you are doing it wrong (and hence your code doesn't work).
Bob Schor
I have the opportunity to take the on site training for TestStand applications but it is easiest to me to take the Online Training (I have access). The certification you got for the Online Training is as valuable as the on site training?
That is not much of a software design specification.
I suggest you buy an RFID reader that either uses a COM port or installs a virtual com port and plugs in USB.
Then use VISA to read and write to the RFID reader just like any other serial device.
That depends on two things:
1) Your agreement with the contractor: It is not uncommon that the contractor uses the license of the entity that wants a system to be developed.
2) If you ever intend to be able to look at the code yourself afterwards.
If you leave everything to the contractor including the whole source code you put yourself into a somewhat vulnerable position, especially if things should end up to not run smoothly. Even if your agreement guarantees you the rights on the source code this means nothing if you don't have a LabVIEW license to actually look at that source code and make changes or let another party make changes to it at a later stage.
And where did you get the so file from? The LabPython package was never released for other platforms than Windows so unless you compiled the .so file for the LabPython shared library yourself using the NI Eclipse toolchain for the cRIO systems, I don't think you have that at all. I definitely don't have it and I was the main developer of that package!
So what to do if I want to use labpython on myRIO. As my VI runs labpython in it.
Hello,
We are using a cDAQ-9174 with 2 TB-9212 and a NI-9220 input module. We are reading from 8 thermocouples and 5 pressure transducers. The program we are creating is for flow test in a wind tunnel and the various measurements taken go into calculations to find the airflow. There are 2 static pressure transducers, 1 total pressure, 1 barometric and 1 delta pressure transducer. The data records just fine up until the point the delta pressure reading goes to zero, at that point it "freezes" and no more data points are recorded. I'd greatly appreciate any feedback including my overall layout and design of the program, different methods to do something I have done or any other input as well. I've only used LabVIEW for a few weeks now and my coding skills are not very strong yet. I have posted a snippet of the program but if you want snippets of the sub-vi's feel free to let me know. Thanks for your help!
Justo
Thanks
@ GerdW,
As always the simplest solution is the best one, thank you for your help. Works perfectly fine, especially since my polynomial is fairly simple. Have a good one.
Pressure goes to the mathscript node as a variable pb.
What happens in there? Rho uses the value pb in the divisor. So it seems like you are getting a divide by zero error. Or if not an error, a very large number.
I don't see any loop in your code, so I don't know how you are running this. Attaching a VI rather than a screenshot snippet would help that way we can see the rest of the code and see what is happening in all those express VI's.
I should probably clarify my purpose for writing these VIs to begin with. We make The World's Finest (tm) electronic test systems for CCDs and IR FPAs (e.g. image sensing devices). All the hardware is of our own design, so there are no off-the-shelf VIs for them. We have developing our own software internally for 30+ years in C/C++, but we have a lot of customers asking if are "compatible with LabVIEW."
Of course we are. Everything is compatible (or can be made compatible). The good news is that the basic control of our instrumentation is via human-readable text commands, passed into and out of 3 separate DLLs, and the output of our instrumentation is a binary data file.
But they want examples. And we are committed by contract with one such customer to provide some rudimentary LabVIEW VIs to demonstrate basic functionality (which functionality is really up to me, since it isn't spelled out in the contract).
So I intend to offer up the following:
So that's a long way of saying that this VI doesn't need to be perfect, but I also don't want it to be embarrassingly amateur. We will also upload these to our website for all users, of widely-varying LV expertise, to use as tools to learn our hardware. That's why the debugging ability (send/pause/step) is so important.
But I also need the VIs to be architecturally simple, even at the expense of elegance, so that newbie LV users (like me 
) can understand and adapt them.
Anyway, that's a long way of saying, thanks!
Thanks guys for all the input.
The client has not come back on this project, yet. But I may have more questions later.
Cheers!
RayR
Dear friends,
I need some help here, I tried many ways, but I can not find out how to do it. Please help.
My target: 1st LED (in 1st state machine) Blinking all the time (never stop) with very slow speed(1000ms), 2nd LED(in 2nd state machine) will blink kinda slow (500ms) if 1st LED is off OR will blink kinda fast(50ms) if 1st LED is on.
Important notes:
1. I do need to KEEP those 2 state machine(SM). Especially, do NOT change the Enum of both SM. I am doing this for much much bigger project, in that project, there are 2 SM. That's why I make 2 SM in here. 2nd SM will be updated again and again (by T or F) from 1st SM (1st SM will give out T or F again and again to 2nd).
2. Both SM should be keep running all the time. In other words, 2 LED should be blinking all the time, just 2nd one with different blinking speed under condition of 1st one one or off.
Please check the attached VI. Could you please just modify this VI and upload it for me? I know it sounds I am asking solution for a homework. But this is not homework and I already spent almost 2 day on this 
The VI is ok to run, but 2nd LED will not be blinking in different speed, because the green wire cannot be updated until 1st LED stop (I do need both SM keep running).
Thank you so much for your time and kindness. Thank you.
Maybe this is a bug for IMAQ with USB Camera. I tried to put the open/configure/close.vi inside the while loop and found that the % is reduced to below 10%. But this is not a good solution as this will keep open/close the camera periodically. Besides, my cameras have initial warm up period which it will take few seconds to focus. For this open/close solution, i only able to grab blur images. I am wondering why this happens to USB cameras only. As my laptop also have an integrated camera but the CPU usage is ok if i run that integrated camera. Maybe i had miss install some drivers?
Search for Mean Pt by Pt.vi. It has an input to define the number of samples to average together.
For your initial question, you can get rid of the input of zero on the Index Array as it would start at the 0 index by default. But you can get rid of the index array completely if you change the tunnel from auto-indexing to "last value".
I ran into this problem today. One workaround, as suggested by Kun02, is to implement your own "Clear Chart" button and when that button changes to True, write an empty array to the chart history via a property node. Then the memory usage drops each time the "Clear Chart" button is pressed.
Doesn't keep the user from right clicking on the chart, selecting Clear Chart from the built in popup menu and using more memory though.
Seems like this should be an easy fix for NI to incorporate into LabVIEW.
Move that boolean and case structure inside the loop so that it can be read every iteration.
