GigE vision on OR cRIO-9068

Similar Questions

• Do IMAQdx and NI GigE Vision 2.0 material support?

  Hello

  From my brief research, GigE Vision 2.0 has features very nice that I'm at the end which are not supported by previous GigE Vision 1.x standards:

  • Compression on the side of the camera
  
  
  • Timestamp and sync IEEE 1588 (PTP)

  OR those taking? If not, are there any plans to add support in the near future?

  Thank you!

  Hi again,

  Thanks for the extra frame.

  Assuming that your only using the camera is saving JPEG images on the disk, and you are concerned about the performance of the acquisition system, I think that an IP camera might be a better choice. These cameras acquire images compressed, so you can very well save the direct-to-disk with no extra charge. This will save time and bandwidth of the network processor. The bandwidth would be nice because you could probably just run 6 cameras in a gigabit switch and connect to a port on the PXI chassis instead of several 8234 ports. This is possible because not only if bandwidth is reduced, but the IP cameras can use TCP and sharing bandwidth much more enjoyable that can cameras GigE vision. To save the raw images on the disk, you can use the IMAQdx VI "Get Image Data", which is a JPEG file that you can save directly to an IP camera.

  Regarding the time stamp data, depends on the accuracy required. Since you recorded all the time after that image returned, is quite imprecise because it is not really correlate with the acquisition time. You might get a more exact time in two ways: record IMAQdx a CPU timestamp on receipt of driver that you can use (useful if the CPU is synchronized to GPS/NTP or similar) or you can use a timestamp saved in the image itself in the form of metadata (GigE Vision and IP cameras can do that). I think the Basler IP cameras can use NTP and testify to the time stamp for metadata EXIF JPEG images that you can extract. This mechanism is of course much more precise because it eliminates the delay/jitter of transmission at the time. If you have a few requirements of precision (microsec, milliseconds, seconds?), it would probably give a better idea of what your options are.

  I suggest you take a look at the range of cameras from Basler IP. You can not control the parameters of the image directly in the IMAQdx driver (you must use their web interface, or write additional HTTP code), but once you have the configured device it will keep these settings.

  http://www.baslerweb.com/en/products/network-cameras/IP-fixed-box-cameras

  It is likely that the cameras will be more expensive that some cheaper GigE Vision cameras can be, but I suspect that you could save enough on other system costs will in this way to make up for it. In my opinion, doing compression JPEG on-the-fly with 350 + MB/sec of camera raw data could be difficult, unless you had a tough multi-core system.

  Eric

• cRIO 9068 + Scan Engine Support error - even if it is installed on the cRIO, after the deployment of error says his lack

  All,

  I have a cRIO-9068 I try to use the scan mode for. I have intalled all the latest drivers and software as explained. However, when I put my chassis to scan mode, then select deployment all, I get this error on my chassis and all my modules:

  "The current module settings require a NI Scan Engine support on the controller. You can use Measurement & Automation Explorer (MAX) to install a software package recommended NOR-Rio with NI Scan Engine support on the controller. If you installed LabVIEW FPGA, you can use this module with LabVIEW FPGA by adding an element of FPGA target under the chassis and drag and drop the module on the FPGA target element. »

  Everyone knows this or know why labVIEW does not recognize that the software is installed on my cRIO or is it not installed correctly?

  AGJ,

  Thanks for the image. I saw a green arrown beside all my pictures of chip and it seemed that meant that the software wasn't really being installed. I formatted my cRIO and did a custom install. My problem was that I had the two labview 2013 and 2014 installed and the cRIO put conflicting versions of software. After doing a custom installation and choose only the versions of 2014, my picture now looks like yours!

• The model Interface Toolkit does support the cRIO-9068 again based on Linux?

  Hello, I have a cRIO-9068 and need to integrate a Simulink model in my controller. The model Interface Toolkit does support the cRIO-9068 again based on Linux? Besides, don't Veristand? This page assumes that it is not:

  http://digital.NI.com/public.nsf/allkb/2AE33E926BF2CDF2862579880079D751

  Thank you

  Hi Southern_Cross,

  Based on the readme:

  http://digital.NI.com/public.nsf/allkb/D3F40C101B66128186257D020049D679

  It seems that it is now supported! These resources should provide a few more details:

  http://zone.NI.com/reference/en-XX/help/374160B-01/vsmithelp/mit_model_support/

  http://digital.NI.com/public.nsf/allkb/E552B0CD4E48215586257DF7005BE055

  Please note that NI VeriStand 2014 can't stand it targets NOR Linux in real time.

  Kind regards

