2
2
2-85
2-85
Technical Explanation > Embedded RDS > Troubleshooting
Technical Explanation > Embedded RDS > Troubleshooting
Remedy 2: Troubleshooting using communication log (COM-LOG)
1) Start [Service Mode].
1) Press [Additional Functions (User Mode)] button on the control panel.
2) Press [2] buttons on the control panel.
3) Press [8] buttons on the control panel.
4) Press [Additional Functions (User Mode)] button on the control panel.
2) Select #E-RDS > COM-LOG, and the following communication log will be displayed.
Displayed log is only five latest log.
No:1 Ecode:840F2003
2011 01/09 17:27
3) Select log and touch [OK] button. The communication log detailed screen is displayed.
*Network is not rea
dy , try later : get
4) When a message is displayed, take an appropriate action referring to “Error code and
No.2
Symptom: A communication test results NG even if network setting is set properly.
Causes: The network environment is inappropriate, or RGW-ADDRESS or RGW-PORT
settings for E-RDS have been changed.
Remedy: The following points should be checked.
1) Check network conditions such as proxy server settings and so on.
2) Check the E-RDS setting values.
• Check the communication log from COM-LOG.
• Check whether RGW-ADDRESS or RGW-PORT settings has changed. If RGW-ADDRESS
or RGW-PORT settings has changed, restore initial values. For initial values, see “E-RDS
setting items”.
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.
Summary of Contents for 1750
Page 12: ...Update Firmware XXV Volume Control XXV Backup Data XXVI...
Page 17: ...1 1 Product Overview Product Overview Product Lineup Features Specifications Parts Name...
Page 235: ...7 7 Error Code Error Code Overview Error Code Jam Code Alarm Code...
Page 250: ...8 8 Service Mode Service Mode Outline Details of Service Mode...
Page 333: ...Service Tools General Timing Chart General Circuit Diagram List of User Mode Appendix...