Ton Plomp

Featured sounds like 'studied and selected' (perhaps paid?), but it looks like it incorperates the last addition. Is that correct? Ton

Name: Variant Probe Submitter: Ton Plomp Submitted: 03 Jul 2009 File Updated: 24 Aug 2012 Category: Custom Probes LabVIEW Version: 2011 License Type: BSD (Most common) Variant Probe V2.4.1 Copyright © 2012, Ton Plomp All rights reserved. Author: Ton Plomp tcplomp@gmail.com Distribution: This code was downloaded from: http://lavag.org/index.php?app=downloads&showfile=19 Description: A custom probe to put on a variant. It will create a tree based on the variant data, and populate the tree with the data, the attributes of the variant will be shown as well. The datatype description will determine the color of the tree items. Historical data is available as well. Version 2.0 introduces a Variant Tree XControl which can be used in any project. Located under the user.lib palette, it gives great flexibility to the programmer. The programmer has the possibility to give the end user permissions for the following actions: -Reset This will reset the whole tree contents -Traverse Variant Attributes This will enable/disable the traversion of variant attributes -Colorize This will enable/disable coloring of the actual datatype All of these customizations are available as properties/methods for the actual XControl as well, or you access them (while the owning VI is in edit mode) via the short cut menu. Installation method 1: Install the OGP file using VIPM (www.jkisoft.com/vipm) and you have a custom VariantProbe and xcontrol To use it add a probe to a variant datatype or to an array of variants. It can pause if the data changes, and will notify you if a change happens. Dependencies: The following OpenG packages should be installed: oglib_string>=2.6 oglib_lvdata>=2.8 oglib_comparison>=2.3 oglib_error>=2.0 Known issues: Is slow on large variants. Support: If you have any problems with this code or want to suggest features: http://lavag.org/index.php?showtopic=10269 Version History: 2.4.1: Fixed issue #132: An array inside another array crashes the probe/XControl 2.4: Immediate updating after changing of attributes Rebuild in LabVIEW 2011 2.3: Fixed a bug that caused attributes not to be traversed on certain data-types 2.2: Fixed a relinking bug 2.1: Fixes a bug where unnamed cluster elements where used (http://lavag.org/topic/10269-discuss-variantprobe/page__view__findpost__p__67677) 2.0: Added an XControl Show XControl in palette (under user.lib controls) Add coloring Add 'user permissions' on XControl Add Reset on XControl Add optionally traversing attributes on XControl Add optionally colorizing on XControl Add optionally restting on XControl 1.2.0: Upgraded to LabVIEW 8.5 to use inheritance Support for Waveforms, timestamps and dynamic datatypes (thanks to Osvaldo) Added probe for an array of Variants Distributed as one .llb and added OGP installer If a Variant hasn't changed it's not decomposed (optimization) 1.1.0: Support for attributes of variants 1.0.1: Controls placed on a seperate pane Resize tree to upper pane Hide unused columns Limited maximum history length (default 10) Window resizable 1.0.0: Initial release of the code. License: This code is distributed under the BSD License Copyright © 2012, Ton Plomp All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the Ton Plomp nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Click here to download this file

You could set a 'time-out' for the event. When an eventstructure is activated and an event gets handled, the data includes the moment of the event, you could discard the event (eg. no processing) if the time is more than n seconds ago. That way you could relatively fast empty the queue. Ton

You'll need a pressure transducer, these normally output a 4-20 mA current (4 mA = 0 Bar, 20 mA = 12 Bar) and are fed using a 24 V power supply, you can interface these with a current measurement device, or a resistor with a voltage measuremernt device. For the pressure controlling you'll need a pump that can be controller by a 5V inpute or via a relays. Then you'll need some code to run a controller. And that is LabVIEW related. Ton

Not as far as I know, for each event structure there are two queues: One with GUI events, and one with dynamic events (which cover user events). When the event structure is activated, it looks at both queues and picks the event with the lowest tick count. That is the single place where the order of events might not be the actual order of events (since WIndows uses a 16 ms. tick count). Ton

Yes. I posted a spinning mercurial logo (gif) to the Mercurial mailing list and got two very prompt responses, one of them was from Matt Mackal (main developer Mercurial) explicitly (but polite) telling that to use the logo you have to license it under a GPLv2+ license or have a written license from him that allows you to create a deriviative. The logo is posted here. I explicitly asked him if I was calling the Mercurial command line only, then there is no need for a GPLv2 license and he acknowledged that. I've read up a little bit on the GPLv2 and it's not that hard of a license, and if you create an executable (thus stripping the icon of the VI) you should be able to use a more general license. The nice thing of the GPLv2 is that it's in the spirit of OpenSource software, it enforces the next-generation of your source-code to be open source as well. Ton

That's a bug in the original version of the framework provided by National Instruments for Icon replacements.