• How compile/link xnet with eclipse for the cRIO 9068

  Hi all

  I use a cRIO 9068 with a NI9862 (DRUM unit).

  I'm programming in C/C++ with Eclipse on windows

  Without seeking to CAN access via xnet, the C app compiles and works very well on the 9068.

  Now, I want to use xnet functions to access the CAN.

  I found a nixnet.h in \Shared\ExternalCompilerSupport\C\include, then the compiler is convinced.

  But the linker can't find a library (I tried "nixnet" and "xnet") or don't find a library for cRIO xnet 9068 on my hard drive.

  Where can I find this library? Do I have to install another driver in addition to the normal driver xnet xnet (I installed, version 14.0).

  Thanks for your response in advance

  Hello!

  the driver Readme reads as follows:

  The NOR-XNET software supports Microsoft Visual C/C++ version 6.

  But for Linux-RT based targets (cRIO 906 x and x 903) in combination with modules XNET (986 x) I found a useful resource that indicates that you should be able to include the header "nixnet.h" (as apparently already do you) and ' link against libnixnet.so at run time to obtain the appropriate symbols.

  You should find the file according to the following folder:

  C:\Program Files (x 86) \National Instruments\RT Images\NI-XNET\Linux-armv7

  Best regards

  Christoph

• GigE Vision all-in-package

  Hello

  I am looking for a solution to a simple problem. I designed the camera IRLS, work GVCP, camera stream UDP packets on request from Max NOR, but these packets are not acknowledged as data and Timeout 0xBFF6901B mistake. Enclosed I send my UDP all-in-package. The same happens on my laptop and the industrial controller WITH Intel network interface. Firewall is still disabled. On what parameters NI Max decides, the current package is the data package? UDP Port?

  I put the 1 value in the XML of my camera and my camera should support All in transfer. Should I put elsewhere too?

  What should I check?

  Kind regards

  Linus

  Hi Linus,

  This feature is new to 2.0, GigE Vision and not yet supported by IMAQdx. By specifying, this mode is optional on both sides and the application software is needed to activate it (SCCFGx) until the device is allowed to use this mode. As IMAQdx never allows it, the camera is required to use the transmission of standard packages.

  Eric

• XML file for GigE Vision camera

  Hello

  I'm working on a model of GigE Vision camera. It should be very simple linescan camera. I put in place the necessary set of registers GigE Vision, can communicate with the camera in MAX. The problem is that I need creata this XML file for the camera. There is this here XML file:

  http://www.EMVA.org/CMS/upload/standards/GenICam_Downloads/SFNC_Reference_Version_2_0_0_Schema_1_1.x...

  What should I do with it? My first version of the camera will have 2 functions: turn on and off I'm confused, because the model xml file has many functions, I don't really have. Should I remove them? Or leave it inside with default values? That she needs a configuration minimum XML file?

  Kind regards

  Linus

  Hi Linus,

  If you look at the GigE Vision specification, you will see that there is a minimal subset of functionality that must be present for the camera be declared compliant. That's all what IMAQdx will need for the camera works fine. All other functions in the XML file that you downloaded are part of the SFNC (features Standard Naming Convention) defines the names/behavior for common characteristics that are often found on machine vision cameras. As a general rule, cameras implement a subset of these features. You should not let any features that are not implemented in the XML because it would be just confused because they would do nothing.

  Eric

