Jump to content

Antoine Chalons

Members
  • Posts

    854
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by Antoine Chalons

  1. omg... hp calcs, i hated them! I was more of a TI-8x guy my first coding experience was on a TI-80 in 1997 😱
  2. I'm parenting today, so wait a bit for screenshot, but let's say you have 2 1d arrays of string and you want to compute the intersection or the diff, how do you do? Also open the vim "remove duplicate from 1d array" in the array palette, it uses sets. And check this https://forums.ni.com/t5/LabVIEW-APIs-Discussions/Tree-Map/td-p/3972244?profile.language=en
  3. ditto. Jump into sets, they're great as well and they can be combined with maps! I rarely use 1D arrays anymore!
  4. Neil, can you explain what made you leave Bitbucket for GitHub?
  5. I very much agree with the need for scripting. It seems some folks at NI think that it's enough if we can use c# to script... almost funny...
  6. which begs for the question : will LV 2020 be released in august 2020 xor at next NIWeek?
  7. https://forums.ni.com/t5/NI-Blog/Designing-LabVIEW-NXG-Collaboration/ba-p/3854567 And as for NXG, it's supposed to be better but not perfect... not sure what that means.
  8. i love your member name 😂 There is a dedicated NI GDS section on NI's forum, maybe it would be a better place to ask for support : https://forums.ni.com/t5/GDS-Goop-Development-Suite/gp-p/5050
  9. Has LAVA search ever worked? Maybe before the big crash, but after that, definitely not. I always use google to search on LAVA with site:lavag.org dll
  10. WOW, thx for sharing this, it looks great! Is there any OS restrictions? I'm thinking about NI Linux RT.
  11. pre-2010 I used one on a project (it was a firewire camera at the time), it was to check the temperature of a incandescent object. nothing too fancy.
  12. Which camera model are we talking about? I believe the recent ones are GigE & GenICam compliant so the set attribute vi from IMAQdx with the correct attribute name (to be found in the camera user manual) should do the job.
  13. it's ok to cross-post, but please mention it : https://forums.ni.com/t5/LabVIEW/camera-postion-stuck-in-3D-picture-control/m-p/3989985#M1138502
  14. 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.
  15. Do you really need/want to support 32 bit? I mean... if it's for vision, you probably use a large size of memory, no? I wish I could offer my collaboration but calling external code is not really my cup of tea, so I'd probably be mostly useless anyway. If you are interested in getting in touch with tensorflow users to have their feedback, get in touch with me via PM.
  16. 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.
  17. I've never tried that, do you have a link to the thunderbolt extention specs? I'd be curious to know if it works well. I think camera-link is not the best option for new product design, my first advice would be to look into CoaXPress. Plus NI-PCIe 1430 and 1433 almost went EOL about 18 month ago.
  18. Graftek Imaging the website does give a few words about the history : https://graftek.biz/aboutus
  19. 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
  20. I can download the files from this thread just fine. I'll try sending you a private message with the VI
  21. When I had to pick one, the options I considered were : DQMH AF JKI SMO G# ALOHA my own that would be much better than all of the above combined I picked DQMH because I love the API tester the scripting tools, also I feel there is a somewhat large community adoption and support.
  22. NI offfers an electrical power toolkit : http://zone.ni.com/reference/en-XX/help/373375G-01/
×
×
  • Create New...

Important Information

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