Pro/E WF4.0 M220
Syntax:
IF search(ASM_MBR_PARAMETER,"string")>0
statement
ENDIF
Error:
Invalid data type combination at left side of expression
As far as I can tell, this is a limitation of Pro/E (or at least the build I am using). The parameter is a string and I can use the extract function, but any search function using a parameter as the argument always returns an errror. Any help would be greatly appreciated!
Is this a cadidate for an assembly cut?
Actually my parts are both curved, but I thought I state simple with two pieces of tubing, one at a 45 degree angle to the other. The one at the 45 will be cut before being welded to the other (no holes in the parent parent part - just structural). How would you go about making the cut to the 45 degree piece?
The material that needs to be removed in order to nest them together before weld.
This is a candidate for the top down design process. You would make the edits in the assembly with the 45 degree tube active. You can use the vertical tube for its diameter reference, location, and even the projection plane.
Just remember that you now have a dependent reference. You can unlink it manually when you are back in the 45 degree part but sustainability is a nightmare. You have to decide if top-down design models are acceptable in your organization.
You can also consider a skeleton model that holds all the tube centerlines. In this way, you can reference only one model for all your assembly references in lower level parts. This is normally much preferred since you will minimize the number of dependent files to 1 (+assembly).
I am working on a bike frame myself (a reverse engineering session for posterity) and I am not using separate tubes. I am modeling the weldment at a part level. If I need tube prep drawings, I would use assembly cut to cut up the master part into the individual pieces. This may seem backwards, but in this way, the "master" is a part file with the prep'd tubes as subordinates rather than masters. In this way, I am reducing the corruption penalty and the final level assembly part count is actually much smaller. The individual tubes are now independent from the overall assembly but dependent on the inseparable weldments which becomes the parent. If all that makes sense.
Hi,
i do not have current maintenace so cannot download M070,i would just like to know about a issue in assembly and has that issue been resolved in M070?
when we do "save a copy" in assembly in creo 2.0 and the resolution is not what is recommended by PTC i.e. 1280x1024....then window opens out of range and it cannot be scaled also....has that issue been resolved?..i mean can it be diagonally scaled now?
please see the link below:
Try the following syntax:
SEARCH_PARAM=search(asm_mbr_user_parameter,"string")
IF SEARCH_PARAM>0
statement
ELSE
statement otherwise
ENDIF
The first line of the code, the assign operation, cannot be declared upfront somewhere in the top of the relations. This is important, You should define this kind of assign operation right before the if statement where you use the conditional with the parameter that comes from this assign operation, else you might get the same error you get above.
In report table relations, conditional operators such as <, >, ==, <> cannot be used along with system parameters such as asm_mbr_name, asm_mbr_type, etc. You have to first make a copy of those by assigning them to another param.
Make sure you only work with one system parameter such as asm_mbr_name at a time, and then close it with ENDIF before working with another. IF statements can be stacked one into another, but I doubt stacked IFs will ever work with conditional operators as said above.
I am wondering if M070 runs better than M060, M050 seemed great for me (like I don't think it crashed once, ever) but then when I went to M060, I had some flakyness (power exits, etc) hopefully M070 fixed that.
Yup, a bit more bandwidth now from PTC.
Hi!
I've been trying to install Creo 2.0 student version using PTC installation assistant, and I get to the application selection menu.
Under "All applications will be installed at:"
I am free to select a drive other than C:. However, when I change the drive I want to install to, a popup warns me there is insufficient space on disk (0 available). I have tried temporarily freeing most of the drive, and the issue persists. Additionally, if I switch to D: and back to C:, it continues to say there is insufficient space (0 available), despite there being sufficient space before I changed to D:!
This is all quite baffling. My C: drive is a small solid-state drive, so I try to keep applications that require frequent or significant loading on that drive for speed. Creo is not such an application, so I would like to put it on my platter drive D:. Unfortunately, I seem to be unable to do this.
I have tried:
- Deleting the downloaded installer files and redownloading.
- Manually typing in the file location (the install button is grayed out as though it doesn't recognize I typed anything into the All applications will be installed at: dialog box)
- Installing to the default location: this works, but is not what I want to do, and I am hoping I won't be forced to do this as it is quite irritating to limit the space on my small C: drive.
I am using Windows 7 x64. This is the only program that has given my this sort of problem in recent years.
Apologies if I have posted this to the wrong place.
Most of us seem to have better luck completely uninstalling the previouos version and do a fresh install from the full install set. The only thing I leave in place is the license manager (I use an older one).
Do you have sufficient disk space that is marginal, or do you have more than 3X the space required? It likely needs the room to load the compressed package file, the unzipped dataset, -and- the installed program dataset.
Hello,
After manually typing in the path to your D drive folder did you click on the arrow at the right from that path line? The path possibly won't get set if you don't click on that arrow pointing, which is pointing to the right till it's clicked.
I am doing a fresh install each time. I have nothing PTC related installed on my computer.
Drive C: has about 15GB available (required is 3.4 max)
Drive D: has hundreds of GB available.
For clarity, the installer never makes it to the installation step. It gets to the point where I can select where to install it, and then exhibits the behavior described in my original post. It will not let me proceed to installation under any circumstances except installing to drive C: (and then, only if I don't change the drive first).
I went back in to try this, and while it didn't work, I found out that to get it to work the expected way, I have to type in the path manually, and then press enter. Absolutely any other form of entry gives the unexpected behavior described in my original post. Using the drop-down arrow as you suggest only brings out the drop-down box, without "entering" my entered data.
Typing followed by pressing enter works just fine.
Manually type in the path, followed by pressing enter.
Thank you both for attempting to solve my problem! I appreciate your time and helpfulness.
If the spring has a constant cross section, couldn't you simply measure the volume then divide by the cross section area to get the length?
It is possible. I do have a relation to find underscorer in the asm_mbr_name parameter in my repeat region relations.
This relation works on Creo Parametric 2.0 M020, but not on M030, M040, M050, M060 because it is bugged there. It's supposed to be fixed in Creo Parametric 2.0 M070.
This same bug happened to be in some of the Wildfire 4 subversions, which goes about 7 years back, but it was propably resolved back then. I'd think it was resolved in the latest WF4 subversions which i guess is M220. It has just leaked in Creo 2.0 M030 somehow.
I do have WF4 M220 at work, but I can't even figure out how to add a model to a drawing there. It's just so different compared to Creo 2.0.
If you can build some dummy assembly with a dummy assembly drawing to test this issue then maybe I can help you out. It really shouldn't be that hard.
Congrats and best wishes Brent! 
I was using an offset feature to resemble a weld between a tube and a bracket.
The features looks well enough in the model but there is a strange issue with and Offset feature... it doesn't merge with intersecting solids!
Here is the feature itself:
Funny thing is, you can trim with extrude across the feaure and remove material.
So I had to cut and refill the feature. This worked okay here but was not nearly as simple in another region.
As persistent as Creo solid models are about merging solids into a single solid part, it is odd that this particular case is ignored.
This is in Creo M040. I will probably send in a case with support on this in the near future if it is still prevalent in M070.
Have you run across this?
I have attached a quick sample file of the issue:
I've attached a zip file containing a drawing with the associated assemblies & parts.
The DESCRIPTION parameter has been added to all parts & sub-assemblies and is shown in the repeat region. In the relation code, I'm trying to look for a specific string & adjust another parameter accordingly. What I'm actually trying to accomplish is a bit more complicated, but this is just an example of the search function not working.
Thanks a ton for helping me with this headache!
Hello Jim and welcome to the forum.
If all your points are showing up as a single point; right click on the point and choose the last option. This should make all the points individual and each fillet can be dimensioned. Careful thought, I just crashed Creo doing this.
It takes some work to disassociate the points from each other, but it works. To be clear, you right click on the single entry in the dialog to expand to individual points. Then you have to turn of the grouping for each point.