Exception Caught in ObjectFunction250__(etc.)

Question

question

Theresa B asked Nov 22 2022 at 2:36 AM Felix Möhlmann commented Nov 24 2022 at 7:29 AM

Exception Caught in ObjectFunction250__(etc.)

Hi, again,

I've been getting this error and I'm not sure how to debug it and find the cause of the issue.

I started with this model InputOutputDifference.fsm, versions of which I have posted before, and it spits out this error message:

Thinking the issue might be related to the trigger that sends flowItems downstream of FloorStorage2, I tried replacing the elements downstream with something simpler and deleted the Source2. execeptionCaughtInObjectFunction250.fsm

This model produced the same error (?) but apparently caused by Transporter1 in the Create Task Sequence activity of the Picking Process Flow:

I've looked through older questions about similar errors but none of them have conclusive answers that I understand.

Are these two errors the same, given the matching ObjectFunction250 code? How can I diagnose the issue given the information in the console?

Thanks in advance!

Software Version:

FlexSim 22.2.0

exception error objectfunction diagnostics

1669083883805.png (207.6 KiB)

1669084822020.png (84.9 KiB)

execeptioncaughtinobjectfunction250.fsm (83.7 KiB)

inputoutputdifference.fsm (289.0 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 · 2022-11-22T07:41:15Z

Felix Möhlmann answered Nov 22 2022 at 7:41 AM Felix Möhlmann commented Nov 24 2022 at 7:29 AM

You repeatedly move items from FloorStorage2 back to Processor2 because in the Process Flow you neither change the item reference nor do you decrement the "NumberStacked" label, so the tokens loop forever.

(Item reference never changes)

(Always returns "False")

When an item enters FloorStorage2 an event is created that will fire when the dwell time elapses. At that point the item will likely not be in the storage anymore, which leads to the error message.

The cause for the error in your second model is that no slot could be assigned to the item and thus the task sequence is invalid.

1669102796801.png (13.9 KiB)

1669102844830.png (12.4 KiB)

· 2

Theresa B commented · Nov 24 2022 at 2:18 AM

Thanks, Felix! A fresh set of eyes when I've been looking at a model for too long is a world of help.

I guess the diagnostic method here is just to look at the parts of the model that the named objects are related to.

Was there anything in the error messages that hinted that the error was in the Process Flow? Is there any way of looking up the meaning of ObjectFunction250?

Fixed model for posterity: InputOutputDifference.fsm

0 ·

inputoutputdifference.fsm (86.6 KiB)

Felix Möhlmann Theresa B commented · Nov 24 2022 at 7:29 AM

I don't believe there is a way to look up what "ObjectFunction250" refers to exactly. The hint I used was that it relates to some timed event (..."_OnTimerEvent"). These mostly occur due to items that are involved in pending events having been moved, so I looked if this happens in your model somewhere involving the FloorStorage2 mentioned in the error messages.

0 ·

question