collision between transporter and rack

Hello friends,

In my project Collision is taking place between the TRANSPORTER and the RACK, while placing back the finished components in the rack.

How can I avoid this? Herewith I have attached the file.

thanks,
naveen kumar.p

Hi Naveen,

be so kind and upload your file. Thanks.

My first approach would be the use of Network Nodes. More advanced is the coding of a tasksequence, which consist of the explicit coordinates the taskexecuter has to go. If you don't want to write the whole way, send the Taskexecuter to a safe location where the taskexecuter can't collide with the rack anymore. Write the Code in OnUnload-Trigger with the highest Priority of all Tasksequences und preempt the current one.

Jörg

sorry vogel,

I've by mistake that model didn't get attached previously my friend.


Kindly, see the video once. The transporter is literally going into the racks and give me suggestions.

Hello Naveen,

you can move the network node, which is connected to a rack. Least collision occurs if it is placed in some distance from the middle in front of the rack.

Jörg

hi jorg,

If you have seen the model, the transporter is literally going into the rack. I have even tried by placing network node a bit away from the rack.

thanks,
naveen

hi jorg,

I've even tried by placing the network node in some distance from the middle in front of the rack and still the problem persists. Kindly, suggest me an alternative.

Thanks,
p.naveen kumar

hi jorg,

Herewith I've uploaded the model after implementing your suggestion. Have a look at it.

regards,
naveen

Look at the the section in the user manual on task sequences and then try building your own in the TransportDispatcher trigger of the queue using a combination of the other task types.

Hi naveenkumar,

am not sure if I understood the question wrong. But you are looking for a visual solution where your transporter doesn´t drive into the rack, but just to the right position near the rack!?
This way it would be very difficult to realize by using tasksequences because you will have to know the place of bay and cell at the moment of creating the tasksequence.
And it even is not possible by using Collisions because they are not working the way most you and I believed. Or better said, it´s not quiet easy to use them as I hoped they work.

The only way I see for this is to use as many racks as bays you need. Give everyone an own Networknode and turning off the option "Travel offset for load/ unload tasks". Now you only need some logic for giving items the right bay.

Originally Posted by Sebastian Hemmann

This way it would be very difficult to realize by using tasksequences because you will have to know the place of bay and cell at the moment of creating the tasksequence.
...
The only way I see for this is to use as many racks as bays you need. Give everyone an own Networknode and turning off the option "Travel offset for load/ unload tasks". Now you only need some logic for giving items the right bay.

When you execute TASKTYPE_PLACEOFFSET on a rack for the first time, it will fire its place-in-bay and place-in-level code if it hasn't already. You can use the placeoffset task to control the order of the offset actions. By default during the unload task, the transporter is doing its x, y, and z offset vectors at the same time. By adding placeoffset tasks, you can get the transporter to do its x before doing the y so that it travels in an L-shape instead of a direct line to where it is going.

Attached is a sample model that shows the placeoffset task used in a custom task sequence.

Depending on how naveenkumar actually wants the Transporter to behave, there are many different solutions other than using a rack and a network node for each bay.

naveenkumar, perhaps you should explain exactly what you want the transporter to do instead of simply saying "the transporter has a collision with the rack. how do I avoid this?" Everyone here gave you advice on how to "avoid it," but you never explained exactly what you want the transporter to do while "avoiding it."

(Although probably not necessary for this model, you can query in a subtask the item's destination bay/level before the task executer has even traveled toward the rack because the place-in-bay and place-in-level code can be executed using a placeoffset task. You can use 0,0,0 for x,y,z so that the item knows what bay/level it is going to but the transporter doesn't actually do the offset movement yet.)

Originally Posted by naveenkumar

Hello friends,

In my project Collision is taking place between the TRANSPORTER and the RACK, while placing back the finished components in the rack.

How can I avoid this? Herewith I have attached the file.

thanks,
naveen kumar.p

hi PHIL,

Firstly, thanks a billion for your post.

I've made the above quote not to prove you wrong; but just to show that I've made my point clear.

Any how no issues. Thanks once again.

From now I'll try to communicate in a better way.

regards,
p.naveen kumar

What would be the right way to use this function without creating whole Tasks as special Tasksequences?
I´ve got many Racks as aim and don´t want to write all different Tasks but use standard functions of Flexsim. But when Transporter arrives at rack it shouldn´t collide with it.
Or is it only possible by using my own Tasksequences?