ATTENTIONThis 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 |
#1
|
|||
|
|||
2 Network Nodes to a fixed resource?
Dear all,
I have connected 2 network nodes to a fixed resource, e.g. rack I would like to use one of the network nodes for unloading whereas the other network node for loading. The purpose is to make sure the transporter uses different network nodes for moving to the rack and moving from the rack. Is it possible to be done in flexsim? Thanks |
#2
|
|||
|
|||
By default the TE will travel to the nearest node that is attached to the rack and then back to that node. You may get what you want using a 'D' connection between the nodes (check the manual), which allows a different 'exit' node.
In a task sequence travel task you can of course specify a network node as the destination. Also look at adding pick and place offset tasks to get a better path to the rack. |
#3
|
||||
|
||||
Which command is useful in order to specify a network node as the destination in a tasksequence?
Quote:
I want to use network node name. Which command can I use? And in straight network node line, after using offset travel, it will not come back to the node linked blue but should go straight to the next node. How can I control it? I need someone help. |
#4
|
||||
|
||||
Hello Syseo,
I build a model on Jasons instructions. But the next network has not to be the nearest node the TaskExexekuter is traveling to. It seems, it works Jörg Last edited by Jörg Vogel; 12-03-2014 at 02:42 AM. |
The Following User Says Thank You to Jörg Vogel For This Useful Post: | ||
Sebastian Hemmann (10-10-2013) |
#5
|
||||
|
||||
Hello Syseo,
if your network consist of bidirectional travel paths you can change the connected offset-travel-netnode with reassignnetnode(..). Then you should change the tasksequence of your taskexecuter(TE) to define which networknode he has to travel to. You can insert a traveltask to the last network before loading in the OnReceiveTaskSequence-trigger and set the rank of the last inserted task as the first one. Then the standard tasksequence contains 6 task. The TE travels over the network to the defined networknode, then he travels to the object he loads the flowitem. That should be the object the networknode is connected to. He is at the right object. Nothing occurs. The task frload let the TE go into the offset-travel. In the Onload-trigger of the TE you change the assigned networknode. The TE is now connected to another networknode. After loading he travels to that networknode and continues the not begun tasks of the tasksequence. Jörg |
The Following User Says Thank You to Jörg Vogel For This Useful Post: | ||
syseo (07-01-2012) |
Thread | Thread Starter | Forum | Replies | Last Post |
automatically connecting network nodes | Albert Munoz | Q&A | 1 | 05-16-2012 12:19 AM |
Trouble with network nodes | Bill Lank | Q&A | 2 | 05-11-2012 09:49 AM |
Basic Fixed resource does not pull from source ot another FR | Shahin Gelareh | Q&A | 1 | 02-02-2012 01:42 AM |
Network Nodes | Rachid Kolfin | Q&A | 14 | 02-03-2011 08:34 PM |
Operator Utilized During Fixed Resource Breakdown | Ramez Tadros | Q&A | 19 | 08-16-2010 07:03 PM |