BIOS resource conflict

[DeWit]

I have a PXI-1000B chassis with a PXI-8176 controller (Windows 2000), a PXI-5411 waveform generator, a PXI-8210 SCSI interfac, a PXI-6115 A/D board and a PXI-6030E A/D board. At start up I get the message:

Resource Conflict - Allocation error at static node # 10
Press to resume, to enter SETUP.

I have installed the latest BIOS version v1.60, but still the error arises. What could be the cause for this resource conflict?

Thanks

[JuliaD]

Hello,

At this point it would be difficult to say what exactly would be causing the problem. The first thing I would try is to remove all of the boards from the PXI chassis so that the only thing installed is the PXI-8176 controller. Boot up the system and verrify that you do not get the error. Then shut the system down and add only one board at a time to see if the problem is being caused by a particular board. Also, at what point in the boot up process are you getting this error?

It might be a good idea to move this support issue to either the phone or email (since there may be a lot of troubleshooting steps involved). You can do that by visiting the following link and selecting "Phone NI" or "Email NI" and following the instructions:

http://sine.ni.co
m/apps/we/niae_asc.main

Regards,

Julia Dinolfo
Applications Engineer
National Instruments

[DeWit]

Thanks for your reaction.

I followed your advice and I found that the PXI-8210 SCSI interface is causing the Resource Conflict. If I start up the chassis with all the boards plugged in apart from the PXI-8210, the conflict does not occur.

The Resource Conflict arises during start up after de message 'mouse initialized.'

Thanks again.

[JuliaD]

Great, we are making some progress. Here is what I would like you to try:

1. Try installing only the controller and the 8210 board in the chassis and see if you still get the error. What if you swap slots for the 8210?

2. Now add one of the other boards and see if you get the error. Test each of the other boards one at a time (i.e. Only install the controller, 8210, plus one other board, like the 6115. Then swap out the 6115 for another board, like the 6030E). Continue until you have tried the 8210 with each of the other boards alone.

The reason why we are trying this is because in researching your question, I found a similar Dev Exchange post with similar problems. Here is a link to this other line of troubleshooting for your refere
nce:

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000F0450000&ECategory=PXI

3. Lastly, can you send me the part number for your PXI-8210 board? In the mean time, I will get more details on it's revision (this may prove to be relevant information).

Keep me posted with the results of your testing. Have a great night!

Regards,

Julia Dinolfo
Applications Engineer
National Instruments

[DeWit]

1. I already did that, the error occurs if only the PXI-8210 is installed even if I put the board in another slot.

2. I have tried several combinations. The PXI-8176 controller (BIOS v1.6) was in slot 1 during all trials.

PXI-8210 in slot 2
-> Resource Conflict

PXI-8210 in slot 2, PXI-6030E in slot 3
-> Resource Conflict

PXI-8210 in slot 2, PXI-6115 in slot 4
->Resource Conflict

PXI-8210 in slot 2, PXI-5411 in slot 5/6
->Resource Conflict

PXI-8210 in slot 7
->Resource Conflict

PXI-8210 in slot 7, PXI-6030E in slot 3
->Resource Conflict

PXI-6030E in slot 2
-> No Resource Conflict

PXI-6030E in slot 2, PXI-6115 in slot 4, PXI-5411 in slot 5/6
->No Resource Conflict

PXI-6030E in slot 2, PXI-6115 in slot 4, PXI-5
411 in slot 5/6, PXI-8210 in slot 7
->Resource Conflict

So it seems to me that the board itself is causing the problem independent of slot number or other boards. The chassis is built into a pod thus I can unplug the boards, but it is not easy to put them into another slot. These are therefore more or less all combinations I can try.

3. I cannot find the part number, only a serial number.

Thanks again!

[JuliaD]

Great testing!

As for the part number, it will have the form "18xxxxxY-xx", where x = numeric and Y = letter. It might be labeled on your board as "ASSY" (assembly number). In any case, go ahead and send me both the serial number (should be on a sticker below a bar code) and the part number if you can find it (it might also be on a sticker).

It does look like the problem is with this particular board alone. It could be that it needs to be repaired, or updated (the part number/serial number will help me with determining this). Was this board working before? Is it a new board? Lastly, do you have another controller you could test with this board?

Regards,

Julia Dinolfo
Applications Engineer
National Instruments

[DeWit]

The PXI chassis was installed by National Instruments and I assume we got a new board. The serial number is Q10085860, I cannot find a part number anywhere in the documentation. Unfortunately, I do not have another controller board to test the set up.

We have had the resource conflict from the start, but it did not seem to influence the operation of the chassis, so we did not really look into it upto now.

Thanks!

[JuliaD]

Well, I have one more suggestion. Open your device manager (Right-click on the My Computer icon >> select "Properties" >> navigate to the "Hardware" tab >> select the "Device Manager" button).

Open up and look at the resources that Windows had assigned to both the ethernet and scsi devices (especially the IRQ). Check to see if this IRQ is conflicting with any other devices.

Lastly, I think it would be a good idea to speak with an Applications Engineer directly because it sounds like we are most likely going to have to send this board in for repair. You can do so via the following link:

http://sine.ni.com/apps/we/niae_asc.main

Regards,
Julia Dinolfo

Applications Engineer
National Instruments

[DeWit]

I hope this helps, we are going in too deep for me now, so I do not really know what to look for exactly.

The Network Adapters, SCSI and RAID Controllers, and the USB Controllers are all set to interrupt request 09.

The NI Data Acquisition Devices, the NI GPIB Interface, and the Intel SMBus Controller-2443 (under System Devices) are also set to interrupt request 09.

There are no yellow warning signs in the Device Manager and everything seems to work fine.

I have already emailed this question to the NI helpdesk (Netherlands). I think they are more or less at the same point now, so there is still no light at the end of the tunnel.

Thanks again!

[JuliaD]

I just wanted to keep you up to speed on the status of this problem. I have managed to track down the person in the Netherlands office that you have been in contact with. I am working with them to help out with this issue. In the mean time, you should remain in touch with this local office.