Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/28/2009 in all areas

  1. Over on the dark side it is possible to see who gave kudos to a post. You can also view various statistics about who you have kudoed the most, who has kudoed you the most, etc. Is it possible to see this info on LAVA as well? I would like to at least be able to see who "voted up" a post. Since we don't allow "voting down" a post, there is no risk of hurt feelings when person A sees that person B (whom they have always admired) is willfully and wantonly voting down every post that they make. Not that that would happen here. -Toby
    3 points
  2. This page has the NI roadmap for OS support. Official Windows 7 support comes in March 2010.
    2 points
  3. If the application is ActiveX or .Net and has the ability to be used as container object (contrary to being an ActiveX/.Net Automation Interface which only provides a interface that can be accessed through Property/Method Nodes), then you can do it through the according container element in LabVIEW. Otherwise there is only an obscure possibility to make the main window of the process you want to embed a child window of the LabVIEW window. This requires in fact only a few Windows API calls, but this is a rather obscure way of doing business, there is typically no way to control the application in any way, starting up the application and embedding it into LabVIEW is an ugly process as the application will first startup as independant process through System Exec and then suddenly get forced into the LabVIEW Frontpanel, and last but not least, depending on non standard menu and window handling of such applcations it can result in strange visual artefacts or even inoperability of the (child) app. While it is theoretically possible, the most likely reaction you would get from your users doing this is a big: WTF!!!!!!!! Rolf Kalbermatter
    2 points
  4. Name: Insert Type Conversion RCF Plugin Submitter: François Normandin Submitted: 21 Jul 2009 File Updated: 03 Jan 2011 Category: JKI Right-Click Framework Plugins LabVIEW Version: 8.2 License Type: BSD (Most common) Insert Conversion Node RCF Plugin v1.2.0.7 Copyright © 2009-2010, François Normandin All rights reserved. *Plugin* Name=Insert TypeConversion Summary=Inserts a type conversion automatically Description=Will insert type conversion for all strings, numbers, paths, variants & enums to the right datatype. Copyright=Copyright © 2009-2010 François Normandin License=BSD Developer=François Normandin Version=1.2.0.3 *Plugin* Author:François Normandin Contact Info: Contact via PM on www.lavag.org LabVIEW Versions: Created and tested with LabVIEW 8.2 Tested with 8.6 and 2009. Dependencies: jki_tool_right_click_framework >= 1.0.2.208 oglib_array >= 3.0.0 oglib_lvdata >= 2.9 Description: This package contains a plugin for the Right-Click Framework of JKI. It consists of a first draft of a tool to automatically insert correct conversion node on a wire (or multiple wire at once). Includes: - Decimal String to Number. - Float String to Number. - Any numeric type (int, unint, floats, complex) to any numeric type. - Variant to string or numerics. - Numerics to Variant. - String to Variant. - Path to String. - String to Path. - Boolean to string. - Enum to String. - String to Enum. - Numeric to Enum. - Numeric to String - Unbundle cluster to terminal indicator. Instructions: After installing package with VIPM, restart the RCF framework. Use the right-click on wires to automatically insert a conversion node if needed. ** VIPM 2010 or higher is required to process this package. Known Issues: 1- Not all typecasts are implemented. 2- Wires with joints will not behave correctly yet. Acknowledgements: JKI for providing with this great framework. Change Log: v1.0.0: Initial release of the code. v1.0.2: Added _rcf_ in package name. v1.0.3: Changed the typecast name for proper "type conversion" name. v1.0.9: Added readme file into .vip file package + some VI documentation v1.1.0: Changed name of package from normandinf to lava (lava_lib_rcf_insert_typeconversion.vip) and added some type conversions (Boolean to string; Enum to String; String to Enum) v1.1.3: Fixed bug with conversion from Enum to Numerics. Added conversion from Numeric to Enum using "Variant to Data" node. Added a lame icon. (Any user suggestion will be considered for next update!) v1.1.4: Updated the description of plugin that now shows up to date info in RCF Options menu. v1.1.8: Fixed bug when a type conversion node was inserted in a structure where the node was inserted on the main diagram. Saved for LV 8.2 v1.1.11: Included all files in source distribution to make compatible with LabVIEW 2009. v1.2.0: Added Unbundle cluster to terminal and corrected problem with Numeric to String. v1.2.0.7: Added Singular to Array & Array to Singular. License: Distributed under the BSD license Support: If you have any problems with this code or want to suggest features: please go to www.lavag.org and Navigate to the discussion page. Distribution: This code was downloaded from the LAVA Code Repository found at www.lavag.org Click here to download this file
    1 point
  5. When I get a kudo on the dark side it means more to me when I see that it's from a LabVIEW Champion or a Proven Enthusiastic Zealot. It's not important, but it sure makes me feel nice.
    1 point
  6. I would recommend looking at the following excample: Noice Cancellation for ECG Signal by Notch Filter.vi You should be able to find them under menu "Help/Find Examples", then searching for "notch".
    1 point
  7. Jim, I encountered some issues with the latest version (I tried the LV 8.2 version): The delete method is not implemented (instead use this ) The code is initially broken because the property used in the timeout frame (in 8.2) has a different name than 8.6 (probably) The drag and drop does not work well (sometime it does, sometime frame are swapped [for instance the "exit" frame become the "Event Structure" frame) Suggestion for improvement: When you duplicate a state, you could pre-populate the new name with the old state name (or ,may be even better, use the prefix such as if the state is "Macro: Initialize" the new state pre-populate name is "Macro:") You may want to consider building the "parse state queue.vi" and "add state to queue.vi" in your llb for people attempting to use this on their own styled state machine. I noticed that you have no glyph for this plugin yet, so I quickly put one together. Feel free to use it (or not if you don't like it). Overall this is getting better and better! Keep up the good work! PJM
    1 point
  8. Hi jcarmody It works fine for me, thank you. There is a little thing about the vertical scroll. If you scroll down and then resize the window then you can't see the top cases! Another one. when I close the VI where I use the CaseSelector, hte CaseSelector window don't close! Is that the right behavior? Regards Bjarne
    1 point
  9. This is absolutely correct! Floating point is dirty I couldn't remember which side of the word the sign bit was on, so I used the rather helpful table here: http://steve.hollasch.net/cgindex/coding/ieeefloat.html I've never used the in-place structure (*gasp* ?), but converting your floating point to an integer is not a single operation (that I know of... maybe there's some crazy opcode for it). I was able to bang out something that did this with a few ANDs, an OR, a multiply (which is just a sign change, so could be replaced with an XOR and an increment), a few increments and a few shifts. Don't forget the extra floating point add of 0.5 to the beginning if you care about rounding (Also, I saved myself the headache of dealing with special numbers like NaN, denorm, etc that you might or might not have to consider) While technically this takes a 32bit number (single) and produces a 32 bit number (i32), there are so many intermediate values that I have no idea if it actually works "in place". It probably doesn't help that I have no feel for how well that structure works. Does it count if I only have one input and one output to my structure ? (And does it matter if I place constants on the inside or outside?) If this is of any interest (and the whole thing isn't broken by the additional N-1 pointer words) I'll happily clean this into something human readable Hugs, memoryleak
    1 point
  10. Ok, was just about to detail it all out, but head to http://eyesonvis.blogspot.com/2009/07/lvspeak-automating-vi-development.html and the newest info/details are on that there. and once that's done come back here w/ questions Thanks, Norm
    1 point
×
×
  • Create New...

Important Information

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