Lawson Labs, Inc. 3217 Phoenixville Pike Malvern, PA 19355 PHONE: 800-321-5355 610 725-8800 FAX: 610 725-9344 world wide web - http://www.lawsonlabs.com email - lawsnlab@lawsonlabs.com Model 141 32-bit WinNT/2k/XP console application Application was compiled using MS Visual Developer Studio 5.0 This directory contains archive of source code, and application for interfacing the Lawson Labs, Inc. Model 141 data acquisition board. =============================================== The following files are included in the m141.zip archive. -- used to build application ------------------ M141_NT. CPP M141_NT. H VC_5.DSW VC_5.DSP VC_5.OPT -- needed to run application ----------------- M141_NT. EXE 141EWIN. CFG NT141Lib.DLL PORT_IO.SYS PORT_IO.REG The files M141_NT.EXE, NT141Lib.DLL, and 141EWIN. CFG should be located in the same directory. The file "PORT_IO.SYS " must be located in 32-bit driver directory, for example c:\windows\System32\Drivers. The file "PORT_IO.REG" must be run once to make required entries in Registry for loading of PORT_IO.SYS. That can be done by simply double-clicking on the file, or RUN from the program manager. Required entries can also be done manually using utility such as Regedit.exe. After registry entries are made you must reboot machine before attempting to run the application. ======================================================================================== BRIEF OVERVIEW --- m141_NT shows two modes of operation: polled and scanning. In polled mode individual readings are taken on command. In scanning mode, a pre-defined group of channels are scanned at a preset interval. Scan timing is achieved by using the function GetTickCount(), which has a resolution of 1 millisecond. Timing accuracy in general should fall within a few milliseconds. The timing precision obtainable in any particular case will depend on the percentage of resources given to the Model 141 code and the number and nature of other concurrent tasks. Disk access, for example, will normally take priority over data acquisition. SPECIAL NOTE: Effective 6-5-2000 DLL Debug option has been added to end of configuration file. The application will look for an "x" at line 43 in the configuration file. If it finds it, it reads the next line for debugging information. If debug information is greater than zero, it enables DLL Debugging. With debugging enabled, the DLL will create and write debugging information to 141debug.txt. That file can grow very large quickly, so don't use the debugging option except for troubleshooting. Last updated: 6-5-00