Jump to content

gocken

Members
  • Content Count

    205
  • Joined

  • Last visited

  • Days Won

    1

gocken last won the day on September 5

gocken had the most liked content!

Community Reputation

2 Neutral

5 Followers

About gocken

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. redesign the tables, category table should include; part types mix cairo_arm 15 cairo_boom 15 sirius_arm 24 sirius_boom 24 phx2_arm 17 phx2_boom 17 phx3_arm 10 phx3_boom 10 phx4_arm 3 phx4_boom 3 phx5_arm 7 phx5_boom 7 Note: in order to make boom line work. First delete part routing arm table then press undo. Then run, now the boom line will work but you should note that this time arm line will not work. Think about how this could be? see attached file. Arm-boom-draft-R1.spfx
  2. Then you should check whether there is any entity to be unloaded in the ridestation of the vehicle at a certain node(s). For this purpose, at each required node define an entered add-process and search the ridestation of vehichle to quest for whether there exist an entity that its destination node is set to be current node. Define an iteger type state variable i.e., "DwellorNot" and assign the search result to this variable (If the search result is successfull you can assign 1 if not assign 0. Then, set MinimumDwellTime property as shown in the figure attached. Try this solution...
  3. Vehicle.RideStation.Contents.NumberWaiting>1
  4. You should probably need to store enough entity in a prespecified place (like a storage element) before you load it. Then search through the storage, taking into account both the number and volume\weight of entities that are waiting at the storage area. You need to develop your own loading algorithm (you can use processes or even develop your own step for this purpose). It's not an easy task, certainly you will encounter some difficulties but be sure that it is doable (for example determining when to search the storage can even be a serious problem. i.e., you can search when 20 entities accumulated (number-based) or at 20 minute intervals (time-based)). Still this solution seems to be the best that comes to my mind.
  5. gocken

    How to make routing process

    Being very very flexible can sometimes be a problem itself. Simio is a very flexible software enjoy it
  6. gocken

    How to make routing process

    I have changed the logic of the server 2's add-on process you included and add an additional search condition to output@server1. Also, delete all others. It seems it works like you want. see how it is? if there are any other issues do not hesitate to ask further pls. RoutingProblem_Myway.spfx
  7. gocken

    User extensions source code missing?

    You are right adam it is not there. There seems to be a problem with user defined steps. For example, ScheduleEventStep appears two times and there is a readmovement step which I have not seen it before. I think things got mixed up... version Simio 10.177.17178
  8. Try setting capacity type of servers to "workschedule" (8h/day, 5 days a week).
  9. gocken

    Add new station on Vehicle

    MEagar is right. Perhaps the most limiting feature (problem!) of the vehicle object is this. Once the entities are picked up by the vehicle object, vehicle's destination is automatically assigned accoding to the entity's destination. Then nothing to do with this. If we have a chance to determine the destination of the vehicle object independently of the destination of the entity, and if we can do this dynamically, the problems with the vehicle object will be greatly reduced. I mean, for example, if we have a chance to search for enitities in the ridestation according to a certain criteria after placing them (just before the vehicle object's traveling) in the entities ridestation station (and set the vehicle's destination as the found entity's destination) and also if we were able to do this at every destination point of vehicle object then we will have included a very very great feature to vehicle object.
  10. gocken

    Splitting an entity into two different ones

    you can use a create step for making a copy of your original entity. Also, you can use seperator object for the same purpose. You can look around simbits by using create step or seperator keywords.
  11. gocken

    Dynamic Server Capacity Management

    I think 2 more entities (at ridestation of vehicle) for server 1 forces vehicle to wait at server 1. Because they have nowhere to go or wait ? Increasing the capacities of inputbuffers of both servers should solve this problem? if this option is not possible for your problem setting then you have to know how many entities to send from source to servers exactly? or think about many other solutions...
  12. First define a real state variable to your modelentity named "livingtime" after its creation. Then make a copy of your modelentity and send the copy of modelentity to a process (maybe called as death_process). Place a delay step and set delay time as modelentity.livingtime. Of course the original one should go its way. Then place a search step and find the original modelenity in the system when the time is up at delay step (while finding the original entity you should set a match condition such as candidate.modelentity.ID==modelentity.ID etc. I am not sure whether the ID's of both entities are same, you should try. If it does not work you should try to match creation times of them (both should be same) or any other user defined state variables or properties). If the search is succesful make necessary controls (i.e., if it owned any resource release them etc.) by placing necessary steps following found branch. You should remove and transfer the found modelentity (it is the original one) to appropriate place. At the end you should place a destroy step following the original branch or even transfer it to appriate place. It depends on your goals.
  13. gocken

    Pickers not avoiding colision

    For your first problem you can place transfer nodes at intersections of lines. By this way the vehicles have to wait each other. and the collisions will be avoided. For your second problem, (I assume that you are using workstation object) you should define an expression property to each modelentity (i.e., processingtime) then assign each modelentity a processing time from its probability distribution. Then while processing them (at a workstation object) set operation quantity as 1 and Processing Time as modelentity.processingtime.
×