Jump to content
News about the LabVIEW Wiki! Read more... ×

Ton Plomp

Members
  • Content Count

    1,991
  • Joined

  • Last visited

  • Days Won

    35

Everything posted by Ton Plomp

  1. I would like to offer my SHA-1, SHA-2 HMAC and AES files to OpenG to add to the MD5 library (I suppose we need to rename that palette). You can find these functions currently in the LAVA Code Repository. The code is currently in 2010, but I can backsave to 2009. Ton
  2. Ton Plomp

    [CR] Encryption

    Name: Encryption Submitter: Ton Plomp Submitted: 07 Sep 2011 Category: *Uncertified* LabVIEW Version: 2010 License Type: BSD (Most common) This package consist of a series of tools in native LabVIEW 2010 code. For encryption/decription the AES (Rijndael) routine is used with key sizes of 128, 192 and 256 bytes. The encryption supports the following block modes: EBC CBC CFB128 OFB For signing of string/packages it performs the SHA-1 and SHA-2 hashing, for MD5 hashing the OpenG functionality is used. The hash functions return a binary string and a hex-formatted string with the hash. The following hashes are supported: MD5 (via OpenG library) SHA1 SHA-2 224 bit SHA-2 256 bit SHA-2 384 bit SHA-2 512 bit For Hashed key authentication the HMAC functionality is provided based on the supported hash functions. The used functions are tested against NIST public test vectors. The use of these functions is not: secure the code does not try to protect it's memory nor the used keys. © Ton Plomp 2011 - No warranty implied. Click here to download this file
  3. RT @BraddJaffy: NYT reporter who broke Trump campaign/Russia story is same reporter who broke Clinton email server story. That's called a f…

  4. It would be nice if I could set the conditional disable settings in the build settings. This would allow for multiple build settings that could incorporate into a single project file. I have the feeling this can be done with separate lvproj files but that feels like a workaround. Any thoughts on this? Ton
  5. I have an app that needs to communicate via the CMD, I think that every call into the CMD is causing quite some overhead. Does anybody know how I can keep a CMD reference open and execute commands in it, and read the output? Ton
  6. 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
  7. Ton Plomp

    JSON LabVIEW

  8. Ton Plomp

    UI Tools

  9. Ton Plomp

    Abort VI

  10. Ton Plomp

    [LVTN] Code Capture Tool

    Name: Code Capture Tool Submitter: Ton Plomp Submitted: 03 Jul 2009 Category: LabVIEW Tools Network Certified LabVIEW Version: 2009License Type: BSD (Most common) The Code Capture tool allows you easily create screenshots of you LabVIEW code for use in documentation, web-sites, wikis, emails. This tool provides an API for creating images of LabVIEW code as well a GUI for easy capturing and use of code. Further info is provided in the help-screen (F1) of the program. For the latest version visit the Code Repository For the latest version of the source code, visit SourceForge For more info, visit the LabVIEW wiki with the documenation. A series of videos is available on screencast: Code Capture Tool Installation ============ To install the Code Capture Tool, run the 'Install Code Capture Tool.vi' in the LabVIEW version of your choice, or use the OGP file in conjunction with VIPM. A wizard will guide you through the installation procedure. Usage ============ After installing and restarting LabVIEW, you can open the Code Capture Tool via the 'Tools' menu to capture an image of the current VI. For more info open the About screen of the GUI. Uninstalling ============ To remove the Code Capture Tool from your LabVIEW installation remove the following files in your LabVIEW folder: Project\Code Capture Tool.vi user.lib\CCT.mnu And the following folder: user.lib\_Code Capture Tool In your LabVIEW data folder (in Windows, this is normally: My documents\LabVIEW Data) is a configuration file called Code Capture Tool.ini, which can be removed at any moment. However this file can be shared between mulitple versions of LabVIEW, I recommand you to use a special LabVIEW data folder for each LabVIEW version. Contact ============ Comments, bugs and thank yous can be expressed to the NI Forums community , and on the LAVA community at the CCT discussion thread. Click here to download this file
  11. Version 3.2.3

    12,205 downloads

    The Code Capture tool allows you easily create screenshots of you LabVIEW code for use in documentation, web-sites, wikis, emails. This tool provides an API for creating images of LabVIEW code as well a GUI for easy capturing and use of code. Further info is provided in the help-screen (F1) of the program. For the latest version visit the Code Repository For the latest version of the source code, visit SourceForge For more info, visit the LabVIEW wiki with the documenation. A series of videos is available on screencast: Code Capture Tool Installation ============ To install the Code Capture Tool, run the 'Install Code Capture Tool.vi' in the LabVIEW version of your choice, or use the OGP file in conjunction with VIPM. A wizard will guide you through the installation procedure. Usage ============ After installing and restarting LabVIEW, you can open the Code Capture Tool via the 'Tools' menu to capture an image of the current VI. For more info open the About screen of the GUI. Uninstalling ============ To remove the Code Capture Tool from your LabVIEW installation remove the following files in your LabVIEW folder: Project\Code Capture Tool.vi user.lib\CCT.mnu And the following folder: user.lib\_Code Capture Tool In your LabVIEW data folder (in Windows, this is normally: My documents\LabVIEW Data) is a configuration file called Code Capture Tool.ini, which can be removed at any moment. However this file can be shared between mulitple versions of LabVIEW, I recommand you to use a special LabVIEW data folder for each LabVIEW version. Contact ============ Comments, bugs and thank yous can be expressed to the NI Forums community , and on the LAVA community at the CCT discussion thread.
  12. RT @airtame: #AIRTAMEGiveAway contest - #LastChance- RT to win a free AIRTAME! 15 devices at stake! http://t.co/DXIpuW5Pad...

  13. Ton Plomp

    [LVTN] Code Capture Tool

    Sorry guys. I had a chat with JKI about this, and there is a fix available for VIPM, or the OGP that Yair posted. I'll see if I can get the version updated soon. Yes the move to New Zealand had been of quite an impact and I moved out of the LabVIEW world, moving to PLCs and SCADAs at an Aluminium Smelter. Working with different technologies has shown me the strengths of LabVIEW and weaknesses. However I can tell that the programming language LabVIEW is far superior to any of the PLC languages i've been working with so far. Cheers, Ton
  14. Name: Align and distribute Submitter: Ton Plomp Submitted: 05 Dec 2010 File Updated: 23 Jan 2011 Category: General LabVIEW Version: 2009 License Type: BSD (Most common) Align Distribute objects v1.2.0 Copyright © 2010, Ton Plomp All rights reserved. Author: Ton Plomp LAVA Name: Ton Plomp Contact Info: Contact via PM on lavag.org LabVIEW Versions: LabVIEW 2009 and up Dependencies: No dependencies, demo VI needs the OpenG time library Description: A set of VIs to align or distribute a set of points or objects, they behave similar to the align and distribute functions in the LabVIEW IDE. These tools are usefull when dealing with objects that needs to be rearranged. The set of VIs is bundled in one polymorphic VI (align_distribute.vi) that has the following tree layout -Align -Top -point -rectangle -Left -point -rectangle -Bottom -point -rectangle -Right -point -rectangle -Vertical center -point -rectangle -Horizontal center -point -rectangle -Vertical center -point -rectangle -Distribute -Top -Left -Bottom -Right -Vertical Centers -Vertical Gaps -Vertical Compress -Horizontal Centers -Horizontal Gaps -Horizontal Compress Installation and instructions: Use the VI whereever you want, or install it into your user.lib with VI Package manage (http://www.jki-soft.com/vipm) Examples: The zip-file includes one DemoVI that moves front panel controls around Known Issues: Acknowledgements: Icons are supplied by National Instruments in the LabVIEW IDE Version History: AlignDistribute - 1.2.0 (Released 2010-06-28) ============================================= - 0000021: [bug] The palette shows Align Distribute.vi as name. v1.1.0: Initial public release of the code. License: This code licensed under the BSD license ==============Start of license================== Copyright © 2010, 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: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. 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. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the . 4. Neither the name of the 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 ''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 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. ==============End of license================== Support: If you have any problems with this code or want to suggest features: please go to lavag.org and Navigate to LAVA > Resources > Code Repository (Certified) and search for the "Distribute objects" support page. Distribution: This code was downloaded from the LAVA Code Repository found at lavag.org Click here to download this file
  15. Hi All, I would like to announce the setup of a LAVAg group on Bitbucket. This will provide us with an easy-to-start collaboration platform. Any member of the group can create repositories for open source projects. The first repository in this group is the JSON LabVIEW API. My goal is to have a groups of repositories of code that are valuable to us all. By moving the repositories into a group it removes the link to a person on the code. Now the code is owned by the group and the value reflects on the LAVA community. If you want to join the group (or co-admin) drop me a message on LAVA or Bitbucket I hope this will give our company a boost in cooperation and code development! Have fun, Ton
  16. Ton Plomp

    completely new to LabView, need help with UDP

    Yes, you can just insert the JSON string into an UDP sent block. Have a look at the UDP examples (under help) how you could connect to another device via UDP. Without your code and/or error codes it's pretty hard to tell what' s going wrong. (first start, can you ping the device?) Ton
  17. Ton Plomp

    Programmatically Exit Without Save

    How do you open the VI? If you have a deamon application that connects to your LabVIEW via VI Server (I would give each LV instance it's own TCP/IP port), and then use the Open VI Reference node it should not display the dialogue per default. Ton
  18. Ton Plomp

    Allow only one instance of executable

    What version of LabVIEW are you using? Ton
  19. Ton Plomp

    Allow only one instance of executable

    Perhpaps you need the correct capitalization? Linux (in general) is capital aware while Windows is not. If I look at a windows LabVIEW.exe it has the following string somewhere in the binary file: allowMultipleInstances so you might need to CamelCase your INI key. I'd test: AllowMultipleInstances allowMultipleInstances And I'd test it with different spellings of False/false/FALSE Ton
  20. I think it is because the GrapChart also covers some 3d graphing objects: (source: http://zone.ni.com/reference/en-XX/help/371361K-01/lvprop/propmeth_class_hierarchy/) Ton
  21. Ton Plomp

    Crude On-Off Event

    How did you resolve it? I have a feeling you wanted controls instead of indicators.. Ton
  22. Ton Plomp

    [CR] JSON LabVIEW

    Here's a trimmed down version of the error (http://i.imgur.com/PY0Masp.png). The fix by james (1.1.3.21) fixes this issue However it's similar for Complex Singles and Complex Doubles. This is fixed in commit d966584f2b63 (not build yet). James: could you add Tag's after building the project? Last issue is with FXP's. I don't understand them well enough to have a good idea how to represent them in JSON... Ton Apparently if the first instance of an array is empty, something goes wrong. I haven't been able to pinpoint it. However the variant we return from 'From JSON' has the correct number of elements (see Variant out). I can understand a little bit how this happens. Finding a fix might be harder. Ton
  23. Ton Plomp

    Mercurial Central Repository Server Structure

    One of the issues you might run into is that you develop your libraries in production.I Would try to develop the libraries in separate projects that have a build result (vip or llb) that can be used in other projects. Active relative paths into the libraries source is a nono IMHO. Ton
  24. Ton Plomp

    Mercurial Central Repository Server Structure

    One of the issues you might run into is that you develop your libraries in production.I Would try to develop the libraries in separate projects that have a build result (vip or llb) that can be used in other projects. Active relative paths into the libraries source is a nono IMHO. Ton
×

Important Information

By using this site, you agree to our Terms of Use.