Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


X___ last won the day on March 3

X___ had the most liked content!


Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2021
  • Since

Recent Profile Visitors

4,954 profile views

X___'s Achievements


Collaborator (7/14)

  • Conversation Starter Rare
  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Dedicated Rare

Recent Badges



  1. Interesting suggestion. Any idea how the multicore option works (Get/Set Number of Threads)? When I test this on a standalone VI, I get a number of 8 for "Transform" (which is what I am interested in testing) or "Linear Algebra" (I am using a 8 cores/16 threads laptop). When I include this as part of a larger project (launching a number of parallel tasks some of which use parallel loops), I end up with a "1" (in both tasks). I am not sure I should necessarily expect multithreading to be particularly useful in my case (rather small array sizes) but there isn't any explanation that I know of as to how this is supposed to work or be understood...
  2. Actually that makes more sense: get an actually debuggable Python code and wrap it into a Python Node call. Un-commented spaghetti code is pretty much useless... The flat (single VI) LabVIEW generated code demo doesn't tell anything about the ability for this type of AI assistant to generate structured code. The first step is for NI to demonstrate that they can use AI to clean up (or expand/shrink) diagrams meaningfully. I believe the way they work is they are predicting each character on the fly I hope not... at least if they are using the thing right.
  3. It's heavily scripted, but on face value, that looks promising.
  4. BT What's wrong with the Picture control BTW? As long as you are not looking for super-fast updates (athough even that is not precluded), this is a very capable object...
  5. Actually, here is the relevant info: Which VIs are Installed with NI-IMAQ and Vision Acquisition Software? and this: Is a License Needed to Work With NI Vision Acquisition Software? So it looks like nothing additional is needed for the computer on which the IMAQ hardware is installed (or from which it is run), but officially, any other computer (including a development computer) would. If your client is not using any IMAQ hardware, they are not supposed to use code (development or runtime) that uses these VIs. But again, I may have this all wrong, although that is what I remember from the time we were using an IMAQ frame grabber.
  6. The latest NI License Manager release page: https://www.ni.com/en-us/support/documentation/release-notes/product.license-manager.html will clarify all that:
  7. It doesn't say much of what the expected position reshuffling is going to be, but based on past history, it it unlikely they will not change anything to the management and strategy. I don't anticipate a reboot of LabVIEW or doubling down on investment and renewal of hopes for the tool though.
  8. Here is an example that shows how that works: https://forums.ni.com/t5/LabVIEW/Can-I-read-16-bit-PNG-files-with-LabVIEW/m-p/4296823#M1255119
  9. You would have to add a dummy graph that you would only show the legend of and fill that with half of your plot names (e.g. adding one empty plot for each pair). And of course hide the legend of your original graph. And respond to actions on the dummy graph to update your original graph.
  10. There is NO public bug tracker in LabVIEW... In fact, I am not even sure there is beta program anymore...
  11. A bit like Egyptian hieroglyphs.
  12. For NI's defense, this is probably only visible on 1080p displays. It speaks volume about the state of LabVIEW when this becomes a new feature worth discussion on LAVA...
  13. OK, my bad. I think I know what you are referring to: I am not sure what this means though, as I see no effect of the default font style on terminal, bundle, etc. sizes, only on the labels (in LV 2021 SP1).
  • Create New...

Important Information

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