Jump to content

Source Arrival Mode


g1h2j3

Recommended Posts

I have a problem with the source arrival mode.For the source "Arrival Mode" i want to use "On Event". So for "Triggering Event" i have 3 options. Object@Entered, Object@Exited and Object@CapacityChanged. So in my model source A is delivering something to sink B. And every time the entity from source A entered sink B a new entity should be created. So i used "Input@SinkB.Exited" and "Input@SinkB.Entered", i tried both. Because i don't really know if there is a huge difference. I guess the exited will create an entity as soon as the one entity left the system through the sink and the entered as soon as the entity enters the sink. But please correct me if i am wrong. So anyhow my problem is now, that the Source is creating more entities as it should. It creates entities even if now entity entered the connected sink. Maybe you guys can help me why that doesn't work as it should be.

Link to comment
Share on other sites

Ok so i figured out that every time a vehicle drive through the input of any sink, that counts as triggering event, even when no entity was unloaded. How can i change the triggering event so that a new entity is only created when an entity leaves the system through a specific sink? I attached a simple example where you can see that Source 2 is always creating an entity when the vehicle is passing by the node of sink 2. But it should only create an entity when the vehicle unloads an entity at sink 2 . Can you help me with that?

ExampleArrivalMode.spfx

Link to comment
Share on other sites

You are correct that the automatic "Entered" event on a node fires whenever any entity enters that node. Unfortunately a Vehicle is a type of entity. So a vehicle delivering an entity causes the event to fire twice, once when the vehicle arrives and once when it delivers the entity and IT arrives.

The solution involves:

1) Create a custom event on the Definitions>Events tab.

2) Trigger that event. Perhaps the easiest way is to add a process the the Sink Entered (Sink>AddOnProcessTriggers>Entered). This process can be a single Fire step that triggers that new Event.

3) Change the source to use that new event.

Here is an example:EntityArrivalEventToSink.spfx

Link to comment
Share on other sites

  • 2 weeks later...

After playing around the model g1h2j3 uploaded, I figured out that the problem is not the vehichle being an entity. The problem is the path directions.

a) The problem is not related to vehicle because "Can transfer in & out of objects" property of the vehicle is false (or off). This means it is not allowed to transfer into sink object via its external node.

b) the problem: The vehicle takes two the entities from two sources to deliver to the related sink objects. Due to path design, it has to pass over input@sink2 for two times (one while delivering entity (the green one) for sink2 and again one for coming from sink1 (after delivering the yellow one)) which causes two entity creation of source2 for one transfer.

Solution: I redesigned the paths and it worked appropriately. see attached file...

ExampleArrivalMode.spfx

Link to comment
Share on other sites

×
×
  • Create New...