jcarmody

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?

Use google: site:lavag.org wmf

I particularly like that the Magic Delay Fairy QD Plug-in is prominently displayed, only one click from the home page.

I don't believe that your intention is to loop through all of the hard-coded PINs twelve times. Remove that constant to the For loop and let the tunnel from your array of PINs auto-index. I'm confused about how you've got a 1-D array of Booleans being indexed into a 2-D array, but your Front Diagram indicator looks like only 1-D. Surely my eyes aren't so bad that I can't see that green wire getting bigger outside the loop...

I had experienced the same (similar) thing, but I just got a new computer and the issue appears to have gone away.

There's an entire forum dedicated to this discussion here - https://forums.ni.com/t5/Certification/bd-p/Certification Good luck!

I've done it using a parameterized query:

I think it was in the early '90s that I took a Fortran class. People only a year ahead of me had used punch-cards; I'm glad I missed that boat.

That brings me back to my time learning BASIC programming on my VIC-20 (in the early 80s).

We use the JKI State Machine, but have begun adding DQMHs. My last project launches up to twelve of them; my current project launches one or two. Both depend upon the number of pieces being tested (and were written by my CLA-colleague). I wanted to use JKI SMOs, but was given DQMH (and am happy about that, too).

Aren't customers just the worst? Well...

There's an OpenG vi that does that - "Number to Proper English Text.vi". You can download here - http://sine.ni.com/nips/cds/view/p/lang/en/nid/209027

Remove any wires connecting them.

I listened to both of them this morning. I enjoyed the content and format, and look forward to more episodes.

I found this while browsing Twitter - https://anchor.fm/quickdrop-podcast Anybody know who Jonathan Hobson is? Is he (are you) on the fora? Good luck! https://quickdroppodcast.wordpress.com

Kidde Aerospace, part of United Technologies Aerospace Systems, has an opening for a really good LabVIEW/CVI engineer. You'll find all the information about it on the UTAS site. I'll put in a good word for you if you're well-known on these fora.

Infilict a diffusing drama.

That's the second tool out of our IT support company's bag.

Reinstall the OS?

I've had trouble on new installations where I've needed to install the Microsoft Database Engine to get my LabVIEW programs to work. This was only on PCs without MS Office, but I thought it was worth mentioning.

https://forums.ni.com/t5/LabVIEW/ADO-Error-0x00000001-Argument-error-The-table-name-given-is/m-p/3712255#M1044410 Answered.

Paintainable?

I remember the good old days where all I needed to do was get added to an admin group and I could do anything I wanted. The pendulum swung so far away from that extreme to the point where I had to launch a two-week workflow to get the simplest of things done. The pendulum is near a sane point now where I can do stuff (I'm installing NXG right now). Have you heard of Viewfinity? It makes the approval to install something take as long as your boss takes to respond to an email. Life is good again.