Similar Questions

• No resource VISA in Labview but all present at MAX

  Hello

  I am unable to find any resource VISA of LabVIEW, however, all materials are available and functional in MAX. I just installed a PCI-8433/2, but also a BOBBIN NI PCI-8512 / HS card. As part of the installation, I think that MAX has been upgraded to version 4.6.2. I will attach the report of max configuration for those who are interested. I work with LabView 8.2. I also uninstalled an agilent GPIB card and thus the NI GPIB card is the only controller and GPIB0... instead of the card of agilent.

  I had a similar problem before that it was the result of a corrupted database, but I was unable to find this issue on the forums this time and I don't get any errors. Just an empty control VISA resource.

  Any suggestions would be greatly appreciated.

  Nate

  MAX Configuration report

  2010-12-27 13:35:05

  Summary of MAX

  • My system
    • District data
      • POUVEZ channels
      • NOR-DAQmx tasks
        • V1P1V2P2
        • V3P3
    • Devices and Interfaces
      • GPIB0 (PCI-GPIB)
        • Instrument0
        • Developpement1
        • Instrument2
        • Facility.3
        • Instrument4
        • Instrument5
      • VISAS various resources
        • GPIB0::INTFC
        • GPIB0::16:INSTR
        • GPIB0::2:INSTR
        • GPIB0::22:INSTR
        • GPIB0::7:INSTR
        • GPIB0::10:INSTR
        • GPIB0::27:INSTR
        • GPIB0::3:INSTR
      • Network devices
      • NOR-DAQmx devices
        • NEITHER USB-9481: "Dev2.
        • NEITHER USB-9481: "Dev1".
      • NOR-XNET devices
        • NEITHER CAN PCI-8512 / HS
          • CAN1
          • CAN2
      • PCI-8433/2
        • PORT1
        • PORT2
      • (Unidentified) PXI system
      • Series & parallel
        • COM1
        • COM6
        • COM9
        • LPT1
    • Scales
    • Software
      • IVI Compliance Package 3.3
      • LabVIEW 8.2
      • LabVIEW Run-Time 7.1
      • LabVIEW Run-Time 8.0.1
      • LabVIEW 8.2.1 Run-Time
      • LabVIEW 8.5.1 Run-Time
      • LabVIEW 8.6.1 Run-Time
      • LabWindows/CVI Run-Time 9.0
      • Measurement & Automation Explorer 4.6.2
      • Measurement Studio for VS2005
        • DotNET
  • Commune
• OR LabVIEW SignalExpress 3.0
• NEITHER Spy 2.7.1
• NOR-488. 2 2.46
• NI-CAN 2.7
• NOR-DAQmx 8.7.2
• NOR-PAL 2.5.3
• NOR-Serial 3.6
• NOR-USI 1.0.2
• NI-VISA 4.6.2
  • NiVisaServer.exe
  • NIvisaic.exe
• Duration of NI-VISA 4.6.2
• NOR-XNET 1.1
• IVI drivers
  • Advanced
    • Instrument Driver software modules
    • Simulation software driver modules
    • Pilot simulation sessions
  • Pilot sessions
  • Logical names

Now that IS odd.

Can you show some screenshots of MAX?

First, expand the software tab and post a PNG of the screenshot (I am not yet convinced that you have not a driver issue)

Then select MAX > TOOLS > NI VISA > VISA Options - Wait for the new screen then expand General settings Mysystem, and select alias.

You can also try 'Clear all the aliases' a from there and restart.

• GPIB-USB-HS will recognize any instrument in LabVIEW but somewhat done in MAX - help

  Hello

  I'm having a problem getting my GPIB-USB-HS device to recognize instruments in LabVIEW.  The unit has been running year last on many instruments.  I tried the GPIB-USB-HS other materials too just to make sure it wasn't a defective unit.

  NOTE: I installed the latest drivers for NI-VISA 5.1.1 and 300 of NOR-488. 2 for Windows XP

  See the images below:

  It's the idsplay to the MAX:
  I'm not sure why there is a yellow "!" next to GPIB0::INTFC, I think it's an indication of my question.  However, note that the instruments connected to my GPIB-USB-HS are counted in MAX.  As you'll see LabVIEW 8.5 does not recognize them.

  

  I get this error Max warning when I try to open TOOLS > NI-VISA > VISA INTERACTIVE CONTROL:

  

  It comes to the image of my LabVIEW 8.5 window when I try to select a VISA of an instrument (including MAX recognizes):

  

  Any help would be much appreciated

  Thank you

  -Brian

  Thank you all for your help,

  Problem solved after hours of uninstallation and reinstallation of all devices/software from National Instruments.

  Once all programs have been uninstalled (with a disk cleanup on my unnecessary hard-maybe records)

  LabVIEW 8.5.1 has been reinstalled

  NOR-DAQ has been reinstalled

  NI-Visa 5.1.1 has been reinstalled

  NOR-488. 2 worm 2.7.3 has been re-installed (correctly)

  Now, LabVIEW recognizes all ports/devices and connects to the instruments properly once more.

  My question must have been installing LabVIEW 8.5.1 after already installing LabVIEW 2009.

  Somewhere during the installation of 8.5.1 - main post problem occurred.

  Thanks again

