ADC 100 Specifiche Scaricare il pdf (Pagina 15)

DOS

From DOS, it is possible to access the ADC-100 in C and Pascal using the DOS driver. It is not possible to

call the ADC-100 DOS driver from BASIC.

The driver uses PASCAL linkage conventions.

The DOS driver does not support huge memory, so the data buffer must be less than 64k bytes.

See ADC100.txt for more information about the DOS driver.

Windows 3.x

In Windows 3.1 it is possible to use the 16-bit Windows driver, or to access the ADC-100 directly.

When running under Windows 3.x, an application is not in complete control- Windows can interrupt at any time.

Interruptions occur every 55 milliseconds, and are also caused by mouse and keyboard input. As a

consequence, the driver cannot always take readings at fixed time intervals. To deal with this, the driver returns

the time at which each reading was taken.

The Windows 16-bit driver is called PICO.386, and is installed in windows\system. It is loaded using a

reference in system.ini:

[386enh]

......

.....

device=pico.386

The driver is accessed using the file ADC10016.DLL: this is installed in the drivers\win sub-directory: for some

applications (eg Visual Basic), it is necessary to copy the DLL to c:\windows\system.

The DLL uses PASCAL linkage conventions, and uses HUGE pointers to data items, so that C and Delphi

programs can access arrays larger than 64k bytes.

Examples are provided for C, Delphi, Visual Basic and Excel.

Windows 95/98/ME

In Windows 95, 98 and ME, you can use the 16-bit or the 32-bit driver: it is also possible to access the ADC-100

directly.

The following applications require 32-bit driver:

• Visual Basic 4 and above

• Excel 7 and above

• Delphi 2 and above

• Borland C 5

• Microsoft C version 2 and above.

• LabVIEW version 4 and above

The 16-bit and 32-bit drivers do not interfere with each other, so it is possible to install both drivers on the same

system, as long as, for any given unit, only one driver is using it at once.

When running under Windows 95, an application is not in complete control- Windows can interrupt at any time.

Interruptions occur every 55 milliseconds, and are also caused by mouse and keyboard input. As a

consequence, the printer port driver cannot always take readings at fixed time intervals. To deal with this, the

driver returns the time at which each reading was taken. Generally speaking, the 16-bit driver gives higher

sampling rates, but the 32-bit driver is less prone to large gaps in the data.

1 2 ... 10 11 12 13 14 15 16 17 18 19 20

Nessun commento

ADC 100 Specifiche Pagina 15