2
2
2-69
2-69
Technology > Embedded RDS > Error code and strings
Technology > Embedded RDS > Error code and strings
Error code and strings
The following error information is output in the communication error log details display screen.
(Here, “a server” means UGW.)
• The error information are displayed in the following form.
[*] [Error strings] [Method name] [Error details provided by UGW]
NOTE:
“*” is added to the top of the error text in the case of an error in communication test
(method name: getConfiguration or communicationTest) only.
No.
Code
Error strings
Cause
Remedy
1
0000 0000 SUSPEND:
mode changed.
Unmatched Operation Mode
Initialize the E-RDS setting
(E-RDS > CLEAR).
2
0500 0003 SUSPEND:
Communication
test is not
performed.
Rebooting the device while the
communication test had not been
performed although E-RDS is
enabled.
Perform a communication test
(COM-TEST).
3
0xxx 0003 Server schedule
is not exist
Blank schedule data have been
received from UGW.
Perform and complete a
communication test (COM-
TEST).
4
0xxx 0003 Communication
test is not
performed
Communication test has not
completed.
Perform and complete a
communication test (COM-
TEST).
5
84xx 0003 E-RDS switch is
setted OFF
A communication test has been
attempted with the E-RDS switch
being OFF.
Set E-RDS switch (E-RDS)
to ON, and then perform a
communication test(COM-
TEST).
6
8600 0002
8600 0003
8600 0101
8600 0201
8600 0305
8600 0306
8600 0401
8600 0403
8600 0414
8600 0415
Event
Registration is
Failed
Processing (event processing)
within the device has failed.
Turn the device OFF/ ON.
If the error persists, replace
the device system software.
(Upgrade)
7
8700 0306 SRAM version
unmatch!
Improper value is written in at the
head of the Main Controller PCB
2 SRAM domain of E-RDS.
Turn the device OFF/ ON.
8
8xxx 0004 Operation is not
supported
Method which E-RDS is not
supporting attempted.
Contact help desk
No.
Code
Error strings
Cause
Remedy
9
8xxx 0101 Server response
error (NULL)
Communication with UGW has
been successful, but an error of
some sort has prevented UGW
from responding.
When (Null) is displayed at the
end of the message, this indicates
that there has been an error in the
HTTPS communication method.
Perform and complete a
communication test (COM-
TEST).
10 8xxx 0201
8xxx 0202
8xxx 0203
8xxx 0204
8xxx 0206
Server schedule
is invalid
During the communication test,
there has been some kind of error
in the schedule values passed
from UGW.
When the error occurs, report
the details to the support
section.
And then, after the UGW
side has responded, try the
communication test again.
11 8xxx 0207
8xxx 0208
Internal
Schedule is
broken
The schedule data in the inside of
E-RDS is not right.
Perform a communication
test(COM-TEST).
12 8xxx 0221 Server specified
list is too big
Alert filtering error: The number of
elements of the list specified by
the server is over restriction value.
Alert filtering is not supported
by UGW.
13 8xxx 0222 Server specified
list is wrong
Alert filtering error: Unjust value is
included in the element of the list
specified by the server.
Alert filtering is not supported
by UGW.
14 8xxx 0304 Device is busy,
try later
The semaphore consumption error
at the time of a communication
test.
Try again a communication test
after a period of time.
15 8xxx 2000 Unknown error Some other kind of communication
error has occurred.
Perform and complete a
communication test (COM-
TEST).
16 8xxx 2001 URL Scheme
error(not https)
The header of the URL of the
registered UGW is not in https
format.
Check that the value of URL
of UGW (RGW-ADDRESS) is
https://a01.ugwdevice.net/ugw/
agentif010.
17 8xxx 2002 URL server
specified is
illegal
A URL different to that specified
by the UGW has been set.
Check that the value of URL
of UGW (RGW-ADDRESS) is
https://a01.ugwdevice.net/ugw/
agentif010.
18 8xxx 2003 Network is not
ready, try later
Communication attempted without
confirming network connection,
just after booting up a device in
which the network preparations
are not ready.
Check the network
connection, as per the initial
procedures described in the
troubleshooting.
Perform a communication
test (COM-TEST) about 60
seconds later, after turn on the
device.