crossrulz

Pay does mean a little bit. The annual raise time is a good place to show how you appreciate your employees (a lack of raise will make people mad). The major things that I have at my current job that I didn't have in my previous job is a manager who actually stands up for me (ie doesn't arbitrarily yell at me because another manager/customer didn't like how I did something, even if it was exactly what was agreed upon) and flexibility (very similar to what Becky was saying). I can point to all kinds of things done wrong at my previous employer. Giving Engineering Excellence Awards to those do you did 90% of the job for and you get nothing; not giving promotions or even a decent raise after a laundry list of reasons why you should; writing up an employee for doing their actual job instead what another manager wanted them to do (which didn't follow procedures at all); changing design architectures in the middle of a project just because a higher up manager said to do it another way; giving all the credit to the person who refused to do anything the way they were told and then blamed you for their code not working; making rediculous schedules that everybody knows will never work but make you do it anyways, and then yell at you for not getting a 1 year project done in 1 month; asking you to do a job but not give you the tools/resources needed to accomplish that job...ok, I have said way too much. Good thing I'm not bitter at them.

Well, I am noticing you are not passing your TDMS File reference from the Open TDMS to the TDMS Write. The other thing to be aware of is where you put the file. I recommend giving this article a good read: http://www.ni.com/tutorial/14669/en/

Use VISA. DONE! Seriously! I took a project I did a couple of years ago that used GPIB for all instrument communications. Luckily I used the VISA drivers. Most of the instruments were changed to use Ethernet. The only part of my code that changed was the initialization.

Make an wire up the i to the right border of your FOR loop. It should default to an indexing tunnel. You can right click on that tunnel and select "conditional". I think it came out in LabVIEW 2012. Very useful tool.

That is different requirements from the Search 1D Array. If you want the all of the indecies that match, then still use the FOR loop, but use a conditional indexing output tunnel that is wired to the i terminal. Your condition should be if the current item matches the lookup item.

Use a FOR loop with a coniditional terminal. Autoindex in the search array. If the current item matches the search parameter, you stop your loop and pass out the data.

Bookmarks is the way to go for this.

There is the complex data type. sqrt(-1) is just i.

I've been told that NI is using the Separate From Compiled for any VI they develop. For Windows only projects, I have never had an issue (working in 2013 and 2014). We had a small hiccup when trying to use the same VI in a project on Windows and cRIO RT. Cleared the object cache once and it was fine again for the rest of the project.

I would also go the CVT route here. The API is really good and quite simple to use once it is set up. It allows for the application growth a lot more than using globals for a very small performance hit.

If computer A is hosting the NSV and it is not running, then B should get an error when it tries to read the variable. With an error, I would expect the default values. But it may be the last read value. But you should be able to look for the error.

cross post on the dark side: http://forums.ni.com/t5/LabVIEW/Matrix-Multiply-slower-on-RT-than-PC/m-p/3053426#U3053426

I do that all the time. Simple queue to send commands to the parallel process. Have some reasonable timeout, do whatever is needed in the timeout case. If a command comes in, do what is needed with that command. But there is usally some need for state. So sometimes a state machine works better. Based on your reading from the FPGA, the simple timeout for read will probably work just fine. And with your FPGA, play around with Dynamic FPGA References. You can take you main FPGA reference and cast it into a more specific reference. This way, you can pass into your subVI a very specific interface, making the code possibly reusable. It at least performs some decoupling.

cross post on the dark side: http://forums.ni.com/t5/LabVIEW/How-do-I-install-instrument-drivers-in-folders-other-than-inst/m-p/3036667#U3036667

The better solution would be to handle the value changes of those controls in the event structure.

The problem with locals is that they are only for inside of a single VI. If we are truely going wireless, the Global Variables are the way to go.

Duplicate thread in the NI forums: http://forums.ni.com/t5/LabVIEW/Is-the-compilation-done-differently-on-Linux-than-on-Windows/m-p/3000819#U3000819

Since you are talking about deterministic loops, they have to run at a certain rate. Therefore you will technically need a polling mechanism. What kind of data are you trying to transfer?

You have to have an NI DAQ card. Something like the USB-6009 would likely work for you.

The term "subVI" just screams that it is called by something. Would you rather call it "subroutine VI" (subVI for short )? I've never heard of there being a confusion with this term. I say educate those who are confused because by making up another term, you are going to just confuse the large majority who understand "subVI".

You must have edited the PNG file directly while leaving all of the header data alone. When I copied that snippet to a blank VI, that TRUE constant wired to the conditional terminal became a FALSE.

It was fun having her around. I'm glad to hear she had more fun than I thought. Yes, she must come next year.

Do you have some code you can share so we can see how you have your task setup? In general, a buffer overflow is cause simply by not reading the data fast enough while in a continuous acquisition or by setting the buffer size (which will always be less than the default buffer size).

Team up with Mark and do it. Just as long as you share your videos

Since it currently looks like I won't be there on Thursday, go for Fab's presentation on Unit Testing.