Issue
LonMaker makes you wait in a 'transaction queue' before it will process any commands that require communications to the network.
Environment
Echelon LonMaker
Cause
This problem seems to arise when changes are made to the structure of a large network in which the majority of controllers have been commissioned, but not yet installed. LonMaker then tries to continuously update these controllers of the network changes that have been made, but it can't since they are not online. Thus, when any requests are made by the user, they must wait in line until LonMaker gets to their requests.
Resolution
The problem has two solutions:
- The first, and most simple, is to bring all of the commissioned controllers on the network online. This will allow LonMaker's updates to be propagated to them all, causing an end to the cycle.
- The second solution is to decommission any controllers on the entire Network that are not online, but have been commissioned prior to the network changes. This will eliminate LonMaker's desire to update these controllers.
These solutions must be applied to the entire network, and not just the channels that have actually had the network changes performed on them.