• Cannot write negative values on server modbus on cRIO 9068

  Hello everyone,

  I'm moving a project from a platform of 9114 cRIO a cRIO9068, the reason for a difference of heavy in terms of power CPU, memory, performance FPGA etc...

  Real time I deploy a modbus TCP server, and I publish just I16 data.

  The problem comes when the program tries to write a negative value to a binded on modbus variable. This variable is in the same format (I16), the program could write negative values, between 0 and -32768, but whenever the modbus force set to zero.

  I tested the modbus also with the 'system of distributed OR 2014 Manager' but always impossible to write negative values on I16, but I can if I consider the data as I32!

  (see files)

  Furthermore, I deployed a modbus server on my PC and in this case, everything is fine.

  More information:

  I work with labView 14.0f1.

  The cRIO are installed 'Labview RealTIme 14.0.0' and 'server Modbus I/O 14.0.0.

  I tested the feature on three different cRIO 9068 with the same result.

  I think it's something wrong with cRIO 9068, can anyone help me?

  Thank you

  MZ

  Hi, Marcello,.

  I was able to reproduce the problem cRIO 9068 and it look like a CAR (corrective action request). I've opened a request for Corrective Action (AUTO ID 511039) to report the issue OR R & D.

  Have you tried to implement MODBUS slave on ana MODBUS master PC on cRIO? I tried and it works even with I16 data types.

  I hope this will help you.

  Kind regards.

  Claudio Cupini

  OR ITALY

  Technical support

• I can connect an NI MXI-Express RIO 9154 off the cRIO-9068 serial?

  I would use the cRIO-9068 a new system but will need a second wreath off the first chassis. Can I use NI MXI-Express RIO 9154? If so, how to connect the MXI cable until the 9068?

  Not the MXI Express, but you can use EtherCAT: chassis NI 9144 8 locations EtherCAT Slave for C series i/o Modules

• use of devices high cRIO 9068 FPGA

  Hello. I have problems with my cRIO 9068 (dual-core, Artix 7 667 MHz), which uses a lot of FPGA resources. I did a little VI FPGA (LabVIEW 2013 SP1) allowing USER FPGA led to two colors (green and orange) for 500ms and then it is off for another 500ms. use of device Watch report 9193 records used(8.6%) and 9744 LUTs (18.3%). I adapted the VI even for a cRIO 9072 (Spartan 3 - 1 M) which have been allotted to me and use of the device is much lower: registers used: 443(2.9%) and read: 644(4.2%) - please see attachments!

  I used the XNET library in the past with the 9068 and 9862 CAN Module: since I knew that these libraries use the FPGA space, I removed XNET 1.8 cRIO software before this test. Before removing, use of FPGAS was even higher!

  Can someone tell me how can I reduce the resources used to 'normal '? Thank you!

  Hi Lucien,.

  The increase in the use of core resources that you see is normal for the family of targets Zync. Try to compile white VI for each (no user written code LabVIEW). You will notice that the Zync platform always uses an important part of the fabric (which targets Zync is used).

  This behavior is due to the very different architecture of the family of chips Zync. As the FPGA and ARM processors are on a shared matrix, a large part of the logic and OR treatment implemented in ASICs Spartan/Virtex advice should be moved on the FPGA itself.

  You should also notice that, although there is an increase in the use of FPGA base fabric, the gross number of LUTs/flip flops at your disposal as a user is much greater on Zync objectives than a Spartan comparable unit.

• Translation in MAX problem when you configure the SSH server on a cRIO-9068

  Hello

  In my view, that there is a problem with the German translation of the remote switches max on the new cRIO-9068. When you look at the English Version, you see "Enable Secure Shell Server". In the German Version, you see "Secure Shell Server deaktivieren" which meens to disable the SSH server. The box did the same features, so after you disable SSH in can access. This it seems that it is probably just a translation problem.

  I have attached two screenshots.

  Andreas

  Thank you Andreas.

  This has already been supported in Nov 2013 and should be fixed soon.

  Marco Brauner NIG.

• cRIO-9068 & OR-time

  I have the system test with a cRIO-9068, a cRIO-9024 (w / 9114 chassis) and an expansion chassis 9146.  None of them are even near being synchronized, and it's a bit frustrating.

  How can I synchronize the 9024 grid and the grid 9068?  I have NEITHER time installed 1.3 on 9024 system, but I don't see an option for time installed on the cRIO 9068.  CRIO-9068 does support the IEEE-1588 protocol software provided by the addon of NOR-time?

  In the meantime, you could Explorer using an implementation open source on the 9068, like Pgwp1588. With this solution, I think you should probably reach synchronization on the order of tens of milliseconds.

