ATTENTION

This FlexSim Community Forum is read-only. Please post any new questions, ideas, or discussions to our new community (we call it Answers) at https://answers.flexsim.com/. Our new Question & Answer site brings a modern, mobile-friendly interface and more focus on getting answers quickly. There are a few differences between how our new Q&A community works vs. a classic, threaded-conversation-style forum like the one below, so be sure to read our Answers Best Practices.


flexsim.com

Go Back   FlexSim Community Forum > FlexSim Software > Q&A
Downloads

Q&A Using Flexsim and building models

  #1  
Old 04-30-2009
Brandon Peterson's Avatar
Brandon Peterson Brandon Peterson is offline
The Flexsim Consultant
 
Join Date: Jul 2007
Location: Salt Lake City, Utah
Posts: 382
Downloads: 29
Uploads: 6
Thanks: 192
Thanked 516 Times in 235 Posts
Rep Power: 490
Brandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant futureBrandon Peterson has a brilliant future
Default Abort a use operator for Process

This is a question from Sung Kim:
"Hi,
Could you please advize me how to cancel the "waiting operator"? I have one multiprocessor currently waiting a operator to process one of the sub-processes. However, I would like to bypass all the processes if the flowitem waits for the operator too long. I tried "moveobject" and "destroyobjectevent" for the flowitem. It successfully move the flowitem out of the Multiprocessor (bypass), but the MultiProcessor state is still "waiting the operator" and yellow box is surrounded. Consequently, the next new flowitme for the Multiprocessor cannot get into the MultiProcessor. Any suggestion?

Thanks,
Sung"

This question is basically asking how to abort the use operator for process if the flowitem waits to long. One question I have for you Sung, What are you doing with the flowitem? Are you processing it without the operator or something else?

Brandon
__________________
thats not normal.
The Following User Says Thank You to Brandon Peterson For This Useful Post:
Phil BoBo (04-30-2009)
  #2  
Old 04-30-2009
Phil BoBo's Avatar
Phil BoBo Phil BoBo is offline
Flexsim Development
 
Join Date: Jan 2008
Posts: 756
Downloads: 109
Uploads: 18
Thanks: 385
Thanked 1,483 Times in 525 Posts
Rep Power: 1174
Phil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond reputePhil BoBo has a reputation beyond repute
Default

Sung Kim,

Attached is a model that shows how to do what you are trying to do by searching through the task sequence queues of the dispatcher and operator(s). If it finds the task to come be utilized, then it destroys that task, destroys the events of the multiprocessor, resumes the multiprocessor, and releases the item.

The main code is in the OnMessage trigger of the MessageHandler object. The Multiprocessor sends a delayed message to the MessageHandler from the Pick Operator trigger.

This works well in this little sample, but if your object/model gets more complicated than this little sample model shows, then you could get into big trouble fast by messing with the standard object functionality using the destroyeventsofobject() command.

You may instead want to use a BasicFR to get more control over exactly what happens to the object using the receiveitem() and releaseitem() commands. The logic would be similar, but then you wouldn't have to bypass the regular multiprocessor logic by destroying its events. This is less likely to give you trouble in the long run when you try to implement this sort of logic in a bigger model.
Attached Files
File Type: zip cancel_calloperator.zip (42.5 KB, 246 views)
The Following 2 Users Say Thank You to Phil BoBo For This Useful Post:
Sung Kim (05-01-2009)
  #3  
Old 05-01-2009
Sung Kim Sung Kim is offline
Flexsim User
 
Join Date: Jan 2008
Location: York, PA
Posts: 85
Downloads: 70
Uploads: 0
Thanks: 70
Thanked 9 Times in 6 Posts
Rep Power: 160
Sung Kim is on a distinguished road
Default Thank you

Thank you much, Phil and Brandon.

I understand that description of my issue might be odd to you. I admit that the description doesn't show the whole picture. For the answer Brandon's question, when the flowitem waits for the operator too long, basically, it cancels the all subprocesses in the multiprocssesor and eventually move to other station and do the rest of processes with other temp operator. It is not exactly but similar to balk in a queue situation.

Phil, thank you for the explanation and the model. It is very good to know about the MultiProcessor's nature. I will study your model soon. While I learn your logic, I will let you know if there is an issue.

Thank you very much for your time and help.

Tags
multiprocessor, states


Thread Thread Starter Forum Replies Last Post
How to set the process of two itemtypes by the MultiProcessor Vic Li Q&A 12 07-21-2015 11:34 AM
Picking process Simon Farsah Q&A 9 03-23-2015 06:55 AM
Re-entrant Process ankus d Q&A 2 02-09-2009 07:53 PM
help! order picking process with global tables Charmaine Ng Q&A 3 11-06-2008 11:24 AM
Operator dependent process times Unregistered Pre-sales Questions 7 05-23-2008 03:01 PM


All times are GMT -6.
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.
Copyright 1993-2018 FlexSim Software Products, Inc.