crossrulz

I'm for the smaller icon personally. Since this VI is called "Clear Specific Error.vi", it should really be "Error Cleared?". For the error array VIs, would it make more sense for this indicator to be an array so the user can figure out which error was cleared?

I just updated my second implementation from above to add a check for an empty array being passed in. So now all errors will be cleared if the array is empty (which is currently the default). Is this a desired feature to clear all errors? Clear error.vi

I've had two versions of the array type. My first attempt uses a for loop. It has the added benefit/feature of inputting an empty array will remove all errors. My second attempt uses the Search 1D Array and check to see if the resulting index is greater than or equal to 0. This should be a little faster than comparing all of the array and OR the results. Similar to Shaun, I made the icons small so I can fit them between property nodes.

I fully understand what you are talking about. I put together something that I was not proud of at all, but I still passed this last month. I could have sworn I put the stupid little comments for "Covers Requirement" for each requirement, but I still lost points there. Anyways, congratulations and I hope to see you at the summit (assuming I'm allowed to go).

Converted to 8.6 Find Arrary Element Clicked On.vi

I recently took the CLA (on the 2nd of this month). My proctor did tell me they changed the format for the CLD in giving the front panel. That could have saved me a good 10-15 minutes back when I took it. For the CLA, I was given the sheet of requirements and a blank USB drive for submission. I thought the CLA was one of the hardest tests I've ever taken, mostly due to the 4 hour requirement. And for what it's worth, I got my results yesterday and I passed!

Kudo up this idea: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-Variant-constant-to-the-Cluster-Class-amp-Variant-function/idi-p/1083987

Hit the diagram cleanup and you'll see exactly what your problem is. It would help you if you changed the direction of the fb nodes (right click option).

Are you dealing with an Invoke Node or a Call Library Function Node? If it is a CLFN, then just double click on the node and there should be a dll location control.

Just open the VIs in LabVIEW 2010 and save. There is also the mass compile option for a little more hands free. You might want to make a backup first just in case.

The frequency domain is made up of positive and negative frequencies. If a signal is real, then X(f) = X(-f). It's just the way the math works. Now since we are dealing with a digital signal, the spectrum repeats every Fs (sampling frequency). So if Fs is 1000Hz, you will see the spectrum that was centered around DC repeat at 1000Hz. If the spectrum bandwidth is greater than the Nyquist rate (Fs/2), then these negative frequencies that I mentioned earlier will show up in the band you are looking at. This phenomenon is called aliasing. So if you have a sine wave at 600Hz and Fs = 1000Hz, you will see a signal alias into the band at 400Hz (1000Hz + -600Hz). If you care about that 600Hz signal, then you need to up your sampling rate (and thereby increase your Nyquist rate). If you don't, filter it out before sampling.

1. That looks like the simulation toolkit is in use. 3. If you go "Tools->Advanced->Edit Palette Set..." there is a palette editor. This is the easiest way to edit the palette in LabVIEW. There is an option to "Place VI Contents". Or the better way would be to use VI Package Manager to create a reuse library. The palette editor in it is second to none IMHO.

Go to VI Properties, select "Window Appearance" from the drop down at the top of the window, click "Customize..." button. There's a checkbox there for "Show Run Continuously button".

Do you see this issue when the enum is not strictly typed (use Type Def instead of Strict Type Def)?

I've been studying up on this as well. My understanding is that for the CLA, you only code what is needed for the architecture. If the XControl is part of the architecture, then make it. If it isn't, don't worry about it. They aren't going to grade you on the use of fancy LV tools, but on the architecture you create and documenting of the requirements.

I'm not a VHDL programmer either. I know just enough to be able to read it...maybe. I just had to interface with other people's FPGAs and microcontrollers that are in the units I had to test. RS-232 was the bus of choice and it proved to work well.

There are FPGAs out there with built in UARTs (or at least an easy interface to one). Using this, I have communicated with FPGAs in our UUT (unit under test) using a simple RS-232 serial port. Other option I have personally done is RS-422. I'm not sure what kind of data rate you need, but these are simple to control (using VISA) and the hardware is cheap (RS-232 port often built into a motherboard).

To turn a FIFO into a LIFO, simply use the "Enqueue Element At Opposite End" instead of the "Enqueue Element".

I'm with DaveC. The simplest way to handle this is to set the drop down box to display in Hex. Then you don't have to worry about the conversions yourself. I would also recommend making a switch to go between ASCII and Hex display. I do this a lot when I have to deal with serial port displays.

I think you are going to need to post some code because I am not understanding your issue. Some code context could help.

What display setting do you have for the 40 constant? If it is in Hex mode, then 40 = @ which will make that VI return a 0. If it is in normal mode, then I don't see anything wrong.

I've been down that road too many times. When it comes to serial communication, you need to separate your GUI code from the serial communication (specifically the reading). The simplest way is to use a producer/consumer architecture. If you have questions about how it works, then I'll be more than happy to answer them. But from what I've seen, you are not going to get where you want to go with your current architecture.

I few years ago, I took someone's c code for AES and turned it into a dll using CVI. I then made wrappers to go around the dll. I we were using AES256, but I think the dll will work with AES128. The arrays are byte arrays. AES.zip

Do you want the ASCII characters '2', '3', '.', and '3' (0x3233 2E33) or do you want the computer language (0x4037 4CCC CCCC CCCD)?

Seems to me like you are going to have to make a counter in software. The brute force way is to throw the input data into a for loop and look for transitions (go above and/or below threshold levels).