Object gets created but does not move to destination (Flow Item)

Question

question

Abhay Bajpai asked Jun 30 2023 at 6:41 PM Jeanette F commented Jul 20 2023 at 8:46 PM

Object gets created but does not move to destination (Flow Item)

The Flow Item (called 'ChassisFlowItem') creates parts as it goes down the conveyor line at every station. All parts are created using Create Object and moved to the flow item using Move Object in a sub flow. Almost all items created move to the flow item except M1_Deck_A and M1_Sidewall_A. They are created but they do not move. Attaching the model to this post.

Upon digging into this issue a bit, i found that the Map called "partMap"-responsible for creating a map for which items need to be created at a station- does not move the first item it creates if there are more than one items in the Map. For example, Station 1 only has one item hence it works perfectly fine. However, station 2 and station 4 have 2 items that need to be created, and hence it does not move the 1st item it creates.

ChampionHomes_V5_Abhay.fsm

Software Version:

FlexSim 23.1.1

move object

1688150239091.png (68.2 KiB)

1688153751732.png (276.8 KiB)

championhomes-v5-abhay.fsm (3.3 MiB)

______

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 · 2023-06-30T21:19:42Z

Jason Lightfoot answered Jun 30 2023 at 9:19 PM Jeanette F commented Jul 20 2023 at 8:46 PM

The reason it's not moving is because the runsubflow is now set to run both tokens at the same time and you've added a delay which means both tokens are looking at the CreateParts[1] which is the same item. Remove the delay or change the runsubflow to run the tokens one at a time.

You should have a different container for each product in which to store the partLocMap. At the moment you only have one container ChassisFlowItem but the script for storing orientations writes the locations onto the container assuming it is the correct container for the modelID. If this were to work - and it could because you have forced unique part names for each model (not necessary on the original concept) - then you would need to position all parts for all models at the same time on the chassis and then run the script. This is, I would suggest, impractical if not infeasible.

If you want the same chassis for each modelID then load items into the Floor objects and put the partLocation maps on the floors and not the chassis.

Where is your production sequence/schedule saying what model is done next?

· 7

Abhay Bajpai commented · Jul 01 2023 at 7:22 PM

Jason, removing the delay worked and now the 2nd item from the array (CreatedPart) moves on the flow item.

The production sequence is in the Global Table ProductionOrder (shown below)

And i slap a label 'modelID' (shownat source every time a chassis is generated and reference that modelID to call for which part needs to be installed on it from the Map 'partMap' at station like you recommended.

Question: Could you direct me on how to control only 1 token to enter the subflow?

0 ·

1688239039873.png (140.4 KiB)

2023-07-01.png (162.4 KiB)

Jason Lightfoot ♦♦ Abhay Bajpai commented · Jul 01 2023 at 9:08 PM

First you need to focus on the premise of the original development which was like this:

Indicating a unique chassis for each modelID. You've now changed that to this:

which seems like you want one chassis for all modelIDs. The code was created to put just one set of part positions on their container. This is why I think you now need to change the container to be the M1_Floor_A and M2_Floor_A etc. objects instead. However these floors need to be container objects which they are not currently - the only container currently is the chassis.

To that end I've made those changes in the attached model. I've also changed the chassis creation to use the default Source schedule which adds the label for you.

Now when you arrange the parts you just select the fullContainer whose flowItem you want to update in the bin as SO()), and then run the script - it will find the correct flowitem by looking at the partID label. I did this for M1A (the first product through the system) but you have some missing BigWalls and other things missing for your definition. I added the floor storage so that you can generate all the parts and then just arrange them while they're in the floor storage.

championhomes-v5-_jl.fsm

0 ·

1688245461582.png (4.4 KiB)

championhomes-v5-jl.fsm (3.0 MiB)

Abhay Bajpai Jason Lightfoot ♦♦ commented · Jul 03 2023 at 5:22 PM

Hi Jason,

What does "token.chassis.first:token.chassis" value return from the whole expression "return (token.chassis.subnodes.length)?token.chassis.first:token.chassis" in Assign Labels? I have been trying to print it but it won't print.

0 ·

1688404845180.png (129.7 KiB)

Show more comments

Abhay Bajpai commented · Jul 19 2023 at 7:59 PM

Hi again Jason, I would like to add more complexity to the model by adding Operators to the jobs. There will be definite number of operators at each station (Station 1 will have 3 operators, Station 2 will have 2 operators....so on) and are solely responsible for parts in that station only. I want them to go to the station every time the Flow Item comes to their station to install the "Part" and then leave the station (maybe a waiting spot next to the station) when they are done with the same.

I want to make sure that if installation of Part is not finished by the operator, the flow item will not move to the next station until it is finished. Not all parts are installed by all Operators at a station. For example, if Station 2 has following parts to be installed: Carpet and Walls, and total 3 operators to do so, I want to tell Flex Sim that 1 operator does Carpet while the other 2 operators will install the Walls. Operators that install Walls cannot install Carpet and vice versa.

How do you recommend I achieve this?

0 ·

Jeanette F ♦♦ Abhay Bajpai commented · Jul 20 2023 at 8:46 PM

Hello @Abhay Bajpai,

Please follow our best practices and start a new post for your question. You can tag Jason in the post and this question if you find it to be relevent.

1 ·

question