Problem Coupling to Car on Signaled Siding?

boleyd

Well-known member
Simple main line with a siding connected to main at both ends. A single car is setting on the siding. There is a USA 02 (2 head) signal before the switch leading to the siding. That seems normal. But, when I run the scenario, with only a single command to couple to the car on the siding the engine goes to the signal (now double red) an sets there. If I change the command to couple at track mark the engine runs the red and goes to the siding but at only 5mph. Note, there is a trackmark several feet before the car to be coupled to.

I faintly remember that the program sees the siding as occupied (true) and sets both signal aspects red thus blocking access to the siding. I thought the couple at trackmark solved this. The coupling does eventually take place but the engine has to go to the car at a maximum of 5mph.
 
The best way of dealing with that kind of issue is to use permissive signals in the affected area (within the siding is best) which will allow the train to pass and couple up.

Shane
 
A permissive does make running the red legitimate but unfortunately the speed to the coupling point is still 5mph. Oh well, it at least works.
Thanks
 
Use a "set signal state" command to force the particular signal to green, allowing your AI to couple to said string of cars at normal speed and keeping your restrictive signal in a situation that requires it.
 
Only one problem there nicky9499. AI drivers do not understand any signals that are not set to automatic control, and will stop at the signal assuming it is red.

Shane
 
Hi Shane, I have done this myself with a fully automated session for my route and the method works well. The specific rule used was: Set Selected Signal State v4,<kuid2:368725:60002:4> by elstoko. The issued commands as follows:

[Set Signal State > Signal XYZ > To Clear]----[Drive to trackmark > AI couple]----[Couple > to car XYZ]----[continues schedule]

Even without the drive to trackmark, in both cases the locomotive will travel at yard speed limit until approximately 30~40' from the string of cars and stop before proceeding slowly for coupling.
 
I'm guessing it's specific to that command if that's the case. I've manually set signals to green myself on an AI session using a different command and had trains stop at the signal. However, it may be related to extended signal states which I know AI trains cannot understand.

Shane
 
Hi

There are two driver commands which will set signals to allow the AI to pass and couple to a consist. The one mentioned above and also "Set Signal Ahead v2" kuid2:368725:60003:2, both by elstoko. The "Set Selected Signal State v4" command requires that the signal to be set is named.

They allow extended states to be set and have the advantage for UK users that if they are used with the old Auran signals they will light the calling on lights as well. The AI has no problems with seeing the extended states as I have made considerable use of these commands at King's Cross on the ECML route in TS12 to allow locos to back down onto their trains.

Regards

Brian
 
I am afraid there are other things the program does not understand. I set a 2 head 06 signal at the entrance to the siding off the main and placed a car on the siding. No problem running on the main. If routed to the siding the engine slows to 5mph until it couples to the car on the siding. If there is no signal at the entrance to the siding then the engine maintains speed and runs on to the siding ok. Coupling is then by way of the Trainz coupling ritual. Then train proceeds as programmed. I forced the signal to green (suggested rule) and ran the scenario and it allowed the engine to enter the siding and couple but at the slow pace of 5mph. That rule seems odd since I don't see how you reset the signal within the operational steps. I tried 06 signals from the USA series and Safetran - no differences.

An engine going to a siding to pickup a car seems to me a normal event yet it only functions in an abnormal manner.
 
Hi again

I should have mentioned that you need to use the driver command "Set Selected Signal State" again after the loco has coupled up to set the signal back to automatic. Sorry about that.

Regards

Brian
 
Back
Top