#1
|
|||
|
|||
Force SysId in a new model.
I'm trying to help a friend having troubles loading an assembly that was saved in 3d-data (sda ans sdpc files).
The problem is that a subassembly is corrupted and generates a 337 error when tring to load it or the parent assembly. The solution could be to create a new group with the same SysID of the corrupted one, and replace the broken one with this new one. so, two questions: 1) How to read the current sysid of the broken assembly *sda file? 2) how to create a new group with the same sysid? I have Modeling V16 and V18.1 (with the related versions of Model Manager). |
#2
|
||||
|
||||
Re: Force SysId in a new model.
Hi,
you MAY have a chance to find the SysId with a command like this: Code:
"C:\Program Files\PTC\Creo Elements\Direct Modeling 17.0\binx64\pb_pub" -S -i yourassy.sdac > yourassy.txt - you should be in the directory where your 3D-data are stored - the pathname of the pb_pub.exe should be correct for your version of Modeling. - yourassy.sdac should be the name of your assy The file yourfile.txt contains the sysid of the assy, amongst other information. More info on pbpub.exe can be found if you go to the folder where it's located (in a DOS window) and type: Code:
pb_pub -h You could try if typing this command in the command line: Code:
(cluster-manager-control :allow-missing-files t) Jaap |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | Search this Thread |
Display Modes | Rate This Thread |
|
|