Ton Plomp

It depends on the DAQ, most DAQs have a measuring rang of +-5 or +-10 Volts, but are protected against higher voltages. You'll need to detect those higher voltages and act upon. Another option could be adding signal conditioning that has higher damage criteria (we use dewetron, those go up to 3 kV. Ton

In reverse order my opinion: Mercurial API (developed by me) is an API to the mercurial command line interface, and does not handle merging or diffing, if you have set up diff properly, then the diff-vi will work. LVMergeHG Looks promising, however I have not used it Mercurial LabVIEW integration, works good for diffs and is very valuable if you want to see what changed in a file for a given changeset! I'm working on a Project integration for Mercurial, however the LabVIEW provider for SCC is not the most stable. Ton

The trick is shown in the example: \general\dynamicevents.llb\dynamically register for events.vi. Ton

We recently sent data in TDMS format to another party (sort of competition), and we decided not to mention the dataformat, jus sent the files. Later I spoke one of there developers, and and I figured out they were using Matlab were able to open the files without any issue. Ton

There's one catch, if both values are the same then greater than and smaller than aren't congruent. However I don't really understand the algorithn, though I think that the while loop should never run more than 2 times. Ton

The first flaw I could find is the following: Resolving this doesn't fix the issue though. What's strange is that if both of these tests are false, the while loop is stale, nother really happens and all values are constant resulting in an endless loop. How is 20 mod 0 defined by Knuth? Here you calculate q* and r*. But if I enter 20 mod 0 into my windows calculator it states 'operation undefind'. So the result depends on your compiler, LabVIEW returns 20 for the remainder and 0 for quotient. (sounds valid). Ton

These tools look good (the location in the Data palette is good.) One small glitch: One of the functions has a 'LabVIEW Object' input while the others have 'Object' Ton

If you are going for using a version control system (VCS) as a deployment server I would advise Mercurial or Git (distributed VCS or DVCS). You would setup a deployment server that only the author of the tool has write access. The author would setup a development server for his hour-to-hour checkins/commits (Save early, save often). When a release is ready you'd push the changes to the deployment server.* On the end user's side the toolkit is installed with 'hg clone http://mercurial-deployment-rep'. Periodically, you can use 'hg incoming', if there are incoming changesets you'd use 'hg pull -u' so that the working copy (visible files) are updated. If you setup the deployment server as a HTTP-server you can also allow the server to have a zip/tar as a single download of the current state of the project (so the client doesn't need Mercurial installed). Now for user engagement a DVCS is particular practical, the end user would pick up bugs and improvements and save them. If they want them to be fixed on the deployment server, they would commit them to there local repo, and publish them somehow (via http, file) to the developer. The developer would look at the changes and accept them (or not). That is a superb way to have your users committed. Such services are provided by commercial hosters like Bitbucket of Github) Ton *If you don't want your users to know the history between the releases you could setup the rebase extension, that pushes the different changesets as a singel changeset.

Hello Randy, you're more than welcome to participate with OpenG. Currently Jonathaon Green is the lead developer of OpenG, so you can send him a direct message if you want some 'tasks'. For instance you could have a look at the bugs posted at sourceforge, and see if you can tackle them (I advise you to take a SF account in the process as well). Another way to participate is to go over the proposals in the OpenG forum, and give your opinion, try to find weak spots or improvements. If you have code you feel is general enough you can add that to the proposal forums as well! Ton

There should be some Terms and Conditions for uploading, however that won't solve the issue. One way is to use the Code Capture Tool for your uploads and customize the header, and the embedded meta data to include some sort of copyright/licensing. Yes, I know it's not easy to see the embedded meta-data, but that doesn't mean it doesn't exist and isn't valid. There are special fields for copyright and disclaimers. Ton

I think that th OpenG sourcebase at sourceforge has the utilities you look for. Most likely this folder. Ton

Yep, the Instance close? filter event is the right one. If you don't close withing N seconds, the user will be shown a 'This app is not responding, end now?' function. What was the reason you didn't directly looked for this event? For future references, here's a snippet of the event. Ton

Recently I realized that I'm starting to use the conditional for loop more and more as an 'Error' catcher. I try to come up with the number of possible resolvers for an error situation, and run these in a for-loop, as soon as any of these resolvers, resolved the issue, I exit the for loop. One example is found in LVDIFF2, where Mercurial outputs mixed paths (using / and \ as path separators), in for different states I try to fix this path: Use a standard string to path function Use a function to read a linux path (only / separators) Use a function to replace / with \ (works on Windows) Use a function to replace \ with / (works on Linux/Mac) After each iteration I check to see if the created path actually exists, and exit the loop if the path is found. If the path is not found at all the code will fail, but at least we tried the best we could. Here's a snippet (with screenshots) of that section: Is anybody else using the conditional for loop in such a way? Other alternatives could be using an array and auto-indexing to limit the number of iterations of the for loop. Ton

Hello MrMike, sorry to hear that it's confusing you. I can understand how that happenend. Currently I am resaving the library for LV2009, and I'll look at your comments and incorporate them in the code. Ton