Difference between revisions of "TUFLOW Message 2051"
Jump to navigation
Jump to search
Melissa1987 (talk | contribs) |
Melissa1987 (talk | contribs) |
||
| Line 6: | Line 6: | ||
|suggestions=Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object. | |suggestions=Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object. | ||
| − | + | ||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 11:40, 23 December 2022
TUFLOW Message
ERROR 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.
Alternate Message
WARNING 2051 - Connection object unused or not snapped to a 2D HX or 2D SX object.
Description
Connection object unused or not snapped to a 2D HX or 2D SX object. All connections (CN objects) must be snapped to a 1D/2D interface object.
Suggestions
Review boundary configuration, if a HX or SX boundary is desired ensure HX or SX object exists and CN object is correctly snapped. If no boundary is desired remove CN object.
| Up |
|---|
 2xxx Messages
|