2
2
2-139
2-139
Technical Explanation > Embedded RDS > Troubleshooting
Technical Explanation > Embedded RDS > Troubleshooting
Remedy 2: Troubleshooting using communication error log (COM-LOG)
1) Start Service Mode at Level 1.
2) Select COPIER > Function > INSTALL > COM-LOG and touch the blank field on the right
side. The communication error log list screen is displayed.
NOTE:
• Only the initial part of error information is displayed in the communication error log list
screen.
• "*" is added to the top of the error text in the case of an error in communication test (method
name: getConfiguration or communicationTest) only.
F-2-182
3) When each line is selected, the communication error log detailed screen is displayed as
shown in the figure below. (Example: No. 04)
NOTE:
• A detailed description of the error appears below 'Information'. (Max 128 characters)
• Touch the [OK] button to return to the communication error log list screen.
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.
Cause: The network environment is inappropriate, or RGW-ADR 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 error log from COM-LOG.
• Check whether RGW-ADR or RGW-PORT settings has changed. If RGW-ADR or RGW-
PORT settings has changed, restore initial values. For initial values, see "Service cautions".
F-2-183