Jump to content

JimPanse

Members
  • Content Count

    47
  • Joined

  • Last visited

Everything posted by JimPanse

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. Hello experts .... Thank you for your answers. The FPS are really 250 kHz @2048 Pixel GPU So a current graphics card e.g. 6GB Asus GeForce GTX 1060 Dual OC Active PCIe 3.0 x16 (Retail) should have a transfer rate of 15 Gbytes / s. This year PCIe 4.0 will come out with twice the data rate. At an expected data rate of about 1 Gbyte / s that should not be the bottleneck, right? So theoretically it should work with CUDA. What should be the limiting element in data transmission? In the USB3.0 variant, the USB3.0 interface is the data bottle neck. This should max. 640Mbyte
  7. Hello and thank you for your answers. Then an FFT of a line with 2048 pixels and corresponding parallelization in 4μs would be possible. As far as I know, the mentioned NI FPGAs run at 400 MHz. The question that arises is which type of FPGA is suitable? Because he has a decisive influence on the costs. According to NI, the FFT runs in 4 μs (2048 pixels, 12bit) with the PXIe 7965 (Virtex-5 SX95T). The card unfortunately costs 10,000 € and would probably blow up the project. Therefore, I would like to know if it also with the variants: Kintex-7 160T / IC-3120 (USB3) Virtex-5
  8. Hello experts, I have a camera application (USB3 or camera link) and would like to do an FFT analysis of a line with 1024 or 2048 pixels. Data type U8, U16, I16. The processing must be very fast due to the process. The processing time should not take longer than 4μs. It would be conceivable to process with an FPGA, e.g. Kintex-7 160T / IC-3120 (USB3) Virtex-5 LX50 / PCIe 1473 (camera link) or on the GPU using CUDA. I also heard that Labview 64 bit FPGA should be much faster. Does anyone know if the processing time of 4 μs is possible with the describe
  9. Hello Rolf, thanks for the expanded view. If I configure a desktop PC with a Pharlab Labview RT system I need the appropriate license. NI also has to pay for this eventually. These costs should not be incurred in Linux. Licensing costs for example, DAQ should not apply also. These costs should be compared with the hardware procurement. Therefore, some applications would be implemented with a desktop Linux NI RT system. Or did I miss something? A pleasant start to the week, Jim
  10. Hi Experts, there is a guide, experience or an image with which you can configure a desktop PC to a Linux NI RT? a pleasant week, Jim
  11. Hi Experts, has someone brought the NI Linux RT kernel with a desktop PC to work? Similar to the PharLab operating system. Or is there a how to create the NI Linux RT operating system itself? Otherwise, I would be very interested in a working group that developed the NI Linux RT operating System for Desktop PC´s. a pleasant start to the week Jim
  12. Hello Experts, I would like to realize an encoder triggered analog acquisition with a PCI-6220 (A = PFI8, B = PFI10, Decoder = X4). At each linear change of the encoder is to be done a anlaloge detection. In principle, the encoder is the analog capture triggers. In the Labview examples I can not find any solution. Google could not help me. About a link to a solution or a description how to configure the analog trigger, I would be very grateful. Thanks in advance, Jim
  13. Hello Experts, it is possible to synchronize the distributet clock from a PXI RT (Phar Lap ETS) EtherCAT Master with a third party slave (Beckhoff EL6692 or el6695 http://www.beckhoff.de/default.asp?ethercat/el6695.htm)? Thanks in advance, Jim
  14. I like the solution with the Mutltimaster EtherCAT system. It also enables synchronisation of the distributed clocks. A LabVIEW RT EtherCAT master and a Beckoff EtherCAT master. Between the Bridge Terminal EL6692. According to http://forums.ni.com/t5/Industrial-Communications/LabVIEW-ECAT-Master-communication-problem-with-a-third-party/td-p/3045981 log it to work. Are there things that speak against it?
  15. Throughput is about 128 bytes per message.When it comes, it should be an industry-standard solution. Another approach would be a multi-master system. With the EL6692 http://www.beckhoff.de/default.asp?ethercat/el6692.htm http://www.ethercat.org/de/products/E2DC6EE8DB5D4740BE8A0E4FCA61A309.htm EtherCAT bridge terminal probably can communicate deterministically two EtherCAT Master. Is that right? Then I could operate the LV RT target as EtherCAT master.
  16. http://www.ethercat.org/en/products/92F6D9A027D54BABBBEAFA8F34EA1174.htm In prinzipell it would be the right way. The PCI Interface could i solve with LabVIEW RT for desktop. But I dont think, there is a driver for the card that works under pharlab ets??? The latency is in the range of 10 ms. The latency period should be constant. However, the jitter should be no greater than 100 µs. Can I achieve this with Modbus TCP? Or is there a other faster RT interface from Labview RT to a Beckhoff control?
  17. Hello and thanks for the help, in the RT system several cameras incl. image processing are required. This is not possible with the 9144. One imaginable solution could with Anybus X-gateway with Its Modbus RTU Slave / EtherCAT slave. Modbus under LabVIEW RT was supposed to work. What do you think? Is there any other indirect solution? Thanks in advance
  18. Hello Experts, I would like to operate a Labview RealTime system (PXI) as EtherCAT Slave. The master system should be a Beckhoff control. Is it possible to operate the Labview RealTime system as EtherCAT slave? Thanks in advance
  19. Hello hooovahh, Thanks for your reply. I use the DAQ card because it is there. I have found no reason why it should not go with the DAQ card. If it does not work I'm going to implement the Arduino. Unfortunately, the question remains as to why the current approach is not working.
  20. hello, I try with the DAQ card PCI 6220 via the digital outputs LINE0: 2 (CS, SCK, SI), the digital potentiometer MCP 41XXX over the SPI interface to control. Unfortunately this does not work. I have a Vi to created the digital signals (picture) and another Vi to output (picture) them on the DAQ card. Phase and polarity of the SCK clock can I change. Unfortunately, the potentiometer can not be controlled with this program. Has anyone a Idea where the problem might be? Thanks JimPanse
×
×
  • Create New...

Important Information

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