LAVA 1.0 Content

i've just started learning labview. Im currently using v8.5 & im trying to place the result into the array but i do not know how i should go about doing it. does anyone have any labview example regarding placing the result into the array? graphical help or website link would be very much appreciated.

QUOTE (scls19fr @ May 5 2009, 10:00 PM) Functionally there isn't a difference between those two. A reference gives the property node the power to operate on different controls, with this method you can place the code inside a sub-vi and call it several times for different controls. Ton

QUOTE (Gary Rubin @ May 4 2009, 09:26 PM) I am suspicious about the array building as well. I haven't looked at the LV2 code, but I don't think that a queue using to store all data and read that as a burst using 'Flush Queue' is standard procedure. To be totally fair I wouldn't include the 'Destroy Queue' in the timing, one other thing is that preset the size of the LV2 global, something you didn't do for the Queue. You only have an overflow flag to detect the slow 'dequeuing' of data. There are some little things allready taken care for in the queue solution that isn't available in the LV2 global, like prevention of getting old data. Ton

The 'File Dialog' express VI has an input called pattern (all files) setting this to *.csv will default the files with an extension of csv. By using this input and the accompanying pattern label you can mimick your own filetypes. For instance you could set pattern label to Measurement files. If you have a path control you can set the browse options to achieve the same effect. However I advise you not to use text based files for Excel, either write directly to excel via the ActiveX interface, or save your data as TDMS and use the Excel TDMS plugin to open the file. This will prevent errors from localization. Ton

I have stumbled upon such thing recently as well, I think the following is the reason: Since all the analysis VIs are placed inside pass-word protected LVLIB's it isn't possible to do a save-as, such a thing would alter the lvlib, the only thing I was able to do is a copy and paste of the code inside a semi-locked VI. I am not sure if this is intended but a 'Save As (and export from lvlib)' functionality would be nice. Ton

Hi everyone, I have just made a new post at the WTI Guy blog entitled 'What is the Best Software Development Method?" QUOTE Read More Regards, Todd VanGilder

The best thing to do would be to send this Vi to your local NI office and ask them to down convert to what ever version you would like to

Hi, I had some free time and just edited your vi (without considering any of the style) and messed it up a little more but i think it will work as intended... Do not use this VI unless and until u clean it up properly.

QUOTE (jdunham @ Apr 29 2009, 08:58 AM) Quick example with mouse over text color change. http://lavag.org/old_files/post-3370-1241026080.vi'>Download File:post-3370-1241026080.vi

FOr the .x, you should change the formatting of the scale to %d. You can change the position of the minimum and maximum by clicking on the outside of the maximum of the scale. To rotate the scale click on the outside of the minimum. To change the size of the needle, I think you have to copy the needle to word, edit the size and copy it back. But I am not sure, I would check this on a dummy control. Ton

And there is an on line list But it helps to explore something via trial and error. Ton

Off course there is the 'Mouse Down' event. Ton

QUOTE (xShadowDanx @ Apr 29 2009, 03:11 AM) Somehow I couldn't download the file, could you upload it to LAVA directly? Ton

QUOTE (candidus @ Apr 28 2009, 12:59 PM) OpenG has a generic solution based on ocurrences as well: Wait (ms) is the name of the code, here is the underlying snippet: Ton

All of the comparison primitives can operate on arrays. The numeric to boolean array primitive makes a bitwise change from numeric to boolean. However in most languages (and LabVIEW alike) a boolean false is a u8 with value 0. To convert such an array to a boolean array use the <>0 primitive: Ton

I have two ideas: Make some data dependency between the tasks, starting the output tasks after you have started the clock task. Let the analog output task generate the clock, and let the analog clock be used for the the digital output. Set the start trigger of the digital task to be the analog start. Then first start the digital task and then start the analog task. Ton

I would try to set the 'Append to file' to true. What is the value that you measured on the graph? Currently the value is 25 m. One advice, I wouldn't use a spreadsheet string format, especially because you loose precision and the decimal sign might change. Ton

One additional warning, don't store settings in the LabVIEW temp folder, on my computer this one gets flushed every reboot. Ton

Why don't you download the file with a temporary filename and then delete the original and rename the temporary file? This is how firefox handles these kind of stuff, they just add a .part to the filename. Ton

QUOTE (Black Pearl @ Apr 14 2009, 09:16 AM) It is good to define access here. I think you mean a physical access via TCP/IP. You can close a SVN repository for any kind of anonymous access, or make the anonymous (or unknown) clients read-only. Clients/Users can be password protected Ton

XControls behave almost like normal controls, you have properties, methods. One of the things missing are custom events. What I mean is a way to trigger a specific event for a specific XControl instance for which an owning VI can register in a normal event structure without adding special code to that VI beside the Event case. This technique would be awesome, especially in alarm XControls. You can see how such events work for Graphs where there are special events for Scales et al. Any thoughts? Ton

Or you could add an undocumented feature/backdoor, where a special key-combo openend the BD. Ton

Attached are my low level LabVIEW VIs for HTTP GET and HTTP POST. Download File:post-3370-1239397633.vi Download File:post-3370-1239397638.vi

QUOTE (normandinf @ Apr 9 2009, 09:06 PM) B states that it is the average of ALL measurements, which is incorrect, since it will only be the average of the last four measurements. An average of all measurements is a weighted running average which is different than this example. During the first three iterations of the loop it will be a weighted average of the initial measurement and the next i+1 measurements.

QUOTE (menghuihantang @ Apr 9 2009, 08:39 PM) I'm not sure who a lot of people are, but C is correct.