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

Similar Messages

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?

[Potentially Solved] Touchpad sometimes not detected possible IRQ.

Edit:
Potentially solved: since adding the below entries to my bootloader I have not encountered the issue, or it may be just a coincidence.
append to the boot line: i8042.nomux=1 i8042.reset
I've been experiencing an issue for the last few years which has bugged me across two different brands of laptop, but has been very hard to debug due to how random the event seems to occur.
One in every 20 or so boots, the touchpad on my laptop (Lenovo Z500) is not detected; not just by X, but by the system as a whole, it's as if it has been physically disconnected somehow.
It will take a few good reboots for the system to detect it again, and the problem disappears for another few days/weeks
One strange thing I have noticed, is that when looking at the listing of interrupts during a 'failed touchpad boot', IRQ 12, which I believe is normally the touchpad, has vanished.
I'm not very clued up on these matters so I'm not sure how to start debugging this, and working out if the issue is down to my setup of the system or not.
Any ideas on what could be causing this?
Thanks.
Output of /proc/interrupts during a working boot:
CPU0 CPU1 CPU2 CPU3
0: 23 0 0 0 IO-APIC-edge timer
1: 16 723 9 10 IO-APIC-edge i8042
8: 0 0 0 1 IO-APIC-edge rtc0
9: 299 118 10 14 IO-APIC-fasteoi acpi
12: 845 21415 146 77 IO-APIC-edge i8042
16: 461 8993 74 44 IO-APIC-fasteoi ehci_hcd:usb1
17: 0 0 0 0 IO-APIC-fasteoi ath9k
23: 2 25 5 1 IO-APIC-fasteoi ehci_hcd:usb2
41: 5 22 0 2 PCI-MSI-edge xhci_hcd
42: 1557 1065 596 500 PCI-MSI-edge ahci
43: 11 2 0 0 PCI-MSI-edge mei_me
44: 266 0 0 0 PCI-MSI-edge snd_hda_intel
46: 4 28 26 1 PCI-MSI-edge i915
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 3002 12958 2572 1842 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 Performance monitoring interrupts
IWI: 88 170 115 197 IRQ work interrupts
RTR: 1 0 0 0 APIC ICR read retries
RES: 367 332 393 431 Rescheduling interrupts
CAL: 129 71 24 58 Function call interrupts
TLB: 99 72 157 892 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 2 2 2 2 Machine check polls
THR: 0 0 0 0 Hypervisor callback interrupts
ERR: 0
MIS: 0
Output of /proc/interrupts during a non-working boot:
CPU0 CPU1 CPU2 CPU3
0: 23 0 0 0 IO-APIC-edge timer
1: 9 235 2 11 IO-APIC-edge i8042
8: 0 0 1 0 IO-APIC-edge rtc0
9: 217 44 24 40 IO-APIC-fasteoi acpi
16: 96 2512 38 173 IO-APIC-fasteoi ehci_hcd:usb1
17: 0 0 0 0 IO-APIC-fasteoi ath9k
23: 3 25 1 4 IO-APIC-fasteoi ehci_hcd:usb2
41: 6 23 0 1 PCI-MSI-edge xhci_hcd
42: 1445 937 649 479 PCI-MSI-edge ahci
43: 9 3 0 1 PCI-MSI-edge mei_me
45: 11 10 4 39 PCI-MSI-edge i915
46: 93 80 94 0 PCI-MSI-edge snd_hda_intel
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 1251 3465 1964 692 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 Performance monitoring interrupts
IWI: 76 97 47 79 IRQ work interrupts
RTR: 1 0 0 0 APIC ICR read retries
RES: 349 252 190 335 Rescheduling interrupts
CAL: 110 72 30 69 Function call interrupts
TLB: 101 52 817 651 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 2 2 2 2 Machine check polls
THR: 0 0 0 0 Hypervisor callback interrupts
ERR: 0
MIS: 0
Output of /proc/bus/input/devices during a working boot (touchpad detected at bus 0011):
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input2
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/platform/VPC2004:00/input/input5
U: Uniq=
H: Handlers=kbd rfkill event4
B: PROP=0
B: EV=13
B: KEY=1400800100c03 400000000300000 0 0
B: MSC=10
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input7
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0003 Vendor=13d3 Product=5170 Version=0730
N: Name="Lenovo EasyCamera"
P: Phys=usb-0000:00:14.0-4/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/input/input9
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0001 Vendor=10ec Product=0269 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input8
U: Uniq=
H: Handlers=kbd event7
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input10
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input11
U: Uniq=
H: Handlers=event9
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input12
U: Uniq=
H: Handlers=event10
B: PROP=0
B: EV=21
B: SW=140
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input6
U: Uniq=
H: Handlers=event11 mouse0
B: PROP=5
B: EV=b
B: KEY=e520 10000 0 0 0 0
B: ABS=660800011000003
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:35/LNXVIDEO:00/input/input13
U: Uniq=
H: Handlers=kbd event12
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:03/input/input14
U: Uniq=
H: Handlers=kbd event13
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
Output of /proc/bus/input/devices during a non-working boot:
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input2
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0C:00/input/input3
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0005 Version=0000
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input4
U: Uniq=
H: Handlers=event2
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
U: Uniq=
H: Handlers=kbd event3
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/platform/VPC2004:00/input/input6
U: Uniq=
H: Handlers=kbd rfkill event4
B: PROP=0
B: EV=13
B: KEY=1400800100c03 400000000300000 0 0
B: MSC=10
I: Bus=0010 Vendor=001f Product=0001 Version=0100
N: Name="PC Speaker"
P: Phys=isa0061/input0
S: Sysfs=/devices/platform/pcspkr/input/input7
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0003 Vendor=13d3 Product=5170 Version=0730
N: Name="Lenovo EasyCamera"
P: Phys=usb-0000:00:14.0-4/button
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0/input/input8
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:35/LNXVIDEO:00/input/input9
U: Uniq=
H: Handlers=kbd event7
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:03/input/input10
U: Uniq=
H: Handlers=kbd event8
B: PROP=0
B: EV=3
B: KEY=3e000b00000000 0 0 0
I: Bus=0001 Vendor=10ec Product=0269 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input11
U: Uniq=
H: Handlers=kbd event9
B: PROP=0
B: EV=40001
B: SND=6
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input12
U: Uniq=
H: Handlers=event10
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input13
U: Uniq=
H: Handlers=event11
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card0/input14
U: Uniq=
H: Handlers=event12
B: PROP=0
B: EV=21
B: SW=140
Last edited by kYd (2014-07-01 18:11:45)

