Board not detected from MAX

The machine is equipped with NT4.0 sp5, and was using an old PC-TIO-10 with NIDAQ6.1.
We decided to sobstitute the board with a PCI-6023E, as we needed some analog signal inputs.
We installed NIDAQ6.8.1 (without first uninstalling 6.1 version), put away the PC-TIO-10, and installed the PCI-6023E.
Once MAX opened, it showed the PCI-6023E, but also continued to show the PC-TIO-10 board. We manually removed this old board from the list("delete"). But, at successive MAX openings, it was impossible to find the PCI-6023E board, also refreshing or setting the preferences at "every time I launch MAX".
We tried unistalling and reinstalling NIDAQ6.8.1, reinstalling NIDAQ6.1 so to try to uninstall it, restarting the machine many times, changing slo
t for the board, but we never more managed to see the PCI-6023E board among the devices.
Now the system is on, the board is in the PC, NIDAQ6.8.1 is installed, but we have not the way to use the board.
We cannot reinstall all (NT, applications, etc.) as the PC is on a plant and cannot be stopped for more than a few minutes.
We are sure that no secondary things may have caused the problems (bios settings, applications, etc.) as the first time after installation the board was correctly recognised.
Many thanks.

Moroli
Here is what I would suggest to do.
1. Uninstall NI-DAQ
2. Clean the registry
-Click on Windows 'Start' Button and goto 'Run'
-Type in regedit to open the Registry Editor
-Follow this path: HKEY_LOCAL_MACHINE >> Software >> National Instruments >> NI-DAQ
-Delete the NI-DAQ folder
-Shutdown computer and take out PCI-6023 board
-Reinstall newest version of NI-DAQ
(NI-DAQ 6.9.1 can be download from ni.com
-After installation is complete, put PCI-6023 board back in computer
By going through these steps, you should be able to use your board normally.
Brian

Similar Messages

  • PXI-8532 DNET card is not detected in MAX

    Hi all,
    I'm using NI PXI-1031(4 slot PXI chassis). I have the following cards in the respective slots
    Slot 1= PXI-8106 Controller
    Slot 2= PXI-6259 card(AI)
    Slot 3= PXI-6509 card(DI,DO)
    Slot 4= PXI-8532 Card(DNET)
    In MAX(Measurement & Automation Explorer), I was expecting all the above cards(PXI 6259, 6509 & 8532) to be detected under Devices and Interfaces. But only the AI and DIO cards are detected in MAX under Remote Systems>>PXI>>Devices and Interfaces.
    PXI-6259 (PXI1 Slot2)
    PXI-6509 (PXI1 Slot3)
    The device net card, PXI-8532 is not detected in MAX. Does MAX shows/detects the DNET card?
    In MAX, I selected Tools menu>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, I pressed OK. A message appears that no device is found.
    Can any one help me how to detect the DNET card in MAX and do the DNET port configuration?
    DNET driver version - 1.6.4
    Thanks,
    Raja
    Solved!
    Go to Solution.

    Dirk,
    Thanks for the reply. After updating the new driver, I am able to detect the DNET card PXI-8532 in MAX
    New driver - NI-Industrial Communications for DeviceNet 2.1
    But Im not able to configure the Device Net port. In MAX, I selected the menu option Tools>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, a message appears that no device interface is found.
    By default, the DNET0 port is configured for the card in MAX. So I tried to communicate from LabVIEW using DNET0 port.
    After installing Devicenet 2.1, an additional function palette has been added for DNET in LabVIEW.
    Old DNET function palette - Instrument IO>>DNET
    New DNET function palette - Industrial Communications
    My original application was written with old function palette VIs which corresponds to DNET 1.6.4 version. In the download link that you shared has a description about the driver compatibility. The description says still the DNET card PXI-8532 is compatible with NI-DNET 1.x LabVIEW VIs.
    With the old DNET VIs, I tried to establish communication with DNET interface port "DNET0". But it shows error while opening the interface.
    Error Code ="-1074388957" - The Interface is invalid or unknown.  Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
    With the new DNET VIs(DNET 2.1.0), Im able to open the DNET interface successfully. But my original application was written in Old DNET VIs (DNET 1.6.4).
    1. Do you know why the DNET 1.6.4 LabVIEW VIs are not working with PXI-8532 DNET card?
    2. Can you help me how to configure DNET port in MAX for PXI-8532 DNET card?
    Thanks,
    Raja
    LV 2009, Windows XP

  • MXI3 (NI PXI-8330) board not detected. Not powering up, no link light.

    MXI3 (NI PXI-8330) board not detected. Not powering up, no link light. Cable looks fine. Any ideas?

    PeteMan,
    I will need to know in more detail how your system is behaving to give you better tips, so please feel free to send me more information.
    For now, let me send you a couple of troubleshooting tips:
    Cable connection
    Make sure both ends of the copper cable are well connected to the PCI-MXI-3 and the PXI-MXI-3 boards. Be careful when disconnecting the copper connectors. you need to push down the plastic connector so it does not get damaged. Damaged connectors could result in bad MXI-3 links.
    If the connector has not been used properly, it could be broken (this rarely happens). Make sure you are not connecting the cable backwards.
    Power - Up order.
    It seems you are controlling your PXI chassis using a PCI-to-PXI extender (copper cable). Make sure you are powering up the PXI chassis BEFORE powering up the PC.
    PXI is built on top of the CompactPCI spec, so it uses the PCI high speed bus. The MXI-3 extender is really a PCI-to-PCI bridge toyour computer, so for your PC, all the slots in the PXI chassis look like more PCI slots. In other words, your computer suddenly has more PCI slots.
    It is very important to power up the PXI chassis first before powering up the computer, because at power up the PC enumerates all PCI slots. If the PXI chassis is OFF during boot up, the slots in the PXI chassis will never get enumerated and your PC will never see the board installed in the PXI chassis.
    Normal Power up LED sequence
    Each MXI-3 board has four LED light on its front panel: two green lights (POWER and LINK) and two orange lights (Tx and Rx). When you power up the PXI chassis you should see one green light and one orange light ON steadily (POWER and ). Then, when you power up the PC, both green lights shoudl be ON steadily and the orange lights shoudl flicker.
    If you do not see this behaviour at power up, most probably one of your boards its damage.
    If you have another MXI-3 extender kit, try to set up the system mixing the boards from the two kits to try isolate which board is the one that is damaged.
    Run the MXI-3 Optimization Software
    The MXI-3 Optimizaton Software makes sure that the link between the PC and the PXI chassis has been set up properly. It will show you an error otherwise.
    MXI-3 Software Version 1.15 for Windows 95/98/NT/2000/ME
    The PC powers up fine if the PXI chassis is OFF, but if I turn on the PXI chassis first and then try to power up my PC, my PC does not boot
    There are several things that could be causing this behaviour:
    It could be that your PC has an old BIOS that has issues detecting PCI-to-PCI bridges. You could try upgrading the BIOS.
    A part of the hardware could be damaged. If you have a main-stream computer (like a DELL or HP PC, for example), test your MXI-3 extender in it to make sure that the hardware is in good conditions. Main-stream computers tend to use new Motherboards with good BIOS.
    There are more tips in the following KnowledgeBase:
    KB 267FAS5P : MXI-3 Troubleshooting Guide
    Hope this helps,
    Claudia Lorente
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • CRIO not Detected in MAX

    Hello,
    I'm totally new to NI and LabVIEW, so I may have done many unnecessary steps or missed something obvious, but here's the rundown (what I can remember) of what I tried:
    I'm trying to make a cRIO-9073 (newer revision, IPreset switch does not reset IP to 0.0.0.0) work with LabVIEW 2011 SP1 (includes MAX 5.1.0f0 and NI-VISA 5.1) installed on Windows 7 Professional SP1 using a crossover ethernet cable.  MAX does not recognize the cRIO in the Remote Systems tab.  After initial problems, I was able to locate 2 IP addresses corresponding to the cRIO, but its still does not appear in MAX.  I have tried the following:
    refreshing the list using F5, rebooting the cRIO, and using the IPreset switch
    reinstalling drivers on the computer using September 2011 NI System Driver Set CD
    manually adding the a new remote VISA system in MAX (tells me that a device is already using that IP address)
    manually adjusted the LAN settings in the Windows control panel and disabled DHCP
    edited Internet Protocol Version 4 (TCP/IPv4)
    manually set IP address and local subnet mask to match the cRIO settings
    Added exceptions to the Windows firewall
    NI-RIO RPC Server
    VISA Interactive Control
    I think that the software and/or drivers on either the computer or the cRIO may not be up to date or compatible with the rest, but I'm not too sure on how to install software on the cRIO if I cannot see it in MAX.  Any ideas?
    Thank you!
    Solved!
    Go to Solution.

    Zach-H wrote:
    To add the device manually you need to select "Remote Device (not on the local subnet)" not "Remote VISA System". The cRIO should try and default to a link local IP address (169.254.x.x Range) if it can't communicate with a DHCP server. This will likely be the case with the cRIO connected directly to the computer.
    If your computer isn't on an agreeing IP and subnet mask its likely that the cRIO wouldn't show up unless you add it manually. You don't want to set them up as the same as the cRIO as they need individual IP addresses. I would recommend setting the subnet masks the same and adding one to the last number of the cRIO's IP address, which should allow it to show up in MAX.
    Very useful document for this kind of a situation: http://digital.ni.com/public.nsf/allkb/abe4bc247e8ac9bc8625734e005cab42?OpenDocument 
    When I tried to add it as a "Remote Device (not on the local subnet)," I got the error message "The device at this address is not supported by the drivers installed on this host."  I checked that my version of NI-RIO 4.0 is compatible with the cRIO-9073.
    Also, I ran through the link you provided, and the steps did not remedy the problem.  When I ran the cRIO with the CONSOLE OUT switch ON, I was able to get lots of information from the cRIO in the command prompt in Windows.  This makes me think that there are no problems with the cRIO, but with the software I have installed on Windows.  I'm not sure what else I can try to install, though.

  • Pxi not detected under max

    Hi...
    I have aPXI 1000B chassis with 8156B controller, i am trying to make the pxi get detected under MAX for 1 month now... still no result... i don know what the problem is...

    i am using windows xp. the labview version is 7.1 with a 7.1 real time. the max version is 3.3 and the controller is 8156B with 1000B chassis. the pxi doesnot boot into anything, but when i connect a vga port the boot screen look like the one in photo i have attached.
    Attachments:
    8156B controller.jpg ‏319 KB
    pxi boots to this screen.jpg ‏311 KB

  • 7332 is not detected in MAX

    Hi,
    We have a PCI NI7332 motion controller purchased with us. We installed the drivers and softwares  from the cd that comes with the package. The problem is PCI NI7332 showing as NI7330 in MAX . Anyway its listing the two axis in max. When i tried to connect an encoder and read it in MAX nothing is happening.  Do i have to change any setting when using the board for the first time?
    With regards,
    Jerry

    Jerry, 
    I don't quite understand this:
    " The problem is PCI NI7332 showing as NI7330 in MAX . Anyway its listing the two axis in max. "
    I'm assuming that the board just isn't showing up in NI-MAX.  If you are running Windows, I would go to the Device Manager on your machine and make sure the computer is recognizing it first (I'm not familiar with the Mac equivalent of this).  If the computer is not recognizing it as a piece of hardward installed on the motherborrd, there may be a bad connection.  Restarting the computer is also not a bad idea just to make sure everything is operating correctly.
    Hope you get it figured out.
    Adam

  • CDAQ-9181 not detected in MAX

    I have NI device which I am trying to connect to in NIMAX however it just not getting connected to it or searched. But I see it running in NI Network browser with some random ip address which I can not ping. Hence I can't configure that device in Network browser either. 
    Any Idea what's wrong? or if there is any utility to configure it? Or it's a NI-DAQ version problem. ??
    I tried NI - MAX 5.1, 5.5 & 5.6 but no use, they all failed to detect it. 
    Where I can download just the device drivers but not whole NI suite?

    Hi prabhushrikant-
    Which version of NI-DAQmx are you using currently?  You can download the latest version here, but make sure first that it meets your O/S and LabVIEW (or other NI software) compatibility requirements.
    What 'random ip' do you see in the network browser for the device?  What happens if you try to click on the link in the network browser?  Can you tell us more about the networking setup on your PC and network?  Do you have multiple NICs in the PC?  What are their networking settings set to (DHCP, static IP, etc)?
    Tom W
    National Instruments

  • KCU105 board not detected in PCIe "TRD02" example design

    Hello everybody,
    Could it be that the KCU105 "TRD02" PCIe example - works only on a PCIe x8 Gen3 system, without PCIe backward compatibility?
    I followed the instructions that appear on "UG919" document and tried to run the –
    " KCU105 PCI Express Memory-Mapped Data Plane TRD".
    The example GUI says that it did not find Xilinx board.
    Nevertheless, the Xilinx board do appear in "device manager" and in "lspci" scan of the PCIe.
    The mentioned above situation is seen the attached screen shot.
    I tried to do as suggested in the "troubleshooting" for this issue, as appear at the end of the "TRD02" document ("ug919" document), but it did not help.
    This example design is for PCIe Gen3 x8 lanes.
    My PC's PCIe slot is Gen1 x4 lanes.
    I expect it to work (PCIe should have backward compatibility), but – could this be the issue for the non-detected board?
    Any ideas and help would be much appreciated :-)
     

     
    Hi,
    balkris wrote:
    Check these ARs
    http://www.xilinx.com/support/answers/34536.html
    http://www.xilinx.com/support/answers/63739.html
    Did you do "Disable Driver Signature Enforcement" as described in UG919? If not, please do that.
    -Anil

  • Zynq custom board not booting from SD-Card

    Hi all,
    I have a custom designed board woth a Zynq XC7Z100 SoC and try to bring it up. The schematics are based on the ZC706 board so the MIO connections on the PS are the same.
    Now I'm trying to boot just the simple Hello World example from XSDK (Vivado Version 2014.3). Booting from JTAG and from QSPI Flash is working but booting from SD-Card fails. The FSBL is producing the following output:
    Xilinx First Stage Boot Loader
    Release 2014.3 Nov 5 2014-17:42:52
    Devcfg driver initialized
    Silicon Version 3.1
    Boot mode is SD
    SD: rc= 0
    SD: Unable to open file BOOT.BIN: 3
    SD_INIT_FAIL
    FSBL Status = 0xA009
    This Boot Mode Doesn't Support Fallback
    In FsblHookFallback function
    I've measured all data pins and they are toggling. What I've found out is that the SDIO Clk is somehow strange. When starting the FSBL it is a very slow clock (kHz) and afterwards it's speeding up to 41.6666 MHz. I've already changed the SDIO clock in Vivado from 125 MHz to 50 MHz but nothing changes, when I'm measuring it. Do I miss something out?
    Any help would be greatly appreciated.
    Thanks
    Christoph

    I believe the clock is behaving properly. The driver should connect at a slow clock at first then increase to the highest clock that the driver thinks the card can support. If you see this clock speed change, the initialization must be getting past the first few SD card messages. You could try to adding printfs in the card driver to see which message failed.
    I've had problems switching from 14.7 to 2014.3 FSBL. The later driver dropped support for older SD card and stop on very first message to the card. Maybe try a different card.
    In going from dev board to custom board, did you switch from full size SD to micro SD? The micro SD format does not have a WP signal. Maybe no CD signal either. The FSBL driver cares about both.
    Some official answers:
    http://www.xilinx.com/support/answers/59476.html
    http://www.xilinx.com/support/answers/52023.html
     

  • Pen Drive is not detected from my Solaris OS

    Hello,
    from my Solaris 10 OS my pen drive is undetected .Please help how to detect my pen drive .
    The configuration of my system :
    1) Solaris 10
    Q) The OS is installed using VirtualBox , Host machine is Windows 7 ?
    Q) My pen drive is working with other OS like Windows 7 .

    Thanks. Have you configured the Solaris Virtual Machine to allow USB Passthrough? ie: are you allowing the guest to see USB devices or is USB disabled? See https://www.virtualbox.org/manual/ch03.html#idp11184832 for how to configure this.
    If you can see other USB devices in Solaris, such as portable or desktop hard drives, then it could be an incompatibility between Solaris and the USB drive itself. Solaris doesn't support all usb drives/pens.

  • AIM ARINC board not detected with MXIe in a PXI-1033 chassis

    Hi,
    I have a PXI-1033 chassis with NI PXI-6229 and AIM boards (ARINC 429 & AFDX) linked to a PC with MXIe.
    Windows can't attribute enough ressources to this device (indicated in the devices manager) so I can't install drivers for my boards.
    If I only put NI PXI-6229 in my chassis, all is OK.
    If I only put AIM boards in my chassis, Windows doesn't boot.
    I tried with a PXI-1036 chassis linked to my PC with MXI-4, all is running correctly (NI and AIM boards).
    Is there anyone who detects a problem of compatibility between AIM boards and MXIe links, and what is the solution ?
    Thanks for answers.
    Matthieu

    Mmonterrat,
    Problems like this are quite often caused by the computer's BIOS.  Is there a BIOS update for your PC, and have you tried a different computer?
    You can get more information here:  http://digital.ni.com/public.nsf/websearch/05B7131814A5DDA38625710F006BB098?OpenDocument
    Robert

  • PS3 Ethernet not detected from homehub 3

    Hi all, new to BT Infinity and are having an issue setting up my PS3 using an ethernet connection. It connects wirelessly with no problems, but when I try to make a wired connection, the PS3 says no ethernet connection is detected. I have been through my hubs settings but can find nothing on switching ports on and off.
    It does not seem to matter which port I am plugged into either. Any help is much appreciated.

    The home hub uses a different IP subnet than many other routers. You will have to reset the network settings on the PS3 so that it gets a new IP address, and DNS servers.
    Better still, assign it a static IP address as described below.
    Using static IP addresses on your home network
    Pay special attention to the bit about the PS3 at the end.
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • PXIe-1073 not detected

    I'm trying to install a PXIe-1073 chassis on a new Dell system running Windows 7 x64.  I have the latest version of Labview, NI-DAQmx, etc.  The PCI express controller shows as properly installed in the Device Manager ("PCI standard PCI-to-PCI bridge").  The chassis and installed DAQ card are not detected in MAX.
    I am actually transferring this system from an older computer.  I recall having exactly the same problem before, and I'm fairly certain I solved it by installing the "MXI-Express BIOS Compatability Software".  There was never any way to actually identify the "PXI System" as anything other than "External PC" even when it was working properly.
    After installing the current version of the MXI-Express software, I rebooted and was able to load MAX briefly before Windows BSODed with an error involving "niraptrk.dll".  This proceeded to occur every time I tried to load Windows.  I was able to start in safe mode, but attempting to uninstall any NI software gave me an "error 1601".  I was finally able to load the last known good configuration and uninstall the software.
    When I checked MAX again, the chassis was still unrecognized, but there were multiple broken entries for the DAQ card installed in it, so I assume it was detected at some point.  It looks like the MXI-Express software worked, but it's obviously unusable if it causes the computer to BSOD every time Windows starts.  Why is the computer unable to recognize the chassis without it?  What else can I do to solve the problem?

    Hello Bob_mcbob,
    After looking over this issue, I think we have a problem with the Windows installer on your machine. I have found a KnowledgeBase about the Error 1601 stating that this is a Microsoft Windows installer error and that the installer will need to be reinstalled. The Knowledgebase explains how to do this.
    As for the BSOD, do you have any more information that it provided when this occurred like the address line, etc? Did you do something in MAX before it crashed?
    Since accessing MAX now gives you a BSOD, I think it would be best to uninstall/reinstall the drivers to fix the issue. What cards do you have in this system?
    Jim St
    National Instruments
    RF Product Support Engineer

  • SCXI-1102/SCXI-1303 not detected in SCXI-1000 chassis

    I am using a setup with SCXI-1303 module in a SCXI-1102 within a SCXI-1000 chassis to take voltage and thermocouple measurements.
    Until recently, everything was working fine. but it now appears I am unable to communicate with the interface. I have tried two different computers and the hardware is not detected in MAX. The power light and fan on the SCXI-1000 still comes on, there just appears to be no acknowledgment of the connection to the computer.
    A few more specific error codes:
    * When I double-clicked the DAQ Assistant in the block diagram window and clicked "Test" on one of my inputs, I received the following error:
    "Error -88705:The specified device is not present or is not active in the system."
    * I have also gotten the error code "Error -89130: Device not available in NI-DAQmx" in the DAQ Assistant test panel
    * When closing the DAQ Assistant test panel, I see the error "Error -89130: Device not available for routing"
    * In MAX, if I try to "test" the chassis or module, I have seen errors either saying that the device is not detected, or that the device needs to be reset or is in the process of being reset, or that Traditional DAQ drivers need to be reset (I've tried these reset suggestions with no result)
    At this point I'm wondering if the board or the cable is shot. I unfortunately don't have another 68-pin cable to test at the moment.
    Thanks in advance...
    Solved!
    Go to Solution.

    mtd12 wrote:
    Thanks guys, I was able to resolve the problem. For anyone who might come across this,
    * I noticed in Windows Device Manager that two PCI devices were listed as not being installed properly.
    * After trying to update the drivers, I couldn't start the computer; got BSOD after BIOS load.
    * Some research prompted me to pull out the two PCI cards that I was not using, and I also moved my DAQ card to another slot to force a hardware reinstall.
    * Booted up, loaded the drivers automatically, and off I went.
    Doesn't explain why it didn't work in the other computer, but in the words of Spinal Tap, the authorities said it was better left unsolved at this point.
    You should move the DAQ board back and verify whether it still works. Perhaps one of the slots went bad.
    You didn't notice that you had two PCI devices that were not installed properly before?

  • Parallel port not detected in measurement and automation explorer

    I have installed labview 2010 in windows XP.
    The problem what I am facing is I could not find "Serial & Parallel port" option in Measurement and automation explorer.
    After seeing the similar problem in forum I have installed Ni-Daqmx 9.0.2.  But still I can not see the ports in MAX.
    I think i have attached enough document .
    If the parallel port is not detected in MAX can we send digital data to parallel port.
    I have tested parallel port with LED connecting one leg in 1st data line(pin 2) and another in gnd(pin 25).
    And my program is to blink the led for every one second but I cannot see the blinking.
    Can anyone help in this regards
    thank you
    Attachments:
    max.jpg ‏90 KB
    port setting tab1.jpg ‏30 KB
    device manager resource tab.jpg ‏34 KB

    Thank you for ur reply Smercurio
    I have changed the bios setting now 
    but still i cant see the printer port in MAX
    Regarding my vi, now i changed it please see that also 
    I have given values to element of arrays as (1,2&4) 
    Now also it is not blinking instead it is glowing all the time without blinking.
    What i have to do next.
    Attachments:
    device manger.JPG ‏43 KB
    device manger2.JPG ‏165 KB
    port test.vi ‏9 KB

Maybe you are looking for