CUTBACK 45 ELBOWS NOT WORKING - ValueError could not convert string to float

[dmckagueN6VZ3]

We are having an issue specifically when trying to cutback less than 45 degrees. If we try to cutback a 90deg elbow, it works fine. If we try to cutback less than 45 degrees I receive an error an error in the command line that says: ValueError: could not convert string to float:
Traceback (most recent call last):
File "varmain\arcsub\cpb_util.pyc", line 101, in CPB_CalcPtsSimple

It seems like one of the out-of-the-box standard python scripts has an error in it. We have this happening on multiple computers with different versions of Plant3D 2022. 

Does anybody know what could be causing this?

[h_eger]

Dear @dmckagueN6VZ3 ,

unfortunately I can not understand this behavior with my AutoCAD Plant 3D installation so I suspect that it is a problem with the installation.
Please contact Autodesk Plant 3D support.

[dmckagueN6VZ3]

After looking into this further, it seems to be an issue with all of our 45s in our built Plant3D catalog. I'm not sure if it got corrupted at some point or what, but we started out with the standard Plant catalog and have added/changed parts over the years to accommodate what we need.

Using one of the standard Plant3D specs like the CS150, the cutbacks work as intended. Our current workaround for this is to model the cutback section using the CS150 spec, then do a spec change to one of our standard specs and it will populate the cutback 45 with our standard spec. I'm not sure why the auto-routing has issues when trying to place a cutback 45, but the spec change workaround seems to be working fully.

We have also had some mixed success by routing using a 3D polyline and then using the "Line to Pipe" command but we still had issues with it just placing a full 45 instead occasionsally.

[matt.worland]

One next step to troubleshoot this would be to compare the CS150 that works to your spec. Look at the elbows and see if there is any difference in the spec/catalog using the spec editor. Maybe something will stand out, and you can fix it that way.

If not, you could also look at specs and catalogs in a database viewer like SQLite Expert. If you haven't looked at a spec or catalog using a database viewer, it will take some learning to understand all of the tables and connections, but maybe there is a difference that can be seen looking at it that way.