Similar Questions

• MAX does not see the cRIO modules!

  Hello

  I have a cRIO-9073 and C 3 (9401, 9239, 9263) modules installed in slots 1-3 respectivly. I can configure the chassis correctly upon arrival 2 months ago and I managed to acquire by a module 9234. Now that the 3 mentioned c modules arrived I installed and have a problem - MAX of nothingness, or analysis of LabVIEW RT engine cannot see modules. Attached are MAX.png and DiscoveryStatus.png that depict. NOR-RIO is version 4.00 and corresponding set is completely downloaded to the cRIO. I do not understand the concept of software cRIO yet but I'm positive, that is the same as used to work the first time that I had tried. The network is OK - host is 100.0.0.1, cRIO is 100.0.0.100 and they see.

  I susspected that perhaps specific drivers are needed for these particular C failet, but I can't verify that the status of software.

  Basic details to accept and understand the CompactRIO concept is spread across many different documents, and it's really hard for the newbees to grasp, so debug/fix situations.

  Does anyone have an idea what is causing my problem?

  Thanks in advance,

  
  

• How to detect if the cRIO modules are connected

  I have a FPGA code that streams of data a 9219 and 9239 module. I want to disable this code if the modules are not connected. I tried looking for the values 0 to the Module ID and serial number, but no one who seems to work. What method or property questions in LVFPGA to see if the module is connected?

  Check an error output on the node of FPGA IO of the particular module. If I/O is not existed, it will give you an error.

• Lightroom CC that I don't have a printer configuration in the Lightroom Module?

  I don't have the option print settings on the bottom of the left side of the print Module! Where is he? I use Ligtroom CC and Windows 7.

  Hi shirleyv,

  The Option for print settings is only for MAC computers, no windows.

  If you click on print... to open the settings of the printer and select it.

  Let me know if it helps.

  Kind regards

  Tanuj

• requirements and configuration of the mobile module

  I want to control an appliance using a PDA. I want answers to the following questions

  1. I have a nokia with great software symbian smartphone, I can use it.

  2. how to set up a laptop, I use lv 2010, do I need to purchase a license (such as the SCCT or something)

  Thank you

  The only way to do so is through the interface of the web server. The mobile module supports only the Windows Mobile OS - and not even the most recent version.

  Mike...

• Serial numbers for the cRIO-9081 Module

  Is there a way for the FPGA in the cRIO-9081 to read the serial number, date of calibration of the NOR-9201 module installed in the cRIO?

  I want to get this information and send it to my Host.vi, because we have a duty to provide information instrument document during a series of tests.

  Thank you

  Paul

  

  Use a property node of the module to read the number of series/VendorId... but the calibration date is not stored. (FPGA code example shows NI9205 data)

  Here a Fifo of DMA target host is used to send the data to the controller of the CR...

• Same code compiled for the cRIO-9074, but reports no diagram component calendar violation for cRIO-9067

  Hi, just got my new cRIO-9067. I have converted my project over the cRIO-9067 since the cRIO 9074. Same layout module, same engine, same scan code custom fpga, (hybrid mode).  I have no problem of compilation for the 9074, which is a lower performance FPGA architecting the 9067 FPGA.

  The final timetable for windows compilation shows that the timing is respected for all clocks - 40, 80 and 120 MHz (I use a clock derived for some code sctl). During the end of compilation, during the phase of gen bitfile, I get the dreaded time violation. Investigation of the breach indicates that it is not the custom code, it is not schema components. One of them seems to be linked to the card series OR 9870 I in the chassis.

  Why? Is there anything I can try with the compiler directives for this problem? You would think that it would be easier to compile for the highest performance FPGAS...

  OK, don't ask me how I thought this output - to run I changed nothing else than this: feed the I/O node a reference FPGA of e/s instead of configure the node via the menu "link to. It makes no sense, but the compilation succeeded when I did this.

  I know it is because I created a very simple test VI in my project and made sure it does not compile without it.

