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

Troubleshooting Communication Problems

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 62 highlights

AVW200-series 2-Channel Vibrating Wire Spectrum Analyzer Modules 8. Troubleshooting Communication Problems 8.1 Unable to Communicate with DevConfig or Terminal Emulator If you are unable to communicate with DevConfig or the Terminal Emulator, verify that: (1) The AVW200 is powered. The red LED at the front of the AVW200 will remain lit for 15 seconds on initial power up and then blink intermittently. (2) The correct COM port has been selected. The COM port entry is provided on the lower left corner of the DevConfig screen. (3) The correct baud rate of the AVW200 has been selected. The default baud rate of the AVW200 is 38400. 8.2 Datalogger to AVW200 Communication If the datalogger fails to communicate with the AVW200, verify that: (1) The AVW200 is powered. The red LED at the front of the AVW200 will remain lit for 15 seconds on initial power up and then blink intermittently. (2) The AVW200 PakBus address is different than the PakBus address of the datalogger. (3) The AVW200 PakBus address is entered correctly in the AVW instruction of the datalogger program. 8.3 Wireless Communications If you can't connect, check out these possible causes: 1. Verify that the AVW20X is powered. The red LED at the front of the AVW will remain lit for 15 seconds on initial power up and then blink intermittently. 2. Active Interface set wrong The active interface on the radio attached to the DL running the AVW instruction must match the ComPort specified in the AVW instruction; e.g., if you are using an RF401 (configured for SDC7) attached to a datalogger to communicate with a remote AVW206, then the ComPort specified in the AVW instruction must be SDC7 (or whatever active interface the RF401 is set for). 3. Low or weak battery voltage or 12 VDC supply voltage The power supply battery may not be charging properly due to solar panel orientation, poor connection, or due to a charging transformer problem. The battery itself may have discharged too low too many times, ruining the battery. Lead acid batteries like to be topped off. 54

  • 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
AVW200-series 2-Channel Vibrating Wire Spectrum Analyzer Modules
8.
Troubleshooting Communication Problems
8.1
Unable to Communicate with DevConfig or Terminal
Emulator
If you are unable to communicate with DevConfig or the Terminal Emulator,
verify that:
(1) The AVW200 is powered.
The red LED at the front of the AVW200 will
remain lit for 15 seconds on initial power up and then blink intermittently.
(2) The correct COM port has been selected.
The COM port entry is provided
on the lower left corner of the DevConfig screen.
(3) The correct baud rate of the AVW200 has been selected.
The default baud
rate of the AVW200 is 38400.
8.2
Datalogger to AVW200 Communication
If the datalogger fails to communicate with the AVW200, verify that:
(1) The AVW200 is powered.
The red LED at the front of the AVW200 will
remain lit for 15 seconds on initial power up and then blink intermittently.
(2) The AVW200 PakBus address is different than the PakBus address of the
datalogger.
(3) The AVW200 PakBus address is entered correctly in the AVW instruction
of the datalogger program.
8.3
Wireless Communications
If you can’t connect, check out these possible causes:
1.
Verify that the AVW20X is powered.
The red LED at the front of the
AVW will remain lit for 15 seconds on initial power up and then blink
intermittently.
2.
Active Interface set wrong
The active interface on the radio attached to the DL running the AVW
instruction must match the ComPort specified in the AVW instruction;
e.g., if you are using an RF401 (configured for SDC7) attached to a
datalogger to communicate with a remote AVW206, then the ComPort
specified in the AVW instruction must be SDC7 (or whatever active
interface the RF401 is set for).
3.
Low or weak battery voltage or 12 VDC supply voltage
The power supply battery may not be charging properly due to solar panel
orientation, poor connection, or due to a charging transformer problem.
The battery itself may have discharged too low too many times, ruining
the battery.
Lead acid batteries like to be topped off.
54