Symptom
10.Email alarms were not sent out.
11.TWS reboots during runtime.
12.TSSP cannot connect to TWS.
Possible Problem
No email was received by expecting recipients when alarm happens.
Intermittent system failure.
No connection between the computer and the TWS.
|
| monitor CMOS battery level. | |
|
|
| |
Possible | Action | Prevention | |
Cause | |||
|
| ||
– No outgoing mail server | – Specify an outgoing mail server address | – Make sure to coordinate and only | |
address specified to the | given to you by the LAN administrator. | use data disclosed to you by the | |
TWS. | – Assign an originating email address to | LAN administrator. | |
– No originating email | the TWS. This item is found in the | – Review all information first in the | |
address specified to the | Company info section of the TSSP. | TSSP before saving and uploading | |
TWS. | – Make sure all the receiving email | to the TWS. | |
– Incorrect receiving email | addresses are correct and valid. |
| |
addresses specified to the |
|
| |
TWS. |
|
| |
– Data collisions in the | – System will always try to revive itself | – Give access only to known | |
network. | when there are unknown internal | personnel. | |
– Unknown Internal DB | problems or restrictions not allowing it | – Make sure that the TWS has a | |
engine problem. | to continue its normal operation. This is | unique IP address in the LAN. | |
– Hard drive problem during | to ensure that the TWS will always be | – Check the content of the log | |
file saving at runtime. | available and running. | directory to keep track of the | |
– Maximum system | – Contact ASI for assistance if the TWS | history of the system from its last | |
utilization reached, and no | keeps resetting for no apparent reason | reboot. | |
more resources are | and cannot resume to normal operation. | – Keep in touch with ASCO Power | |
available to use. | – Make sure to notify your LAN | Technologies for new releases and | |
– Internal thread problem. | administrator if sympton persists. | service packs. | |
– Hackers. |
|
| |
– Incorrect serial cable used. | – Check serial connection of the client | – Follow this Installation Manual for | |
– TSSP was not configured to | station running the TSSP and the TWS. | how to install the TWS and use the | |
the right port being used. | – Make sure you are connected to COM1 | TSSP. | |
– Damaged comm. port. | of the TWS. |
| |
– Damaged serial cable used. | – Check if you are using the right cable. |
| |
| You must use the serial cable that came |
| |
| with the product. |
| |
| – Configure the TSSP properly, assigning |
| |
| only the appropriate port and baud rate |
| |
| settings. |
| |
| – Use another available port. |
| |
| – Use another spare serial cable. |
| |
|
|
|
