Neil Pate

Wow, that is keen!

🤣 sounds like a cash converter service...

I had a real struggle with some USB3.0 cameras and a Windows 10 PC. They were Basler cameras, and even Windows device manager sometimes did not pick them up. They would regularly just "not appear" in MAX. Never managed to solve the problem to my satisfaction and pretty much decided to not use USB hardware.

Now that I think about it, I also cache the This VI ref in another VI which I use as sort of an actor debugger to allow me to open the FPs and BDs of any running actors including clones (not AF actors, my own home rolled framework). I poll all the refs multiple times per second to get status about the clone name and running status, and have never seen any weird crashes which I have attributed to that.

I think the warning is related to the Open by name. I really hope so as I too use the technique you describe where the clones themselves get their own references so that they can insert themselves into a SubPanel (and do other stuff to the FP like title etc). Been using this architecture for five or six years now and never had any run-time crashes I can think of.

This works. Note in my example I do not wait for the command to complete, I test for the result in some downstream code not shown in this snippet.

Search the forums for calling a batch file from inside LabVIEW. Sometimes it can be a bit tricky to get the path right with the all the "" that you need. I dont have any code in front of me that does this right now, I can dig something up in a few hours.

In situations like this with a not trivial set of arguments I normally create a batch file (from code) and then run that using the System Exec, with no parameters needed. I have done it like this for as long as I can remember so am not really sure if it is still necessary to do this.

Not directly LabVIEW related, but a good listen anyway: https://www.codingblocks.net/podcast/why-date-ing-is-hard/ I seem to remember several people on this forum talking about ISO8601 a while back, the more you get into it the deeper the problem goes!

Sure we all have our preferences, but please don't tell me everyone does this manually on new installs? Maybe I just install LabVIEW *way* too many times a year. Coping the LabVIEW.ini file seems like the only sensible option for me.

Nice solution Rolf, thanks!

Wow, glad I have my fireproof jacket on this morning! 🤣

Cool, will try it out. Thank you.

And then I have two problems...

Yup, and now we are way too deep in the rabbit hole. A standard boolean does pretty much exactly what I need it just does not have an icon on it. As soon a NI open sources LabVIEW we will be able to fix things like this 🙂