Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/24/2018 in all areas

  1. 11 points
    You know how you can change the wire appearance for a class in the class properties? As it turns out, LabVIEW internally allows for more flexibility than that dialog gives you. So I made an advanced wire editing tool...and unlike a lot of stuff I post, you can actually use this for serious projects, because it does not use any private/unsupported LabVIEW functionality! With this tool, you can set wire size without limits (with results similar to this), customize both wire layers with any 8x8 monochrome pattern, and also mess with different draw options. Strangely, a few of these settings seem to have no effect, and many of the options for one of them actually crash LabVIEW. (These ones are disabled in my tool, but you can re-enable them by editing a typedef.) Given that this is actually a documented, supported property that's officially supposed to work, I've reported this as a bug to NI; if any NI engineers see this and feel like investigating, you can refer to service request #7762024. Latest version: Wire Studio 2.zip Old versions: Revision 1
  2. 9 points
    Hey folks. this year we're trying something new. All Videos for NIWeek 2019 can be found here: https://labviewwiki.org/wiki/NIWeek_2019 Feedback welcome. Thanks to @Mark Balla and other volunteers for recording the videos. Edit: We're starting to add the back catalog to YouTube. NIWeek 2018 videos are also up.
  3. 7 points
    Greetings Friends of LAVA, colleagues, cohorts, and Wireworkers Extraordinaire -- it's LAVA BBQ time! Date: Tuesday, May 21, 2019 Time: 7:30-10:00 pm Location: Uncle Billy's Brewery and Smokehouse, 1530 Barton Springs Rd, Austin, TX 78704 (1.5 miles from Convention Center) Cost: $25 Early Bird (through April 30th) $30 Regular Admission (through May 20th) $35 Door Price (May 21st) Meal Options: Expect to enjoy your choice of meats (brisket, turkey, ribs) with sides like street corn, cole slaw, and bbq beans. A vegetarian option is available when purchasing tickets. Cash beer bar. Who: Everyone is welcome, including spouses traveling with you. Even if it's your first time, expect to recognize many faces/names from the forums and NI R&D. What to wear: It's a covered, outdoor venue in Austin during Spring, so dress for the weather and comfort. Door Prizes: We will have a drawing to give away prizes. All attendees are eligible and will receive a door prize ticket upon entry. See below about sponsoring a door prize yourself to share the love. Hope to see you there! Chime in once you buy tickets to let everyone know you're coming. ------------>>------------>> Get LAVA BBQ 2019 Tickets Here <<------------<<------------ The venue is a 30 minute walk from the convention center, or a $6 Uber. Get together and carpool, people are typically gathering at Challenge the Champions in the Expo Hall, which is great fun. There is a free parking garage behind the building. We'd love for you to sponsor a door prize - Continue Reading: If you or your company want to sponsor a LAVA BBQ door prize, please post a reply below. You can also include a small blurb about your company and a link to your website in the post below. By donating a prize you and your company will receive a small announcement of your choosing, during the event. We will ask you to write the announcement on a post-it note and will attach it to the prize to be read before awarding it. We love the door prizes, but we love time for socializing too. Here are some guidelines to keep our event balanced and streamlined. Single item donations work best. If donating more than one item, then multiple identical items is strongly preferred. If donating non-tangible items or something that is not physically with you, then please bring a card with your contact info and instructions on how to collect the prize. This will be given to the winner. Donations are typically $25-$200 in value. Not recommended: Apparel (hats, t-shirts, underwear, etc.) - never the right size Software licenses (Toolkits, add-ons, LabVIEW) Branded trade show booth type giveaways (mouse pads, pens, keychains, etc.) Jokes or something meant as a gag and not a real prize
  4. 7 points
    There are a bunch of objects in LabVIEW that aren't exposed in the default palettes, and are normally inaccessible except through scripting. I made a Quick Drop plugin that exposes all of these. Many of these are no longer supported, and others never were supported in the first place. Hidden ones are displayed with an "X" next to them to warn you: as I often say, be careful with these, and don't use them in any code you care about, as they can cause crashes, data corruption, and who knows what else! Download the LLB below and place it in your <LabVIEW install dir>\resource\dialog\QuickDrop\plugins folder. Then press Ctrl+Space, Ctrl+S to open this dialog. Select an item from the list and click OK, and there you go. There's some interesting/strange stuff in here! EDIT: Couple things I forgot to mention. The first time you open this (and whenever you rebuild the list) it uses two private properties on the app reference, to get the list of controls and indicators in the palette. Since this is just a property read, I'm sure the worst that could happen is a crash when you try to open the dialog, but I can't make any guarantees. Also there's some false positives for hidden items, mainly with front panel controls/indicators that come in different styles. Place by Style.llb
  5. 6 points
    You people are so laid back and forgiving. I’m an editor on multiple wikis across cyberspace, and none of the others are anything less than draconian. Capitalization whatever?! Wow. I’m going to need to wear my oversized Hawaiian shirt and cargo shorts when I’m editing, just to get in the right state of mind! 🙂
  6. 6 points
    We'll grow into it eventually 😋
  7. 6 points
    I just started down the rabbit hole of making a new XControl recently. Oh man such a pain. Here is a little graph I made complaining about the XControl creation process, and the time needed to make something useful. Any alternative is appreciated.
  8. 5 points
    After I made this post I decided to bring the LabVIEW Wiki back online. It was not easy and took several days of server upgrades and hacking. The good news is I was able to bring up all the original pages.. The even better news is I talked with @The Q and @hooovahh and we are all on the same page as to how to move forward. @The Q did a great job of stepping forward and trying to fill the void that the LabVIEW Wiki's absence had left. He's agreed to migrate all the new content he created over to the LabVIEW Wiki, from Fandom and continue to develop new articles and content moving forward on the new site. He will also help in moderating the Wiki and will be promoted to Admin rights on the Wiki. His help is much appreciated. The LabVIEW landing page created here on LAVA is awesome but the forums don't lend themselves to static content creation. Instead @hooovahh has agreed to move the old landing page to here. That will be the new home for the landing page. This will become a valuable resource for the community and I hope all of you start pointing new people in that direction. With many editors, it can only get better and better over time. Where do we go from here: Logging in. - The old accounts are still there. If you're a LAVA old-timer, then you can try to login using your LAVA username. If the password doesn't work then reset it. You can also create a new account here. I'm going to announce a day when new accounts can be created. I'm limiting it for now because of all the spam accounts that can be potentially created. There's an issue with the current Captcha system. if you are super-eager to start creating content now and want to help, send me a direct message on LAVA and I can manually create an account right away. - New account creation is now open. Permitted content: - I'm not going to put restrictions on content at the moment. Obvious vandalism or offensive\illegal content will not be tolerated of course. However, the guidelines will be adjusted as time goes on and new content is created. There's just not enough content right now to be overly concerned about this. We need content. Discussions about the Wiki. - Each article page has an associated discussions page where you can discuss issues related to that article. Please use that mechanism (same etiquette as wikipedia). General Wiki issues\questions and high level discussions can be done here. So now, if you need to add content, you can do it yourself. Feedback as always is welcome.
  9. 5 points
    I think this is a valid comparison: (from https://forums.ni.com/t5/LabVIEW/Global-Variables-Are-Better-than-Functional-Globals-So-There/td-p/1528392/page/5) You are either Novice or Guru 😋
  10. 5 points
    The best thing about a UDP joke is I don't care if you don't get it.
  11. 5 points
    The preference to use init methods instead of non-default class constants is so strong, LabVIEW NXG is planning to never support the feature. Any class constant there will always have only the class’ default value.
  12. 5 points
    I found it! Unfortunately it's deprecated. It takes dotted inputs as either names or ID codes.
  13. 5 points
    Proud to say that lavag.org and labviewwiki.org both get an A rating from an SSL labs security check. Even better than ni.com which is getting a B rating. 😎
  14. 4 points
    You can extract the labels from the type descriptor, once you know where to find them in the array. I added support for it in this open source DataManipulation library. Check out the OpenDescriptor palette. You can install the latest release (1.1.0.5) from here: https://github.com/LabVIEW-Open-Source/DataManipulation/releases/tag/1.1.0.5 (download VIP file and install with VIPM). Once installed, you'll find the "List Element Names" method under Addons>DataManipulation>OpenDescriptor palette. (It can list enums and cluster elements as well, although those are natively supported under the Variant Utilities palette.)
  15. 4 points
  16. 4 points
    Writing the notes forced me to watch the videos closely. I'm going to use the notes as a quick-ref whilst getting started and hoped others might have a go if they had them too. Feel free to make changes/fix wrong stuff in whatever way you like - expect you're a busy man. I'm happy to own the doc and expand it given the info. It's written in libreoffice writer, which exports a good pdf. Now looking fwd to cooking up a few actors. LabVIEW_Messenger_Library_-_Programmers_Notes_v1.7.pdf LabVIEW_Messenger_Library_-_Programmers_Notes_v1.7.odt
  17. 3 points
    Hello everybody! During a few last years I received multiple appeals to release AES library that I developed in 2011 into open-source. So, I've just done exactly this: https://github.com/IgorTitov/LabVIEW-Advanced-Encryption-Standard I released it under MIT license (which means that there are no restrictions whatsoever). No VI passwords, no uglification. LabVIEWishly Yours, Igor Titov.
  18. 3 points
    Version 1.2.0.6 released. https://github.com/LabVIEW-Open-Source/DataManipulation/releases/tag/1.2.0.6 Added support to return a list of Event reference types (class of event) for Event Registration Refnums Controls, Panes, Splitters, VI References and Application References. Array is empty for all other datatypes. ** Please note that this does not drill into clusters of Event Registration Refnums. This is only one-level deep. I have not tried, but I assume that getting the cluster elements and then looping on those should work...
  19. 3 points
    My first ever meme prompted from this post
  20. 3 points
    Have the topics been converted to the lava forum with the same topic id? If so, you can just enter the topic-id in the url and add a - with anything behind it https://lavag.org/topic/1524-anything-you-want works just fine
  21. 3 points
    NI is bringing 2 NI myRIO devices for Door Prizes.
  22. 3 points
    am I doing this right?
  23. 3 points
  24. 3 points
    Dating will always be a problem for software engineers.
  25. 3 points
    I agree with James. That could be achieved through composition and adding an abstraction layer. (Sink and Source in the diagram below)
  26. 3 points
    1. Place a control refnum 2. Right-click, Select VI Server Class, Generic, GObject, Control, Pixmap 3. Now it's a "Pixmap Refnum". Right-click again, Show Control 4. Drag the control out. Unfortunately, I first noticed this control in the VI Scripting style ring, where it was labeled as "warning: dangerous" or something like that. But the class isn't marked private, and it can be placed in the manner I described without any kind of warning, so maybe that warning is obsolete and it's been fixed? Then it would probably be in the palette, I guess, but I'm curious to hear what NI has to say. Maybe it's a bug that it can be placed that easily without generating any warnings. :p
  27. 3 points
    Let's take a look inside labview.rsc first... Four of the connector pane patterns actually have names: 4833: "monnie pleaser" 4834: "super monnie pleaser" 4835: "monnie would be pleased-er" 4836: "add supports 2 ddt" I guess this book wasn't lying. Two cursors with rather...interesting names: 64: "order sucker" 65: "order squirter" Someone at NI has a dirty sense of humor 😛 There's some resources that correspond to the style values for VI scripting. Some of them aren't in the style list; unfortunately attempting to use these just gives an error: 2051: "Comment Node" - says "Case" in the data, and gives "Unable to create new object" instead of the usual "object not found" error 2358: "Line of Script" 3902: "Growable Node with Header" 3905: "ExtFuncTerminalTipStrings" - data says "External Function Node", and has names for "path in", "path out", and the standard error in/out terminals 9008: "Select Menu Item" - with all the menu nodes. Looks like at one point they were working on a primitive for programmatically activating menu items. Someone found some hidden structure types a while back. All but one of them didn't work, and that other one is now an official part of LabVIEW. I found the image for the "Race Structure", which I've posted to that thread: There's also this super-minimalist "Alternate Splash Screen": And some monochrome sprite sheets—looks like the old Boolean constant graphics are still there. From what I know about internal VI data structures, I wouldn't be surprised if those were still used if you load a VI created in an old version of LabVIEW. Just thought I'd share. Curious if anyone has seen these before!
  28. 3 points
    Loving this central location of organized and searchable LabVIEW knowledge! (Just like LAVA.😁) I've made a couple of small contributions to this so far. Mostly clicking on "Random Article" and reviewing it for typos and broken links. I set somewhat of a personal goal of trying to do this at least once per workday. Every little bit helps, right? Granted, they're not contributions on a grand scale yet, (i.e I'm not creating articles, etc.) but maybe I'll get there. This is my first time contributing to a Wiki of any kind, so I'm a n00b at it.
  29. 3 points
    Does anybody know how to get a LabVIEW built application to ignore the scaling setting in Windows? I have some code designed to fit nicely in 1280x1024 pixels, but some of my customers say that even on a 1920x1080 display the menu bar at the top is cut off. I guess this is probably because their windows scaling is set to some number other than 100%. In my experience LabVIEW looks really rubbish when run on Windows 10 with this setting to anything other than 100% (blurry and inconsistent). I suppose is to be expected from an application like LabVIEW that is approaching retirement age! Am I missing something obvious here? Although I always set my Windows scaling to 100% on all the PCs I control it is not really practical for me to expect ask my clients to change this setting as some of them have probably gotten used to seeing Windows text nice and big at 125 or 150%. Edit 1 I have done quite a bit of googling and not really come across anything LabVIEW specific. The closest I got was some NI KB about LabWindows. Edit 2. Success! https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000004A7eSAE Note a newer Windows update adds a few more options which are now tucked away in a separate dialogue. I have not tried playing around with the other options yet as this fix works fine on my PC. Edit 3. And this is how it can be done programatically: https://blogs.technet.microsoft.com/mspfe/2013/11/21/disabling-dpi-scaling-on-windows-8-1-the-enterprise-way/ (i.e. as part of an installer action)
  30. 3 points
  31. 2 points
    Here is a library I created to wrap the WinSCP .NET library. You can use it to connect to a remote server via SSH and transfer files, create remote directories,etc., with WinSCP from LabVIEW. I know there is a commercial library for I think $500 a pop, but this is something that is missing from LabVIEW that really ought to be included with native functions in the file I/O palette. The VI's in this packed library are built around the "WinSCPnet.dll" library that installs with WinSCP. You will have to download and install WinSCP to get the DLL, as I do not want to distribute it without their permission: Download WinSCP Here After downloading and installing WinSCP, you will have to connect the VI's in the packed library to WinSCPnet.dll. I make no warranties here, and no promises it will work, since I already have the stuff installed. The use WinSCP with an SSH Key, you will have to generate a key and copy the public key to your server. WinSCP uses the Putty format for SSH 2. You will also have to obtain an SSH fingerprint from your server for input to the session. Otherwise, you will have to provide user login credentials. You can use the "C:\Program Files (x86)\WinSCP\PuTTY\puttygen.exe" utility to generate a key. I use Git, so I used the SSH utilities included with that to generate and copy the key to my server. If you do that, you will have to use puttygen to import your OpenSSH key and convert it to putty format for use with the WinSCP/LabVIEW library. Sorry I don't have more time to do full docs and directions for use, but maybe someone else can comment with additional directions. I will monitor this topic and try to answer any questions. Good luck, and happy SFTPing! PS: No I will not save it to an earlier version. Maybe someone else can. WinSCPnet.lvlibp
  32. 2 points
    I found some spam on the wiki and would like to request deletion, but there doesn't seem to be an option (probably because I don't have the rights). So, is there a way to notify administrators (currently only @Michael Aivaliotis?) directly or should we open new topics here? Here are the offending pages. https://labviewwiki.org/wiki/Is_there_some_magic_to_get_URLForUbiquityContainerIdentifier_to_work_besides_setting_up_the_Entitlements_Stupid_http://nfltickets.me/baltimore-ravens-tickets/_thing_keeps_returning_nil https://labviewwiki.org/wiki/Being_The_Best_Pet_Owner_In_Town:_Tips_And_Tricks_by_Gita_I._Reimnitz https://labviewwiki.org/wiki/Caring_For_Your_Kitty:_Top_Tips_And_Advice_by_Sindy_P._Lanterman https://labviewwiki.org/wiki/Jijijijijiji_te_dije_q_lo_usaras_http://convenientcarpetcleaning.com/washington/carpet-cleaning-in-pasco-wa/_rapidooo_merf https://labviewwiki.org/wiki/Prohibir_el_acceso_a_los_Colocolinos_que_portan_sus_entradas_es_sumar_mas_violencia_a_una_actividad_http://kyleleon-musclemaximizer.com/reviews/_que_esta_en_crisis https://labviewwiki.org/wiki/This_man_just_said_she_get_more_miles_than_a_18_wheeler_smh_http://convenientcarpetcleaning.com/new-mexico/carpet-cleaning-in-farmington-nm/_mauryshow Edit: There also seem to be some orphan files that should be released of their existence: https://labviewwiki.org/wiki/File:Bomboniera_solidale_matrimo_2359.jpg https://labviewwiki.org/wiki/File:Betting_on_nfl_5601.jpg https://labviewwiki.org/wiki/File:Bitcoin_piracy_3126.jpg https://labviewwiki.org/wiki/File:Binary_options_3986.jpg https://labviewwiki.org/wiki/File:Abogados_Madrid,_Despacho_de_Abogados_laboralistas_2813.jpg https://labviewwiki.org/wiki/File:50_shades_darker_1556.jpg https://labviewwiki.org/wiki/File:Bomboniere_matrimonio_4754.jpg https://labviewwiki.org/wiki/File:Buy_dianabol_3532.jpg https://labviewwiki.org/wiki/File:Cakes_4375.jpg https://labviewwiki.org/wiki/File:Capetown_wedding_venues_1999.jpg https://labviewwiki.org/wiki/File:Cheap_costume_jewellery_2542.jpg https://labviewwiki.org/wiki/File:Cercacasa.it_5533.jpg https://labviewwiki.org/wiki/File:Cheat_hidden_chronicles_3336.jpg https://labviewwiki.org/wiki/File:Chicago_tuckpointing_2777.jpg https://labviewwiki.org/wiki/File:Christmas_bows_1816.jpg https://labviewwiki.org/wiki/File:Computer_system_clock_2606.jpg https://labviewwiki.org/wiki/File:Computer_training_1367.jpg https://labviewwiki.org/wiki/File:Contact_Us_-_4664.jpg https://labviewwiki.org/wiki/File:Bomboniera_solidale_matrimo_2838.jpg https://labviewwiki.org/wiki/File:Descuentos_3610.jpg https://labviewwiki.org/wiki/File:Does_wartrol_work_4699.jpg https://labviewwiki.org/wiki/File:Dog_ideas_1934.jpg https://labviewwiki.org/wiki/File:Driving_lessons_in_solihull_1129.jpg https://labviewwiki.org/wiki/File:Driving_schools_in_Solihull_1174.jpg https://labviewwiki.org/wiki/File:Find_out_more_about_Access_control_2363.jpg https://labviewwiki.org/wiki/File:Fixing_laptop_toronto_1598.jpg https://labviewwiki.org/wiki/File:Folding_camper_transport_884.jpg https://labviewwiki.org/wiki/File:Food_distributors_4956.jpg https://labviewwiki.org/wiki/File:Going_here_2091.jpg There is no end to this... https://labviewwiki.org/wiki/File:Government_Debt_Relief_Programs_2346.jpg https://labviewwiki.org/wiki/File:Graphic_design_schools_2392.jpg https://labviewwiki.org/wiki/File:Hair_Style_Tips_4044.jpg https://labviewwiki.org/wiki/File:Healthcare_Administration_Training_Riverton_WY_1392.jpg https://labviewwiki.org/wiki/File:Help_available_5233.jpg https://labviewwiki.org/wiki/File:Here_3240.jpg https://labviewwiki.org/wiki/File:Hidden_chronicles_cheats_2585.jpg https://labviewwiki.org/wiki/File:Hidden_chronicles_cheats_4737.jpg https://labviewwiki.org/wiki/File:How_to_sell_gold_3730.jpg https://labviewwiki.org/wiki/File:Howto-grow-yourpenis.net_4497.jpg https://labviewwiki.org/wiki/File:Htc_one_x_update_2387.jpg https://labviewwiki.org/wiki/File:Illinois_home_inspector_directory_5003.jpg https://labviewwiki.org/wiki/File:Juridische_vertalingen_5007.jpg Saving because I don't want to loose progress... https://labviewwiki.org/wiki/File:Laserbehandeling_ontharing_1003.jpg https://labviewwiki.org/wiki/File:MerrimanSnippet.png https://labviewwiki.org/wiki/File:No_No_hair_removal_reviews_2507.jpg https://labviewwiki.org/wiki/File:Paintball_1581.jpg https://labviewwiki.org/wiki/File:Pc_technical_support_toshiba_scarborough_4170.jpg https://labviewwiki.org/wiki/File:Personalised_christmas_sacks_and_stockings_5390.jpg https://labviewwiki.org/wiki/File:Pool_service_columbia_sc_4213.jpg https://labviewwiki.org/wiki/File:Privacy_Policy_959.jpg https://labviewwiki.org/wiki/File:Pure_argan_oil_for_face_2042.jpg https://labviewwiki.org/wiki/File:Read_here_4467.jpg https://labviewwiki.org/wiki/File:Reputation_management_1152.jpg https://labviewwiki.org/wiki/File:Reviews_3461.jpg https://labviewwiki.org/wiki/File:San_Antonio_Interior_Decorator_2940.jpg https://labviewwiki.org/wiki/File:San_Antonio_Interior_Decorator_4834.jpg https://labviewwiki.org/wiki/File:San_Antonio_Interior_Design_3474.jpg https://labviewwiki.org/wiki/File:Schedule_a_carpet_cleaning_2023.jpg https://labviewwiki.org/wiki/File:Smartrank_778.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_1160.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_1318.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_1515.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_2486.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_2917.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_3584.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_3672.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_3744.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_4150.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_4849.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_5002.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_5239.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_5436.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_757.jpg https://labviewwiki.org/wiki/File:Social_bookmarking_service_880.jpg https://labviewwiki.org/wiki/File:Too_much_iron_in_your_blood_1972.jpg https://labviewwiki.org/wiki/File:Toppik_uk_4349.jpg https://labviewwiki.org/wiki/File:Used_iphone_3_for_sale_1589.jpg https://labviewwiki.org/wiki/File:Valley_view_casino_1963.jpg https://labviewwiki.org/wiki/File:Video_promotion_by_ytpros_2952.jpg https://labviewwiki.org/wiki/File:Watch_avi_on_android_3765.jpg https://labviewwiki.org/wiki/File:Web_design_1869.jpg Done.
  33. 2 points
    No problem, I just want to make sure people know the difference between "Darren the G programmer says _____" and "Darren the NI employee says _____". In my "Don't Wait for LabVIEW R&D... Implement Your Own LabVIEW Features!" presentation, after I clarify that I'm presenting my personal opinion and not an official NI position, I contraindicate XControls because of numerous stability issues I've seen with them in large applications over the years. You can see my slides and watch a recording of the presentation here: http://bit.ly/dnattlvhooks
  34. 2 points
    Maps in LabVIEW 2019?
  35. 2 points
    Disclaimer The following details are oversimplified for the sake of clarity. Feel free to point out important details that aren't covered by this post. --- There is a higher chance of finding better results by searching for "labview reference". Here are a few examples. https://labviewwiki.org/w/index.php?search=reference&title=Special%3ASearch&go=Go https://labviewwiki.org/wiki/Control_References http://www.ni.com/example/28769/en/ That said, you should be familiar with the normal data flow in LabVIEW. Data goes from one end of a wire to the other. A branch in the wire will create a copy in memory if either branch of the wire is changed. Loosely speaking, a wire represents the data. A refnum on the other hand doesn't represent the data, but the location of the data in memory (*). It is similar to a pointer in C-like languages. This changes the behavior of the wire Data still goes from one end of a wire to the other. Each branch of a wire receives exactly the same value as the other (no copy is made). (**) In order to access the data you need to make use of Property Nodes, Invoke Nodes and more. The benefit is, that you can access the same value from different places in your program. Even better, this is not limited to controls. It works for controls and indicators, VIs, objects, the project, the whole application and everything. https://labviewwiki.org/wiki/Refnum http://zone.ni.com/reference/en-XX/help/371361R-01/lvconcepts/controlling_front_panel_objects/ However, it doesn't work for variables and due to its nature, race conditions can occur if you don't take care of the execution in your program. This is why for variables there is a more specialized type of reference, the data value reference (DVR). It allows you to access the same variable in memory from different places in your program. http://www.ni.com/product-documentation/9386/en/ There is obviously much more to it than these few points. However, the links above should give you some insight. (*) Here is some information about the memory structure of a refnum. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019ZT5SAM&l=en-US (**) Technically speaking a copy is still made if you change the "value" on either branch of the wire, but since it is a pointer you shouldn't change it under any circumstances.
  36. 2 points
    It's a conjugation. I think Americans are the biggest perpetrators especially for "setted". They do other funny stuff like leaving out letters and putting dates the wrong way round
  37. 2 points
    Apollo 13? (It's a NASA saying)
  38. 2 points
    LV 2019 augments the right-click menus for class wires/terminals to provide a method list you can drop, which should alleviate this issue. I found a way to make the right-click menu plug-in able to add the graphical palette menus and then built a right-click plug-in that builds the method palette on the fly if the class doesn't already have its own default palette.
  39. 2 points
    PS: Did I mention that the design of these things was arcane and bad? Yes? Ok. 'Cause it's true. I have a long list of lessons I hope NXG learns.
  40. 2 points
    XControls work just fine... if you dance with them the way they were intended. *head bang* If you don't want data to be saved, one way is to not put it in the State data. If you only need the data in the facade, add a shift register. But if you need it lots of places, put a global unique ID (GUID) in the XControl's state data, something that never changes after creation, and create an LV-2 style global with a lookup table from the unique ID to the data. You can create GUIDs on any LV OS using: LabVIEW 2017\resource\Framework\Providers\API\mxLvGenerateGuid.vi Changing the state shouldn't cause the VI to need to be saved unless it needs to be saved. So, yes, sure, in the IDE in a directly called VI, yes, changing state dirties the VI. But obviously that doesn't happen in a built app. AND, importantly, it doesn't happen in the IDE for any dynamically loaded VI (unless you are adding the 0x1 flag to track changes, in which case you get what you requested). If you're loading the hosted VI into a subpanel, that means you're working with it by VI Reference. So load it using Open VI Reference (without the flag) and the problem of being prompted to save should go away.
  41. 2 points
    Here's a shortcut menu plugin I wrote that does something I've found myself needing every now and then. You select some objects, right-click, select "Ad-Hoc Scripting", and then it'll open a new VI with pre-populated refnums in a cluster. All selected objects with a label (even a hidden one) will be included in the cluster, as will a refnum to the VI, its panel, and its diagram. Ad-Hoc VI Scripting.llb
  42. 2 points
    Try this. Windows User Login 2017.zip
  43. 2 points
    Why would you need an Open Sourced LabVIEW for something like that? This was possible in the Control editor since LabVIEW 3!!! (Discloser: the Browse button in the Path control was not added before somewhere around version 6 to 8 but the principle worked in LabVIEW 3). 1) Place a path control on your front panel 2) Right click on it and select Advanced->Customize => The path control opens in the control editor 3) Right click on the browse button and select Advanced->Customize => The browse boolean control opens in the control editor 4) Save this as your Browse Boolean.ctl file or whatever you want to call it. 5) Use as you wish and enjoy that it automatically adapts to the platform style for the system you run it on Browse.ctl
  44. 2 points
    Could you use an adaptor around the DVM that inherits from the desired abstract classes? That has been my solution to this problem in the past.
  45. 2 points
    Thanks for the interesting conversation. I've resolved the issue however, in a roundabout way and by cleaning up my code. The UDP communication code in question is a model written in LabVIEW running on VeriStand, which is essentially a bunch of LabVIEW RT timed loops running on a Phar Lap target. So the model essentially opens a UDP connection, sends the message, then closes the connection. This is done at a rate of 50Hz. I changed the code so that it opens the connection at the start of the test and the model just continuously sends the message at the 50Hz rate, then at the end of the test I close the UDP connection. This resolved the issue because now the ARP is not sent anymore, like at all. Well, maybe at the start? But I haven't checked that, so I should do that later. The explanation I can come up with is, I was closing the connection every 20ms, so the OS considered the port closed, so it took that time to do the normal housekeeping of sending the ARP? But since the port was always open to a known IP address (and thus mac ID), it didn't need to do the ARP. I don't know, just my guess. Ok, so bring on the comments about, why I would keep opening and closing the port. Bring it on, I can handle it... 😀
  46. 2 points
    Wait, what about the person who already had the name Bryan?
  47. 2 points
    Every now and then I hope for a bright future and open the latest NXG - and my head hurts. They've changed too much, and gained so little🤯. I immediately get irritated by how disrespectful the whole thing is of the strengths of LV, but try to push myself to get more used to it. Then I hit a brick wall in a lack of functionality, and my patience runs out. Back to LabVIEW 2018. Home sweet home☺️ (sure, the roof is leaking and the style is a bit 90's, but it beats NXG).
  48. 2 points
    The context help for the "RemoveXnode" method says "Removes the XNode from the diagram. The contents of the diagram of the XNode are merged with the diagram" However if you try it, it may or may not work. That's because this method just calls the "ReplaceSelf" ability; so if an XNode doesn't have a "ReplaceSelf" ability, the "RemoveXnode" method will do nothing. So if you want your XNode to work with the "RemoveXNode" method, you must create a "ReplaceSelf" ability. Fortunately doing so is very trivial: Your ReplaceSelf ability only has to call the "GenerateCode" Ability; like this: Paul Cardinale P.S. Note that the "ReplaceSelf" ability of some NI Xnodes doesn't work properly. For instance if you call "RemoveXNode" on the "Match Regular Expression" function, it will make a mess, breaking the VI.
  49. 2 points

    Version 1.0.0

    109 downloads

    There it is. The complete library for the MCP2221A. I2c adapter, I/O in a single IC. I love that one. Let me know if any bug is found. I try to make that library as much convenient as possible to use. Two version available 32 bit and 64 bit. little note: to open by serial number, the enumeration need to be activated on the device first. (open by index, enable the enumeration) It needs to be done only once in the life time of the device. PLEASE do not take ownership of this work since it is not yours. You have it for free, but the credit is still mine... I spent many hours of my life to make it works.
  50. 2 points
    Check out the awesome home page updates that @The Q has made. Huge improvement. I love it! https://labviewwiki.org


×
×
  • Create New...

Important Information

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