Choose direction to calculate values

[gert-leonvanlier]

I have an issue and I hope I can make it clear enough for everyone to understand and possibly give me a solution.

In our company we are working with Factory Design Utilities (FDU) for Inventor. We create assets of all our equipment, mostly conveyors. In the way these conveyors are designed we created a realistic way of connecting these assets in a layout. All dimensions, heights etc. are calculated using iLogic. This works great, however, depending on the setup the calculation order of these dimensions matters a lot.

Let me give an example. We have a conveyor placed with a HeightIn. Depending on length and angle a HeightOut is calculated. From the HeightOut a so called ConnectorHeightOut is calculated. This is the real connection point as it is when placing the conveyor in the field. This is important to us so that our layout is exactly as it will be installed. From the ConnectorHeightOut we pass this value to the next conveyor that is connected using the connector dots from FDU by using the connector class. This value is placed in ConnectorHeightIn of the second conveyor. From ConnectorHeightIn HeightIn is calculated and everything starts again. See also my poorly drawn sketch with even more terrible handwriting.

The user will only see HeightIn and HeightOut. ConnectorHeightIn and ConnectorHeightOut are not accesible for the user. When connecting two conveyors, ConnectorHeightIn is leading. When a user places the conveyor he/she sets HeightIn (and not ConnectorHeightIn). The trouble is that iLogic/the code does not know which parameter is leading and therefore blocks one or the other, depending on the order the iLogic rules are placed.

My question therefore is: is there a way in iLogic/VBA to set the calculation order given by some sort of trigger? Meaning, wehn a user places the conveyor he/she enters a value for HeightIn and then HeightOut, ConnectorHeightOut and also ConnectorHeightIn are calculated. When the user connects a conveyor to another conveyor the connector dot sets ConnectorHeightIn and HeightIn, HeightOut, ConnectorHeightOut are calculated. Essentially, how can an asset/conveyor know if HeightIn is leading or ConnectorHeightIn is leading?

It has become a long story, everyones reply or idea would be much appreciated.

[J-Camper]

I think you could initiate the iLogic rule with a search Function to find existing conveyors with open/unused connectors for the Out connector.  Depending on the Returned Result:

If there are none, then you would request the User to supply starting HeightIn.  After the Calculation, you can ask the user if they would like to add to the current conveyor system, and then pass in the "Out" Connector's point. 

If there are "Open" connectors available, then ask the user if they want to start a new conveyor or connect to existing conveyor. 

• If they want to add to, then you can retrieve the "Out" Connector Point to pass into the next conveyor.
• Else you request the User to specify the new HeightIN for the New conveyor system

Was any of this thought process helpful?

[gert-leonvanlier]

Thank you for your answer.

I just read your solution and it may be the solution for me, but I have to think everyone over and how to implement this. I will get back and give an update later.