comsof error messages and solution approaches

Warnings and error messages during the calculation

Warning of unconnected points

“Nodes are not connected to the area”

The calculation of the system has two stages. In the first step of the calculation, the potential trench network is converted into a point-and-line model. All trenches are broken at crossings and at these points additional points are created. After this process, the following statement appears:

 mceclip0.png

  • “19 points not connected:” > The 19 points listed in the example are not connected to the rest of the trench network. This is due to unconnected street centerlines.
  • “1 demand point or central office locations are not connected:” > Sometimes, one of the 19 points might be a demand point. This means that the demand point is not connected to the remaining potential trench network.

Solution:

Evaluate the affected points and check the trench network.

 

Multiple connections are not supported

“Multiple connections are not supported”

During the calculation, the calculation process may be aborted if clusters overlap and demand points are located in this overlap region.

mceclip1.png

Demand points must lie unambiguously in one cluster.

Solution:

Prior to the calculation, perform an object validation. There, these neuralgic points are displayed and you have the option of manually correcting the course of the clusters.

mceclip2.png

 

Errors in planning settings

“Error in Design Rules”

Errors that occur within the planning settings are listed in a dialog box and must be corrected.

mceclip4.png 

Solution:

In the example, the bundle size of a cable type was set incorrectly and must be corrected.

 

Planning settings do not exist

“Cannot locate Rules & Material file”

 mceclip5.png

Solution:

In this case, creating the planning setting has been forgotten and needs to be caught up with.

 

Warnings after the calculation

In contrast to the error messages, warnings at the end of the calculation are merely notes on the calculation. The calculation itself has been successfully completed.

 

Cables and/or ducts of different distribution clusters are overlapping (distribution layer)

“Check distribution points for overlapping ducts”

This warning message indicates that cables and/or ducts of different clusters are laid in the same trenches. In other words, cables and/or ducts of one cluster are partially laid in another cluster.

The specified AGG_ID designates the cluster from which cables run in other clusters.

 mceclip6.png

Solution:

The easiest way to find the locations is to only show the layer of the distribution cables. In this way, you can recognize the affected area. The clusters must then be corrected there accordingly.

mceclip7.png

 

Clusters greater than the specified cluster size of 86 have been found

“Clusters were found with a very small size”

If clusters are blocked or clustered automatically due to the distance determination (see Rules Distribution Layer), there may be a notice after the calculation that clusters are too small.

mceclip8.png

In the example, the cluster with AGG_ID 0 is too small. According to the planning settings, a maximum of 48 cables should be connected in a cluster. In the “0” cluster, however, only 2 cables are connected. 

The same can also happen if clusters are larger than the set cluster size from the planning settings. 

Solution:

Adjustment of the cluster size with blocked input clusters.

Blocked point is ignored

“No blocked polygon found”

Specified points are ignored by the system in the calculation if the associated cluster was not blocked. This warning can arise at all network layers. Here is the example of an ignored distribution point in the distribution layer.

mceclip9.png 

Solution: 

Block the cluster associated with the network point.

 

Maximum blowing-in length exceeded

“Maximum blow distance violated”

mceclip10.png

If too short a blowing-in length is selected or the demand points are too far apart, it may be that the double blowing-in length is exceeded when setting an additional handhole. This warning can arise at all network layers. Here is the example for the distribution layer.

 

Error message for manual rings

BackBone Layer: Edges in ConnectionLayer and CableLayer do not match

Solution