relation help

[wayne.beck]

How do I turn the correct rounds for the rd4 i want. Right now it is just selecting the last option in red. The rd4 is driven from a family table.


IF RD4 == 41.75
ROUND_5_IN = YES
ROUND_4_IN = YES
IF (RD4 >= 41.71875 & RD4 <= 39.67775)
ROUND_5_IN = NO
ROUND_4_IN = YES
ENDIF
IF RD4 >= 39.61525
ROUND_5_IN = NO
ROUND_4_IN = NO
ENDIF

 

[charleskim]

Try putting 'else' in the relation.


IF RD4 == 41.75
ROUND_5_IN = YES
ROUND_4_IN = YES
else
IF (RD4 >= 41.71875 & RD4 <= 39.67775)
ROUND_5_IN = NO
ROUND_4_IN = YES
else
IF RD4 >= 39.61525
ROUND_5_IN = NO
ROUND_4_IN = NO
ENDIF
ENDIF
ENDIF

 

[wayne.beck]

Thanks for the input. Although this did not work. it is still solving just for the last part of the relation.

 

[charleskim]

Last if statement should be Less than.


IF RD4 <= 39.61525


Charles

 

[wayne.beck]

thanks again for the input. but it is still just using what is in red. maybe i am not clear in my first post. I would like pro/e to know what rounds to turn on depending on rd4. right now it seems to only use the last part of the else statement. What i am doing is trying to to control one dim and turn features on or off and not have to add all of them to a family table.


IF RD4 == 41.75
ROUND_5_IN = YES
ROUND_4_IN = YES
else
IF (RD4 >= 41.71875 & RD4 <= 39.67775)
ROUND_5_IN = NO
ROUND_4_IN = YES
else
IF RD4 <= 39.61525
ROUND_5_IN = NO
ROUND_4_IN = NO
ENDIF
ENDIF
ENDIF


Thanks,

 

[charleskim]

Wayne,


Does this really turns feature off?
ROUND_4_IN = NO
I never done this before. Is 'ROUND_4_IN' a feature name?


I think relation is ok except for 2nd IF statement.
IF (RD4 >= 41.71875 & RD4 <= 39.67775)
This will never be True.


Charles

 

[wayne.beck]

yesthat is a feature name.

 

[Isair]

OK so maybe I didn't understand it correctly but this is what I think:
If "ROUND_4_IN" is a feature name, and if thats written in relations it will newer work because you cannot say that feature is = No or YES.
Second if you do this in generic model then in all other instances this will be turn off or on so there is no point in doing that statement in family table (put feature in family table).
Solution to your problem might be something like this:
First decide that those feature you are trying to turn on or off must be in all instances the same or different. If are the same then you must do this only in generic model and you don't need those features in family table.
Then go to Tools-Program and find where are those features, it will be something like this (it depends on what feature is but main goal is to find where it says Add, and End Add):


ADD FEATURE (initial number 47)
INTERNAL FEATURE ID 9485
PARENTS = 1(#1)



Mirror


NO. ELEMENT NAME INFO&n bsp;&n bsp;&n bsp;&n bsp;&n bsp;
--- ------------- -------------&nbsp ;&nbsp ;&nbsp ;&nbsp ;
1 Feature Name Defined&nbsp ;&nbsp ;&nbsp ;&nbsp ;&nbsp ;
2 Mirror Plane Y-Z:F1(DATUM PLANE)
3 copy no copy Defined&nbsp ;&nbsp ;&nbsp ;&nbsp ;&nbsp ;






MEMBER OF A GROUP, NAME =
LEADING FEATURE OF THE GROUP: ID = 9485
LAST FEATURE OF THE GROUP: ID = 9487
THIS FEATURE WAS CREATED BY MIRRORING
END ADD


Now add your statements before ADD FEATURE, and after END ADD put either ELSE or ENDIF . Close it Save it and then try does it work. You must do that before every feature you wish to turn on or off. Program will regarding statement suppress or not suppress features.

Hope it will help you.

 

[phoxeoy]

Is there a way maybe in a family table to have features completely gone from an instance? Not just surpressed but completely gone from the model. Reasonwhy I ask is we can't have surpressed features in are models and sometimes we will have options for models with extra features added but are not on original model.

 

[wayne.beck]

I beleive I have my relations working correctly now. But now I have the problem my family table instance needs to be regenerated once after I open it for my relations to work. I have a simple model working now, but my complex model will fail when I try to open it. Is there a way to regen the model to get the values need not to make the model fail.


Thanks,