VXI-MXI-2 is not detected in VIC / VISA panel

Hello,
I have a VXI work station (VXI-MXI-2)  with Windows XP (PCI-MXI-2). I had installed the nivxi 3.1.1.
The VXI-MXI-2 card is not detected / showing in the VIC panel. Only the PCI-MXI-2 is detected as VXI0 (PCI-MXI-2).
No error occoured while running the Resman. It was completed successfully.
Regards,
Perumal.V

My Friend.
            I understood your frustration totally. I got the same problem. There is not much you can do about it. Probably you won’t like my solution either. It is very painful experiences. Are you ready? Here is the solution.
                        Reinstall all of your software.
                        Yes, Reinstall it. The whole thing, LabVIEW, Drivers, and etc. But you must uninstall first.
                        If it does not work, change the computer.
                        The system should run and found the device. It may takes you a couple of days to do it. But it should work.
                        I ran into this issue a few times. Every time I end it up uninstall and reinstall every thing. And it runs without any problems.

Similar Messages

  • MXI-3 interface not detected?

    Hello to you all,
    I was using PXI/PCI 8335 with PXI 1000B chassis. Everytime I run the MXI-3 optimization it says MXI-interface not detected.
    I checked the LEDs.
    For PXI-8335, the PWR and RX were both solid on, one green and the other orange. For PCI-8335, the PWR and TX (nor sure it's TX or RX, just the one in the same row with PWR) were both solid on, one green and the other orange.
    No LINK light.
    The whole system was powered in proper sequence and the fibre optic cable was fine.
    So there seems to be something wrong with the cards.
    I was wondering is there any way to know particularly which one of PXI-8335 and PCI-8335 doesn't work well without replacing them one by one, since I don't have any extras?
    Like, does the LED tell other information except they are not linked?
    Thank you in advance.
    Yaqiong

    Yaqiong,
    In general you can't differentiate between a bad transmitter on one side or a bad receiver on the other, so it's often hard to tell which side is bad.
    In your case, it sounds like one side or the other has a broken transceiver.  Power and RX on both sides means the boards aren't communicating at all, meaning a transceiver is bad, or a cable is bad in both directions, or a cable is not plugged in or is plugged in backwards.  If you power it up without a cable you should get the same LED behavior -- PWR and RX, the two LEDs next to each other.
    If that's the case (same LEDs without a cable as with a cable), you should be able to tell which card is bad if you connect both ends of a half cable to one card (a loopback).  On a working card connecting RX to TX will "link" to itself according to the LEDs (at least it did for me on both the PCI and PXI card).  On a broken card you'll get something else.
    - Robert

  • Should VXI-MXI-2 work with an old Colorado Data Systems 73A-021 Mainframe (card rack)

    I am attempting to use an old CDS 73A-021 Mainframe with a VXI-MXI-2 card.  The host is Windows XP with a PCI-MXI-2.  Resman runs fine, but when I look at the configuration in MAX the frame and the VXI-MXI-2 does not show up.  (See attached image).  I have tried removing all other cards from the VXI Rack, but no effect.
    On systems that do work I see a frame as the child of the MXI-2 bus 0 and the VXI-MXI-2 card as slot 0 child of the frame.  As shown in the attachment I thnk Max is only seeing the PC card and the cable.  If I run resman when the vxi cage is turned off, I see the same results.
    Attachments:
    vxi-mxi-2.pdf ‏85 KB

    Hi JeffERobertson,
    To eliminate the chassis as the potential culprit I would check a working module in the questionable system.  You've said your CDS 73A-021 doesn't work in another system so the module itself could also just be broken.  Another thing to consider would be the slots that you are using.  It would also be worthwhile to try multiple slots.  Post back if you have any more questions.
    Regards,
    Dustin D

  • Total available graphics memory not detected

    I was trying to connect my notebook to tv useing HDMI cable, got message - no signal, and it said to check my drivers. I checked display adapter and monitor driver, it says they are up to date.
    In performance information and tools it says - total available graphics memory not detected.
    In control panel/display/advanced settings - graphics card is listed.

    Hi,
    The following link shows its specs:
        http://www8.hp.com/emea_africa/en/products/laptops/product-detail.html?oid=7427730#!tab=specs
    It uses:
    Graphics   Integrated:
      Intel® HD Graphics
    And information is right with 64MB of VRAM. System will assign available system RAM to graphics up to max allowed when required.  Please try to hit F4 to send signals to monitor.
    Regards.
    BH
    **Click the KUDOS thumb up on the left to say 'Thanks'**
    Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

  • MXi-3 card is not detecting

    hello,
    when i run mxi-3 optimization code, dialog box indicate that mxi ink is not proper. But, in PXI-MXI3 controller and pci-MXi controller, link led is glowing continousuly.total 3 led's are glowing continously named them as, power,link,Tx.plz provie the solution.
    regrads
    chandu

    Hey Chandhuu,
    I found a great KB Article: MXI-3 and MXI-4 Troubleshooting Guide. It seems like they cover the issue you're mentioning exactly under problem 3. A good test would be to try another computer if possible, or try to update the BIOS of the computer.
    Regards,
    Nick D.

  • Can not install VXI-MXI-2 driver under Windows XP

    I have a new IBM IntelliStation M Pro PC with Windows XP Pro (but only Service Pack 1) that is having a hard time getting the VXI-MXI-2 PCI driver installed. It reports: "There was a problem installing this hardware: PCI-MXI-2 This device cannot start. (Code 10)".
    Taking a look at some issues raised on the "Troubleshooting PCI-GPIB, PCI-DAQ, PCI-MXI-2, PCI-IMAQ Installation Problems" page, I have dealt with the following:
    1) "PCI Bus Mastering" - originally this was turned off for both PCI slots.  I have turned both slots on, but no change.
    2) PCI slots - I have tried the card in both PCI slots in this machine.
    3) "More that one PCI bridge (very rare)" - my system reports two other PCI bridges: one for the SCSI interface to my hard drive and another for use of the 1394 port. Could this be the issue and what would be needed to fix it?
    Thanks!

    NI-VXI 3.3.1 installs an older version of NI-VISA (2.6, I believe)
    which sometimes has problems with newer systems and results in this
    "Code 10."  Installing the latest version of NI-VISA (currently
    3.5) should fix the problem.
    Robert Mortensen
    Software Engineer
    National Instruments

  • VXI-MXI-2

    I have multi test stations with a PC runing Windows XP, each configured with an NI PCI-MXI-2 Card. Each station has two VXI Chassis, each with it's own Slot-0 controller, daisy-chained to run off the same VXI System, which the system identifies as VXI0.
    When I build a new station, I ghost a Hard Drive from an existing station and use that in the new station. The ghosted drive works fine on the station from which it was created. On a new station with a ghosted drive when I open up MAX, I see two VXI systems listed...VXI0 and VXI1. VXI0 is listed but not recognized (i.e. I can't talk to it). VXI1 appears to be recognized by MAX, but not by NI-VISA. (I can't open up a VISA session from either MAX or VIC).
    I can delete VXI0 and rename VXI1 to VXI0, but VISA still can't talk to it. Also, Resman reports still think the hardware resides on VXI1.
    I get similar problems with NI-GPIB cards. In this case, I believe each PCI GPIB card has it's unique Serial Number encoded in it's ID, so when I move drives from one station to another, I'm able to successfully delete GPIB0 and rename and then used GPIB1 to GPIB0 and all works fine. It appears the same approach does not work on my PCI MXI card.
    Is there something else I need to do to re-identify the newly found VXI1 to VXI0? I have multiple files that expect all my instruments to be located on VXI0.
    Solved!
    Go to Solution.

    Hello TomMcG,
    I believe the issue you are seeing with ghosting a hard drive and moving it to a new station is that it is carrying over the Measurement & Automation Explorer (MAX) configuration with the VXI0 configuration, and the current configuration of the chassis plugged in does not match the previous one from thus it creates a new resource name called VXI1. I would like you to delete VXI1and VXI0 from Measurement & Automation Explorer, and then uninstall the VXI driver for the VXI-MXI 2 from the Device Manager.  This will dissociate the driver from the hardware and not allow you to detect this hardware in MAX. Then when your restart your machine the association will be reinstated and (since there is no VXI0 in MAX) be titles VXI0 in MAX. You can access the device manager via Start>> (Right Click on) Computer and select manage. Then navigate to Device Manager underneath Computer Management>>Systems Tools>>Device Manager. Check to make sure the VXI Bus/devices is there, then right click on the MXI 2 module and click uninstall.  You will have to restart your computer in order for the connection and software to be reinstated. Hopefully this will allow the VXI to re-identify the newly found VXI1 as VXI0. Also when you attempt to use Visa Interactive Control (VIC) does it throw you an error?  
    Regards,
    Izzy O.
    Applications Engineer
    National Instruments 

  • VXI-MXI-2 loses register values during normal operation. Causing Bus Errors.

    The Setup:
    I have a system with two VXI chassis and a MXI2 bus running
    between them.  Each VXI chassis has a
    VXI-MXI-2 card in slot zero.  The first
    chassis has VXI cards and the second chassis has VME cards.  I set registers 0xA, 0xC, 0xE, and 0x10 to
    0x6100 on the first chassis’s VXI-MXI-2 card and 0x6180 on the second chassis’s
    VXI-MXI-2 card. 
    The Problem:
    This configuration runs smoothly 99% of the time.  Every so often we get a hiccup and lose the
    values in the 0xA, 0xC, 0xE, and 0x10 registers on the VXI-MXI-2 card in the
    second chassis.  The registers on that
    card are set to their default values of 0x1800. 
    This causes a problem, because we are unable to access the VME cards in
    the second chassis until the register’s values are reset properly.  We have verified with a bus analyzer that our
    software is not writing zeros across the VXI/MXI bus to those register.  It appears as though the second VXI-MXI-2
    card is seeing a hard reset.  The first
    chassis is definitely not experiencing a hard reset.
    Attempted fixes that have not worked:
    1) We put back the register values back into place whenever
    we detect that the MXI2 registers have been reset.  We poll the registers at 1Hz.  While this fix is semi-adequate, there are
    times that we access the registers in the second chassis more frequent than
    1Hz.
    2) We have tried swapping out our second VXI-MXI-2 card with
    a new card, but the problem persists.
    3) We have also swapped out the second VXI chassis with a
    new chassis, and that did not work.
    My questions:
    What could be causing this problem?  Has anyone else seen this problem?  What would cause the values in the VXI-MXI-2
    card to reset to zeros besides a hard reset? 
     Any suggestions?
    Thanks for your input,
    Mike Arthur

    Hi Mike,
    We currently have a support request open on this issue, and we are working on it.
    Thank you!
    Regards,
    Ebele O.
    National Instruments

  • My imac will not detect external monitor after recent update. Is there a way to fix this?

    I have a VGA monitor plugged in to my imac using the VGA adapter to the mini-DVI.  All was working well.  Since I updated over the weekend, the computer will not detect the monitor.
    Any ideas how to fix this?

    Pcantin wrote:
    I have tried another VGA monitor and that failed as well.  Since you don't think the update was the cause, it may be that the adapter I am using decided to call it quits.  I will see if I can find another and test that out.
    I will look into the external drive idea as well.
    Thanks for your help on this.
    I didn't think about the adaptor, but you should at least visually inspect both the adaptor and the cable at both ends. If one or more pins got bent even slightly the connection might fail. The cables can also fail internally. Replacing the adaptor and cable may be the quickest thing to do initially. If you want to try to save money, first replace the adaptor, and if the problem persists, then go replace the cable (or vice versa).

  • Airplay can not detect apple tv

    Airplay mirroring can not detect apple TV.
    I upgraded to mountain lion this morning and the air play icon appears on my macbook pro but it can not detect my apple tv. Apple tv is running 4.4.4 gen 2.
    Any ideas?
    Here's the interesting part, when I disable airplay on the appleTV the icon on my macbook disappears and vice versa.

    4.4.4 is old.  It may be the reason but I can't confirm as my AppleTVs are 5.0+ and none of my Macs can Airplay.

  • Reading the serial number of a VXI-MXI-2 through software

    Is there a way to read the serial number of my VXI MXI 2 through software? I can find the model number and manufacturer number in the registers, but no serial number.

    I think the short answer is no, there's not a way. Getting things like the model and manufacturer number are inherent in the design of VXI - so an API can support it for any vendor. But the serial number is not something inherent in the design of VXI - so no API can expose that in a consistent fashion for all devices.
    Some instrument drivers do have a method for retrieving a device's serial number. But since the VXI-MXI-2 is more of a controller than a normal device (technically it's actually an extender, but close enough) there isn't an instrument driver for it.
    The serial number is also part of the response string for 488.2 compliant message based devices - but again, this is not a message based device.
    There is, however, something that may help you
    . If you need to manually find the serial number, then you should use Measurement & Automation Explorer (MAX), right-click on the VXI-MXI-2, and choose Hardware Configuration. The serial number should be displayed in the title bar of the popup configuration dialog.
    But I don't think there's a way to get this programmatically.
    Dan Mondrik
    National Instruments

  • Multi-Mainframe with VXI-MXI-2 on VxWorks problem

    I have two VXI Mainframes and use two VXI-MXI-2 boards connected. My OS is VxWorks 5.5 running in VXIpc874B. After running resman, it must show borads in two mainframes. but it usually show boards in first mainframe. I try to run resman several times. Sometimes,  the boards of second mainframe apear again. When the boards of second mainframe disapear, the second VXI-MAI-2 disapear too.
    How do I configure my system?

    MyController(VXIpc874) is in Mainframe 1 and LA is 0
            1st VXI-MXI-2 in Mainframe 1      2ed VXI-MXI-2 in Mainframe 2
    LA      1                                                128
    S2     Off                                              Off                                        50 Terminal for External Trigger Input
    S3     Out                                             Out                                       SMB CLK10 Direction
    S4     Off                                               Off                                        20 Terminal for SMB CLK10
    S5     Inverted                                       Inverted                                SMB CLK10 Output Polarity
    S7    Drive CLK10 out MXIbus             Receive CLK10 from MXIbus
    S8     No                                              No                                        VXI-MXI to left
    S9     No                                              No                                        VXI-MXI to right
    W2    Auto                                           Auto
    W3    From onboard oscillator            From MXIbus
    U35 - 1   Yes                                       Yes                                       Terminal MXIbus
    U35 - 2   Yes                                       Yes                                       Automatic MXIbus Terminal
    U35 - 3    No                                        No                                        Change Factory Configuration
    U35 - 4    No                                       No                                         Restore Factory Configuration
    I referance these configure from the VXI-MXI-2 User Manual. I am not sure if lost some setting.
    Another question. Is any sequence to power on the mainframe? Does first mainframe need to power on first or second one? Or never mind this.
    Thanks if anyone can check my problem.

  • NI Scope Sorf Front Panel will not detect NI PXI-5122

    Hello,
    I am trying to use NI Scope Soft Front Panel 2.7f0 to acquire simple waveforms;
    however it will not detect my NI PXI-5122. I have confirmed that the digitizer
    works under MAX 4.2.1 and can see waveforms under the test panel. I have
    installed NI Scope 3.3.1 on my machine and have updated the driver on the PXI
    to version 3.3.1. Any ideas on what is wrong?
    ~Buck

    It is unclear from your post whether or not the 5122 is on the same physical device as you are running the soft front panel (SFP).  The SFP only works on local devices.  It does not have the capability to attach to RT or remote systems (MAX does).  However, if you are running Windows on your PXI controller or are using MXI to control the chassis, there is another issue.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • PXIe-1073 sytem not detected

    I connected a PXIe-1073 system (PXIe-6363 and PXI-2567 connected) to the PC (running Windows 7) and the PC does not detect the chassis. It started happening when I recently upgraded to LabVIEW 2013 and NI-DAQmx 9.7.5.
    I also installed the MXI BIOS compatibility software Ver 1.4, changed the DIP switch1 to ON position on the MXI express card 8361 and rebooted the computer. That did not solve the problem.
    Then, I upgraded to PXI Platform services 3.2.3 and restarted the computer. I still don't see PXI system recognized in NI MAX. When the computer was restarted, the 8361's MXI card's switch 1 was still in ON position.
    Any ideas on how to fix this issue ?
    Thanks
    Jeet

    Hi Matt
    Sorry for delay in replying.
    After a lot of uninstallation/installation/repair of different driver versions, i have currently got the following software (see attached pic): NI-DAQmx 9.5.5, Ni PXI platform services 3.2.1.
    In the picture, you can  see that all my cards are detected in NI-DAQmx devices as Dev1, Dev2 etc.
    My PXIe-1073 is not detected or listed in MAX. I expect to see chassis controller detected and all the cards listed under the chassis controller as "PXI2slot2" device or "PXI2slot4" device etc.
    The attached pic shows NI-MAX and device manager snap shot.
    Please advise.
    Thanks
    Jeet
    Attachments:
    nimax dev man.jpg ‏316 KB

  • VXI-MXI-2 missing in resource manager

    Hello,
    I have a VXI-MXI-2 and I configure the A16 write posting to enable. After that i can not work with VXI-MXI-2.
    When resman run, it found a instrument at address 1 but got a Generic I/O error on VXI D16 peek.
    I try to set all jump status to default and set the U35 Restore Factory Configuration to Yes. it is the same.
    How do i fix this problem?

    My Friend.
                I understood your frustration totally. I got the same problem. There is not much you can do about it. Probably you won’t like my solution either. It is very painful experiences. Are you ready? Here is the solution.
                            Reinstall all of your software.
                            Yes, Reinstall it. The whole thing, LabVIEW, Drivers, and etc. But you must uninstall first.
                            If it does not work, change the computer.
                            The system should run and found the device. It may takes you a couple of days to do it. But it should work.
                            I ran into this issue a few times. Every time I end it up uninstall and reinstall every thing. And it runs without any problems.

