Mitsubishi Electric MELSEC iQ-R User Manual page 243

Message log
WeeklySchedule[n] is not Primitive
WeeklySchedule[n] Type=X is different from
Type Y
NotificationClass N not found
Event cannot send (Broadcast is used for
Confirmed)
CClient_Base::SendRequest Device not
operational
CClient_Base::SendRequest Device not
found Device-XX
CClient_Base::SendRequest Device not
operational Device-XX
CClient_Base::SendRequest Unknown
RemoteServer Address Device-XX
CClient_Base::SendRequest Dev-XX
networkno Y not found
CClient_Base::SendRequest Dev-XX
NonSegment RemoteServer
SendByteCount>Y Device-ZZ
Log level Message detail
Moderate A data type other than the following data
error 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
Moderate The same data type is not specified for all
error "Data Type" of WeeklySchedule[1] to
WeeklySchedule[7] in the WeeklySchedule
property of the Schedule object.
Moderate An attempt was made to send an Event
error notification, but the NotificationClass object
to specify a send destination was not
registered.
Moderate An attempt was made to send an Event
error 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.
Moderate Sending failed because the value of the
error 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.
Moderate The instance number of the BACnet device
error of the specified destination is one that the
BACnet module does not recognize.
Moderate Sending failed because the value in the
error 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.
Moderate Sending failed because the IP address of
error the BACnet device of the destination
specified with the device instance number is
unknown.
Moderate Sending failed because the BACnet module
error does not recognize the network number of
the destination.
Moderate An attempt was made to send a packet by a
error 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.
Corrective action
• Check the setting in the WeeklySchedule
property of the Schedule object.
• Check the setting in the WeeklySchedule
property of the Schedule object.
• Check the settings of both the RecipientList
property of the NotificationClass object and
the NotificationClass property of the object
that sent an Event notification.
• Check the destination set in the RecipientList
property of the NotificationClass object.
• Select [BACnetDevice], and check the value
in the "DeviceStatus" column of the send
destination device on the "BACnetDevice"
screen.
• 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.
• Select [BACnetDevice], and check the value
in the "DeviceStatus" column of the send
destination device on the "BACnetDevice"
screen.
• 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.
• 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.
• Check the setting of the BACnet device
(communication target).
• Check a cause to become the packet size
large.
3 TROUBLESHOOTING
3.5 Message Log List
3
241