I have a situation in SimTraffic where a car is not turning out of a channelized right turn pocket when the signal for the corresponding thru movement is green and there is no traffic blocking the car from turning. The car is just sitting there refusing to move even when it has a clear opportunity and it is creating a huge, unrealistic backup in my simulation. The simulation will run just fine for a while (it varies from run to run but is usually around 45 min. to an hour into the simulation) and then a car will hang up with this issue. I have tried re-recording, recording with multiple runs, reseeding and re-recording with multiple runs, and I am still having the same issue on most of the runs.

Has anyone else experienced this issue or have any suggestions about how to resolve it?
Thanks, Kelli

This message has been edited. Last edited by: kellig,

I have seen it also. you may want to increase the right turn speed from default 9 mph. if the control is yield, put it in signal and vice versa. if it is for future, may use longer min initial.

I've seen this happen to me before. I don't know why it happens, but I suspect it may have something to do with pedestrians in the instances I've seen. example - car approaches signalized intersection, but has to wait for pedestrian to cross street. after the ped has crossed, the car still won't turn right, even on green. wasn't channelized, but similiar circumstances perhaps?

If you are getting SimTraffic error code 212, this has to be taken seriously. The channelized right reduces the amount of space for a lane change. Here is the message from the User Guide:

"Link distance is too short for lane changes with upstream channelized right. If there is an upstream right turn channel with 1 add lane on a 3-lane link. The vehicles from the right may need to make two lane changes on this link. If the distance is less than 80ft plus curb radius plus the distance for lane changes. The distance for lane changes is 60ft for a single lane change or 180ft per lane change when two or more changes are required".

Thanks,

John.

to my understanding, the post is not about the error message. it is in the simulation ceratin car is not moving.
the code should only come when there is an interruption on the direction.

John,

I did get that message, but I did not think it was causing the problem because the car holding up the queue in most of the runs was destined for lane 4 and already in lane 4, and its next turn was either thru or right; therefore, no lane change was required.

The downstream node that causes the link to be too short for the lane change is actually a right turn only driveway that should not affect the thru traffic anyway. Is there a way to reflect this in the settings so that the error message will go away?

The only way to get ride of this error code is to delete the channelized right, shorten it (maybe), move the node further away or delete the downstream node. Even if it is a right out, it still creates an intersection space. Vehicles are not able to lane change in the intersection and only on links. If the angle is acute, you might use the link offset to help. You might even try using the Crosswalk Width to give a smaller intersection footprint.

I'd be happy to look at the file (SYN) if you wanted to send it to me at support.

Thanks,

John.

I am having a similar situation with error 212. I checked this thread and now am attempting to fix the error. The one question I have is.... if I need 160' for a two lane cross (even though my next intersection after the channelized right is two throughs and a right turn lane, so there is no need to go acoss all the way to the left), plus 80' plus the curb radius (50' channelized radius), this equals approximately 310'. I have 465 between intersections. Isnt that enough space?