jcarmody

Jake isn't self-aware, yet...

Says the account with "AI" right in the name. Hiding in plain sight! eta: In fact, you can't even pronounce it without saying "AI" - "A I va lee oh tis". Well, I can't, anyway...

[I hope] I'm within ten years of retirement and I expect that there's plenty of support work here to last me that long. In the meantime, our larger team has been developing in Microsoft Java C# for years now and it's moving into our business. It's time for an old dog to learn a new trick.

Did ChatGPT make a passable TL;DR?

Ask an AI.

If it was hard to write, it should be hard to read.

One of my past managers said, "This isn't a laboratory so why are we using LabVIEW?" I'm sure he didn't capitalize it correctly when he said it, but I'm glad he (and his colleagues) aren't here anymore. :shakesfist:

I have latest LabVIEW 2020.

Cross-posted on NI's forum.

This sounds ambitious. >> After annotating the dataset, I will train a machine learning model to detect the block diagrams. This sounds like it should come first? This feels more approachable because, as Shaun said, there is a lot of code available in VIPM. There's also a ton on these (and NI's) fora that can easily be labeled as having a block diagram. Labeling a diagram as an "experimental setup" is more difficult; labeling it with the specific type of setup will be even harder and judging the quality of the programming (so you can "recommend how the investigation can continue from the similar setups") will be (nearly) impossible. Good luck, though.

I asked it to and it said something about not being able to do graphics. Sounds like a lot of people I've worked with.

Please forgive the intrusion as I'm neither of the "A"s* in "LAVA", but I just finished the NI OO class (and slept in a Holiday Inn last night) and wonder if that's not something I could use interfaces for. * neither Advanced nor Architect

>> If anyone is interested I can share the results later on. Done, and interested. I want to know how many I got right! 😕

I worked with an engineer named "Glen". Glen was the inventor of GXI, or "Glen's Expense-able Interface" with a small selection of I/O devices to choose from. It sounds similar to what your guy did, but for a different reason. None of his projects came with a budget for test equipment!

Off topic, but you've struck on a perfect name for my next online chess account! I'll drop the "you're" and add a few underscores, but that's it. Thanks.

This is pertinent to the discussion on Unicode, but more related to the meme - https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/

I had dreams of someday going to one and taking selfies with all of my LabVIEW heroes.

Hi.

Once you fix the link...

I worked for an NI Alliance Member company and signed a (legally non-binding) non-compete agreement, which meant I wasn't supposed to be poachable. I found a job opening at a company that turned out to be working with my employer on an unrelated-to-me project which I wasn't hired to take over, so I wasn't competing and jumped ship.

I'm nearly certain that you can't create a new control in a running VI, You can make hidden buttons that you show/position/resize.

After years of mergers, acquisitions and reorganization I've finally ended up in a Test Engineering group that primarily uses C#. The current environment of legacy LabVIEW systems will keep me gainfully employed (maybe) but I'm glad to be facing the specter/opportunity of learning a new language. Wish it was python, though...

I can confirm that uninstalling the later RTE resolved my problem (as did recompiling with that switch deselected). I can also say that I've told NI in the context of my currently-open-but-about-to-be-closed Service Request. If you worked with me, drjdpowell, I'd get you a cash award large enough for a nice dinner for two (or more). Here I can only say thank you. Thank you very much. Jim

I've posted this on NI's forum, but the Machine Vision group isn't particularly active. - https://forums.ni.com/t5/Machine-Vision/IMAQ-image-indicator-is-black-now/m-p/4137840#M53508 We've been running a version of a machine-vision/control software since 2012, with the latest revision being LabVIEW 2018 released a year ago. It uses two analog cameras and some digital IO, and the cameras stopped displaying the image on Friday. I can snap/grab images in MAX, but not with the LabVIEW software (or an executable built on just the image-grabbing part of the larger code.) I made a smaller program that snaps a picture and saves it to disk. This, too, fails to show me the picture but does put the picture to disk. Only, when I read the saved image (using IMAQ ReadFile 2) I get the same black-filled indicator (but it works properly on my dev PC). The problem seems to be only with IMAQ displaying the images to an image indicator. We thought that something broke when someone installed another LabVIEW program the day the problem started, but I replaced the (Win7) PC with a freshly-imaged (Win10) PC this morning and reinstalled our software along with MAX (20) and Vision Acquisition (18.5, the same as was on the original PC). This had no affect on the problem. You could have knocked me over with a feather. We've since swapped the video card, camera and NI PCI-1410 frame-grabber. I was grasping at straws here, but I'd take a straw at this point. Do you have any ideas? Any troubleshooting steps I could take?