Exception caught in start() of activity

Question

question

Shinya O asked Jun 07 2024 at 9:10 AM Nil Ns commented Jun 21 2024 at 7:16 AM

Exception caught in start() of activity

Hi,

A TS with priority 0 is created at time 0, and then a TS with priority 1 is preempted. When another TS with priority 1 occurs at the moment that TS ends, if you observe the activetasksequence of TaskExecuter, the TS that occurred at time 0 is first executed for 0 seconds, and then the TS with priority 1 starts, and an error occurs there.

time: 7.620335 exception: Exception caught in start() of activity "Create TS" in process flow "ProcessFlow". Continuing throw...
time: 7.620335 exception: Exception caught in Executive::processeventinlist().

Is this a bug? Actually, I'm creating a model with ver.2023.0.11, so it would be nice if there was a workaround.

Thanks in advance.Exception caught in start() of activity.fsm

Software Version:

FlexSim 24.1.0

agv create ts preempt

exception-caught-in-start-of-activity.fsm (49.5 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-06-07T09:58:53Z

Jason Lightfoot answered Jun 07 2024 at 9:58 AM Nil Ns commented Jun 21 2024 at 7:16 AM

The 'workaround' is to turn off the option 'UseNavigatorForOffsetTravel' or to specify a Tigger for the offset travel in the AGV Network properties.

· 3

Nil Ns commented · Jun 20 2024 at 7:29 AM

Hey Jason, by turning off the 'Use Navigator For Offset Travel' option, do you mean to include that option in all AGVs?

I have put it in my model, but I am still receiving the error message. What is the code that needs to be added to the trigger?

time: 6013.061628 exception: Exception caught in start() of activity Control AGVs/AGVs/Create TS4 in process flow "ProcessFlow". Continuing throw...
time: 6013.061628 exception: Exception caught in Executive::processeventinlist().

*Note that I have a very complicated model. I have exactly the same error, but I am not sure if it is caused by the same bug. It is just to be sure.

Thank you in advance!

0 ·

1718868533639.png (3.1 KiB)

Jason Lightfoot ♦♦ Nil Ns commented · Jun 20 2024 at 10:11 AM

What trigger?

If it's the onSet of a parameter to set the number of AGVs from a Group, then after this line:

 applicationcommand("recreateObjectConnections", newObj, firstObj);

add this:

   newObj.setProperty("OffsetTravel",1);

and either set the first object's offset travel manually or add this line:

firstObj.setProperty("OffsetTravel",1);

You can set it to 0,1 or 2 - just not 3 which is the option for using the navigator for offset travel.

0 ·

Nil Ns Jason Lightfoot ♦♦ commented · Jun 21 2024 at 7:16 AM

Hello, sorry, I read ‘trigger’ instead of ‘tigger.’

I had a similar logic in place as you indicated, but I modified the node number.

Even so, I replaced it with this one, and I’m still getting the same error.

From what I’ve observed, this sometimes happens when an operator starts a new task sequence without finishing the previous one.

As I mentioned, I move a lot of token, and it’s possible that this is what’s causing the error, rather than an issue with the offsets.

Thank you very much for your response!

0 ·

question