LabView driver Middle semester presentation Shmulik Zobel Pia Zobel advisor- Mony Orbach

The structure of the driver The driver will be built of different VI ’ s. Each VI will be used for a different command. For example: reading from the instrument, writing to it, to initialize it, etc.

Hierarchy of the driver

The structure of the VI ’ s The top level of the VI will be put together with nodes from LabView. As much as possible will be done with functions called from the top level of the VI. This is to ensure more flexibility for the universal driver.

An example of a VI

Communicating with the instrument Our driver will communicate with programs. These need to be programs that continue running by themselves and only talk to the driver when it asked for them. These programs are the instrument ’ s driver which comes with the instrument.

Our VI As we saw in the example of a VI the VISA node talks to the instrument.example of a VI Since our driver will be communicating with programs we will use functions to talk to the programs.

Using functions in LabView To call an outside function from LabView there is a built in Call function node. By adding this node to a block built of different nodes it is possible to receive and return variables to and from the function.

Call function node

Configuring the node In the configure window, it is chosen which file from the disk will be used.

The disadvantage Since each time the function is called again probably we will need to save needed variables at the top level.

An example of a VI calling a function

Our immediate plan To build a driver to talk with the monitor driver. Once the driver for the physics device is finished we will update our driver to match it.

Schedule 7.6 – קוד של windriver בסיסי ל PCI רץ – הבנה בסיסית של הדריבר ויכולת שימוש לצורך כתיבה למרחב הכתובות של המסך – קריאה לפונקציות של הדריבר מתוך LabView תוך שליטה על הפרמטרים – שליטה על הדריבר תוך שימוש בפונקציות שלנו שיופעלו מתוך LabView. 2.7 – שימוש בדריבר של כרטיס ה USB ושליטה עליו ע " י פונקציות שלנו.