crossrulz

What do you consider "expensive"? For most of my test systems, by the time I put in certain upgrades, I have been quite consistant at $1500 with Super Logics.

There's a reason I always gave management an estimate that was 4x what I thought it would take. They would always cut an estimate in half trying to win the bidding war and then crap happens which causes things to take twice as long as you initially thought. Hey, I was right on budget! How did that happen?

Do you really have an application that needs that much optimazation? You likely have other issues if that is the case. Anyways, you can do that exact logic easily enough without the AND. Note: The FALSE case just has the FALSE value passed through.

It should NOT be enabled by default as of LabVIEW 2014. NI knows that is a security hole and has WebDav instead enabled.

Sounds like somebody make a new Shortcut Menu Plugin. A bunch of community made plugins were posted here, but I don't think I've seen a spell check one.

A solution was found in the cross post I linked to above. The solution was to use Unflatten From String

I actually got a couple of wrist wraps that had a pad built in. These helped a little bit. In the end, I found that the desks that I was using (mostly at a customer site) was the main issue. Been working from the office a lot more (which have musch better desks) and my wrists have not bothered me hardly at all for almost 2 years now. I haven't even used the wraps.

Sounds like you need a digital output. How much current do you need for this 5V output? You may need a relay to control the output voltage.

I also highly recommend Tom's book. It was well put together and even taught me a couple of things.

I'm moving my current projects to use 2015. Have not ran into any issues yet. As Brian stated earlier, NI has focused a lot of their energy on stability. So 2015 is practically 2014 SP2 (just with a couple of new features). If you are going to upgrade, I would just move up to current and then use the SP if/when it comes out.

cross-post on the NI Forums

Yep, ran into that issue as well. I had to take the cycle mean and subtract that from the waveform and then calculate the RMS. I wonder if I still have that code floating around here...

Something I learned on one project is that you want a whole number of cycles of your waveform when you do the RMS calculation. You could do a check for zero crossings to determine when a period ended. I ended up doing some math with the sample rate and the expected frequency of the waveform I was capturing to figure out how many samples to truncate before doing the RMS calculation.

1. The requirement tags are just free labels with the right text in them. You can also put them in the VI and control descriptions if you want. 2. I would just use a queue to send the error information to your error handling module. It is simple and quick to do. But I now have to put out a shameless plug: Certification Nugget: CLA

Here are a few news articles for you to look over. NI Helps Engineers Solve Big Data Challenges With New CompactDAQ Hardware and DIAdem 2015 Software NI Launches Next-Generation Control Systems Optimized for the Industrial Internet of Things (IIoT) Write Code Faster with LabVIEW 2015

I do this as well. But I take it one step further and have it all inside of a library. I then make the Action Engine and the enum controlling it private. This makes it so that the API is nothing but the wrapper VIs. It helps by keeping other people away from the AE and screwing something up. I can't wait to look at your code here. Sounds like something I could possibly use.

If the Application Font got changed, then everything will be a little different. I especially saw this happen when going from Windows XP to Windows 7. I haven't tried Window 8 yet, so I'm not sure if that would have changed there.

Matt Pollock (an NI SE) has a really good presentation of what is expected for the CLED. He is free with hints as well. I also failed my first attempt, but I also was unable to test my system due to the sbRIO going into a constant reboot mode. NI found a defect and is letting take the exam again for free. But my main takeaway from that experience was to keep things as simple as possible. Do not make this as you would a real life system. Use Network Published Shared Variables to send update information (tags). Do not make a complicated communication scheme. Don't even worry about getting all of the functionality in there. You only need about 70% of the functionality to pass. So get the simple points.

Ask in the NI forums. You are likely to get an AE to track it that way.

The Version Conversion Board over at the NI forums is the place to make this request. But I'm feeling generous here. Relax 3.26.2 R&S phase.vi

I've never heard of saying that a folder has X free space. It is always determined by the volume. But since your folder is pointing to a folder on the C drive, the Volume should be C:\ and it is telling you how much space is available on that disk. It is working perfectly.

Not as of LabVIEW 2014

Error code 7 is File Not Found. Maybe you should pass in the file path to be used instead of trusting what the Express VI is setup to do.

I would multiply by 10 and then wire the result directly into the case selector. You can then make ranges and proceed as needed in each case.

In general, that is correct. But always check the documentation to be sure. This last year we got bit by the Destroy Stream Endpoint (for Network Streams) not executing on an error.