Maybe you are looking for

  • How do you connect AppleTv to Insignia 1080p television?

    how do i connect my appletv to my tv screen directly? I don't want to stream through my mac. any help will be appreciated.please help. thank you:)

  • Restrict visitors to a site by IP address

    Not sure if this is the right place to ask this question but thought I would give it a shot. I need to build a small website to collect entries to a sweepstakes. My client wants me to use an Internet application form service (Wufoo.com) to create the

  • Can I make the browser in iWeb transparent?

    Can I make my browser image in the iWeb transparent somehow? I do my photo editing in Aperture, and can't find a transparency there.  Using the graphics inspector transparency in iWeb does not seem to work on the uploaded browser image. I like the lo

  • Error 1256 The remote system is not avilable - REPL summary

    Hi all For the past 3 days I am getting the below  error  while checking the  AD replication.  our present setup is RDC and ADC was available in the same site.  and DR ADC was configured in  remote site. we have P2P link  connectivity  for OUR AD and

  • Video Footage not working on my Mac but only on PCs.. i need it on the Mac!

    I have uploaded movie footage from a JVC Everio and a Sony Vario-Tessar- both of which use the HDD (Hard Disk Drive) technology. The footage works perfectly on any PC computer however on my Macintosh when attempting to play them or edit them using Fi