Hello guys,
We have a problem with cutting a whole layer. The only thing the separator does is to cut one by one string and only the first bit of the String from the OnExit expression. Just take a look at the attached model.
It should cut all the combined items a little bit down and then press the whole layer forward and cut the next bit and so on.
Is there any possibility to simulate this ?
Thank you in advance.
The separator is not cutting false. The object splitts only one item, because you can't set the maximum capacity at all. The Separator may be not a suitable object to get what you want. You can unpack or split your package of raw material and then cut each piece in another separator by splitting again.
What you are doing is repeating a cutting process on one item several times. This is a job of a multiprocessor. The number of processes defines how many pieces you get. After each single process you have to create another item in your model and move this to the next object in your material flow model. This copied item get the size of the part you cut away and the raw material's size is reduced in its size, too. Then the next Process starts.
In the final step you probably like to see cylinders instead of boxes. The permament rotating is troublesome. You can rotate the shape of an object by code. Unfortunately the attributes doesn't exists at the objects in their tree. You have to edit the shape factors at the properties Genaral tab once. Here is the picture story to get a correct rotated shape of a cylinder item.
If you start to code without activating the shape attributes, you get this error. Then activate the shape factors.
Now you can run the model without any system errors.
The shape get a new orientation. The shape is located next to the object frame. Adjust the shape position.
The shape fits into the object frame. This can you all do in the Shape Factors Editor, too, but sometimes you need to change the visual look of an item at an object. Then you can change the rotation, location and size by code.
Hello Jörg,
Thank you very much for your help thats what we where searching for.
Would it be possible to give us the simulation from the gif? Because the second simulation (saw-mill-packaged) is just the same like the upper one.
Thank you in advance.
@Marie Lisa, the second one is the variant with a packed item. If you add a Separator and use the funktion unpack, you get all the small pieces. I'll add the enhanced model at work.
@Jörg Vogel Do you know how i can seperate the "Ausschuss" from the good pieces at the end of the Multiprocessor?
Greets :)
@Elisabeth Sestili, in the multiprocessor you can only decide if a packed item (10 pieces together) is good or faulty. The instrument to distinguish where the good items or the bad items go, is the port number of the releaseitem(..) function in the OnProcessfinish trigger code. It is the last parameter in the function. Momentarily all items, which are separated from the original item, go to port 1. But the output port of the original item, that leaves the Multiprocessor last, is defined in the SendTo-function of Flow tab of the properties of the Multiprocessor.
Instead of releaseitem-function you can use "moveobject(..)", but then you overrule the optional methods to initiate the transport by a taskexecuter.
If I understand correctly, you have steel coming in to the separator, that needs to be cut into small layers, and you want to see an animation of the steel being pushed forward a little, then cut, then pushed forward a little more, and then cut again, until the steel is all used up.
If this is the case, then the Separator might only be part of the solution. The Separator does not split items incrementally. Instead, it asks how long it takes to split all the items. In your case, the Separator is making all the cuts simultaneously, rather than cut by cut.
Maybe you could use the Separator, with a queue and a processor to get what you want. You could use the separator to split the steel into all the pieces you need in zero model time. Then you could send all those pieces to a queue, and feed them one at a time to a processor.
I have attached a simple model of this second approach. I will say, though, that @Jörg Vogel's approach is a lot cleaner.
Neither of these approaches have the exact animation effect you are looking for, but both are (or can be) mathematically correct, as far as the simulation time goes. This kind of animation is surprisingly complicated, and so is difficult to create without a lot of code.incrementalcutter.fsm
7 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
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.
