Working on OpenRoads Designer CONNECT Edition.
When I placed the nodes I opted to not used the active terrain to set the top elevation and was able to input the elevation desired. However, when I am trying to adjust the invert elevation of the node/inlet it resets the top elevation. I have looked at all the options and default design constraints to see if there was a constraint set but I didn't saw anything. I have tried adjusting the elevations in the Utilities tab under Properties and also in Drainage tab but no success. Is there something that am not seeing that could be the reason I can't adjust the elevations.? Thank you in advance for your help.
The cells used in these instances are based upon a bottom cell definition and a top cell definition along with a plan cell definition. The plan cell matters but little here, but the relationship between the top cell and the bottom cell may be quite concerning. I will provide an instance: we have a top cell which includes our grate, and a bottom cell which includes the total vault. The top of the top cell is located at 0, 0, 0, and the bottom of the bottom cell is located at 0, 0, -2.66666. If I attempt to place this cell, the top may be located at any elevation, but the invert may only be located at an elevation of -2.66666 below that elevation or deeper (less). It seems like you are dealing with an issue where the cell definitions cannot match your needs; that is, one which is less than 2.66666' in my example. The top cell and the bottom cell cannot exceed less that the mathematical definitions which they have been designed with. Most of the time, if one tries to provide an invert definition of a smaller value, the top elevation moves up or the bottom elevation moves down. Sometimes, nothing happens at all depending upon other cell definition data.
Survey my information here and see if such may help you understand your issue.
Thank you for you response Mark. Is there an option to adjust the top and bottom cell definition?
The cell definitions are called from the DU dgnlib via element templates tied to feature symbology/ feature definitions. As they are cells, they are static in the definition of the top node and the definition of the bottom node. If the difference in elevations (invert to top) is greater than the cells, the software "fills in" this difference when placing the node. So one does not "adjust the top and bottom cell definition", one has to come up with entirely different cells to accomplish a need which is less in difference than the original cells used to construct the node.
The Bentley default DU dgnlib has many examples of the element templates, feature symbologies and feature definitions. Such is how I learned what is truly going on when placing a node in DU. I do suggest learning from their examples.