• cRIO appears in MAX, but he can't see in LabVIEW, why?

  I had to hang a cRIO-9012.  I can see it in MAX, buy do not see it in LabVIEW.  LabVIEW is a PXi-8195 installed on the same network, but it doesn't seem to find the cRIO.  While setting up to MAX, I got the following warning; "... you enter the subnet mask is the target and the door of entry into two subnets. ».   The entry door is not specified, so I'm not clear on what that means.  I ping the cRIO from the command line, and it appears in MAX, is visible on the network.  LabVIEW just don't see it when I try to add to my project.  Any thoughts?

  I guess you look at something like that? http://forums.NI.com/NI/attachments/NI/280/1546/1/no%20cRIO%20Target.jpg

  This occurs when the NOR-RIO is not associated with your LabVIEW installation. What version of LabVIEW you run? NEITHER RIO 2.4.1 supports up to LabVIEW 8.5.1, if you use 8.6, you use NI RIO 3.0 or higher.

  If this is not the case, simply install NI RIO 3.0 will fix probably the problem.

  In regards to the subnet is the thing:

  The reason that a device on another subnet does not appear in the list of 'existing or peripheral targets' in LabVIEW is because it only goes to search for the same subnet, your computer is on. If it was looking for all possible IP addresses, should be... forever. It's one of the reasons for which subnets were created in the first place. If your cRIO and your computer are in different subnets, LabVIEW automatically find it. You can add it manually by selecting "Existing device on the remote subnet" and typing in the IP address. Or you can go back to MAX and place them on the same subnet.

• LabVIEW does not allow me to add SBRIO project, but SBRIO appears in MAX

  Hi, I have my SBRIO appears in MAX, but I can't create a project in LabVIEW 2009 which has the SBRIO as target. I would like a program for the SBRIO FPGA VI.

  Sorry for any inconvience caused by the huge images.

  

  Three different screenshots into one image below. They show what I did after creating a new project and the lack of the SBRIO appear.

  

  
  

• 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

• 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.

• How to get sony xcd-x710cr appears in MAX

  Hello

  I have a sony xcd-x710cr firewire camera connected to my computer via an express card firewire Belkin PCI not appearing in MAX.  I have Labview 8.5.1 installed on an XP Professional (SP3) machine.  I have the latest version of the IMAQ software installed as well.  The firewire card appears in (with Texas Instruments OHCI drivers) Device Manager, but the camera does not work.  The camera is in green, indicating that it is powered.  What must I do to get the camera appears in MAX so that I can use it?  Thank you

  Chad

  
  

• 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!

• 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

• 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

• GigE vision on OR cRIO-9068

  Hello:

  We are planning a project in which we intend to use embedded vision and transformation of vision GigE cameras. Our client is interested in the cRIO-9068 embedded platform.

  The question is: is there support for GigE Vision on the cRIO-9068?

  I can't find a document that says, so I guess that no public support is granted. If this is the case, I would like to know why.  I think that the VxWorks targets do not GigE support, but this cRIO running Linux. From the outside, I think it would be possible to provide a GigE for Linux support.  The only devices that seem to favor GigE run Phar Lap ETS.

  Thanks in advance for your kind reply.

  Just to answer he question, the 9068 does not support GigE Vision. Layer MAC Ethernet embedded on the chip of architecting it uses does not meet the requirements of GigE Vision (similar to the old cRIOs VxWorks/PPC).

  The 9068 does support USB3 Vision cameras via its USB 2.0 port well and a lot of GigE Vision cameras have identical models in variants of the USB.

  Eric

• 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.

• 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.