LAVA 1.0 Content

QUOTE (PaulG. @ Jun 1 2009, 06:16 PM) Is it a http://forums.lavag.org/Variant-To-Control-file89.html' target="_blank">typedef? Ton

Submitted to NI, please Kudo! Ton

NI has setup a web site where you can submit ideas, I think it is a good idea to develop an idea here and then submit the idea to the NI site, so we can all vote on it. Use the mass of LAVA to provide NI with valuable feedback! Perhaps an Idea of the month/quarter contest is a good form? Ton

QUOTE (David Wisti @ May 30 2009, 05:04 PM) Well legal and supported are two very different things... I think we still will see the occasional crash when we 'script'. Shouldn't we come up with a better name than script? Meta-Programming for instance? Ton

QUOTE (Aristos Queue @ May 30 2009, 01:25 AM) Yes I can understand, but now if I look at my RSS reader, it is quite annoying. Strange how such little things distract you. QUOTE (Aristos Queue @ May 30 2009, 04:04 AM) Opening up the project integration to just two non-NI groups has produced maintenance headaches. There is no interest at all from the NI side in maintaining binary compatibility of project plugins across versions of LV. OK, what have JKI and Endevo (I assume you mean those two) done? Ton

QUOTE (Michael Aivaliotis @ May 29 2009, 05:28 PM) I second that! Dany

QUOTE (Aristos Queue @ May 29 2009, 06:50 PM) OK AQ the guidelines of LAVA clearly state that 'CAPS ONLY' is forbidden, for once we let it pass through. Now it is so wonderful, every Q ever asked can be replied with 'scripting will help you', 'let the LabVIEW API guide you', 'You could write a script that writes the code you need'. Ton

Stay tuned. Ton

Hi all, I think that it is quite unclear on how to start a new thread for novice users. This should be made more easier (consider how Stackoverflow directly let you ask a question, or how twitter only asks you to specify the message to broadcast). On LAVA you have to hit the 'Forums' button and then select the forum to post into, followed by the quite small 'Post a new thread' option), even I find this cumbersome. The reason I bring this up is the following: Two days ago I receive a PM from a new member, asking some detailed question. I reply and say I consider this SPAM and advice him/here to post a 'new thread' on LAVA. The next day I receive another PM with 'new thread' as the title. Then my mind kicked in. I am online a lot of times, I have a lot of posts. My name might be one of the first links to hit, followed by the 'PM me' function. So I think new members 'just don't get it'. Maybe an 'Ask a question' or 'Start new Thread' next to the Guidelines is a good way. Ton

There is difference where DAQmx gets the 'raw' data from, it should be mentioned in the help for that function. But the I16 output is not the raw data for an E device (it is different for an M device), to go from I16 to float you should get an array from the 'Device Scaling Coefficients' that returns per channel the polynomial components for conversion from I16 to engineering units. Ton

Maybe the following solution works for you? I can't test it right now, but I assume it should work. Ton

The solution is quite easy, you make a normal probe and display the current time when the probe is executed. The problem is that I think that probes are not time critical for the LabVIEW compiler and parallel processes might continue to run while the probe evaluates, so I would keep the probe as simple as possible. Ton

There are several options: INI-Files For this type I recommend the OpenG Variant Config tools, it allows you to easily read and write random data to a file in a human readible form XML-Files For this type I recommend the JKI XML Toolkit, it behaves like the OpenG Variant Config tools. Plain binary data You can use the binary read/write functions to store the data directly to disk, disadvantage is that if you change your datatype your files will be useless, and you cannot edit the data with an other editor There are other options as well, I usually use the OpenG or JKI routes. Ton

QUOTE (Neville D @ May 22 2009, 02:08 AM) Many thanks for all those who reply. My group mate have figured out what he needs.

QUOTE (ragu @ May 20 2009, 01:42 PM) It is part of the OpenG Array Toolkit, installable with VIPM Ton

QUOTE (oldskool @ May 19 2009, 04:04 PM) Is there any better method for it? any graphical help would be welcomed. many thanks.

QUOTE (Norm @ May 19 2009, 08:31 AM) At the link you provided. Ton

The property Top Left Visible Cell will deal with that. You define which cell is at the first position. Ton

If I wish to use array to store data & take the data out to be used?

Here is an 8.0 version (haven't tested it). The code looks messy but should be OK. Ton

It seems that this bug is resolved by Commit #758 by Dafemac, and is covered by Unit Test # 1:I am changing it's state to 'Closed' Ton

QUOTE (Norm @ May 15 2009, 10:16 PM) Does the data always start with the header? Is the header always the same size? If both answers are true your code is quite easy: Read the header and use that as the selector for a case structure, for every possible header you have a different case that reads the correct amount of bytes. QUOTE I do understand that to calculate the checksum, I've got to go (input) string to byte array and loop with an XOR to get the number. Not sure how to implement that solution, though. Microwave Dave posted some code, unfortunately it's in LV 8.6 (I'm using LV 8.0), which I don't have. I think there are several checksum VIs available, where is Microwave Dave's post? QUOTE BTW: This endgame for this code is logging visible satellites by time along with their c/no, az, el and satellite health. I'm thinking 32 individual .txt files would probably be the way to go. Each file can be imported into excel and sorted that way. Any ideas here? I'd like to log the data by day (0000-2400utc). I advise you to use TDMS or TDM data, this can be opened by excel with a plugin but makes sure that the data is correct, you will lose no significance data. QUOTE Offer of dinner: If you are local to Binghamton, NY (within 100 miles) I'll spring for dinner in exchange for being able to pick your brain about LV and writing code.. Maybe a donation to LAVA is a good idea to keep things running! Ton (or if you come to the Netherlands we could have dinner)

The only thing limited on the pushOK interface is that you always get a 'Action Succeeded Dialog' that you have to 'OK'. Besides PushOK there are other gateways, TamTam for $10 or another one for €70 whose name I can't remember, haven't tested them, I was pleased with PushOK enough. Remember you will need a full-blown client (like Tortoise) for tagging and branching. Ton

I would advise you to use the OpenG lvzip toolkit it features an installer and is tested on all LabVIEW development OS's and targets. It includes compressing and decompressing, listing and many other features linked to zip functionality. Ton

QUOTE (Mark Yedinak @ May 15 2009, 10:25 AM) Many thanks.