setting contraints on assemblies

[Anonymous]

We have upgraded to 2014 and the sub-assembly/assembly method seems to be different. I tried the old method of building each reach of the sub-assembly the old way by using the generic tools in the toolbox but it throws everything to one side of the baseline. Then I decided to simply draw a polyline of my template and create an assebly from this. I was successful in doing so but I still haven't found a way to set the constraints for each reach in the assembly.

The template is fairly simple. It is not a road job but a levee job w/ an adjacent berm w/ an access channel attached. I need to set point to surface constraints on several of the points and horizontal and slope parameters for other reaches. My goal is to create a typical section that can be dumped into the library and later retrieved and modified for site specific designs.

Any help would be greatly appreciated. I have gone through the help menu and I can't seem to find a solution to this problem. I'm sure it's there somewhere but I can't seem to find it.

[Anonymous]

We have upgraded to 2014 and the sub-assembly/assembly method seems to be different. I tried the old method of building each reach of the sub-assembly the old way by using the generic tools in the toolbox but it throws everything to one side of the baseline. Then I decided to simply draw a polyline of my template and create an assebly from this. I was successful in doing so but I still haven't found a way to set the constraints for each reach in the assembly.

The template is fairly simple. It is not a road job but a levee job w/ an adjacent berm w/ an access channel attached. I need to set point to surface constraints on several of the points and horizontal and slope parameters for other reaches. My goal is to create a typical section that can be dumped into the library and later retrieved and modified for site specific designs.

Any help would be greatly appreciated. I have gone through the help menu and I can't seem to find a solution to this problem. I'm sure it's there somewhere but I can't seem to find it.

[Anonymous]

Which Subassembly are you using.  Some have a left/right parameter others have plus/minus offset parameter to determine side.  Try the "LinkWidthAndSlope" subassembly on the generic tab.  Before or after adding that subassembly, you can change the side parameter to left or right.

[Anonymous]

Which Subassembly are you using.  Some have a left/right parameter others have plus/minus offset parameter to determine side.  Try the "LinkWidthAndSlope" subassembly on the generic tab.  Before or after adding that subassembly, you can change the side parameter to left or right.

[Anonymous]

OK, I'm setting the baseline (horizontal alignment) @ the CL of the fill. From there I was using 'link offset and slope' to define the top width of the fill in both directions. For the side slopes of the fill, I was using 'link slope to surface'. For the berm it was back to the 'link offset and slope'. For the cut slope of the channel (opposite side of the berm from the fill) I used 'link slope to elevation'. For the bottom width of the excavation I went back to 'link offset and slope'. Finally on the backslope of the excavation I used 'link slope to surface'.

I thought this would set the constraints I was looking for in the previous version of the software (V2012) but it isn't. The fill slope has to connect to daylight (surface), the slope on the top and sides of the fill have to be constraned to certain values. The length of the berm has to be constrained. The slope of the excavation has to be constrained. The elevation of the bottom of the excavation has to be constrained. The backslope of the excavation has to run to daylight.

This was very easy to do in V2012. You drew in the segments of the subassembly and put 2 constraints on each segment. You could pick each point and edit the constraints to fit your needs for the design. What happened to this method??

[Anonymous]

OK, I'm setting the baseline (horizontal alignment) @ the CL of the fill. From there I was using 'link offset and slope' to define the top width of the fill in both directions. For the side slopes of the fill, I was using 'link slope to surface'. For the berm it was back to the 'link offset and slope'. For the cut slope of the channel (opposite side of the berm from the fill) I used 'link slope to elevation'. For the bottom width of the excavation I went back to 'link offset and slope'. Finally on the backslope of the excavation I used 'link slope to surface'.

I thought this would set the constraints I was looking for in the previous version of the software (V2012) but it isn't. The fill slope has to connect to daylight (surface), the slope on the top and sides of the fill have to be constraned to certain values. The length of the berm has to be constrained. The slope of the excavation has to be constrained. The elevation of the bottom of the excavation has to be constrained. The backslope of the excavation has to run to daylight.

This was very easy to do in V2012. You drew in the segments of the subassembly and put 2 constraints on each segment. You could pick each point and edit the constraints to fit your needs for the design. What happened to this method??