• How to compile and install the kernel modules after nation and nipalk for installation of Gentoo 64 bit?

  We are trying to install a PCIe 6251 DAQ card in a box of Gentoo 64 bit running Linux kernel 2.6.28 - gentoo-r5 4.3.2 - gcc and glibc - 2.8.  We have installed RPM utilities to manage the installation.  The current problem is that we are not able to compile and install the kernel modules: nidmxfk, nimsdrk, nimstsk and nipxirmk.  Here's a summary of what we have done so far, and to what extent we got.

  First of all, we have changed the configuration of the kernel that we could export the init_mm unused symbol by changing the configuration option of the CONFIG_UNUSED_SYMBOLS = o kernel and recompile the kernel.  Then we installed LabView 8.6.1.  Then we ran the nation 1.9 installer who has installed the source code in vain on the compilation.  To resolve this problem, we have changed the function of pte_offset to pte_offset_kernel by editing the file/usr/local/natinst/nation/configures following the instructions here:

  http://decibel.NI.com/content/docs/doc-4511

  We were then able to compile and install the kernel nation module thanks to:

  . / configure
  do
  make install

  lsmod said that nation has been properly installed.  Then we ran the installer for DAQmx 8.0.1 by:

  . / INSTALL - nodeps

  To do this, we have received errors indicating that LabView support could not be installed because check addictive (incorrectly we think) stated that labviewbase86 has not been installed; This caused the installer to have an abortion.  Therefore, we refused to install support for LabView 8.6 and revived the installation program which produces the output:

  Installation of the driver NOR-DAQmx Distribution of Linux Installer version 8.0.1f0...

  Already to jump Edward - 1.9.0 - f0.noarch.rpm installation, same or newer
  installed.

  Pre Installation...

  Preparing... ########################################### [100%]
  1:nitimingi ########################################### [ 4%]
  2:nipalki ########################################### [ 7%]
  3:nipali ########################################### [ 11%]
  RC0.d directory not found, startup script is not accredited with init levels.
  4:labview80 - rte # [14%]
  5:ni653x ########################################### [ 18%]
  6:nicdigi ########################################### [ 21%]
  7:nidaqmxcapiexmp # [25%]
  8:nidaqmxcapihelp # [29%]
  9:nidaqmxcapii # [32%]
  LN: create the symbolic link ' / usr/local/include/NIDAQmx.h': no such file or directory
  10:nidaqmxcfgi # [36%]
  11:nidaqmxef # [39%]
  12:nidaqmxhelp # [43%]
  13:nidaqmxinfi # [46%]
  14:nidaqmxswitch # [50%]
  15:nidimi ########################################### [ 54%]
  16:nidsai ########################################### [ 57%]
  17:nimdbgi ########################################### [ 61%]
  18:nimioi ########################################### [ 64%]
  19:nimru2i ########################################### [ 68%]
  20:nimxdfi ########################################### [ 71%]
  21:nimxpi ########################################### [ 75%]
  22:nimxs ########################################### [ 79%]
  RC0.d directory not found, startup script is not accredited with init levels.
  23:niorbi ########################################### [ 82%]
  24:nipxirmi ########################################### [ 86%]
  25:nirpci ########################################### [ 89%]
  26:niscarabmm # [93%]
  27:niscxi ########################################### [ 96%]
  28:nistci ########################################### [100%]

  After Installation...

  At this point, after reading this report, we used the Gentoo rc update utility to add several scripts for the boot runlevel initialisation:

  update of RC - a boot nipple
  update of RC - a bunch of nipxirmu
  update of RC - a bunch of mxssvr
  update of RC - a bunch of nisvcloc
  update of RC - a bunch of nidevldu

  When the computer reboots, you get an error message indicating that the following kernel modules are not: nidmxfk, nimsdrk, nimstsk and nipxirmk.  lsmod shows that the nation and nipalk are installed, but no other kernel modules NOR are present.  modprobe-l shows that only nation and nipalk are available.

  So we have several questions:

  1. we install drivers in the correct order?  Should use us NI-VISA 4.5 or NOR-488. 2 rather than DAQmx 8.0.1?

  2. What kernel modules should be loaded for this equipment run?  How to compile and install the ones that we have yet, specifically nidmxfk, nimsdrk, nimstsk and nipxirmk?  Are there others?

  3. How can we get the installer to properly recognize that we have installed LabView Core and install support for LabView?  Are there additional kernel modules related to the support of LabView?

  4. What is the symbolic link that was not created in the DAQmx installation report? (ln: create the symbolic link ' / usr/local/include/NIDAQmx.h': no such file or directory)?

  I apologize for so many questions, but these seem to be the last obstacles to obtaining OR runs correctly on this system.  Is there other information that we can provide that would be useful?  Thanks for any help or suggestions you can offer.

  Craig

  Hey Craig,.

  Given that you use 64-bit Linux all kernel modules must be compiled for 64 - bit.  User mode binaries can be 32-bit, assuming that you have installed the 32-bit support libraries.

  NOR-DAQmx is a complex architecture and requires several kernel modules to support your PCIe card.  Most of these kernel modules have not been brought to support 64-bit Linux.  Some kernel modules are components infrustructure that are shared with other pilots OR as NI-VISA and NOR-488. 2 and have been brought to support 64-bit Linux.  Unfortunately, you need all the modules to use your hardware.

  I hope that answers your question.

  Shawn Bohrer

  National Instruments