Hi gav989,
welcome to the forums. Please have a look at our forum etiquette, esp. at the "Pasting Pictures and Code" section.
The image you posted is too big, but only slightly, so I leave it there for now. You may want to look at these screenshot posting rules as well.

Ethernet not dectect link, despite NIC link light

My ethernet card is:
# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pg
Wake-on: d
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: no
Sometime, when I plug the link, it's not detect the LAN has been linked despite NIC link light. I must reboot the system to reenable it.
# dhcpcd eth0
dhcpcd[15257]: version 5.6.3 starting
dhcpcd[15257]: eth0: waiting for carrier
I've tried restart Networkmanager and Dbus services but it't not detect the link.
can you help me how to fix it?

Here is mine
lspci -k
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: agpgart-intel
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: i915
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
Subsystem: Acer Incorporated [ALI] Device 0260
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: uhci_hcd
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: uhci_hcd
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03)
Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: uhci_hcd
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: uhci_hcd
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: uhci_hcd
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: ehci_hcd
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: lpc_ich
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: i801_smbus
00:1f.6 Signal processing controller: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem (rev 03)
Subsystem: Acer Incorporated [ALI] Device 0260
04:00.0 Network controller: Intel Corporation WiFi Link 5100
Subsystem: Intel Corporation WiFi Link 5100 AGN
Kernel driver in use: iwlwifi
05:00.0 Ethernet controller: Atheros Communications Inc. AR8131 Gigabit Ethernet (rev c0)
Subsystem: Acer Incorporated [ALI] Device 0260
Kernel driver in use: atl1c

Why does my ipad not work when powered up and screen just lights up dark blue?

IPad Model A1219 does not respond when powered up, screen barely lights up just a dark blue screen thats it. will not do anything else, why?

I think the subVI is working just fine when called from the main. I think what you're expecting is an indicator on the main VI to update as the subVI runs. What you will see on the main front panel is just the last value that a subVI has. That is the intended behavior of subVIs and function calls in all other languages. If you want to to update a front panel indicator while a subVI runs, pass a reference to the indicator into the subVI and update that reference instead of the indicator on the subVI. The other way is via a global variable. I've attached a modified version of your porgram.
Attachments:
Pass_a_Reference.vi ‏11 KB
GL_Flicker_mod.vi ‏66 KB

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

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

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

Pxi cards on 1000b cahssis not detected under windows 98

my mxi-3 card is being detected on windows startup (mxi-3 optimization software is running correctly) but all other pxi cards on my 1000b pxi chassis are not detected.