[Anonymous]

BTW- I've tried the +/- thing and it doesn't change the direction on the X axis.

[Anonymous]

BTW- I've tried the +/- thing and it doesn't change the direction on the X axis.

[Anonymous]

BTW- I've tried the +/- thing to get the segment to change direction on the X axis and it doesn't work. It will work on the Y axis.

[Anonymous]

BTW- I've tried the +/- thing to get the segment to change direction on the X axis and it doesn't work. It will work on the Y axis.

[doni49]

Screenshot of your typical section would go along way to helping someone understand what you need.  Once we understand what you need, we can better assist you.

• In Windows, press Print Screen.  This will put an image of everything that's on our screen(s) onto the clipboard. 
• Open Microsoft Paint and click Ctrl V to paste contents of your clipboard into the image file.
• Save the image file with a PNG extension.
• Insert the image into your message using the image icon in the toolbar above (assuming you're not using the mobile version of the forum board).

[doni49]

Screenshot of your typical section would go along way to helping someone understand what you need.  Once we understand what you need, we can better assist you.

• In Windows, press Print Screen.  This will put an image of everything that's on our screen(s) onto the clipboard. 
• Open Microsoft Paint and click Ctrl V to paste contents of your clipboard into the image file.
• Save the image file with a PNG extension.
• Insert the image into your message using the image icon in the toolbar above (assuming you're not using the mobile version of the forum board).

[Anonymous]

OK Doni-

Here you go-

I think if you put this together w/ the previous explanation of what constraints I need it will all synch up.

Bear in mind, this is simply a polyline that I drew and I changed it into an assembly. The control points are there.

Thanks

[Anonymous]

OK Doni-

Here you go-

I think if you put this together w/ the previous explanation of what constraints I need it will all synch up.

Bear in mind, this is simply a polyline that I drew and I changed it into an assembly. The control points are there.

Thanks

[Anonymous]

Forgot about the dual monitors!!

Template on the left screen.

[Anonymous]

Forgot about the dual monitors!!

Template on the left screen.

[doni49]

---

@Anonymous wrote:

@Anonymous, I'm setting the baseline (horizontal alignment) @ the CL of the fill. From there I was using 'link offset and slope' to define the top width of the fill in both directions. For the side slopes of the fill, I was using 'link slope to surface'. For the berm it was back to the 'link offset and slope'. For the cut slope of the channel (opposite side of the berm from the fill) I used 'link slope to elevation'. For the bottom width of the excavation I went back to 'link offset and slope'. Finally on the backslope of the excavation I used 'link slope to surface'.

I thought this would set the constraints I was looking for in the previous version of the software (V2012) but it isn't. The fill slope has to connect to daylight (surface), the slope on the top and sides of the fill have to be constraned to certain values. The length of the berm has to be constrained. The slope of the excavation has to be constrained. The elevation of the bottom of the excavation has to be constrained. The backslope of the excavation has to run to daylight.

This was very easy to do in V2012. You drew in the segments of the subassembly and put 2 constraints on each segment. You could pick each point and edit the constraints to fit your needs for the design. What happened to this method??

---

It sounds like your complaint has to do with needing to tell the corridor what objects to use as targets. 

LinkSlopeToSurface has have a target surface defined (always has needed it) -- otherwise how would it know what surface to target?  The LinkOffsetAndSlope needs an offset distance and/or an alignment to use as the offset target.  Again, how would it know how far to go otherwise?

[doni49]

---

@Anonymous wrote:

@Anonymous, I'm setting the baseline (horizontal alignment) @ the CL of the fill. From there I was using 'link offset and slope' to define the top width of the fill in both directions. For the side slopes of the fill, I was using 'link slope to surface'. For the berm it was back to the 'link offset and slope'. For the cut slope of the channel (opposite side of the berm from the fill) I used 'link slope to elevation'. For the bottom width of the excavation I went back to 'link offset and slope'. Finally on the backslope of the excavation I used 'link slope to surface'.

I thought this would set the constraints I was looking for in the previous version of the software (V2012) but it isn't. The fill slope has to connect to daylight (surface), the slope on the top and sides of the fill have to be constraned to certain values. The length of the berm has to be constrained. The slope of the excavation has to be constrained. The elevation of the bottom of the excavation has to be constrained. The backslope of the excavation has to run to daylight.

This was very easy to do in V2012. You drew in the segments of the subassembly and put 2 constraints on each segment. You could pick each point and edit the constraints to fit your needs for the design. What happened to this method??

---

It sounds like your complaint has to do with needing to tell the corridor what objects to use as targets. 

LinkSlopeToSurface has have a target surface defined (always has needed it) -- otherwise how would it know what surface to target?  The LinkOffsetAndSlope needs an offset distance and/or an alignment to use as the offset target.  Again, how would it know how far to go otherwise?

[doni49]

---

@Anonymous wrote:

Which Subassembly are you using.  Some have a left/right parameter others have plus/minus offset parameter to determine side.  Try the "LinkWidthAndSlope" subassembly on the generic tab.  Before or after adding that subassembly, you can change the side parameter to left or right.

---

A simple way to remember which is which:

• An "Offset" is the distance from the baseline.
• A "Width" is the width (length in X direction only -- not Y direction) of that particular link.

An Offset will be positive (right side) or negative (left side) relative to the baseline.  If the link wants a Width, it will also expect a Side parameter.

[doni49]

---

@Anonymous wrote:

Which Subassembly are you using.  Some have a left/right parameter others have plus/minus offset parameter to determine side.  Try the "LinkWidthAndSlope" subassembly on the generic tab.  Before or after adding that subassembly, you can change the side parameter to left or right.

---

A simple way to remember which is which:

• An "Offset" is the distance from the baseline.
• A "Width" is the width (length in X direction only -- not Y direction) of that particular link.

An Offset will be positive (right side) or negative (left side) relative to the baseline.  If the link wants a Width, it will also expect a Side parameter.

[Anonymous]

It sounds like your complaint has to do with needing to tell the corridor what objects to use as targets.

---------------------------------------------------------------------------------------------------------------------------------

Yes sir. You hit it on the head.

 

LinkSlopeToSurface has have a target surface defined (always has needed it) -- otherwise how would it know what surface to target?  The LinkOffsetAndSlope needs an offset distance and/or an alignment to use as the offset target.  Again, how would it know how far to go otherwise?

----------------------------------------------------------------------------------------------------------------------------------------

I was trying to use a default name for the surface. I used a distance from baseline when I first tried this and it didn't work.

Bottom line?? I'm trying to set up a default template to load in the library that can be opened and modified for site specific applications. I was assuming I could do this??

[Anonymous]

It sounds like your complaint has to do with needing to tell the corridor what objects to use as targets.

---------------------------------------------------------------------------------------------------------------------------------

Yes sir. You hit it on the head.

 

LinkSlopeToSurface has have a target surface defined (always has needed it) -- otherwise how would it know what surface to target?  The LinkOffsetAndSlope needs an offset distance and/or an alignment to use as the offset target.  Again, how would it know how far to go otherwise?

----------------------------------------------------------------------------------------------------------------------------------------

I was trying to use a default name for the surface. I used a distance from baseline when I first tried this and it didn't work.

Bottom line?? I'm trying to set up a default template to load in the library that can be opened and modified for site specific applications. I was assuming I could do this??

[Anonymous]

Let me know if this is possible to set up (a default template).

If so, how would you approach this??

I have to run but I will be back early tomorrow morning to check this.

Thank you for your time.

[Anonymous]

Let me know if this is possible to set up (a default template).

If so, how would you approach this??

I have to run but I will be back early tomorrow morning to check this.

Thank you for your time.

[Anonymous]

I went back to the subassembly toolbox. I used the 'linkwidthandslope' command on the generic tab. I entered the width as a negative number and set the direction to left and IT STILL puts the subassembly section in my 'right' column under the baseline in the Prospector even though the graphics show otherwise..

What's going on here??

I've had similiar blowups recently concerning graphics not accurately shown in the Prospector.

[Anonymous]

I went back to the subassembly toolbox. I used the 'linkwidthandslope' command on the generic tab. I entered the width as a negative number and set the direction to left and IT STILL puts the subassembly section in my 'right' column under the baseline in the Prospector even though the graphics show otherwise..

What's going on here??

I've had similiar blowups recently concerning graphics not accurately shown in the Prospector.

[doni49]

---

@Anonymous wrote:

Let me know if this is possible to set up (a default template).

If so, how would you approach this??

I have to run but I will be back early tomorrow morning to check this.

Thank you for your time.

---

If there's a way to do this without doing some programming yourself (using .net), I don't know what it is.  And in fact, I really don't beleive it is possible and am not sure how I'd even go about it using .net.

[doni49]

---

@Anonymous wrote:

Let me know if this is possible to set up (a default template).

If so, how would you approach this??

I have to run but I will be back early tomorrow morning to check this.

Thank you for your time.

---

If there's a way to do this without doing some programming yourself (using .net), I don't know what it is.  And in fact, I really don't beleive it is possible and am not sure how I'd even go about it using .net.

[doni49]

---

@Anonymous wrote:

I went back to the subassembly toolbox. I used the 'linkwidthandslope' command on the generic tab. I entered the width as a negative number and set the direction to left and IT STILL puts the subassembly section in my 'right' column under the baseline in the Prospector even though the graphics show otherwise..

What's going on here??

I've had similiar blowups recently concerning graphics not accurately shown in the Prospector.

---

Post your dwg and I'll take a look at it.

[doni49]

---

@Anonymous wrote:

I went back to the subassembly toolbox. I used the 'linkwidthandslope' command on the generic tab. I entered the width as a negative number and set the direction to left and IT STILL puts the subassembly section in my 'right' column under the baseline in the Prospector even though the graphics show otherwise..

What's going on here??

I've had similiar blowups recently concerning graphics not accurately shown in the Prospector.

---

Post your dwg and I'll take a look at it.

[Anonymous]

"If there's a way to do this without doing some programming yourself (using .net), I don't know what it is.  And in fact, I really don't beleive it is possible and am not sure how I'd even go about it using .net."

Don-

This would be of great use if a programmer from AutoDesk or a 3rd party could write a .lisp or whatever to pull this off.

I know this functionality is available in other CADD products that I have used in the past.

A great time saver, not having to reproduce templates for every file if you have a few standards and can simply call them up and

modify them, depending on design parameters.

D

[Anonymous]

"If there's a way to do this without doing some programming yourself (using .net), I don't know what it is.  And in fact, I really don't beleive it is possible and am not sure how I'd even go about it using .net."

Don-

This would be of great use if a programmer from AutoDesk or a 3rd party could write a .lisp or whatever to pull this off.

I know this functionality is available in other CADD products that I have used in the past.

A great time saver, not having to reproduce templates for every file if you have a few standards and can simply call them up and

modify them, depending on design parameters.

D

[Anonymous]

"Post your dwg and I'll take a look at it"

Will do.

[Anonymous]

"Post your dwg and I'll take a look at it"

Will do.

[doni49]

1. I don't see where you've added a "LinkWidthAndSlope". 
2. Your file contains an assembly with NO subassemblies assigned to it and an UNASSIGNED subassembly (one that's not assigned to an assembly).
3. I just realized that you said you entered a negative value for the width and Left for the side.  That will force C3D to treat it as RIGHT -- it's basicaly like saying 0 - (-1).  THe negative tells it to do the opposite of what it would otherwise do.

[doni49]

1. I don't see where you've added a "LinkWidthAndSlope". 
2. Your file contains an assembly with NO subassemblies assigned to it and an UNASSIGNED subassembly (one that's not assigned to an assembly).
3. I just realized that you said you entered a negative value for the width and Left for the side.  That will force C3D to treat it as RIGHT -- it's basicaly like saying 0 - (-1).  THe negative tells it to do the opposite of what it would otherwise do.

[Anonymous]

---

@Anonymous wrote:

I went back to the subassembly toolbox. I used the 'linkwidthandslope' command on the generic tab. I entered the width as a negative number and set the direction to left and IT STILL puts the subassembly section in my 'right' column under the baseline in the Prospector even though the graphics show otherwise..

What's going on here??

I've had similiar blowups recently concerning graphics not accurately shown in the Prospector.

---

The subassembly is grouped under the parent subassembly it is attached to.  Groups are created automatically whenever a aubassembly is attached to the assembly centreline.  For example a subassembly set to right attached to the baseline creates the first group called "right", a subassembly set to left connected to that subassembly will be in the same group called "right"

With the LinkWidthAndSlope subassembly, you use the the side (left/right) parameter for direction and leave the width parameter as a positive number.  You've told it to go left and then the negative width pushed it back to a right direction.  That would be the same as right with a positive direction.  If attaching this to another subassembly, left or right has no impact to the assembly construction grouping.

[Anonymous]

---

@Anonymous wrote:

I went back to the subassembly toolbox. I used the 'linkwidthandslope' command on the generic tab. I entered the width as a negative number and set the direction to left and IT STILL puts the subassembly section in my 'right' column under the baseline in the Prospector even though the graphics show otherwise..

What's going on here??

I've had similiar blowups recently concerning graphics not accurately shown in the Prospector.

---

The subassembly is grouped under the parent subassembly it is attached to.  Groups are created automatically whenever a aubassembly is attached to the assembly centreline.  For example a subassembly set to right attached to the baseline creates the first group called "right", a subassembly set to left connected to that subassembly will be in the same group called "right"

With the LinkWidthAndSlope subassembly, you use the the side (left/right) parameter for direction and leave the width parameter as a positive number.  You've told it to go left and then the negative width pushed it back to a right direction.  That would be the same as right with a positive direction.  If attaching this to another subassembly, left or right has no impact to the assembly construction grouping.

[Anonymous · Accepted solution]

---

@Anonymous wrote:

It sounds like your complaint has to do with needing to tell the corridor what objects to use as targets.

---------------------------------------------------------------------------------------------------------------------------------

Yes sir. You hit it on the head.

 

LinkSlopeToSurface has have a target surface defined (always has needed it) -- otherwise how would it know what surface to target?  The LinkOffsetAndSlope needs an offset distance and/or an alignment to use as the offset target.  Again, how would it know how far to go otherwise?

----------------------------------------------------------------------------------------------------------------------------------------

I was trying to use a default name for the surface. I used a distance from baseline when I first tried this and it didn't work.

Bottom line?? I'm trying to set up a default template to load in the library that can be opened and modified for site specific applications. I was assuming I could do this??

---

Are you using the LinkSlopeToSurface subassembly?  As Doni49 advised when using the LinkSlopeToSurface subassembly the surface is only specified in the corridor object target parameters.  It is not specified in Assembly layout design.  To target a surface (surface contraint) you must use a subassmbly that is able to target a surface.  Right-click the subassembly tool-palette button and help to see the target documentation for any subassembly.

By default "template" do you mean a typical section (Assembly in Civil 3D) or do you mean a DWT template file.  Once you have a Civil 3D Assembly set up you can drag it into a tool-palette tab, or you can wblock it out and set up a library of Assemblies (typlical sections) to reuse in other projects.

[Anonymous · Accepted solution]

---

@Anonymous wrote:

It sounds like your complaint has to do with needing to tell the corridor what objects to use as targets.

---------------------------------------------------------------------------------------------------------------------------------

Yes sir. You hit it on the head.

 

LinkSlopeToSurface has have a target surface defined (always has needed it) -- otherwise how would it know what surface to target?  The LinkOffsetAndSlope needs an offset distance and/or an alignment to use as the offset target.  Again, how would it know how far to go otherwise?

----------------------------------------------------------------------------------------------------------------------------------------

I was trying to use a default name for the surface. I used a distance from baseline when I first tried this and it didn't work.

Bottom line?? I'm trying to set up a default template to load in the library that can be opened and modified for site specific applications. I was assuming I could do this??

---

Are you using the LinkSlopeToSurface subassembly?  As Doni49 advised when using the LinkSlopeToSurface subassembly the surface is only specified in the corridor object target parameters.  It is not specified in Assembly layout design.  To target a surface (surface contraint) you must use a subassmbly that is able to target a surface.  Right-click the subassembly tool-palette button and help to see the target documentation for any subassembly.

By default "template" do you mean a typical section (Assembly in Civil 3D) or do you mean a DWT template file.  Once you have a Civil 3D Assembly set up you can drag it into a tool-palette tab, or you can wblock it out and set up a library of Assemblies (typlical sections) to reuse in other projects.