AutoPLANT V8i SS4 and SS5 (tested both) AutoCAD 2012 Hi Everyone, It seems like it is not possible to place a General Wye in AutoPLANT. I added them to the CS150 spec, and the placement starts out fine but once you enter the CTR_END measurements in the dialog and press ok, you will see the following error at the command line: Unable to insert Wye. Could not identify the branch and run indices. I ran it in debug mode, and I was able to trace it back to TEE.EBS, where the function attempts to determine whether the centerlines of the component are symmetrical or not. This function fails somehow and that's where the error comes in. I was able to work around this by modifying the methods.ini file entry for AT_GENERAL_WYE as follows: [AT_GENERAL_WYE] ORIGIN_METHOD = %APP_DIR%\Util\Origin ; at_Wye_determineOrigin DRAW_METHOD = %APP_DIR%\Draw\genWye ; at_GeneralWye_draw ORIENT_METHOD = %APP_DIR%\Util\Orient ; at_Wye_determineOrientation INPUT_METHOD = Common\GenWye ; at_GeneralWye_DlgInput CENTERLINE_METHOD = %APP_DIR%\Util\Ctrline ; at_Wye_Centerline PORT_METHOD = %APP_DIR%\Util\Ports ; at_Wye_definePorts ;EQUIV_PORTS_METHOD = %APP_DIR%\Util\EqPorts ; at_InlineASym_determineEquivPorts //THIS METHOD WOULD NOT PLACE THE WYE EQUIV_PORTS_METHOD = %APP_DIR%\Util\EqPorts ;at_Wye_determineEquivPorts TAP_PORT_METHOD = %APP_DIR%\Util\TapPorts ; at_Tee_determineTapPortLocation PROP_METHOD = Common\CompProp ; at_ComponentProperties_set DATA_METHOD = Common\PipeData ; at_Piping_Data COORDS_METHOD = %APP_DIR%\Util\Coords; at_Wye_defineCoords JSM_OUT_METHOD = XCHG\JSM\GenWyeOut ; JSM_OUT_GENWYE PCF_OUT_METHOD = XCHG\PCF\TeeOut ; PCF_OUT_TEE ;VALID_DATA_METHOD = Common\Tee ; at_Wye_validateAngles // THIS METHOD WOULD NOT PLACE THE WYE VALID_DATA_METHOD = Common\Tee ; at_Wye_validateAnglesMain CHANGE_PLANE_METHOD = %APP_DIR%\Util\chgpl ; at_BendBranch_changePlane SPEC_UPDATE_DATA_METHOD = Common\SpecUpd ; at_SpecUpdate_NoUpdate COG_PIPING = Common\BomDescr ; at_Branch_cog This uses the same methods as the true wye for the adjusted (highlighted items) above. I think this should be logged as a defect so I am reporting it, but this workaround suits us for now. Thanks!!
↧