• Configuration of the BIOS XW8600 for SSD and HDD

  Until recently, my xw8600 has been configured with the emulation of SATA under storage on the separate IDE controller Options.  250 GB hard drives connected to the SATA 1 and SATA ports 0 and readers of DVD RW Drive connected to 2 SATA and SATA 3 ports.

  I wanted to install a GTX240 Neutron Corsair SSD, but discovered when I changed the SATA RAID + DCIS emulation (to activate all 5 ports of SATA controller and optimize the performance of the SSD), the system could not find the boot drive.  I checked the startup command settings and found the slot drive HARD listed title module of memory into the attached USB printer HP Officejet 7500 a first and could not be changed.

  I decided to go back to SATA IDE emulation separate, remove the optical drive on SATA 2 port and attach the SSD it.  This facility is expected to start successfully; but after installing windows 7 x 64 on the SSD (Windows XP, x 64, still on the HARD drive), I found Windows 7 has been very very slow.

  Can anyone offer any suggestions or comments on how I can improve this situation?

  Thanks for any help, you can suggest.

  What is an installation of Windows 7 Pro 64 - bit of a retail installation DVD purchase, or something HP?  If I remember well Vista 64 was the latest HP OS with sold.  In this case you won't have to deal with a set of HP restore disks.  I would never do an "upgrade" of a prior installation of OS in W7.  I only do not clean install W7 on a freshly long-type reformatted hard drive or an SSD.  I buy my "system builder" OEM license W7Pro 64 - bit DVD/COA from newegg.com (you can find that many sources and approximately 140.00 each).

  Plan to do a clean install on this SSD from scratch and when you format before that settle does long formatting version, while it is booted from the W7 DVD.  That will take some time.  Or, if you have a functioning before the OS install on a hard drive, you can restore the xw8600 you can connect the SSD in the second or third SATA port and reformat (long version) management of records like this.

  The boot drive or SSD, Spinner, must always be connected to the primary SATA port, which in these workstations, is usually blue plastic, while the rest are a dark black.

  Make sure that your BIOS is later... There was a version for this and the xw6600 with a few months ago.  It is an important.

  Put the SSD in your favorite mount, hang it in the main SATA port, prepare the W7 DVD in the DVD drive (which should be attached to the second port SATA or IDE cable if it's a DVD ATA drive). Throwing xw8600, go straight into the BIOS and go to which you can change the SATA emulation.  Change that on "RAID + AHCI.  Save on the way out of the BIOS, and the workstation will now reboot usually requiring formal approval of the change F1.

  Demarrer start on the DVD, select clean install and things will be fine.  I usually set my boot order to start hard drive/SSD first and second optical drive.  Then, when I load an OS I just use the F9 key during the early start to switch to the DVD player for this single event.

  It's the key information: If you have correctly set to "RAID + AHCI" SATA emulation for the W7 installation process, then the appropriate drivers will not be loaded from the DVD on the startup disk, and you won't receive anywhere near your expected speed.  I helped a friend who had done exactly what you did, and when we corrected things literally double SSD performance scores.  I recommend that the reformatting/clean reinstall from zero here, because you want to really perfect the basics and the way he was treated initially can leave you with a few important questions.

  After you have things working with the SSD and the DVD player you can add in your other material sequentially.  I would like to make a reboot between each addition, just be very careful.  Some old HP DVD drives have a problem with W764 loading during the emulation of the SATA BIOS is set correctly and there is a solution for this, but you don't want from now this info.

  All the advice I have written in this forum about the xw6400 installs apply to the xw6600 and xw8600, including information on the upgrades of the processor.

  Let us know how things are, so that others can enjoy...

• Calibrate the NI 9265 cRIO module

  Hi guys

  I have a few output current modules NI 9265, analog and I would like to perform an external calibration using a digital multimeter to 8 1/2 available in the laboratory. I tried to do it using a MAX interface, but I discovered that it is not possbile because the analog module is installed in a cRio-9074 control. I don't have this controller and an EtherCat chassi to install modules. Is there another way to calibrate with DAQmx with the NI 9265 installed in the cRio control? Would it not possible in LabView?

  Hey Lane,.

  Unfortunately cRIO or EtherCat frame can be used with DAQmx since they do not belong to the data acquisition platform. Some (e.g., NI 9265) cSeries modules are supported by both platforms, but it can only be calibrated by a cDAQ platform.

  If you check the manual for calibration for the NI 9265 (if you have not yet verified) you will see that it is recommended to use a cDAQ-9178, including a cDAQ chassis 8.

  http://www.NI.com/PDF/manuals/372667b.PDF

  If you really need an external calibration, please contact your local office of OR to get more information on calibration Services.

  Best regards.

• Configuration of the basic Source of time to master for the 9234

  I have several cDAQ modules I use to collect data.  I use vi to Write can Express to save data to a file of PDM.

  When you examine the recorded data files, the measured data from NI 9215 provide pleasant timestamps to match how the DAQmx task has been set up--delaying the sampling frequency of 1000 with a 1 ms in the While loop.  However, although in the same vi - different tasks, but the same while loop - horodateurs of the NI 9234 do not correspond to the task of DAQmx implemented - sampling frequency of 1000 with a 1ms delay. After reading the material provided with the NI 9234, I found that maybe the machine clean master Timebase Source. There were documents that says he can be configured to be originally of Timebase of Master for the other modules:

  Configuration of the basic Source of time of the master for the NI 9234 (Interface FPGA)

  It is desirable to have the timestamps for data measured across all modules to match. We do not have the FPGA Module for LabVIEW. Is there a method in LabVIEW for all modules use the same master time base Source?  I assumed that because all the data collection has place in the same while loop by using the time delay of 1 ms it was forced through the code. This hypothesis seems incorrect from my review of the PDM data files.

  The NI 9204 provides a trigger only.

  Software:

  Windows 7

  LabVIEW 2010 SP1

  Material:

  CDAQ-9174 chassis

  Slot 1: NEITHER 9204

  Slot 2: NEITHER 9215

  Slot 3: NEITHER 9234

  Slot 4; Vacuum

  Hi MgDAQ,

  An important concept to note is that the 9234 uses a delta-sigma converter and a clock of oversampling to read analog data. There is an inherent delay of entry due to analog and digital filtering built-in. Since the 9215 has a lower resolution there will be a lag the 9234 and 9215 finished. I've included some resources below:

  What are the for the NI 9233, NI 9234, and NI 9237 valid sampling rates? : http://digital.ni.com/public.nsf/allkb/593CC07F76B1405A862570DE005F6836?OpenDocument

  
  

  Synchronization of DSA, S and X series devices with a NEITHER-DAQmx single task series: http://digital.ni.com/public.nsf/websearch/78E44565FD87E7D686257108007F94F8?OpenDocument

  
  

  Synchronization with NOR-DAQmx of acquiring dynamic signals (DSA) products:http://digital.ni.com/public.nsf/allkb/A133ED27DF9BCC5986256F2E004BA342?OpenDocument

  Have you tried to put two modules in the same spot? Alternatively, you can export the sample clock 9234 and tasks installation separately.

  Best,

  CARISA

• Using the CRio NI9265 module as current source

  My apologies for what is pretty basic - I come to this Chem Eng background rather than electric. I have a CRio-9012 controller with a 9265 module 0-20 my (among others). The power supply to the CRio is 24VDC. I want to use one of the outputs as input to a power controller Watlow DIN-a-mite, which will lead in turn 10 a / 2.5KW heating.

  The datasheet for the power controller indicates that the input command is powered by current loop linear, 4-20 my DC, requiring an available with 6.5 VDC power source. Am I right in saying that I should compare 6.5 VDC voltage compliance for this module (12 DC max), so this arrangement work?

  Kind regards

  Chris.

  Hello ChrisTighe,

  That's right, that the installation will work.

  The 9265 will display up to 12 VDC, and your device requires a maximum of 6,5 VDC.

• MSG for error in Windows 7: "unable to load DLL 'Gpib - 32.dll': the specified module could not be found."

  Hi people, I have a project in VB. NET (VS2010 specifically), which has been updated from an old VB6 project. The old project

  use Niglobal.bas and Vbib - 32.bas to communicate with the GPIB plugged into one of our litters.
  Now in the 64-bit Win7 with the Niglobal.bas and the Vbib - 32.bas converted to Niglobal.vb and Vbib - 32.vb,.

  I get an error when debugging to

  Public void RegisterGPIBGlobals()

  in the Vbib - 32.vb, the error msg says:

  Unable to load DLL 'Gpib - 32.dll': the specified module could not be found. (Exception from HRESULT: 0x8007007E)

  It seems like this Gpib - 32.dll, that I found under SysWOW64 on my Win7 is not designed for a 64-bit application and when I copy this dll file on

  C:\Windows\System32, the msg of error becomes:

  An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)

  So I think my question is double: 1. the drafting of my own app in VB. NET can I still use Gpib - 32.dll (including the Niglobal.vb and Vbib - 32.vb)?

  2 Will the application I am writing with .NET work in x 64 Windows 7?

  The Almighty gurus and Mods please help. Thank you!

  Hi Joel, thanks for the answer! I have the 3.0.2 driver.

  I was looking around for a while after I posted here and further in the use of NI4882 manual, page 4-4, I found this:

  «To bring an application in an environment 64-bit requires the application to migrate the NI4882 API and be recompiled.»

  So I'm ditching the gpib - 32.dll (vbib - 32 & niglobal) and currently I am using NI4882.dll and restructuring of my project.

