Jump to content

jcarmody

Members
  • Posts

    947
  • Joined

  • Last visited

  • Days Won

    39

Posts posted by jcarmody

  1. 21 hours ago, dadreamer said:

    no good TL;DR was invented. You

    Did ChatGPT make a passable TL;DR?

    Quote

    The author of the article discusses their exploration into creating callbacks in LabVIEW using .NET delegates. They explain that they initially wanted to create a .NET event at runtime but found it to be impossible. They then investigated the LV native Register Event Callback node but ran into some challenges. They eventually discovered a middle layer generated by LabVIEW that converts native calls to VI calls using the NationalInstruments.LabVIEW###.dll assembly. They were able to use this assembly to call a delegate and successfully invoke a callback VI. They provide an example of how to do this and note that while it is possible, it involves several hacks and may not be suitable for real-life applications. They conclude that this information may be useful as a reference for future development ideas.

     

    • Like 1
  2. 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.

  3. 2 hours ago, drjdpowell said:

    it is easy to add additional parent levels that represent only simple capabilities

    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

  4. On 4/9/2022 at 7:24 AM, ShaunR said:

    [...]

    So he designed a 64 channel card with 32 digital in and 32 digital out that could sink 3 amps per channel. [...]

    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!

  5. 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. :P 

  6. 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...

  7. 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

  8. 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?

     

  9. 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...

×
×
  • Create New...

Important Information

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