Anis,
Well, I always prefer to try the simplest things first. In this case, that would be fully powering down the chassis and the computer. Then powering on the chassis first, and a few seconds later, powering on the computer. If this doesn't help, then you would probably want to try any or all of the following troubleshooting steps to try and isolate the problem:
- Try removing all but the mxi-3 and one other card from chassis and then try booting up.
- Try placing the pci mxi-3 card in a different slot in the computer.
- Try uninstalling and reinstalling all the NI software on your computer. (better yet, format and reinstall).
- Try the pci mxi-3 card in a different computer.
- Try a different set of mxi-3 cards (if available)
- Check
device manager to see if there are any errors or warnings.
So those are the things that I would try. If after all that you still have no luck connecting you may have a hardware problem and need to RMA (Return Materials Authorization) your hardware.
Please post back with what you find.
Regards,
Jed R.
Applications Engineer
National Instruments

Logic Board Does Not Detect Hard Drive???

Problem on startup shows "Folder with (?) Mark on it". Tried to use Disk Utility but it does not detect. Replaced drive and still nothing. Use the drive as external and it boots normal. It looks like it's something else. I have order a new cable connection that goes from the logic board to the hard drive, as it's cheaper to obtain than a logic board, but lets just say that it wasnt that and there is a problem with the logic board, can I buy a "9.5 mm SATA Optical Bay SATA Hard Drive Enclosure" to place the hard drive and boot from it? When I went into Disk Utility it did detected the DVD drive, so I know that portion of the logic board works fine. I don't use or need the DVD drive, and wondering if I can do this, it cost less than buying a logic board.
Please let me know if this is possible, Thanks in advance.

Well logic board seems faulty from the connecting point of the hard drive but not from the optical drive. Optical drive is detected by the Disk Utility, but not the hard drive, and thats why I was thinking of using the optical bay to run the machine.

NI PXI-1033 not detected if turned on after PC

Hi,
I noticed that MAX does not detect the presence of the NIPXI-1033 if it is turned on after the PC.
There is a programmatic solution to resynchronize the device? My application using C # and C + +.
thanks
Roberto Guerzoni
Solved!
Go to Solution.

Thank you Roberto
It is normal what happens. Your PC has to see the device during the boot up. It is a BIOS matter.
Have a great weekend!
Antonios

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

DVD-Audio and "can not detect sound blaster card" with Audigy2 Va

