NI cRIO IP camera support

Question

Hi,
          I am working with a cRIO 9022. Also, I have an ethernet based camera (Panasonic C210A). It should be given power supply through its converter. The converter has got 2 LAN slots and the Ethernet cables are such that, one goes to the camera and one goes to the cRIO and the camera is given power through the converter using a 9V Adapter.
          Now, when I create a VI under the target(cRIO) and try to search for this particular IP camera(not sure if it's IP camera or not), it doesn't show up in the Vision Assistant sub vi. I have the drivers for this camera installed on the HOST PC. But, those drivers aren't installed on the cRIO, the target. I am not sure if the drivers can be installed on the target also in some way. (Should the files from the Host be transferred to the Target using FTP Client, for installation)?
          The ethernet slot on the cRIO has got 2 LEDs above and below the ethernet cable. They both glow green when I connect the camera. But, I can't find the camera when I use Vision Assistant.
Can anyone help me with this issue?
Amar Makana.
Solved!
Go to Solution.

Answer 1

Hi Amar,
Let me preface my comments by saying that you should post this question here, on the Multifunction DAQ discussion board. Our applications engineering group monitors our forums, and you should get input from a DAQ supporter. In addition, you will likely get a response from our very large forum community. You would not likely get a community response to your 6216 question on this thread, since it is categorized under machine vision.
With that said, it is hard to say what might be causing these waveform breaks without knowledge of the type of signal being monitored. When you post in the DAQ thread, you should include a description of the signal being read in addition to the screenshots you mentioned. However, since you mentioned that N-samples worked, but continuous did not, that leads me to think that the read buffer size should be increased. When using low-level DAQmx VIs, you can specify the size of the read buffer, which allocates a certain amount of computer memory to read samples in from your DAQ device. Then, every time a loop containing the DAQmx read executes, it will pull this many samples out of the buffer. Also, depending on the signal type and number of signals being read, you might be seeing aliasing from not sampling fast enough, or from multiplexing error since the 6216 does not support simultaneous sampling. These are a few things to consider, and I would encourage you to mention them in your DAQ post.
Hope this helps!
Matt J.