Connector Point - Parameter

mk92
Collaborator
Collaborator

Connector Point - Parameter

mk92
Collaborator
Collaborator

Hello,

 

i have connector points with custom connector classes. When i connect the assets the class commited the parameters.

 

Now my problem: I connect two assets but later on i have to change only one of them. The position of the assets remains! Only something like the width changes for one of them.

 

How is this possible to do with keeping the connection?

 

Regards

0 Likes
Reply
730 Views
12 Replies
Replies (12)

mk92
Collaborator
Collaborator

Or is there a way to suppress the parameter passing?

0 Likes

XuesongBai
Alumni
Alumni
Hi there,

We can pass the parameters through designating the specific connector in the connector class. Given your case,maybe you need to pick up a connector and say only this connector is connected,width parameter can be passed.
I am curious about the real case.If possible,please let me see the snapshot of the layout.

Thanks,
-Xuesong
Please mark as a solution if somehow I got it right.
0 Likes

olegd.prod
Autodesk
Autodesk
Unfortunately there is no way to suppress/disconnect the connector.
An (ugly) workaround is to republish one of the assets without the connector, and then "Update Assets" in your layout. That will result in the asset instance being updated not to have the connector, and you'll be able to manipulate the instances independently

Oleg
0 Likes

mk92
Collaborator
Collaborator

Thanks for your reply.

Okay, a feature/button like "Update only this asset" would be nice 😉

 

I have another question. I have to assets a conveyor and a support. Ther support has one connector point. The conveyor has 2 for connecting supports. On both of them i would like to give the support the height and the width. But the conveyor has to more connecting points where i dont want to pass parameters to the next conveyor.

 

How do i write this in my connector class? The support connector point is called Support. In my conveyor i have Support_1 and Support_2 because i cant give them the same name.

0 Likes

tpking
Alumni
Alumni
The connector class is a way to match the Inventor parameter names in the assets on both sides of the connection. I have 2 ideas that you might want to try: 1) In the connector class, only put in an entry for the connector that you want to pass along parameter updates (e.g. Support_1). 2) If you want entries for both connectors in the connector class, provide a bogus parameter name for the connector you don't want to pass along the parameter value, like this BogusParameterName When I say a bogus parameter name, it just means that the parameter name is not in the list of parameters in the Inventor parameter dialog. Hope this helps, Tim


Tim King
Software Engineer
Digital Factory
Autodesk, Inc.

0 Likes

olegd.prod
Autodesk
Autodesk
Hopefully this response keeps the formatting.

The connector class is a way to match the Inventor parameter names in the assets on both sides of the connection.

I have 2 ideas that you might want to try:


1) In the connector class, only put in an entry for the connector that you want to pass along parameter updates (e.g. Support_1).

2) If you want entries for both connectors in the connector class, provide a bogus parameter name for the connector you don't want to pass along the parameter value, like this:

BogusParameterName

When I say a bogus parameter name, it just means that the parameter name is not in the list of parameters in the Inventor parameter dialog.

Hope this helps,

Tim
0 Likes

tpking
Alumni
Alumni
Since the formatting won't keep the example connector class entry, I added it as a file.


Tim King
Software Engineer
Digital Factory
Autodesk, Inc.

0 Likes

olegd.prod
Autodesk
Autodesk
technical difficulties - trying to add the file
0 Likes

olegd.prod
Autodesk
Autodesk
we seem to be having difficulties with the forum software - can't attach a file or post the XML :-( the file is here: https://autodesk.box.com/s/tzy4izjz7ivgsxdrybl045kf2kp5szoe
0 Likes

mk92
Collaborator
Collaborator

I have still some problems with the connector classes.

 

I need a connector class which works for this scenario:

My Part_A has the connector point "Support" and my Part_B has a few connector points for Part_A "Support_1", "Support_2" [...]

 

Both have the Parameter "Hight" and i want to connect Part_A to B and share the parameter "Hight"! This should happen with each connector point "Support_1" "Support_2" and so on.

 

How should the connector class look for Part_A and B ? Do they have the same? Or does only Part_A need the class?

 

Regards.

 

0 Likes

XuesongBai
Alumni
Alumni

<?xml version="1.0" encoding="utf-8"?>
<connector _schemaversion_="1.0000">
  <Height family_type="Part_A" value_source="parameter">Height</Height>
  <Height family_type="Part_B" connector_name="Support1" value_source="parameter">Height</Height>
  <Height family_type="Part_B" connector_name="Support2" value_source="parameter">Height</Height>
</connector>

 

Please try to use this connector class. Select family type as Part_A for the Part A and the Part_B for Part B when you assign the connector class properties.

 

Thanks,

-Xuesong

Please mark as a solution if somehow I got it right.

petestrycharske
Advisor
Advisor

mk92,

 

I have been reading up on your situation and have another suggestion.  To manage the connector class information, you should definitely utilize what Xuesong is talking about, building a different family_type for each part.  When you are going to publish the asset, make sure that you select the proper family_type from the custom connector class file.  To help manage how connectors are utilized and whether or not to pass values between try the following.

 

If you are familiar with iLogic, you could create different conditions that can be used to expose and suppress different sets of connectors.  In this simple example, I have created a name plate that has two identically placed connectors.  One of the connectors "Pass_Text" will pass the "Customer" parameter.  The other connector "No_Pass_Text" will NOT pass the parameter and will only join the two.  The iLogic rule simply takes the vale from the "Customer_YN" parameter and uses that to determine which connector is active.  If "Customer_YN" is 0 (false), then the "Customer" value is not passed, and if 1 then it is passed.  Give it a try and see if it helps, you can also see my screen shots below to help walk you through the process.  I have also attached the part model, so that you can see the iLogic rule utilized as well.

 

The custom connector class file looks like this, so you can copy and try it out.

 

<?xml version="1.0" encoding="utf-8"?>
<connector _schemaversion_="1.0000">
    <Customer family_type="normal" connector_name="Pass_Text" value_source="Parameter">Customer</Customer>
 
</connector>

 

Parameter that controls the connector.png

Set the "Customer_YN" to 1

 

Result of Pass_Text Connector.png

Use the Connector tool to join them together and notice the Text changes

 

Pass_Text Connector On.png

Set the "Customer_YN" to 0

 

Result of No_Pass_Text Connector.png

Use the Connect tool and notice the Text does NOT change!

 

Hope this helps and have a most blessed day!

 

Peace,

Pete

Just a guy on a couch...

Please give a kudos if helpful and mark as a solution if somehow I got it right.
0 Likes