How can I solve the fact that the buses and trucks are passing over the bicycles and motorcycles even when i'm using a non passing connection and an spacing of 2 meters? This is related to my question asked here.
It looks like the spacing value on network nodes isn't working correctly when the items are largely different sizes and speeds.
If you want better control over objects with diverse sizes and speeds, you should use the Conveyor or AGV modules instead of network nodes.
@phil.bobo
How can I use a TaskExecuter flowitem with an AGV network?
Attached is an example model that shows how you can connect TaskExecuterFlowitems to an AGV Network.
The "TaskExecuter as Flowitem" code has been slightly changed with these additional lines to connect to an AGV Network:
treenode controlPoint = cpconnection(current, "Location", 1);
if (objectexists(controlPoint)) {
function_s(controlPoint, "addConnection", -1, item);
}
This shows how it can be done, but modeling vehicle traffic would probably be easiest using Conveyors rather than network nodes or the AGV navigator.
@phil.bobo
I have a doubt. You told me it is easier to use conveyors, but how can you manage different velocities for the different flowitems on the conveyor if the velocity is selected for the conveyor in the conveyor system?
Yeah, I guess you are right. If you want to have different speeds for different types on the same stretch, then using conveyors is probably not the best way.
I could not reproduce your problem. Attach is my test model.
Edit: The gap is only available direct on the network. If the taskexecuter goes into offset travel there isn't any edge that control the speed or a passing anymore.
@Jörg Vogel here I attach the link where you can download the model with the 3d images in the same folder in order for you to see the problem. The problem is between the big flowitems as the truck and the bus with the smaller ones as the bicycle and motorcycle.
The taskexecuters overlap at the first node when they get from offset travel to travel on the network. This is caused through the handling of the objects in their object center. I haven't tested, but it may work to change the centroid attribute to an object corner.
The standard script template to use a flowitem as a taskexecuter associates the flowitem in the model node. If you activate in the flowitem the option do not travel offset for load und unload task and you connect the flowitem right after moving the item in the model to a network node the behaviour might change in the way you like, too. The command might be contextdragconnection.
I haven't found the command to switch or associate a taskexecuter in a 'd' type network to use instead of the contextdragconnection.
6 People are following this question.
