Vaisala viewLinc 4.3 User Manual Page 185

  • Download
  • Add to my manuals
  • Print
  • Page
    / 206
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 184
Troubleshooting Tips
viewLinc 4.34| 4177
Alarms
Q: I'm receiving communication alarms in viewLinc. I think my
network Device or Vaisala Veriteq Device has stopped respond-
ing. What do I do?
1 Ensure your Vaisala Veriteq Devices are plugged in and/or batteries
charged (HMT140).
2 Ensure your network Devices are connected to a power supply and
the power supply is plugged in. On a Digi or vNet Device, the power
light on the front of the Device should be solid red.
3 Ensure the Device is connected to and communicating with the net-
work. Try to ping the Device by typing the following at a command
prompt: ping <IP address of the Device>.
4 If there is communication between the Device and the network,
check that the Vaisala-supplied cable is connected properly. If the
light is solid red, there is a problem with the network Device or
Device cable. Ensure your Device has been configured to use
RealPort (see http://www.vaisala.com/en/lifescience for more). If
this still doesn’t fix the problem, go to step 6.
5 If the light is working correctly but you are still receiving com-
munication alarms, open the Windows Device Manager on the
viewLinc computer and ensure the Device is still installed:
a From the Windows Control Panel select System and Security |
Administrative Tools | Computer Management | Device Man-
ager.
b Under the Multiport serial adaptor category in Device Manager,
you should see an entry for the Device with the address you con-
figured. If you don't see the Device, try connecting another
working Device, or reinstall the Device.
6 If the light on the cable is not working properly, open vLog and
determine if the cable can communicate with the Vaisala Veriteq
Device. If there is a problem with the Device communicating with
the vLog graphing application, it is likely the Device or Device cable
is not functioning properly. Try connecting the Device to a new vNet
Page view 184
1 2 ... 180 181 182 183 184 185 186 187 188 189 190 ... 205 206

Comments to this Manuals

No comments