viMove 0xBFFF003E (VI_ERROR_IO)

[bbwpdad]

I have opened the soft front panel for two instruments in my VXI chassis and when I switch focus between them I occasionaly get a VI_ERROR_IO.  From the spy capture, it always occurs during a viMove operation.  What does this error mean?

I also noticed that the session handle is the same value.  Could this be causing the I/O error?

17791.  viSetAttribute (VXI0::3::INSTR (0x01017940), DEST_ACCESS_PRIV, 4)
Process ID: 0x00000398         Thread ID: 0x00000310
Start Time: 13:03:46.920       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

17792.  viSetAttribute (VXI0::2::INSTR (0x01017940), SRC_ACCESS_PRIV, 0)
Process ID: 0x00000AF4         Thread ID: 0x000009B4
Start Time: 13:03:46.920       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

17793.  viGetAttribute (VXI0::2::INSTR (0x01017940), USER_DATA, 26476624)
Process ID: 0x00000AF4         Thread ID: 0x000009B4
Start Time: 13:03:46.920       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

17794.  viIn16 (VXI0::2::INSTR (0x01017940), 1, 0x00000024, 51479)
Process ID: 0x00000AF4         Thread ID: 0x000009B4
Start Time: 13:03:46.920       Call Duration 00:00:00.000
Status: 0 (VI_SUCCESS)

> 17795.  viMoveOut32 (VXI0::3::INSTR (0x01017940), 3, 0x00040000, 764, {0x00000000,0x00000000,...})
> Process ID: 0x00000398         Thread ID: 0x00000310
> Start Time: 13:03:46.920       Call Duration 00:00:00.000
> Status: 0xBFFF003E (VI_ERROR_IO)

Robert Applebee

[Chris-G]

Hi Robert,

This may be an issue with the DMA used between the hardware and the computer. I've seen evidence of similar issues sometimes arising when using a newer, faster computer with an older VXI system. KnowledgeBase: VXI MXI DMA Move problems in Linux addresses this issue. Although it specifically addresses the problem for Linux, this sounds like it might be applicable in your situation. This forum also addresses and outlines a solution to a very similar problem.

Essentially, disabling DMA might solve the occasional error. I would recommend giving this a try. Keep in mind however that this will increase the CPU usage in your computer. You might end up having to trade off the occasional error for slower PC performance.

Hopefully this helps!

Chris G

[bbwpdad]

Hi,

This issue has appeared again in one of our systems.  Can you tell me what conditions specifically cause this error to be returned?

Knowing what condition(s) cause this specific error code in the viMove functions would allow us to troubleshoot the system.

Robert Applebee

[M.J]

Hi Robert,

This is a known hardware issue with a certain revision of the VXI-MXI-2 Controller when used with relatively fast computers. If you would like to verify that your controller is affected, you can reply with your part number. Next, you can proceed with an RMA to update the outdated portion of the card which is causing trouble. There would probably be a cost associated with the RMA process. 

For potential work around, as mentioned above by Chris, please either turn off DMA or refer to the below forum link for other options:

http://forums.ni.com/t5/VXI-and-VME/VI-ERROR-IO-while-viMOVE-operation-on-VXI-MXI-2/td-p/1302260.

Hope this helps you move forward.

[bbwpdad]

MJ,

I have two serial numbers that exhibit this issue:

131BE7A

AED81C

Robert

[MCOTO]

Hello Robert,

One of your devices is affected with this issue (S/N:AED81C). If you would like to process an RMA please contact us calling to the 877-493-2406. Otherwise, you can implement the workaround mentioned by M.J in a previous interaction.

Regards,

MCOTO

Applications Engineer

National Instruments

[bbwpdad]

You mention that only one of the devices has this issue yet both serial numbers exhibit the same failure.  I have two other modules that lock up the PC and the only way to recover is to force power down the PC.  I have tried disabling the DMA with no luck.  Do you have any other suggestions?

[bbwpdad]

I was curious why one PC locked up and one generates an IO error so I swapped the VXI-MXI2 and the PCI-MXI2 cards between the PC that locks up and the PC the gets the IO error (Both PCs are identical).  Swapping the VXI-MXI2 card did not change the error but when I swapped the PCI-MXI2 card the PC that was locking up now generates IO errors.

PCI-MXI2 card that generates IO error SN A30909

PCI-MXI2 card that locks up SN 1311243

[Nick-A]

The link that MJ referenced has some other possible workarounds that could potentially help.  Did you have a chance to look through those and give those a shot?  The end solution could potentially end in an RMA.  That is odd behavior that you are seeing since both of the computers are identical.

Nick

[bbwpdad]

I have tried the registry key and disabling DMA without success.  Slowing down the system by disabling the DMA would not be acceptable to our customer even if it did solve the problem.  A previous reply indicated that this is a knwn issue with the VXI_MXI2 controller but my test indicatted that the issue is with the PCI-MXI2 card.  This issue seems to date back as far as 2010, is there fix that doesn't slow down the system?

Robert