Jump to content

Antoine Chalons

Members
  • Posts

    854
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by Antoine Chalons

  1. 9 hours ago, Neil Pate said:

    I am a bit late to the Map party. I love them though, thanks NI. 🤩

    For those that have not tried them, take a quick look. I have only used the Map a few times (so cannot comment on Sets) but the API is nice and simple. Goodbye Variant Attributes 🙂

    ditto.

    Jump into sets, they're great as well and they can be combined with maps!

    I rarely use 1D arrays anymore!

  2. Quote

    So I have been trying to think of a way to attempt to allocate a very large string with a graceful way to fail if there is not enough memory.   Has anyone else found a way to do this?

    I have not.

    Last I faced a similar case a few years ago (on a 32-bit Windows), after some discussion with the users we agreed to check the file size before loading it and if it was larger than 400Mb the soft would reject the load request with a nice message telling the user to use another soft that would split the large file in several 400Mb files.

  3. My advice is to "look into CXP", I never got round to trying the bitflow HW + driver which they claim is fully compatible with LabVIEW, CXP seems to be the future of industrial high res / high speed vision. So if you're looking to build a vision system for the next 10 years, I think you should test out bitflow's CXP option.

    I'm a bit disappointed with NI's "wait n see" approach with CXP, last I asked the answer was "we don't think the ROI is big enough". Which is a fair point but leaves NI Vision with very limited options.

    CXP open a lot of options in term of cameras.

    Good luck to you, and - again - if you do test bitflow cxp framegrabber in LabVIEW i'd love to hear how it works.

  4. 26 minutes ago, Neil Pate said:

    So out of curiosity, how does everyone else handle their name generation? Multiple cameras with multiple image processing steps each needing temporary storage. I usually try and programitically generate the name but now that I think about this thread there must be a better way that I don't know about. 

    I have a "rule" something quite basic like "VisionSystemRef_CameraName_BufferType_Index"

    For the buffer type I have a typedef with a few options :

    - "Acq" for acquisition only buffer, I never do any processing on these, they are used only to store an image that has just been acquired from a camera

    - "Save" buffers reserved to store images that will be saved to disk

    - "Proc" for processing

    - "Disp" buffers reserved for images to be displayed on the UI

    So I use the "image copy" VI a lot do to transfer image data from a buffer to another

    • Like 1
  5. 6 minutes ago, Sam2004mai said:

    Why this website suffers from broken links i cannot download any of post linked examples. can anybody help post again the MCL example with multi Glyph.

    I can download the files from this thread just fine.

    I'll try sending you a private message with the VI

×
×
  • Create New...

Important Information

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