LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

viEnableEvent returns error 0xBFFF0083

Solved!
Go to solution

I am trying to enable interrupts in a driver using VISA and I am receiving an error that does not make any sense.  Here are the calls that I am making to VISA and viEnableEvent returns 0xBFFF0083 or VI_ERROR_INV_LENGTH.

 

status = viOpen(defaultRM[0], desc, VI_NULL, VI_NULL, &instr[0]);

status = viInstallHandler (instr[0], VI_EVENT_PXI_INTR, IHandler, /*uhandle*/ (ViAddr)0);

status = viEnableEvent(instr[0], VI_EVENT_PXI_INTR, VI_HNDLR, VI_NULL);

 

If anyone has encountered this error or can dig into the function to see what causes it, I would appreciate it.

 

Thanks,

John

0 Kudos
Message 1 of 5
(3,198 Views)

Hello John,

I this same error related to some other VISA calls, like the viMove, but also related to the address that you are accessing with the VISA Event call. However, they seem to be corrected on later VISA versions. What's the VISA version you have? You could always download the latest VISA driver and see if it persists. It would also be a good thing to rule out the hardware you are talking to. Can you give more details on what instrument you are talking to and on what interface (serial, Ethernet, etc)?

Regards,
Daniel REDS
RF Systems Engineer

Help us grow.
If a post solves your question, mark it as The Solution.
If a post helps, give Kudos to it.
0 Kudos
Message 2 of 5
(3,183 Views)

Hi Daniel,

 

I am porting over interrupts to VISA for a ARINC 664 PCIe board.  I currently have interrupts working in a Windows version of the driver so I know that the board is functioning properly with interrupts.  The VISA driver works, I just want to add the interrupt callback functionality to it.

 

I am currently working with VISA 5.0.2, I will try upgrading to 5.1.2 to see if it helps.

 

Thanks,

John

0 Kudos
Message 3 of 5
(3,179 Views)

Hello John,

 

Have you tried Example 7-1 on page 90 of the VISA Manual? It seems that you are calling the same functions, except maybe for the malloc function, but let's see if you get that same error with this example code.

Regards,
Daniel REDS
RF Systems Engineer

Help us grow.
If a post solves your question, mark it as The Solution.
If a post helps, give Kudos to it.
0 Kudos
Message 4 of 5
(3,171 Views)
Solution
Accepted by topic author J_A_B

In case anyone else runs into this error, the error was caused by interrupts not being implemented in the inf file.  After going through the driver wizard again and setting up interrupts in the inf file everything worked as expected.

0 Kudos
Message 5 of 5
(3,149 Views)