Why Do I Get iberror EDVR(0) After UD1023?Primary Software: LabWindows/CVI Run-Time EnginePrimary Software Version: 3.0 Primary Software Fixed Version: N/A Secondary Software: N/A Hardware: GPIB
Problem: When I run my application that communicates with a GPIB device, it crashes and I receive an error that a subscript is out of range. When I use NI Spy to troubleshoot I get iberror EDVR(0) and I notice that it occurs after a function that uses UD1023 as the device or board descriptor. Solution: The reason this error occurs is that your application is continuously opening UD device handles without closing any of them. A device handle is created every time you use the ibdev function and if you don't close them, it just increments the handle to the next value up until UD1023 and then it runs out of possible values. This happens if you have placed a ibdev command within a while loop or within a function that is called often. There are two things you can do to solve this problem: 1. Use ibdev once at the beginning of your application and pass the UD device handle throughout the rest of the application. 2. When you're done using the handle for a while in your application, call ibonl(ud, 0) to close the device handle. Related Links: KnowledgeBase 1EF6ALQA: Causes of EDVR Error on the GPIB-ENET Device KnowledgeBase 2I3LF9YY: I Am Communicating with My GPIB Instrument and I Receive the EDVR Error After a Few Hours of Operation Knowledge Base 1DREQIQA: GPIB Error Codes and Common Solutions (Part 1) Attachments:
Report Date: 01/11/2009 Last Updated: 12/23/2009 Document ID: 4TAK3PDP |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
