Issue
Multiple NS errors may occur in LonMaker / LNS environments during application loading, device commissioning, or network management. These include:
- System Image / Application Load Errors
- NS #184: Neuron model mismatch when loading application
- NS #186: System image cannot be written
- NS #187: System image memory failure during upgrade
- NS #188: System image upgrade failed
- Device, Channel, and Network Errors
- NS #72: Device on wrong channel
- NS #79: Unable to determine channel when adding/registering device
- NS #67: Subnet limit reached
- NS #138: Network interface in wrong/unconfigured state
- LonMark Object / Network Variable Errors
- NS #285: LonMarkObject not dynamic
- NS #286: Network variable not dynamic
- NS #287: LonMarkObject in use (bound variables present)
Product Line
TAC Vista
Environment
- LonMaker
- NL220
- Vista
- LNS
Cause
System Image / LoadEx Related Causes
- Application image incompatible with the device system image (model mismatch)
- LoadEx invoked but system image cannot be written (e.g. not stored in flash memory)
- Failure writing system image due to insufficient or incorrectly located flash memory
- System image successfully transferred but activation/switch to new image fails
Channel and Network Configuration Causes
- Device defined or placed on the wrong channel
- Device added without a channel handle and system cannot determine the correct channel
- Channel topology contains repeaters or bridges preventing correct channel resolution
- Network interface is unconfigured or in the wrong state
- Network subnet limit (255) has been reached
LonMark Object and Network Variable Causes
- Attempting to perform operations on static LonMarkObjects instead of dynamic ones
- Attempting to perform operations on static network variables
- Attempting to delete LonMarkObjects that still contain bound network variables
Resolution
System Image / Application Load Resolutions
- Upgrade the device system image so it matches the application image (NS #184)
- Use the LoadEx method to automatically handle compatibility where supported (NS #184)
- If system image write fails, reattempt loading using Load or LoadEx (NS #186)
- If memory-related failure occurs, reload the application (device may remain applicationless) (NS #187)
- If upgrade fails after transfer:
- Retry the LoadEx method
- Reload the previous system image
Channel and Network Configuration Resolutions
- Move devices to the correct channel in LonMaker (NS #72)
- Ensure the Network Interface is on the correct physical and logical channel (NS #72)
- Recommission devices after correcting channel placement (NS #72)
- Set routers to Repeater mode during commissioning, then return to configured mode (NS #72)
- Ensure the channel is properly configured and topology is not ambiguous (bridges/repeaters) (NS #79)
- Perform a cold reboot of the controller if channel cannot be determined (NS #79)
- Set MgmtMode to lcaMgmtModePropagateConfigUpdates (0) and recommission the interface (NS #138)
- Run the LNS Database Recovery Wizard when required (NS #67, NS #138)
- Use LonWorks Plug ‘n Play Control Panel and select the NSI NI Application where applicable (NS #67, NS #138)
LonMark Object / Network Variable Resolutions
- Check whether objects or variables are dynamic using the IsDynamic property (NS #285, NS #286)
- Avoid assigning, unassigning, or deleting static objects or variables (NS #285, NS #286)
- Before deleting LonMarkObjects:
- Disconnect bound network variables
- Or use lcaLonMarkObjectRemoveAndDisconnectNVs (3)
