Mitsubishi Electric MELSEC iQ-R - Page 243

3 TROUBLESHOOTING
3.5 Message Log List
241
3
WeeklySchedule[n] is not Primitive Moderate
error
A data type other than the following data
types is specified for "Data Type" of a
schedule set for the WeeklySchedule
property of the Schedule object.
•Null
•BOOLEAN
•Unsigned
• Signed
•REAL
•Bitstring
• Enumerated
•Date
•Time
• ObjectIdentifier
• Check the setting in the WeeklySchedule
property of the Schedule object.
WeeklySchedule[n] Type=X is different from
Type Y
Moderate
error
The same data type is not specified for all
"Data Type" of WeeklySchedule[1] to
WeeklySchedule[7] in the WeeklySchedule
property of the Schedule object.
• Check the setting in the WeeklySchedule
property of the Schedule object.
NotificationClass N not found Moderate
error
An attempt was made to send an Event
notification, but the NotificationClass object
to specify a send destination was not
registered.
• Check the settings of both the RecipientList
property of the NotificationClass object and
the NotificationClass property of the object
that sent an Event notification.
Event cannot send (Broadcast is used for
Confirmed)
Moderate
error
An attempt was made to send an Event
notification, but the send destination, which
was registered for the NotificationClass
object, was set to send a packet with
confirmation even though a broadcast
address was set.
• Check the destination set in the RecipientList
property of the NotificationClass object.
CClient_Base::SendRequest Device not
operational
Moderate
error
Sending failed because the value of the
SystemStatus property of the Device object
in a BACnet device, for which the specified
destination address was set, was regarded
as one other than Operational.
• Select [BACnetDevice], and check the value
in the "DeviceStatus" column of the send
destination device on the "BACnetDevice"
screen.
CClient_Base::SendRequest Device not
found Device-XX
Moderate
error
The instance number of the BACnet device
of the specified destination is one that the
BACnet module does not recognize.
• Select [BACnetDevice] to open the
"BACnetDevice" screen. Check the IP
address displayed between a slash '/' and
colon ':' in the "BACnet Address" column.
• When sending an Event notification, check
the destination set in the RecipientList
property of the NotificationClass object.
CClient_Base::SendRequest Device not
operational Device-XX
Moderate
error
Sending failed because the value in the
SystemStatus property of the Device object
for the BACnet device of the destination
specified with the device instance number
was regarded as one other than
Operational.
• Select [BACnetDevice], and check the value
in the "DeviceStatus" column of the send
destination device on the "BACnetDevice"
screen.
CClient_Base::SendRequest Unknown
RemoteServer Address Device-XX
Moderate
error
Sending failed because the IP address of
the BACnet device of the destination
specified with the device instance number is
unknown.
• Select [BACnetDevice] to open the
"BACnetDevice" screen. Check the IP
address displayed between a slash '/' and
colon ':' in the "BACnet Address" column.
• When sending an Event notification, check
the destination set in the RecipientList
property of the NotificationClass object.
CClient_Base::SendRequest Dev-XX
networkno Y not found
Moderate
error
S
ending failed because the BACnet module
does not recognize the network number of
the destination.
• Select [BACnetDevice] to open the
"BACnetDevice" screen. Check the IP
address displayed between a slash '/' and
colon ':' in the "BACnet Address" column.
• When sending an Event notification, check
the destination set in the RecipientList
property of the NotificationClass object.
CClient_Base::SendRequest Dev-XX
NonSegment RemoteServer
SendByteCount>Y Device-ZZ
Moderate
error
An attempt was made to send a packet by a
segment send (divided send) because the
send packet exceeded the number of
packets that could be sent in one packet, but
the BACnet device, communication target,
did not support the segment reception.
• Check the setting of the BACnet device
(communication target).
• Check a cause to become the packet size
large.
Message log Log level Message detail Corrective action