2
2
2-188
2-188
Process/Operation > Embedded RDS > Troubleshooting
Process/Operation > Embedded RDS > Troubleshooting
No.3
Symptom: Registration information of an E-RDS is once deleted from the UGW server, and is
re-registered after that. If a communication test is not performed, then device information
on the UGW becomes invalid.
Causes: When registration of the E-RDS is deleted from the UGW, the status will be changed
to that the communication test has not completed because related information has lost from
a database.
So, device information will also become invalid if that condition will be left for seven days
without performing the communication test.
Remedy: Perform a communication test before becoming the invalidity state.
No.4
Symptom: There was a log, indicating "Device is not ready, try later" in error details of COM-
LOG list.
Cause: A certain problem occurred in networking.
Remedy: Check and take actions mentioned below.
1) Check networking conditions and connections.
2) Turn on the power supply of a device and perform a communication test about 60 seconds
later.
No.5
Symptom: "Unknown error" is displayed though a communication test (COM-TEST) has done
successfully.
Cause: It could be a problem at the server side or the network load is temporarily faulty.
Remedy: Try again after a period of time. If the same error persists, check the UGW status
with a network and UGW administrator.
No.6
Symptom: Enabling Service Browser (BRWS-ACT) results NG!
Cause: A communication test with UGW has not been performed, or a communication test
result is NG!
Remedy: Perform a communication test, and check that the test with UGW finishes
successfully.
No.7
Symptom: I cannot make a service call request.
Cause: There has been already a service call request.
Remedy: Perform either of the following remedy works:
• Touch the [Cancel] button to cancel the service call request that has been made.
• A service technician performs a complete processing for the service call request that has
been made.
No.8
Symptom: Initializing the CA certificate (CA-KEY) results in NG!
Cause: Initialization process of the CA certificate has completed abnormally.
Remedy: Initialize the HDD.
