My PCI-6250 does not see my SCXI box

[mz6yx6]

Hello,

I am installing a station using a PCI-6250 connected to a SCXI chassis via the 68 pin cable.  We have a couple of these configurations, so I was given some setup disk which have our setup already done.  However, I did have to install some software they neglected to give me.  I got the latest driver for these from NI.   Well, running max, my tree is different from a previous setup.  And, mine does not communicate with the SCXI.  My cards are "x"ed out.  The "Chassis Communicator" in the SCXI Chassis Configuration is greyed out (no options).  I have checked the cabling and disconnected all the blocks to the cards.

Here is my tree. 

NOTE: Mine also does not have the "NI-DAQmx Devices" under the "Devices and Interfaces" section, only in the software section.  The other setups do have this listed.  I do not know how to get "NI-DAQmx Devices" shown.

Any help would be appreciated.

My System

• Data Neighborhood
• Devices and Interfaces
  • GPIB0 (GPIB-USB-HS)
  • Network Devices
  • NI PCI-5402 "Dev1"
  • NI PCI-6250 "Dev2"
  • NI SCXI-1001 "SC1"
    • 1: NI SCXI-1125 "SC1Mod1"
    • 3: NI SCXI-1124 "SC1Mod3"
    • 4: NI SCXI-1160 "SC1Mod4"
    • 5: NI SCXI-1163R "SC1Mod5"
    • 6: NI SCXI-1163R "SC1Mod6"
  • PXI System (Unidentified)
  • Serial & Parallel
    • COM1
    • COM2
    • COM7
    • COM8
    • COM9
    • COM10
    • LPT1
    • LPT1.4
• Scales
• Software
  • IVI Compliance Package 4.0
  • LabVIEW Run-Time 2009
  • LabVIEW Run-Time 8.0.1
  • LabVIEW Run-Time 8.2.1
  • LabVIEW Run-Time 8.5.1
  • LabVIEW Run-Time 8.6.1
  • LabVIEW SignalExpress 2009
  • LabWindows/CVI Run-Time 9.0
  • Measurement & Automation Explorer 4.6.2
  • Measurement Studio for VS2005
    • DotNET
      • Common
  • NI Script Editor 1.3.1
  • NI Spy 2.7
  • NI-488.2 2.73
  • NI-DAQmx ADE Support 9.0.2
  • NI-DAQmx Device Driver 9.0.2
  • NI-DAQmx MAX Configuration 9.0.2
  • NI-FGEN 2.5.1
    • FGEN Soft Front Panel
  • NI-HWS 1.4.5
  • NI-PAL 2.5.2
  • NI-TClk 1.6.1
  • NI-USI 1.0.2
  • NI-VISA 4.6
    • NiVisaServer.exe
    • NIvisaic.exe
  • NI-VISA Runtime 4.6
  • Traditional NI-DAQ 7.4.4
• IVI Drivers
  • Advanced
    • Instrument Driver Software Modules
    • Simulation Driver Software Modules
    • Simulation Driver Sessions
  • Driver Sessions
  • Logical Names

[Brad_K · Accepted solution]

Hi mz6yx6,

First of all, don't worry about trying to get "NI-DAQmx Devices" to appear. MAX 4.6, which was first included with NI-DAQmx 9.0, has a revised UI layout that displays devices inside "Devices and Interfaces" instead of displaying them in sub-folders such as "NI-DAQmx Devices".

Also, thank you for posting a MAX report of the system configuration. The report shows that the SCXI chassis and modules are configured as simulated devices, which I think is the problem. DAQmx (>=8.7) does not support configurations where a simulated SCXI chassis and modules are connected to a real communicating DAQ device. Since your system has no simulated DAQ devices (other than the SCXI chassis and modules), the "Chassis Communicator" menu has no options to display.

To resolve this, delete the SCXI chassis in MAX and create a real (non-simulated) one. How to do this depends on whether you're manually configuring the chassis or you're importing a configuration from a .nce, .ini, or .txt file:

• Manual: right-click "Devices and Interfaces", then select "Create New...". In the "Create New ..." window that pops up, open up the "NI-DAQmx SCXI Chassis" sub-tree and select the chassis type from there. Don't select "Simulated NI-DAQmx Device or Modular Instrument". The modules should be auto-detected, but you will have to manually reconfigure the accessories.
• Import from a .nce, .ini, or .txt file: in the "Configuration Import Wizard" dialog, make sure that the "Warnings and conflicts" column displays "XYZ will be replaced" or "Create device", and does not display "Create simulated device".
• If the setup disk is doing the SCXI configuration programmatically or from an application installer, then more information about what's on the setup disk would be helpful.

Brad

[mz6yx6]

Thank You very much!!!  I have already test one output on a card, so it looks like everything is OK.