Owner manual

OpenLNS Programmer's Reference 992
persistent update failures on a device, you should re-commission the device with the
Commission method.
lcaErrNsUpdateFileXferError 4034
The database updates were successful, but an update error occurred. The NSS will
continue to try to update the nodes in the background if the UpdateInterval property of
the System object is set to a non-zero value, and you can force a retry with the
RetryUpdates method. You can keep track of which devices are up to date using
commissioning events and by reading the CommissionStatus property of each AppDevice
object.
You can keep track of which devices are up to date using commissioning events, and by
reading the CommissionStatus property of each AppDevice object. If you are receiving
persistent update failures on a device, you should re-commission the device with the
Commission method. Most file update errors map to this status during an update.
lcaErrNsUpdateWhenUncnfg 4035
The database updates were successful, but one or more nodes could not be updated
because they are not configured. You should ensure that all applicable devices are
configured when this error occurs. The NSS will continue to try to update the nodes in
the background if the UpdateInterval property of the System object is set to a non-zero
value, and you can force a retry with the RetryUpdates method.
You can keep track of which devices are up to date using commissioning events, and by
reading the CommissionStatus property of each AppDevice object. If you are receiving
persistent update failures on a device, you should re-commission the device with the
Commission method.
lcaErrNsUpdateWhenAppless 4036
The database updates were successful, but one or more nodes could not be updated
because they are applicationless. You can load a node’s application by calling the Load
method on the AppDevice object associated with the node. The NSS will continue to try
to update the nodes in the background if the UpdateInterval property of the System
object is set to a non-zero value, and you can force a retry with the RetryUpdates
method.
You can keep track of which devices are up to date using commissioning events, and by
reading the CommissionStatus property of each AppDevice object. If you are receiving
persistent update failures on a device, you should re-commission the device with the
Commission method.
lcaErrNsUpdateCpFileTooShort 4037
The database updates were successful, but one or more devices was not updated because
a configuration property file in the device is shorter than specified in the database. This
is usually due to an inconsistency between the device’s configuration property template
file and its data file. The configuration property template file should be the same for all
devices of a given type. If you encounter this type of error, check to make sure that the
device is using the appropriate external interface file. The NSS will continue to try to
update the nodes in the background if the UpdateInterval property of the System object
is set to a non-zero value, and you can force a retry with the RetryUpdates method.
You can keep track of which devices are up to date using commissioning events, and by
reading the CommissionStatus property of each AppDevice object. If you are receiving
persistent update failures on a device, you should re-commission the device with the
Commission method.