crossrulz

You have a data dependency between your two loops. Combine the loops into a single loop. You can have a counter keep track of your time to state when to toggle your LED.

Do you have an example of your text file you can share? Do you have any code to show what you have tried?

The answers should be in the back of the sample exam. If you have questions on why those are the answers, ask those.

Do a search in the LabVIEW Example (Help->Find Examples) for Digital Output. You should find plenty of examples of how to control some digital IO.

cross post

You will want to create some digital output tasks to control some of the DIO. Use the DIO to control your relays. You will very likely need a buffer circuit to supply enough current to control the relays.

Anymore, I doubt it. When the In Place Element Structure was first made, it would tell the compiler to do things in place (no data copies). I believe the compiler has gotten a lot smarter since, so there likely isn't any difference anymore.

It really depends on who did the presentation for when or if it will be posted. At least we have Mark's videos for some.

I've been told that it is retroactive. If you doubt it, send an email to certification@ni.com to get your expiration date.

If you want to make sure, then open a VI in the project and go to the VI Properties. In the List Unsaved Changes dialog it will tell you what version the file was last saved in.

Yeah, that is definitely a database situation. TDMS is not good for this. Look to the SQLite solution you were given before.

TDMS is setup for waveform data. For what you are referring to, you need an actual database, not TDMS.

As I said, I always copy the LabVIEW.ini file whenever I have a fresh install. This will copy all of your settings, including the quick drop shortcuts.

The best way would be to turn your plugins into packages with VIPM. I just keep a copy of my plugins in a central network location and copy them over to whichever versions they are compatible with. Are you talking about the plugins that you can make with scripting or shortcuts to quickly drop functions from the palettes? Those shortcuts are in your LabVIEW.ini file, which I always copy over when I make a fresh install.

Look in the Signal Processing->Signal Generation palette. There is a Gaussian White Noise.vi in there that will give you noise with a bell curve distribution. Now go to the Mathematics->Probability & Statistics palette. There is a Histogram.vi in there that can create your distribution. Make a graph from the output and you are done.

It's like I started a trend! I begged for the CPI course to be with the Summit last year. It does make sense to allow CLAs to take the course right after the Summit. Makes sure you have good people teaching and it saves the CLA travel time. Good to hear from you again, Dave. Hopefully I will see you at the Summit.

Back when I was asking about the CPI, it was pretty much NI wanted you to go through their 2 day course. Mine was a Thursday/Friday after the CLA Summit last year (which made it a lot easier to justify going down). The NI course was really good and they go through a lot of the "here's how things work" when it comes to how classes are scheduled and all of that. I would highly recommend just taking the CPI course.

You have the event setup to freeze the front panel to until the event completes. This is the default setting. So what happens is if you are not regularly checking for events with the event structure, the panel will freeze once you hit that button. Once the state machine comes back to the idle state, it should call the event structure, react to the event, and go running again. The simple solution to this is to disable and gray out the button. Use a property node to set the Disabled state. Use the "Enable" and the "Disable and Gray Out" options. So after the button is pressed, you disable the button. When you go back to the idle state, you reenable it.

Almost all of the plugins I used with RCF are also available with Quick Drop. I haven't used RCF since 2011 came out. NI did something with that release that messed up the RCF and JKI has no intentions what-so-ever to keep RCF up to date. I was told by a couple of them that they only made it to force NI to release scripting.

How I have used TestStand is more of a sequencer. We want to set the power supply, so that is a step in TestStand. We then want to measure the voltage with a DMM. That is another step. And we go along like that. It makes test developement really easy. For drivers and low level stuff, we use LabVIEW. So a lot of your LabVIEW code can still be used. You are just invoking them via TestStand instead of calling them in LabVIEW.

This is sounding strictly like a display format issue on the numeric indicator. Right-click on the indicator and choose "Display Format". You can also get to this via "Properties" and finding the Display Format tab. I recommend going into the Advanced editing mode and put in "%04d". This will require the display to have at least 4 digits, filling on the left 0s.

I finally started really using LabVIEW 2013 and have repeatedly ran into a problem with the CCT. I load the CCT and create a snippet. The snippet is successfully created. However, then the tool starts to save the 271 CCT VIs. It seems to pause at VI 258 and then closes. With previous LabVIEW versions it would save the VIs the first time exiting the tool. But 2013 is always trying to save the VIs. Windows 7 64-bit (in case that matters at all).

Been there. I make a RCF Plugin to do that very thing for me. I haven't ported it over to QD yet.

And here I thought I was bad about trying to align things up between cases. Looks like I'm just normal and everybody else I have worked with are just sloppy.

I think you mean Wait (ms) for OpenG DOES NOT come up, but the primitive Wait (ms) DOES. Here's the conversation on the dark side that caused Darren to look into this:http://forums.ni.com/t5/LabVIEW/Duplicate-Quick-Drop-Item-Names/m-p/2521400#M766275