• Controls in real-time for the cRio

  I use a cRio 9074 sinking a sensor and to acquire data from ADC module.  I store this data from a DMA FIFO in a table on the RT.  I need to change my detector running program, so I need to change the control on the RT variables after it is deployed from my host PC.  Is this possible?  I also want this picture to be feeding continuously, but I want to be able to pull the data on my host PC from time to time.  What is the best way to do it?  I was trying to use shared variables, but I was getting an error (error-1967357949 cannot request measurement and automation to the shared Variable engine.  Make sure the shared Variable engine exists on the target of RT and verify that the network connection is valid").

  Shared variables are the way to go on this.  Reading http://www.ni.com/white-paper/4679/en should help.  Try the manual deployment of your SV engine to the cRIO in the Project menu.  Your cRIO has the shared variable software installed?  You can check through MAX.

• MAX self test is not available for the 9237 module

  I had been successfully using a VB.NET program to control the ENET-9237 module to read a load cell.

  I've been using 9.4 DAQmx drivers.

  Things were working well for months...

  Today when I tried to use it, I couldn't communicate with the device.  When I looked in MAX and ran the self-test I got an error indicating that the device is not active.

  I deleted the network device and it still added.  He added just fine and I can see the system state is in place, but now the self-test button is gray.  I can not even use my software to connect to the device.  So the ethenet part seems OK, but I can't get access to the real load cell module.

  This indicates a hardware failure of the 9237 module?  Or is there still something in the software I should try?

  It turns out that it was a software problem.  I moved the material to another computer and automatic test worked fine.

  I've uninstalled and reinstalled the DAQmx v9.4 drivers on the computer with a problem.

  Now everything works as it should.

  Not sure what was wrong with the original installation...