Hello Filip,
what you want to achieve can do an taskexecuter, but there is a very big BUT.
You tweak the standard flow of a Flexsim model. The standard consists of sending or pulling flowitems between fixed resources. A Taskexecuter is just an aid to transport flowitems. It should not be a source of the action in the model.
It can do that because the developers have implemented a method where a flowitem enters a fixed resource is processed. But the resources are not checking several conditions like the capacity of the receiving objects. The best approach is to get a model work without the use of Taskexecuters. The next developing step is to implement the Taskexecuters. Then the user has to organize the order the tasksequences get executed. This you can do it in a dispatcher in combination with the break to requirement function in the taskexecuter and the priority of the Tasksequences. This can become tricky, because a taskexecuter receives as much tasksequences as he has capacity to transport flowitems, but you can close the connection into the taskexecuter when the current order list's last item is moved to him. If he unloads the last item to transport he opens the connection to the dispatcher again.
Your global table comes into play, when you organize the model without the Taskexecuters and a second time when you dispatch tasksequences to a particular taskexecuter. Then it is useful, if you know which tasksequence belongs to an order list. For example you can insert a task of the tasktype tag to every tasksequence which and where it is created to keep this information at the tasksequences. This sounds all in all very complicated, but please start with a small model to get used to every new function or method you want to learn.
Come back, if you don't understand something. Then describe what you have done, what you have tested and what your problem is.
Jörg
|