I recently purchased an "Audigy2 Value" card from an eBay user, because I recently purchased some DVD-Audio discs. I downloaded the Audigy2 drivers from the website, and the Creative MediaSource player. 5. Surround sound worked fine for me, though sometimes the driver would reset to the default 2/2. sound and I would have to re-select 5. sound, which was annoying.
Then I was completely unable to get the MediaSource player to recognise my DVD-Audio discs, and the EAX functionality of the player would never work. The EAX logo never appeared in the player. When I tried installing the MediaSource player from an install disc, I got the message "can not detect sound blaster card". Then I discovered the world of EEPROM problems.
I followed advice from some other threads, including using ScanPCI to get information on the card, which yielded the following result.
When installed on my machine (Asus A7A266 motherboard) the ScanPCI reads:
Vendor 02h Creative Labs
Device 0008h Unknown
Command 0005h (I/O Access, BusMaster)
Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
Revision 00h, Header Type 00h, Bus Latency 20h
Self test 00h (Self test not supported)
PCI Class Multimedia, type Audio
Subsystem ID 0002h Unknown
Subsystem Vendor 02h Creative Labs
Address 0 is an I/O Port : 0000A800h
System IRQ 5, INT# A
New Capabilities List Information :
Power Management Capabilities
Supports power state D2
Supports power state D
Current Power State : D0 (Device fully-operational, no power saving)
On another machine (specs unknown, it's a "house pc") I got this (with 3 entries!):
Vendor 02h Creative Labs
Device 0002h EMU0K Audio Chipset (SB Li've!)
Command 0004h (BusMaster)
Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
Revision 04h, Header Type 80h, Bus Latency 20h
Self test 00h (Self test not supported)
PCI Class Multimedia, type Audio
Subsystem ID 002002h CT4850 SBLi've! Value
Subsystem Vendor 02h Creative Labs
Address 0 is an I/O Port : 00009000h
New Capabilities List Information :
Power Management Capabilities
Current Power State : D0 (Device fully-operational, no power saving)
Vendor 02h Creative Labs
Device 7002h PCI Gameport Joystick
Command 0004h (BusMaster)
Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
Revision 0h, Header Type 80h, Bus Latency 20h
Self test 00h (Self test not supported)
PCI Class Input, type Other
Subsystem ID 002002h PCI Gameport Joystick
Subsystem Vendor 02h Creative Labs
Address 0 is an I/O Port : 00008800h
New Capabilities List Information :
Power Management Capabilities
Current Power State : D0 (Device fully-operational, no power saving)
Vendor 02h Creative Labs
Device 0008h Unknown
Command 0004h (BusMaster)
Status 0290h (Has Capabilities List, Supports Back-To-Back Trans., Medium Timing)
Revision 00h, Header Type 00h, Bus Latency 20h
Self test 00h (Self test not supported)
PCI Class Multimedia, type Audio
Subsystem ID 0002h PCI Gameport Joystick (Guess Only!)
Subsystem Vendor 02h Creative Labs
Address 0 is an I/O Port : 00008400h
New Capabilities List Information :
Power Management Capabilities
Supports power state D2
Supports power state D
Current Power State : D0 (Device fully-operational, no power saving)
(Just a note: above you can clearly see that it does not say I have an Audigy, it thinks it is a SBLi've. Is this normal? The card IS an Audigy 2, it says so on the card.)
So, I put the card back on my own PC, thinking this has fixed my EEPROM, but I get the same as before. Subsystem ID 0002h. And of course the install software will not detect the card.
I realise that I could go back to using the web drivers, but this still leaves me with MediaSource not recognising the card and not enabling DVD-Audio or EAX, which is why I bought the card in the first place!
I have heard that the VIA chipset is possibly to blame for the EEPROM problems on the Audigy cards, and certainly it seems like it is not permanent, since it gave different information on the other PC. So now I am seriously considering getting a new motherboard.
Do other motherboards cause this same problem? I don't want to buy another board and get the same trouble. All I want is to be able to install my MediaSource and have it recognise my card so I can listen to my DVD-Audio discs.
Cheers,
Russ.

Figured out my problem. Installing the drivers from the web to begin with was a bad idea. They just did not work properly with the card.
The "card not found" problem has gone as well, after installing it in another PC. I am also using the proper install disc now, as the other one I was using turned out to not be for the Audigy 2 value after all, but was an Audigy 2 install disc. That easily explains the "Card not found" error. The differing results from the ScanPCI program are still bizarre, though.
Thanks to all of the people on the forum who posted information in other threads to help me deal with this issue. For now I am sticking with the original drivers from the disc and I am not upgrading.

Cinema Display not detected

I got my 20" Cinema Display back from repair today (backlight problem) and now I can't get my MacBook Pro to detect that it's attached. While it was at the repair center, I used a CRT as a second monitor. So today, I just closed the MBP (didn't shut it off, which I think is what cause the problem), disconnected the CRT, connected the ACD and opened the MPB back up. Completely black screen, with the little LED on all the time.
So, troubleshooting:
- The MBP still detects the CRT
- ACD is detected by both a G4 and G5
- A different 20" ACD is ALSO not detected by my MBP
- Reset NVRAM and SMC
- Booted MBP in safe mode
- Booted MBP from startup CD
- Tried various resolutions while the CRT was connected, thinking maybe it was stuck on one that's not compatible with the ACD
- Moved and recreated the com.apple.windowserver.* files
I'm running 10.4.9 and here's what the graphics/displays info says, WITH the Cinema Display connected:
ATI Radeon X1600:
Chipset Model: ATY,RadeonX1600
Type: Display
Bus: PCIe
VRAM (Total): 256 MB
Vendor: ATI (0x1002)
Device ID: 0x71c5
Revision ID: 0x0000
ROM Revision: 113-xxxxxx-086
EFI Driver Version: 01.00.086
Displays:
Color LCD:
Display Type: LCD
Resolution: 1680 x 1050
Depth: 32-bit Color
Built-In: Yes
Core Image: Supported
Main Display: Yes
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Display:
Status: No display connected
Been messing with this for four hours, and I still have a blank display. Any other ideas? From one thread someone mentioned replacing the logic board fixed a similar problem.
MacBook Pro Mac OS X (10.4.9)

UPDATE:
I just got back from my visit to a mac genius. Of course Murphy's law was in full effect! With my MBP connected to the cinema display in the Mac store, everything worked as it is supposed to.
Well, I rush home thinking that maybe mine would now work - - no luck! He did suggest that I try connecting analog with the provided dvi-to-vga adapter. This suggestion DID work! BUT, I want my video digital! That is why even though I was happy with the iBook G4 that I bought last year, I wanted digital video + expanded desktop!
I think I will make another reservation with the Mac Genius, but this time, bring my monitor. Will keep you posted...

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

Similar Messages

Maybe you are looking for