Campbell Scientific AVW200 AVW200-series Vibrating Wire Interfaces - Page 85

in DevConfig under device type AVW200 Series called Off Line Analysis

Get Campbell Scientific AVW200 PDF manuals and user guides View all Campbell Scientific AVW200 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 85 highlights

Appendix E. Status Table Status Fieldname MSPClkFreq(3) MSPClkFreq(4) MSPClkFreq(5) CalOffset VarOutOfBounds SkipScan TrapCode WatchDogCnt ResetTables BattVoltage SRAMMemSize Description MSP430 CPU #3 RC oscillator frequecy in Hz MSP430 CPU #4 RC oscillator frequecy in Hz MSP430 CPU #5 RC oscillator frequecy in Hz Calibration offset voltage Number of times an array was accessed out of bounds Number of skipped scans that have occurred while running the current scan. When making the vibration wire measurement it is normal for the skipscan's to increment A code number that describes the last watch dog event that has happened (updated at power up). Number of Watchdog errors that have occurred while running this program Not Used Current value of the AVW200 battery voltage (value updated every 8 sec). Size of the SRAM memory User can change? No No No No Yes (clear to zero) Yes (clear to zero) Yes Yes (clear to zero) Yes (function disabled) Yes No NOTE The SRAMMemSize parameter was added to OS version STD.02. Older modules have 128 Kbytes of SRAM and newer modules have 512 Kbytes of SRAM. If the SRAMMemSize = 512 K, then the AVW200 will create and overwrite a file for every measurement on each channel. The files are called TS_chan1.bin and TS_chan2.bin. These files have the 4096 samples or TimeSeries data for the last measurement. These files can be retrieved using LoggerNet FileControl or the datalogger instruction GetFile(). A post-processing program in DevConfig under device type AVW200 Series called "Off Line Analysis" can be used to analyze the files. E-3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
Appendix E.
Status Table
Status
Fieldname
Description
User can change?
MSPClkFreq(3)
MSP430 CPU #3 RC oscillator frequecy in Hz
No
MSPClkFreq(4)
MSP430 CPU #4 RC oscillator frequecy in Hz
No
MSPClkFreq(5)
MSP430 CPU #5 RC oscillator frequecy in Hz
No
CalOffset
Calibration offset voltage
No
VarOutOfBounds
Number of times an array was accessed out of
bounds
Yes (clear to zero)
SkipScan
Number of skipped scans that have occurred while
running the current scan. When making the vibration
wire measurement it is normal for the skipscan's to
increment
Yes (clear to zero)
TrapCode
A code number that describes the last watch dog
event that has happened (updated at power up).
Yes
WatchDogCnt
Number of Watchdog errors that have occurred
while running this program
Yes (clear to zero)
ResetTables
Not Used
Yes (function disabled)
BattVoltage
Current value of the AVW200 battery voltage (value
updated every 8 sec).
Yes
SRAMMemSize
Size of the SRAM memory
No
The SRAMMemSize parameter was added to OS version STD.02.
Older modules have 128 Kbytes of SRAM and newer modules
have 512 Kbytes of SRAM.
If the SRAMMemSize = 512 K, then the AVW200 will create and overwrite a
file for every measurement on each channel.
The files are called TS_chan1.bin
and TS_chan2.bin.
These files have the 4096 samples or TimeSeries data for
the last measurement.
These files can be retrieved using LoggerNet
FileControl or the datalogger instruction GetFile().
A post-processing program
in DevConfig under device type AVW200 Series called “Off Line Analysis”
can be used to analyze the files.
NOTE
E-3