Separated Flowitems not destroyed on reset

Question

question

Maston asked Nov 08 2024 at 1:56 AM Maston commented Nov 20 2024 at 11:30 PM

Separated Flowitems not destroyed on reset

I created a pre-packed pallet in the flowitem bin. When the pallet runs through a separator, the boxes that were unpacked from the pallet do not destroy on model reset. I have to set switch_destroyonreset to 1 on the items on exit from the separator.

Am I doing something wrong when I am setting up the nested flowitems? Or is there a way to set the destroyonreset flag on the items in the flowitem when I am setting up the custom flowitem?

Attaching an example model in 24.2.2

separator problem24.2.fsm

Software Version:

FlexSim 24.2.2

flowitem flowitem bin flowitems inside flowitems

separator-problem242.fsm (45.1 KiB)

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2024-11-20T18:01:57Z

Jordan Johnson answered Nov 20 2024 at 6:01 PM Maston commented Nov 20 2024 at 11:18 PM

I'm not sure the flowitem bin was designed with making pre-packed objects that can be unpacked later.

Instead of building a pre-packed flowitem in the flowitem bin, I would create a packed item using Process Flow. See this model: separator-problem242-pfsource.fsm

I made an Object process flow. I attached that flow to a Queue. I changed the shape of the Queue to match the Source.

The main idea of the flow is to mimic the logic of a 3D source:

Wait for the next arrival time
Make an item
Wait for the item to be released

By default, a Queue releases items instantly. So the flow closes the queue's output ports until an item arrives. Then it opens them long enough to release the item. Note that it opens in them in the On Listener Initialized trigger in the event triggered source.

The main advantage of this approach is that it avoids your original issue. In addition, it is highly flexible. You could easily change the number or type of cases in a layer. The downside is that it is a bit more work.

separator-problem242-pfsource.fsm (51.6 KiB)

· 3

Joerg Vogel commented · Nov 20 2024 at 6:10 PM

@Maston , you may not need to create every packed pallet anew. You can create on model start a packed pallet in your model, then you duplcate it every time you need a new one.

1 ·

Maston Joerg Vogel commented · Nov 20 2024 at 11:18 PM

This works really well.

0 ·

Maston commented · Nov 20 2024 at 11:15 PM

Thank you! I usually use a variation of this and is probably why I've never run into the behavior I was seeing. In this specific case there were about 40 fixed layer configurations, and they wanted case orientations on each layer in the model to reflect this. I figured it was easiest to arrange the cases on the "Layer" by rotating and dragging in 3D space, creating 40 different "Layer" Flowitems. The thought of using PF arrange the cases on all those different layers didn't seem like a good time to me. Apologies for not mentioning that.

0 ·

Answer 2 · 2024-11-20T19:00:52Z

Joerg Vogel answered Nov 20 2024 at 7:00 PM Maston commented Nov 20 2024 at 11:30 PM

I saved a packed pallet from an combiner output as a user library object:

packedPallet.fsl

You can use it in a create object activity directly by its main path to get a packed pallet item into your model.

MAIN:/project/userlibrary/UserLibrary 1/Product_my

Copy the above path into the Object field of create object activity. Or you copy the path by exploring the user library object in the tree view

BUT you must open the user library in attached model previously from main menu file menu.

userLib_item_model_example.fsm

Activating the user library by selecting the user library entry, did not make the packed pallet available in a new opened model.

packedpallet.fsl (1.8 KiB)

userlib-item-model-example.fsm (42.8 KiB)

· 1

Maston commented · Nov 20 2024 at 11:30 PM

@Joerg Vogel Thanks a bunch for this suggestion! If I ever have this kind of use case again, I am going to go this route. For future me, and anyone else wanting to try this method, I think the workflow might be something like this:

In my use case I had approx. 40 different fixed layer configurations and it was easiest to arrange the cases on the "Layer" by rotating and dragging in 3D space, creating 40 different layer Flowitems.

1. Using PF create a "Layer" Object in a standalone Queue

2. Using PF create a number of "Cases" on the "Layer" that is in the Queue

3. Stop the Model

4. Name the "Layer" object accordingly

5. Arrange the "Cases" in 3D space accordingly

6. Right click the "Layer" object and save to a user library

--Do I need to create another "Layer" configuration with the same number of cases?

IF YES:

7. Rename the "Layer" object accordingly

8. Arrange the "Cases" in 3D space accordingly

9. Right click the "Layer" object and save to a/the user library

IF NO:

7. From the Main Tree set each "Layer" objects visibility off (optional)

8. From the Drag-Drop Library "Save Library"

9. Reset and Save the model

Note:

Every time I would have to reload the user library, I would lose reference to the user library objects used by the Create Object activity. To avoid losing the reference to the user library objects I used maintree().find("project/userlibrary/.......") in the object field in the Create Object Activity. You still have to open the user library.

I use loaduserlibrary("somefilepathhere"); in an "on model open" trigger to automagically load a specific user library.

0 ·

question