can anyone gives more details on what is a navigator.

can anyone gives more details on what is a navigator. The manual doesn't say much about it.and I want know why op walk along Network,how control it?

what do you know by now?

you can tell me what you know,thank you , I can not describe what i know.

The Navigator objects are black boxes. Users don't really need to know much about how they work. They just work. What users need to know in order to make them work is documented in the manual. Similarly to how a driver doesn't need to know how internal combustion or a transmission works in order to drive a car, a Flexsim user doesn't need to know the internal working of the navigators so it is not documented thoroughly in the manual.

From the user manual's documentation on the Travel Task type:

Here the TaskExecuter travels to the object specified. This is done by make a travel request to the navigator that it is connected to. If it is connected to a network, then it will make a request from the network navigator.
Note on TaskExecuters and navigators: Some objects by default are not connected to a navigator at all. If the TaskExecuter is not connected to a navigator, then it will do nothing for the travel task. The following objects do not connect to any navigators by default: ASRSvehicle, Elevator, Robot.

The use of a navigator is only associated with the travel task. The TaskExecuter notifies the navigator that he needs to get to some destination, and at that point the navigator takes over and "pushes" the TaskExecuter like a pawn on a chessboard, according to its own "black box" rules. The network navigator will push the object along a network path, whereas the default navigator will just send him directly there. It really is a "black box" type situation, and you don't really need to know the nitty gritty details. It just works. Additional learning should be in how to build/configure networks, which is documented in the NetworkNode topic in the user manual.

If you want to get details on a given network, i.e. distances between nodes, etc. you can look at the "NetworkNodes" category in the command reference.

http://www.flexsim.com/community/for...ight=collision i want to know the answer about this thread,but nobody help him. i think this question have something with navigator or node

“Can anyone help me about the problem I marked my previous post?
The AGV's cuts the network and goes directly to the destination after collision ends.
How can I make them to follow network after collision?”

??????????? linweixu is infamous around these parts?
what is this..

I wrote something wrong
http://www.flexsim.com/community/for...ight=collision i want to know the answer about this thread,but nobody help him. i think this question have something with navigator or networknode

I didn't look at the model, but I assume it uses task sequence preemption to implement collision avoidance. When a travel task is preempted, the preemption mechanism will take the object off of his current path on the network, making him "inactive" on the network. From the user manual:

Whenever a TaskExecuter finishes a travel operation, arriving at the node connected to the travel operation's destination object, the TaskExecuter will become "inactive" at that node, and the red line will be drawn to the TaskExecuter while he is doing other operations in that node's area. What this means is, the next time the TaskExecuter gets a travel task, he must return to the NetworkNode he was inactive at in order to get back onto the network.

The preemption mechanism basically does the same thing as described above, but by the fact that it's preemption, it must make the TE "inactive" before the TE can actually get to his destination. So when the TE takes up his next travel task after the preemption, he will go directly to the next node, instead of following the path. To avoid this, you must use the redirectnetworktraveler() command instead of using preemption. For the next version we've added some special logic that, given the right circumstances, will automatically call redirectnetworktraveler for you when a TE is preempted, so that he can continue on his path, but instead travel to a new destination as part of the preemption.

Originally Posted by Anthony Johnson

I didn't look at the model, but I assume it uses task sequence preemption to implement collision avoidance. When a travel task is preempted, the preemption mechanism will take the object off of his current path on the network, making him "inactive" on the network. From the user manual:



The preemption mechanism basically does the same thing as described above, but by the fact that it's preemption, it must make the TE "inactive" before the TE can actually get to his destination. So when the TE takes up his next travel task after the preemption, he will go directly to the next node, instead of following the path. To avoid this, you must use the redirectnetworktraveler() command instead of using preemption. For the next version we've added some special logic that, given the right circumstances, will automatically call redirectnetworktraveler for you when a TE is preempted, so that he can continue on his path, but instead travel to a new destination as part of the preemption.

hi Anthony,I found this problem remains unresolved in flexsim 6.02