cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

We are aware of an issue causing pages to load incorrectly for some users and expect a fix soon. Sorry for the inconvenience.

Translate the entire conversation x

Cant add string in family table

joe_c
14-Alexandrite

Cant add string in family table

Hello

 

i am struggling to add the new dim Parameter in another instance in the family table. Apparently, it doesnt like parameter names.  i thought i could rename the original dim (A, B,..so on), add an offset, create new dim as a parameter,

 

error "you have entered an invalid text string or a numeric value"

 

apparently, it needs to be a number. what will be another workaround?  Ultimately, i want use these new parameter (A1, B1, C1, D_1, E1, F1. G1, H1) in a drawing table. 

 

It seems that i have to convert the string into a number?

family-table.png

 

relation.png

ACCEPTED SOLUTION

Accepted Solutions
MartinHanak
24-Ruby III
(To:joe_c)

Hi,

you have to define parameters and relations.

MartinHanak_0-1764920653554.png

Then you have to add another "parameter" column into family table and verify instances.

MartinHanak_1-1764920719252.png

 


Martin Hanák

View solution in original post

11 REPLIES 11
SikiF
10-Marble
(To:joe_c)

Hi,

What you are trying to achieve is not possible due to invalid value types.

 

Explanation:

For dimension d34 (A), the value type is real (this applies to the entire column), and for A1 it is a string type (A1 in this case is not treated as a parameter used in the relation, but as an actual value).

These two types are not compatible with each other.

 

As the dialog says, you must use a value of the same type!

MartinHanak
24-Ruby III
(To:joe_c)

Hi,

you have to define parameters and relations.

MartinHanak_0-1764920653554.png

Then you have to add another "parameter" column into family table and verify instances.

MartinHanak_1-1764920719252.png

 


Martin Hanák
joe_c
14-Alexandrite
(To:MartinHanak)

thanks Martin

But i already did that but A1 is assigned to the 1st instance instead of the second.  I want to keep the 1st instance at a zero offset (which is the original A, B,,, dimensions). The second instance at the 0.006 offset with the new A1, B1 the third instance at a 0.013 offset and so on..... Right now, i am typing the calculated new dimension in the table instead of the using the relation based dimension

 

i also want to add the new parameters in a drawing table so the threads can be machined at the different offsets from the shoulder (left or right)

 

family-table-3.png

MartinHanak
24-Ruby III
(To:joe_c)

Hi,

please pack you model into zip file and upload this zip file. I need to work with your model to understand you "situation".

 

Note: If every instance has its own OFFSET value then you have to put it into appropriate cell. See below.

MartinHanak_0-1764939822935.png

 


Martin Hanák
joe_c
14-Alexandrite
(To:MartinHanak)

Martin

 

sorry i am not explaining it clearly.. is pretty simple.  i dont want type the dimensions in the table maybe for the offset only since is not a parametric dim, i would like to use the calculated parameters in the family table and drawing table as well.   

 

 

KenFarley
21-Topaz II
(To:joe_c)

Seems from what I see that you could define all the dimensions from B to H as distances from A. These seem to be unchanged for all versions of the part. Then your family table would only need to specify the offset. For your first "nominal" version, just enter an offset of zero. 

A version table or list of the versions on the drawing would then consist of a list of the offsets for each version.

MartinHanak
24-Ruby III
(To:joe_c)


@joe_c wrote:

Martin

 

sorry i am not explaining it clearly.. is pretty simple.  i dont want type the dimensions in the table maybe for the offset only since is not a parametric dim, i would like to use the calculated parameters in the family table and drawing table as well.   

 

 


Hi,

I opened knurls.prt.3 part.

What I can see ...

1.] dimensions A to H are defined in Revolve 5 feature

2.] dimensions A to H have columns in family table

3.] OFFSET parameter has column in family table -AND- OFFSET  is set in relations, too ... this combination represents a conflict

 

Problem: Unfortunately you did not explain what is requested result. For example: You did not post Creo drawing or a picture of drawing showing it.

 


Martin Hanák
joe_c
14-Alexandrite
(To:MartinHanak)

Martin

here is creo picture of what i am trying to do accomplish.. by moving the threads/knurls to the right using the equation in the relations and add it in the family table instead of typing the numbers 

 

 

MartinHanak
24-Ruby III
(To:joe_c)


@joe_c wrote:

Martin

here is creo picture of what i am trying to do accomplish.. by moving the threads/knurls to the right using the equation in the relations and add it in the family table instead of typing the numbers 

 


Hi,

1.) I finally understood that the main topic of the question is the fact that you don't want to enter values ​​manually in FT

2.) on the other hand, you have to understand that values ​​are always entered into FT manually

3.) FT can also be edited in Excel ... if I were you, I would generate the necessary values ​​using Excel and then copy them into FT

4.) if you don't have Excel, then find another tool to generate the values ... for example Google Sheets


Martin Hanák
SikiF
10-Marble
(To:joe_c)
KenFarley
21-Topaz II
(To:joe_c)

I've done things like what I presume you are attempting. An approach I think would work well is as follows:
(1) Define a set of parameters that will contain the "nominal" values of a particular instance.

     Anom, Bnom, Cnom,...,Hnom, etc.

(2) Define a parameter for your offset

(3) Define a set of relations that use the nominal values and the offset to set the pertinent dimensions

     A = Anom - 2 * offset

     B = Bnom - 2 * offset

     ...

(4) In your family table, for each instance, specify the nominal values and the offset.

Announcements
NEW Creo+ Topics: Real-time Collaboration

Top Tags