How to wait for event until conditional is true?

Question

question

shanice.c asked Sep 08 2021 at 10:04 AM Felix Möhlmann commented Sep 09 2021 at 6:47 AM

How to wait for event until conditional is true?

In my AGV process flow, AGV is waiting in standby point in the beginning, so I use wait for event activity to control. I have a table used to record all tasks for AGVs, I want to check if AGV still has any tasks to do after completing one. I'd like to use a condition like:

int getTaskID = query("SELECT MAX(TaskID)FROM TaskTable WHERE AGVID = tempAGV AND Done = 0");

if(getTaskID>0){

AGV will execute a new task.

}else

stay in standbypoint.

I would like to know which event I should use? The object field is token.agv. I want to fill in the if statement above for the event field. Also, for the if statement, how could I let AGV leave/stay in wait for event activity if that statement is true/false. I think I'd like to use "return", but I still couldn't find a suitable event to use.

0907.fsm

Software Version:

FlexSim 21.2.2

process flow wait for event flexsim 21.2.2

1631094532617.png (25.3 KiB)

1631095078234.png (55.2 KiB)

0907.fsm (586.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 · 2021-09-08T11:49:51Z

Felix Möhlmann answered Sep 08 2021 at 11:49 AM Felix Möhlmann commented Sep 09 2021 at 6:47 AM

As the name of the activity suggest, "Wait for Event" reacts to a distinct event triggering and can decide whether to send the token onwards based on parameters of that event. It can not directly be used to continuously check for a condition.

What you might do instead, is use a "Decide" activity in the place of the "Wait for Event". In there you can use you code to return which connection the token should be send to next. If no task is available, the token can then enter into a "Wait for Event" that reacts to a new entry being added to the table and routes the token back to the "Decide" activity to reevaluate the condition.

As there is (to my knowledge) no event for a row being added to a global table, you will have to listen to something else. If I'm not mistaken, rows currently get added by a custom code activity in another process flow. You could have the "Wait for Event" listen for a token exiting that activity, because if that happens, a new row will have been added to the table. Or you listen to a token entering that activity (as it currently doesn't lead anywhere). In that case put a 0-second delay after the "Wait for Event" to be sure the code of the other activity has finished before the token is send to the "Decide".

Another alternative would be to send a message to the process flow (or some other object) in the same place where the table rows are added and listen for that message.

1631101504537.png (30.1 KiB)

· 2

shanice.c commented · Sep 09 2021 at 5:14 AM

@Felix Möhlmann Thanks for the method of using decide and wait for event.

As there are many kind of Tasktypes, I think I would like to change a little bit, as the wait for event activity cannot deal with listening to several activities at the same time or maybe it can do that way, but become complicated.

My condition to release token form wait for event is any task exists, but doesn't mind which kind of tasks they are. So I would like to add a new label on token.agv or a global variable to record the number of an AGV has. The expression would be SELECT COUNT FROM TaskTable WHERE Done=0 AND AGVID = token.agv. And I would wait for event until this label value > 0. I hope this way could work. I'm having problem with how to declare the variable, could I assign a sql query count to an integer?

0 ·

Felix Möhlmann shanice.c commented · Sep 09 2021 at 6:47 AM

@Fiona C

I understand what you want and yes, you could listen to a tracked variable label, however you can't have a label be both a tracked variable and a flexscript label. So either you would have to continuously update the label value (in a fixed interval or by reacting to events) or evaluate the query contiuously, which is what my solution above does.

Having a larger number of events to listen to shouldn't be an issue. You can simply add all activities you want to react to into a group and have the "Wait for Event" listen to that group as a whole.

Sample Model: WaitForGroup.fsm

Another alternative would be to use a list to determine tasks for the AGVs. Each time you create a row in the task table, you could push the row number and AGV that is assigned to the task to a list and pull those entries with the AGV-tokens. Then you use the pulled row number to reference the details of the task.

0 ·

waitforgroup.fsm (32.2 KiB)

question