What Is State Caching in an IVI Driver, and How Is It Different from a Traditional Instrument Driver? Primary Software: Instrument Drivers/IVI>>IVI Compliance PackagePrimary Software Version: N/A Primary Software Fixed Version: N/A Secondary Software: N/A
Problem: What is state caching in an IVI driver, and how does it differ from the way that a traditional instrument driver operates? Solution: IVI drivers are based on an attribute model, which is unique for each given instrument type. They constantly keep track of the state of all of an instrument’s attributes, or current configuration settings. When a user programmatically performs some operation to change the state of the instrument, the IVI Engine compares the desired state to the current state and determines which actual I/O commands need to be sent. IVI drivers avoid a significant amount of overhead associated with traditional drivers by sending the instrument only those commands which are absolutely necessary to perform a given task. These drivers take full advantage of knowing how an instrument is set at any time, and do not perform time-consuming I/O operations, unless necessary. Of course, this state caching feature can be tuned extensively for your own driver. Related Links: Knowledge Base 18C82DIQ: What is IVI? Attachments:
Report Date: 04/30/1998 Last Updated: 04/17/2008 Document ID: DIRECT-3U2SYE |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
