Jump to content

hooovahh

Moderators
  • Posts

    3,451
  • Joined

  • Last visited

  • Days Won

    294

Posts posted by hooovahh

  1. A11A11111, or any such alpha-numeric serial from that era worked.  For a while at the company I was working at, we would enter A11A11111 as a key, then not activate, then go through the process of activating offline, by sending NI the PC's unique 20 (25?) digit code. This would then activate like it should but with the added benefit of not putting the serial you activated with on the splash screen.  We would got to a conference or user group to present, and if we launched LabVIEW, it would pop up with the key we used to activate all software we had access to.  Since then there is an INI key I think that hides it, but here is an idea exchange I saw on it.  LabVIEW 5 EXEs also ran without needing to install the runtime engine.  LabVIEW 6 and 7 EXEs could run without installing the runtime engine if you put files in special locations. Here is a thread, where the PDF that explains it is missing but the important information remains.

  2. 11 hours ago, Thomas Robertson said:

    Just wanted to chime in on this Zombie thread and say I have all of these problems and it's driving me crazy.  LV2023, Roughly 18,000 vis in the project.

    My projects can be on that order of size and editing can be a real pain. I pointed out the difficulties to Darren in QD responsiveness and he suggested looking for and removing circular dependencies in libraries and classes. I think it helped but not by much. Going to PPLs isn't really an option since so many of the VIs are in reuse packages, and those packages are intended to be used across multiple targets, Windows and RT.  This has a cascading affect and linking to things means they need to be PPLs, made for that specific target, and then the functions palette needs to be target specific to pull in the right edition of the dependencies. AQ mentioned a few techniques for target specific VI loading, but I couldn't get it to work properly for the full project.

  3. Wow that is a great tool.  My suggestion (which is not as good) is to use a NoSleep program.  I made one in AutoIt scripting years ago and have been having it run on startup of test PCs for years.  There are a couple versions, one would turn on and off the scroll lock every 30 seconds, but sometimes it did need a mouse jiggle to keep it awake.  Here is one I found online that is similar to what I have used.  One down side of this I did discover is that if you use remote desktop, and you remove into a machine that has a mouse jiggle no sleep, then it will do weird things in the host PC.

  4. 41 minutes ago, Rolf Kalbermatter said:

    As to running LabVIEW directly on a HA, that is not currently possible. Well it may be possible with some emulation if you get an x86_64 emulator running on your ARM HA hardware but that is:

    1) a major project to get running, with lots of obstacles, many tricks and a huge chance that what worked yesterday suddenly fails for unexplainable reasons

    2) a taxing solution on the poor ARM CPU in your typical HA box

    My HA install is running on bare metal computer, which is an 8th gen I3 embedded PC, 8GB of RAM 250GB SSD.   Here is the install instructions.  I wanted a bit more performance, and a company was throwing these computers away.  Besides this can give me more head room to do other things if I ever want to.  There's even an option to install HA on windows, but it mentions it in a VM specifically.  Nevermind, this is explaining how to have it on Windows, which involves having a Linux VM.

  5. 9 hours ago, Vandy_Gan said:

    Hi David Koch,

     thanks for your reply, I have a question that how to make the glyphs to place center in cells?

    David has posted to LAVA 1 time, and it was 10 years ago. I don't think he's going to respond.  You cannot control the position of the glyph with the built in function.  The only solution I know of is a pretty time consuming one, where you put a transparent picture control on top of the tree, and then you can do whatever you want.  I've applied this to a sequence editor.  The left and right are tree controls (as noticed by the collapsing icon). The tree on the right has two centered columns.  This has two picture controls that position themselves to look like it is part of the tree.  There's a decent amount of work on the back end to handle things like window resizing, collapsing the tree, and other random behaviors. But the end result is something I have full control of.

    SequenceEditorStepUI.png.c6d922e5e1faf1bb33b0f7e73824e4fd.png

    Also in a related topic here is an idea exchange to support larger glyphs.  There is a linked example on how to fake it in a fairly convincing way.

  6. You've probably already found some stuff but here is an old thread that talks a bit about it.  It is an unofficial feature that NI seemingly never finished, or never documented.

    INI keys can help you, or I think you can copy a MCLB that has the feature enabled. Another solution I've done in the past is to have a 2D picture box on top of the control, then having that be an image that you can set. This gets way more complicated with scrolling, and resizing windows, but it allows you to have glyphs that aren't the default size which is also what I wanted.

  7. 11 hours ago, ShaunR said:

    Just be aware that the Caption property is often used for translations.

    Oh yes great point.  I've always been in the world of English applications, but a Label would probably be a safer choice.  I'm just thinking about situations where at runtime connecting to things could be changed for a more dynamic UI.  It has been done before different ways of course.

  8. On 9/30/2025 at 8:44 AM, Rolf Kalbermatter said:

    I assume that support for the old *.cdf NI-Max format for installation onto pre LabVIEW 2020 RT targets is not a topic anymore and you guys rather expect *.ipk files?

    Maybe add a download feed to the OpenG Github project for this? 🙂

    I've been manually installing it myself.  I copy the liblvzlib.so to the controller, then I SSH in with Putty, and sudo copy to /usr/local/lib/liblvzlib.so, then restart the controller.  I was happy using the old CDF format custom install for as long as I could.

  9. Very neat looking. I like the concept. I do think people might not like the unprotected nature of being able to read and write to tags from anywhere.  Imagine I have a sensor that keeps flipping back to NaN.  I suspect trouble shooting where the tag is getting written from, or debugging this type of wireless program can be a challenge. If tools are made for tracking this type of thing it might make it easier.  

    This also would make something like dynamic UIs easier.  You can have a set of controls that can be inserted into subpanels, and then to read/write data you just need the controls named something specific.  Oh that gets me thinking, can the tag be based on the Caption of the control not the label?  That way it can change at runtime.

    Also I think the video should have been a youtube link. Watching such a long gif is a weird experience without pause, or playback controls.

  10. 4 hours ago, ShaunR said:

    Just download VIPM today and activate a 30day trial to try out VIPC files.

    Pretty sure it is a pro feature. You may be able to use VIPC files in the Community version but I'm sure you can't create them without the pro version. Maybe it's changed since I last looked though.

    Here is the Community Edition announcement. https://www.jki.net/blog/news/vipm-2020-community-edition

  11. On 8/28/2025 at 9:07 AM, ShaunR said:

    If you are just looking at toolkits installed with the JKI Package Manager then the full version can create super packages where you can create a list of toolkits to install. you could then walk from PC to PC with that package and install them with the package manager.

    This feature is the VI Package Configuration (VIPC) and is free and included in the community version of VIPM.  The VIPC can contain a list of packages to install, or it can contain the list, along with the actual packages.  This is quite handy since you can have a single VIPC file that you double click, and all those packages and their dependencies are installed offline (NIPM should take notes).

  12. 15 hours ago, Mads said:

    You should have used Grok...

    It was equally as bad as Gemini in my work with Task Scheduler.  It is far too much to paste in here but I created a Task with the command line, and provided it then said: This all works but I'd like to turn off the feature Stop the task if it runs longer than 3 days, and turn off the Start the task only if computer is on AC Power. What command line switches do I need for this?

    Gemini made up switches, and I had to keep pasting back the error I got over and over with Google eventually telling me it isn't possible.

    I just hit the limit on free Grok messages and it had similar behavior. I'd run the command it gave with a paragraph explaining how it should work. I'd reply back with the error. It would tell me why the error existed and what command to use. That would generate a new error which I would tell it, and it would do the same. Over and over until I can't chat with it anymore.

    I use AI primarily for writing assistance, but coding or technical assistance on the surface looks great. But in practice is lacking.

  13. 6 minutes ago, ShaunR said:

    Do you see the unresponsiveness in dadreamer's example?

    The newest version of LabVIEW I have installed is 2022 Q3.  I had 2024, but my main project was a huge slow down in development so I rolled back.  I think I have some circular library dependencies, that need to get resolved.  But still same code, way slower.  In 2022 Q3 I opened the example here and it locked up LabVIEW for about 60 seconds. But once opened creating a constant was also on the order of 1 or 2 seconds.  QuickDrop on create controls on a node (CTRL+D) takes about 8 seconds, undo from this operation takes about 6.  Basically any drop, wire, or delete operation is 1 to 2 seconds.  Very painful.  If you gave this to NI they'd likely say you should refactor the VI so it has smaller chunks instead of one big VI.  But the point is I've seen this type of behavior to a lesser extent on lots of code.

  14. 22 minutes ago, ShaunR said:

    There was a time when on some machines the editing operations would result in long busy cursors of the order of 10-20 secs - especially after LabVIEW 2011.  Not necessarily XNodes either (although XNodes were the suspect). I don't think anyone ever got to the bottom of it and I don't think NI could replicate it.

    It has gotten worst in later versions of LabVIEW. I certainly think the code influences this laggy, unresponsiveness, but the same code seems to be worst the later I go.  

  15. In the past I have used the IMAQ drivers for getting the image, which on its own does not require any additional runtime license.  It is one of those lesser known secrets that acquiring and saving the image is free, but any of the useful tools have a development, and deployment license associated with it.  I've also had mild success with leveraging VLC.  Here is the library I used in the past, and here is another one I haven't used but looks promising.  With these you can have a live stream of a camera as long as VLC can talk to it, and then pretty easily save snapshots.

    EDIT: The NI software for getting images through IMAQ for free is called "NI Vision Common Resources". This LAVA thread is where I first learned about it.

    • Like 2
  16. 3 hours ago, Neil Pate said:

    Done some simple testing.

    On a directory containing 838 files it took 60 ms.

    That's how I'd do it.  Then combine that with the Foreign Key Sort from my Array package, putting the Time Stamps into the Keys, then paths into the Arrays, and it will sort the paths from oldest to newest.  Reverse the array and index at 0, or use Delete From Array to get the last element, which would be the newest file.

    ForeignKeySort.png.fd9ab39f83ed774e23f35816a3682a20.png

    • Like 1
×
×
  • Create New...

Important Information

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