Operator doesn't follow code

Question

question

Daniel C asked May 15 2018 at 8:23 PM Emily Hardy commented May 24 2018 at 2:55 PM

Operator doesn't follow code

I have this rack with queues. Any item can go in any queue but once it enter only items from the same type can enter (see color). the it leaves and any item can enter. his codes works just fine but when i use the 'Use Transport' option the operator doesn't respect the code and puts the item anywhere. See images below.

Any idea?

Software Version:

FlexSim 18.1.1

queue operator code

with-operator.gif (742.6 KiB)

no-operator.gif (372.2 KiB)

· 3

Jeff Nordgren commented · May 15 2018 at 8:42 PM

@Daniel C,

I have a good idea what might be happening. If you are using manual code to control the Operator, what I'm thinking is that you are not taking into consideration the time it takes the Operator to travel to the loading and unloading stations or checking to make sure the downstream object is even able to accept new flowitems. It's hard to be specific and I don't know if that is the problem without a model to look at. Can you send in your model or a sample model of the problem area so that we can see exactly what the model is doing?

Thanks.

1 ·

Daniel C Jeff Nordgren commented · May 17 2018 at 1:06 PM

I'm not using code to control the Operator, I'm using it to control the queue's flow. The Operator only transports the items.

Here is a smaller model about this.

test-racks.fsm

0 ·

test-racks.fsm (800.8 KiB)

Joshua S commented · May 15 2018 at 8:34 PM

Can you upload your file so we can take a look at your logic?

0 ·

______

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 · 2018-05-17T17:26:39Z

Joshua S answered May 17 2018 at 5:26 PM Emily Hardy commented May 24 2018 at 2:55 PM

The reason this was happening was a timing issue. When the operator was not in use, it could dump every item created at the 2 main queues instantaneously to the racked queues, which would then fire each of those queues "on entry" events, changing their "tipo_actual" labels to the first item entered "Tipo" label.

With an operator in use, the racked queues receive a list of objects that will be sent to them before their "on entry" event is activated. I added a line of code to each of the racked queues "pulled requirement" code which then takes the first item it pulls then changes the "tipo_actual" label to that items "Tipo" label.

this is the line I added:

setlabel(current,"tipo_actual",Tipo);

See if this model is what you are going for 11913-test-racks-fix.fsm

I also connected both main queues to the bottom racked queue, it wouldn't fill without doing so, don't know if that is something you wanted to do as well.

Hope this helps.

11913-test-racks-fix.fsm (801.0 KiB)

· 1

question