Jump to content
Simio Forum
Kingsburgh

Flow Library PickUpDropOffFlow SimBit Transfer Problem

Recommended Posts

Hi All


The PickUpDropOffFlow Simbit shows users how to model a entity such as a ship transferring flow from Tank1 to Tank2 and then moving onto a sink.


I would like the flow in Tank2 to flow through a series of connectors to another tank and/or sink. If I connect a flow connector from the Output@Tank2 to a tank or sink, the entity originally in Tank2 does NOT flow out. It seems to get stuck in a queue. I have gone through all the add on process logic and checked the status of Output@Tank2.FlowRegulator.Enabled property.


Please advise on how to get the entity flowing again.


Regards

Martin Kingsburgh

Share this post


Link to post
Share on other sites

It wont...You need to model your tanks as separate objects and use transfers between them. A tip...You also need to set the LowLevel to be some small value and you HAVE to remove the entity in the output flow q, when your tank in the middle hits empty...This is needed if your input rate is larger than your output rate...


I have a model small model if you have an email address....

Share this post


Link to post
Share on other sites

You can get get the flow going again by clearing the destination of the entity.


I would attach a revised version of the sim bit but files cannot be attached in public forums. Regardless, only ONE extra step is needed. Add a Set Node step to the beginning of Empty Ship process. Use this node to clear the destination. The properties of this step are:

  • Advanced Options/Entity Type: SpecificObject
  • Advanced Options/Entity Object: ModelEntity.Container1.Contents.FirstItem.ModelEntity

 

For your information, these options were copied from the transfer step in the same process.


When the entity is in tank 1, it has a destination node of Output@Tank1 -- which it never really gets going through. This destination gets carried along with the entity. When the entity arrives at a sink input node, the destination is different. Therefore, the 'onEnteredToAssociatedObject' process which will send the entity in to the sink is not called. If we clear the destination with the extra step as described above, then the entity will enter the sink.

Share this post


Link to post
Share on other sites

Alan, please hit me up on skype...


I would like to understand this a little better....Pulled my hair out when fluctuating rates as well as reversing them...Clearly they have change the internals of the nodes....

Share this post


Link to post
Share on other sites

Future Flow Library enhancements to add new filler / emptier / container entity objects, should render this kind of modeling approach probably somewhat obsolete. We are hoping to have some better solutions coming down the road later this year.

Share this post


Link to post
Share on other sites

×