Appendix G Frequently Asked Questions (Faq) - Omega Engineering UWTC-REC3 User Manual

Wireless-to-ethernet receiver
Table of Contents

Advertisement

Appendix G
Frequently Asked Questions (FAQ)
Q: Java applet is not loaded?
A: Check Java Setting (icon in Control Panel). Make sure cache is disabled and your
web browser is enabled for Java.
Q: I do not see any readings even if the applet is loaded, what could be wrong?
A:
1) Check if the battery is still good. You should be able to see the LED when you power
the Connector/Transmitter on.
2) Make sure that there is no Connector/Transmitter with the same Device ID.
Q: What are the error messages that appear on the "Reading", "Chart", and "Diagnostic"
pages?
Open
A: It means that the Connector/Transmitter cannot detect any process sensors.
Check the connections for the process sensor.
Lost
A: It means that the Connector/Transmitter found the Receiver when it was powered on,
but it cannot communicate with it currently.
Make sure the Receiver is powered on, DIP switch #1 (of the 8-DIP switch) on the
Receiver is ON, and there is no obstructive objects blocking the communications path
(see Section 5 for more details). If the obstructive object is only temporary, you will get
the sensor readings once the path is open.
Q: Nothing happens when I click on the Data Logging button, what could be wrong?
A: The Java policy file is not setup properly. Make sure you get a Java policy file and
copy it to a folder in the host computer. Then input the java runtime argument in Java
Setup (Control Panel) with the appropriate path to the policy file. Close all web browser
and re-open the applet again. See Java Setup Section.
Q: The Chart trend line for all the variables are broken, what could be wrong?
A: It indicates that a TCP connection to the Receiver was timed-out and no data was
obtained. Make sure the Receiver is still on in the network and powered up. If there are
too many broken lines, it may indicate that the network load is too heavy.
Q: The trend line for one of my sensors inside one Connector/Transmitter is broken,
what could be wrong?
A: It indicates that TCP connection to the Receiver is good but the Receiver did not
have any readings from the corresponding Connector/Transmitter. Make sure
Connector/Transmitter is still blinking according to the update rate. It could be caused by
a reset/power cycling of the Receiver as well.
55

Advertisement

Table of Contents
loading

Table of Contents