I'm building a large conveyor model and sometimes I use a centerport connection to have a reference to another conveyor (especially with reversing conveyors I use it) So the connections are being made but the quick properties don't show a port section. Is this by design or an omission?
It's always been that way - the need for ports is mostly on transfers, but I agree that a GUI interface is really needed for port type connections so you can easily change the rank when you have multiple connections.
I tend to steer clear of centerport connections and use a label pointer instead, which you can then easily refer to by name. The only disadvantage is that it's not by default a bidirectional relationship, for which you need a coupling (as per the centerports), but that you can also fudge using labels with ownerobject.
@jason.lightfoot Yes there are different ways of doing it but if you can make a port connection with the object I think there should also be a GUI for it. Not only for changing the order but also for knowing what is connected to what, especially with photoeyes, decision point and transfers in the neighbourhood, the amount of connections and the positions make it difficult to see what is connected to what.
13 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
