beautypg.com

System operation, 1 pc based tools, 1 software and driver installation – Campbell Scientific CDM-VW300 Series Dynamic Vibrating-Wire Analyzer System User Manual

Page 36: Pc based tools, Software and driver installation

background image

CDM-VW300 Series Dynamic Vibrating-Wire Analyzers

A clean display of data, as shown in the previous figure, is obtained by
deactivating all but channel 1 in the CRBasic program. If channels 2 through 8
had not been deactivated, erroneous, but perhaps seemingly-real, data would be
displayed. Channels 2 through 8 are deactivated by setting line 24 in the
CRBasic example in Appendix G.1.2, 20 Hz Measurement Example – One
CDM-VW305, Eight Channels
, to th
e following:

Dim

Enable(8)

As Long =

{ 1, 0, 0, 0, 0, 0, 0, 0}

If proper frequencies are shown, the datalogger has successfully communicated
with the CDM-VW300 via the SC-CPI device and obtained data. A permanent
data collection program for field operation can now be loaded.

7. System Operation

IMPORTANT — Do not connect the CDM-VW300 analyzer or SC-CPI
interface to a PC until AFTER installing DVWTool 1.0 or later or DevConfig
2.04 or later. Consult Section 7.1.1, Software and Driver Installation, for more
information.

7.1 PC Based Tools

All PC software is for use on Windows

®

XP, Windows

®

Vista, Windows

®

7, or

Windows

®

8 operating systems.

7.1.1 Software and Driver Installation

USB communication between the PC and the CDM-VW300 analyzer, and
between the PC and the SC-CPI interface, require that USB drivers be installed
on the PC. For driver installation to work seamlessly, the drivers must be
installed before making the physical USB connections. These drivers are
installed automatically when DVWTool 1.0 software or DevConfig 2.04
software or later are installed.

• If the physical USB connection is attempted before the installation of

the drivers, a non-functional placeholder definition is created in the
Windows

®

USB device list. This placeholder prevents that device

from becoming active during subsequent driver installs and device
connections via USB. The following procedure should correct this
condition:

26