• Call to a shared library a VI on a target NI Linux RT (cRIO 9068)

  Hi, I wrote a very small shared library (.so) with Eclipse (toolchain 2014), which essentially serves as a wrapper for more complex, but I am having problems with the call go to in LabVIEW RT on a target Linux RT - specifically, the cRIO 9068. First: the library was copied in/usr/lib and ldconfig has been correctly implemented. More important yet, I have also written a C program (using Eclipse as well) that calls the single function currently implemented in the shared library: this works perfectly, both in Eclipse and you connecting directly on the cRIO with a Putty terminal. So I guess the shared library itself is ok and can be called from code/external programs. Now, dating back to LabVIEW (2014 here btw). Here's where things get difficult, I guess. Initially, I had the symptoms listed here--> http://forums.ni.com/t5/LabVIEW/How-to-create-a-c-shared-library-so-for-linux-real-time-for/td-p/302... who prevented me from actually run any code on the target of RT. Then I changed the call library function node: various tutorials suggest to put name_of_library.* in the path text box or the name of library, but unfortunately it doesn't seem to work, so I had to put the name and the extension too. But it still produces the error below ("the name of the function is not found" etc.) So I check the box 'specify path on diagram' and add/usr/lib as a parameter to the node library function call: now the VI can work and is actually transferred to the target of the RT... but the cluster of output error returns error 7, which is a kind of "File not found" error. However, I believe that this error message is misleading: indeed, if I try to debug remotely this library shared under Eclipse, I am actually able to pause it. and when I press the Pause button on the debugger, the goal of RT VI pauses, then continues as soon as I press the Resume button, I'm stuck... I tried searching forums and Google as well, but I have not yet found a solution. Any ideas on what's going on? Moreover, I can add more details if needed.

  Problem solved, it was a bad configuration of the node library function call which prevented the actual library (.so) to be called.

• Connection of the GigE Vision camera

  Hello

  I develop a GigE Vision camera.

  I want to connect GigE Vision Camera to NIMAX.

  When you first connect GigE Vision camera, I can see the NOR-IMAQdx list devices. ("cam0:mycamera")

  When I click on "cam0:mycamera", a the IMAQ error has occurred.

  Error message is "cannot load the XML of the camera.

  Attached file is the package that was the problem.

  MAX OR send command "Read memory" to retrieve the device XML configuration file.

  (Package no. 11, 13: address 0x200, 0 x 400 memory read command)

  GigE Vision camera send response.

  (No. 12, 14 package: XML URL first choice, second choice of URL)

  I think the number of package 12 and 14 are erroneous data, but I can't find the point of evil.

  Advice me please on this issue.

  I would be greateful to receive the sample package.

  Thank you.

  Hi hkgige,

  These questions can be better adapted to the Committee mailing list GigE Vision standard, I suppose that your company would be a member to develop a device with the GigE Vision standard.

  However, I take a look at your track of package and I don't see anything that looks obviously incorrect. One of the reasons why the software could stop after reading the two URLS, is that he thinks he has already downloaded the file previously. These are cached in a directory on your local system (usually C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data\XML on Vista and Windows 7). Check if you have the XML file for your camera.

  The error you get usually indicates GenICam has some difficulty in parsing the XML of your camera. If you join the XML itself, I could see if this is the problem.

  Eric

• adapt the code on CRIO 9068

  Hi all

  I have a code (supposed) job working on NI 901 x and x 900 dish-forms. I want to adapt to run on NI 9068.

  I can connect to my CRIO 9068 but the local chassis is stil named (NI 9101), I can change it for CRIO 9068 but compilation failed during the compilation of the code (which is a simple use of NI 9870).

  What can I do to adapt my code for CRIO 9068?

  Kind regards

  SASA.

  I recommend the establishment of the new target of your project and then drag old cRIO target to the new everyingthing.  Then delete the old target.  You can recreate your specification of generation.