Jump to content

JimPanse

Members
  • Content Count

    42
  • Joined

  • Last visited

Everything posted by JimPanse

  1. Is there an official statement from NI how long Labview will be supported?
  2. so, if you look at the share price. https://www.nasdaq.com/de/market-activity/stocks/nati you can see a nice separation there. until 2016, ni was reasonably solid and had a slow steady growth. in 2016 they decided to make everything more efficient and lived at the expense of their customers. at some point the customer notices the reduced performance and looks for an alternative. which is reflected in a share price decline since 2018..... a bold summary... this roughly reflects the correlation of the share price with my personal experience with ni.
  3. I found the strategy of approx. 10-15 years better for my needs. if you continue to operate the current strategy like this, then I won't give labview much longer. that is the view from my field of application.... that might be enough for me until retirement. i would be interested to know how high the profit per employee of ni was 10-15 years ago and how it is now. then you could estimate whether it is a successful course or whether it is going down.
  4. I also think that it is the strategic staff that is leading labview in the wrong direction. the concept of labview is certainly unique and has its justification. the strategic decisions are simply the wrong ones. the management should be fired and a few innovative engineers should be left to make the decisions. there are enough new technologies waiting to be implemented with labview.
  5. Every now and then a small improvement comes along. a real innovation was the leap from version 7x to 8x. I think fpga is not bad either, but it is actually too expensive and there is no real support for it either. I work a lot with realtime and vision and I have to say that nothing has happened since usb3 vision. where, for example, are the coax press frame grabbers? also that pharlab was discontinued without an alternative for desktop pc's. that's why i switched to labview linux and built the realtime system myself under linux. and if you ever need support for labview linux you're really on
  6. Hello experts, I'd like to make a general assessment. I have been working with Labview for about 20 years and occasionally contact Ni to solve technical problems or to find out about and buy products. I have been observing the trend that service has been getting worse and worse over the years for years now. I have not seen any real new developments in labview over the last 10 years. with the termination of nxg and the associated waste of resources, I have the impression that ni has to save money at every corner to keep the shop running. of course this is at the expense of customer support
  7. Hello, experts, I am just taking my first steps with Labview on Linux. For the implementation of various projects I am missing the drivers for Linux as I am used to from Windows or Pharlab. I have heard that Imaq and Vision will come at the end of this year.... all without rifle. Which image processing tool would you recommend for Linux? For Ethercat I have discovered the following : https://openethercatsociety.github.io/doc/soem/index.html Does anyone have any experience with this or are there already Vi`s for Ethercat under Labview Linux? Furthermore I would lik
  8. It is about an image processing where the result is a parameter for a control. Here I need a real-time in the range of 1 ms.
  9. Is it possible to make Windows 10 realtime capable, so that i can use Vision?
  10. I could imagine that RT Linux from a PXI system also works on a PC. This will certainly not be allowed by licensing law.
  11. This means that RT Linux for Desktop PC is theoretically possible. Can I buy a Linzens from RT Linux for Desktop PC´s? And how long will Pharlab ETS be available?
  12. Hello, experts, in the current description of the NI Vision Acquisition Software it says: http://www.ni.com/pdf/manuals/375130k.html Deprecated Features ◾NI - IMAQ 19.0 .... ◾Removed support for LabVIEW Real-Time targets running Phar Lap ETS OS Will the OS Labview Real Time (Phar Lap ETS OS) be discontinued and is there an alternative based on Linux? a good time Jim
  13. Hello, Rolf, thank you for your message. I don't know if I understood it right. The software should be developed under Windows. The program created in this way runs independently on the FPGA and communicates via RT FIFO with RT? If I understood that correctly. Is there an example or a forum post where this is discussed? A nice week start Jim
  14. Similarly I tried to integrate the framegrabber under RT. Since the framegrabber is not found there is no RIO reference. I don't know how this works. A direct image processing is absolutely necessary. And also the data exchange of the results with the fieldbus. The question (which I cannot answer yet) is whether you need an FPGA or can implement it with CUDA. Since I already have experience with FPGA, I chose this solution. I have no experience with CUDA. If I would use CUDA then Windows is mandatory. I don't think CUDA works on RT. The advantage with CUDA would be that you don't
  15. There is currently no 100% definition of the requirements. This is all in a state of flux. Full or Extended Full is required. Power over CL is not mandatory. I need real-time for communication with the 5 most common fieldbus Systems. I didn't understand your suggestion to transfer the FPGA code to the frame grabber under Windows and then use it under RT. How should the communication under Labview Realtime with the frame grabber work if the frame grabber is not recognized under RT?
  16. It can't be that the specification says that the frame grabber is supported and then it doesn't work. I can't afford such a procedure with my products. I could also imagine a different solution approach, e.g. with an additional extension. Make Windows real-time capable. But here I am still at the beginning. Providers who promise this are among others www.intervalzero.com/ https://kithara.com/ www.sybera.de/ …. There are certainly many other providers here. Advantage: The Framegrabber works under Windows. No Labview Realtime would be necessary anymore and the a
  17. Hello, bbean, thank you for your answer. The frame grabbers PCIe 1477 and PCIe 1473r work under my Windows System. I had the frame grabber PCIe 1473r on loan from NI and can't test it under Labview Realtieme anymore. The frame grabber PCIe 1477 does not work with Labview Realtime on my System. According to the specification: http://download.ni.com/support/softlib//vision/Vision Acquisition Software/18.5/readme_VAS.html NI-IMAQ I/O is driver software for controlling reconfigurable input/output (RIO) on image acquisition devices and real-time targets. The
  18. Hello, experts, it's a shame that nobody has had any practical experience with the frame grabber under LabVIEW REaltime (Phalab). The documentation contains the following, among other Things: http://download.ni.com/support/softlib//vision/Vision Acquisition Software/18.5/readme_VAS.html NI-IMAQ I/O is driver software for controlling reconfigurable input/output (RIO) on image acquisition devices and real-time targets. The following hardware is supported by NI-IMAQ I/O: ....... NI PCIe-1473R NI PCIe-1473R-LX110 NI PCIe-1477 This means that the f
  19. Does anyone have an idea what you need for the framegrabber to work under LabVIEW Realtime? Has anyone ever made one of the two framegrabbers work under LabVIEW Realtime? Greetings, Jim
  20. The FPGA tool is also available. The frame grabber runs on the same PC under Windows 7 (other hard disk). Does anyone have an idea why the frame grabber is not recognized in realtime? a nice weekend Jim
  21. The frame grabber requires the Imaq IO 18.5. According to NI, Vision Acquistion is supported by Labview Realtime (Pharlab). And all the hardware included in it http://www.ni.com/download/ni-vision-acquisition-software-18.5/7840/en/ It would be interesting to find out if anyone was able to integrate the frame grabber (pcie 1473r or pcie 1477) under Pharlab. Then there would be hope then :) a pleasant time Jim
  22. Hello, experts, I am trying to put the frame grabber PCIe 1477 into operation under Labview Realtime (Desktop PC). Unfortunately the card is neither displayed in the MAX nor in the project. As an alternative the frame grabber PCIe 1473r LX110 would be conceivable. Has anyone ever worked with such a frame grabber under Labview Realtime? Or does anyone know what to consider to make the frame grabber work with Labview Realtime ??? Many thanks for the numerous answers Regards, Jim
  23. Hello experts, I've figured out how it works by now. A code on the FPGA side like on the PCe 1473 is no longer necessary. The required VI´s on the host side for the serial communication can be found at: \LabVIEW 2018\examples\Vision-RIO\PCIe-1477\Common\CL Serial NIFlexRIO Merry Christmas Jim
  24. Hello experts, I am interested in the frame grabber PCIe-1477. http://www.ni.com/de-de/support/model.pcie-1477.html Unfortunately, the examples are not complete in my opinion. At first glance I do not have the serial communication for the parameterization of the camera. (Requires: NI Vision Acquisition Software 18.5). Does anyone have experience with the frame grabber and how was the parameterization done? Have a nice Weekend Jim
  25. Thanks for the friendly answer! The FFT calculation does not have to be done every 4 μs. At that point I should have contributed more. It is a 250 kHz continuous detector and this processing must be guaranteed. It would be quite conceivable to store a certain amount of data and then parallel to processing. For example ... So if an FFT calculation takes 100 μs, you could cache 25 measurements and calculate them in parallel. If that would be feasible .... The question arises, which low-cost FPGA is able to store the data between and calculate it in parallel? Simulation can determine
×
×
  • Create New...

Important Information

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