One thing to remember is that Mercurial itself is licensed as GPLv2+, this license includes the Mercurial logo. If you are just calling the Mercurial command line interface you don't need to use the GPLv2+ license. Ton

I am working on an interface in the LabVIEW Project window (NI calls them Providers), as a set-top of my Mercurial API. I am working on the details, but the NI system is quite tricky! Is the code for the full merge available somewhere so I could have a look? Ton

Could you make your question a little bit more clear? I don't really understand what you mean with XML and automation. And how this matches with front panel configuration. Ton

What is an Array? (see next) Shaun's answer provides the number of visible elements for an Array control. However you could get the 'Value' of the array control, that would return a Variant with the OpenG function Array Size(s) the actual size of the data stored in the control: Ton

I appreciate how you are open about this! And I can understand how it's viable to keep your standards high (and pure) for the LVTools Network. Regarding OpenG: As a community member I cannot guarantee that there always will be an appropriate response within 2 days, some of the packages are more obscure than the others. However I think there is a possiblity to use the SourceForge's issue tracker. We should be able to set that issue tracker up in a way, that when an issue (bug/feature request/support request) is raised a certain group (yes, those are volunteers) get a direct notice (email) about the issue. And beyond that there is no better promise than any other (commercial) party can make, but I guess that there is some sort of complaint from a customer that could revoke the Gold status of any package (commercial or community supported). One thing that might 'scare' people is the public nature of these discussions. However I believe in an open communication about bugs etc. But that should be stated clearly at the LVTN page. Regarding other community supported packages that might want to go LVTN: I think it's not possible to keep the community active to keep these packages supported. It needs commitment, if I look at the Code Capture Tool, I sometimes don't have the inspiration to respond to a question (and sometimes I just lack time). However if I look at the community supported packages that I use (Mantis, Mercurial) I have noticed that the response time is very short. For instance a question on the Mercurial Mailing list results in a very fast (and correct) answer by the main developer. It will be though for us to get the same standards running. Regards, Ton

Oh, I misunderstood! I thought it was a delete button with a weird icon... Ton

I found a bug in version 1.5.0: When removing a state, the last state is removed, and not the selected state: <object id="scPlayer" class="embeddedObject" width="922" height="516" type="application/x-shockwave-flash" data="http://content.screencast.com/users/TonPlomp/folders/Jing/media/71859c08-f387-4c6b-a9ea-0523d139aa15/jingswfplayer.swf" > <param name="movie" value="http://content.screencast.com/users/TonPlomp/folders/Jing/media/71859c08-f387-4c6b-a9ea-0523d139aa15/jingswfplayer.swf" /> <param name="quality" value="high" /> <param name="bgcolor" value="#FFFFFF" /> <param name="flashVars" value="thumb=http://content.screencast.com/users/TonPlomp/folders/Jing/media/71859c08-f387-4c6b-a9ea-0523d139aa15/FirstFrame.jpg&containerwidth=922&containerheight=516&content=http://content.screencast.com/users/TonPlomp/folders/Jing/media/71859c08-f387-4c6b-a9ea-0523d139aa15/JKI%20StateEditor%201.5.0%20bug..swf&blurover=false" /> <param name="allowFullScreen" value="true" /> <param name="scale" value="showall" /> <param name="allowScriptAccess" value="always" /> <param name="base" value="http://content.screencast.com/users/TonPlomp/folders/Jing/media/71859c08-f387-4c6b-a9ea-0523d139aa15/" /> Unable to display content. Adobe Flash is required.</object> Regards, Ton

FP.Resizable = False: Ton

I know that the Infrared Laser FELIX at Rijnhuizen is operated by LabVIEW. I guess a lot of the experiments in the Physical world are controlled by LabVIEW in cooperation with Matlab. Ton

Name: Mercurial API Submitter: Ton Plomp Submitted: 08 Jan 2011 File Updated: 25 Aug 2012 Category: *Uncertified* LabVIEW Version: 2011 License Type: GNU Public An API for the Mercurial command line interface (hg), includes all the basic commandos: Add Archive Backout Branch Clone Commit Diff Forget Init Log paths Push Pull Remove Rename Revert Status Tag The API provides an interface to communicate with a Mercurial Repository.This API is not meant as a integrated Mercurial provider in LabVIEW. Installation is performed by VIPM, after which a palette is created in the user.lib palette. You can access the sourcecode of this API at Bitbucket. Licensed under GPLv2, since it creates a derivative on the Mercurial icon. © Matt Mackall Copyright © 2012 Ton Plomp This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. Click here to download this file

Sometime ago (LV 8.6?) LabVIEW stopped supporting inter-application communication, meaning that you cannot share Queues, Notifiers between them. I assume that extends to events as well. Norm Kirchner wrote a framework called LvX that could be used for those cases. I have never used it, but you can try it out, it is hosted somewhere on LAVA Ton