viIn16() Non-Fatal Run Time error

[herbertwatson]

I am  having an issue with this section of the code.  When I run the following steps on TestStand 2012, LabWindows CVI 2012, and Window 7.0

      ReturnCode = viIn16 (hInstr, VI_PXI_CFG_SPACE, 0x00, &VendorId);
      ReturnCode = viIn16 (hInstr, VI_PXI_CFG_SPACE, 0x02, &DeviceId);

 I receive the attached error.

I do not get this error with 11 of my 14 PXI devices.

The devices I get this error from are

National Instruments,     PXI-8360,             PXI Bridge
National Instruments,    PXI-2576,            PXI Switch Multiplexer

This error also occurs in NI-MAX VISA Test Panel.  

This error does not occur on our test station running Windows XP, TestStand 4.2.1 (4.2.1.83), Lab Windows CVI 8.51(356), NI-MAX 4.6.2f1.

I am attaching the section of code.

[jallen88]

herbertwatson,
Which version of VISA is being used in each of these setups?

Have you tried using viIn16Ex() or viMoveIn16Ex() to see if those also return an error?

Windows 7 changed the way they allow access to memory registers on devices, so this may be the issue.

[herbertwatson]

I am using VISA version 5.2.  viIn16Ex() or viMoveIn16Ex() do not cause a Non Fatal Run Time error.  However, both functions return an identical error message and incorrect data.

[jallen88]

herbertwatson,
When you say that both viIn16Ex() or viMoveIn16Ex() return an identical error message, do you mean that their return code is also -1073807257 and the message is "The given session or object reference does not support this operation."?

Have you tried the '8' or '32' versions of these functions to see if the devices can accept a different data size?

[herbertwatson]

Yes the return code is also -1073807257 and the message is "The given session or object reference does not support this operation.".

I have tried the '8' or '32' versions of these functions with the same result?

[jallen88]

herbertwatson,

Can you capture and attach a log from NI I/O Trace so we can gain more insight into the VISA calls that are being made?

KB 4P3FR2LQ: Performing a Good NI I/O Trace Capture for Debugging/Troubleshooting