Pipe Data Connection Error

[Anonymous]

We have just switched from 2010 to 2013, and are experiencing some problems on two different projects.  The issue is that we have our pipe networks located within on drawing, then data shortcuted to our production drawings.  However, the pipes are not drawing either in plan or profile to the correct size.

They read correct in the pipe size, the style is set to display the correct "parts" of the pipes, but they are incorrect.  It is not consistent within regards to a single pipe size being incorrect, nor is it the same sizes between the two projects.

Has anyone had this issue before?

[jmayo-EE]

Type SetNetworkCatalog into the command line and make sure it is pointing to the correct catalog path. If you just upgraded it is set to the default catalog location.

[Anonymous]

That was already done, we direct everyones catalogue to a central location in an attempt to ensure that everyone is using the same parts.

[jmayo-EE]

How about partcatalogregen?

[Anonymous]

That has been completed as well.  It is the oddest of glitches.  Everything about the parts themselves seems correct.  But the display to outer walls sometimes in plan sometimes in profile display as different sizes.

Also sometimes the pipe labels will reference a third different size altogather.  Even though the pipe is reading the correct part.

[tom_berning]

We had that problem when we went from 2008 to 2010. I was told that the parts list stores unique identifiers to the pipe catalog and if you open a drawing using a different catalog, the pipe network may have problems. Our only solution was to keep a copy of the 2008 pipe catalog and a copy of the 2010 catalog in different folders. When we worked on the project that came from 2008, we would map to the 2008 catalog. The problem was to remember to change the catalog mapping back afterwards so drawings created in 2010 wouldn't have problems.

[jmayo-EE]

You are correct and Help staes the same but I don't think you would have those problems if you updated the 2008 catalog with the new items in the 2010 catalog. You also would not need to make all new custom part sizes and families when you upgrade. We are still using the catalog we started with from 07 and it has been updated each release. We use the same catalog for all files on all releases.

Migrating the new parts to your existing catalog if pretty easy. Just copy the new part dwg, xml and bmp files to your catalog location, open C3D and type partcatalogregen.

More in help and here

http://civilsurveysolutions.com.au/files/Migrating%20Data%20and%20AutoCAD%20Civil%203D.pdf

This from Help

http://docs.autodesk.com/CIV3D/2013/ENU/index.html?url=filesCUG/GUID-4AAB71D5-5BA6-4EE6-86EC-1ED3207...

[Anonymous · Accepted solution]

Both of the above answers are correct, however once the error has been made the fix is slightly more complicated.

We had to first swap all of the offending parts to working sizes, then remove them from the parts list within the drawing.

Then recreate the sizes to be correct.  Then swap all parts back to the correct sizes.

Also any plans that were referencing the affected parts needed to have the data shorcuts removed, then readded.

We did attempt to do the partcatalogregen fix, but it seems that once the parts become "corrupted" the damage is done so to speak.