Coupling behind a switch / track mark.

[kurby]

I am working on an AI set up. One of the things I need to do is couple an engine to the first car on a siding. Problem is I do not know what the car name is at any given moment. Is there a way I can tell TS12 to couple to the first car behind a switch, or a track mark?

What this will look like when done is a long haul train will come in with empty cars. Drop them off on one siding then pick up the full cars from another siding and take them to the industry. As this is going on, switchers will be taking the empty cars to various places and getting them filled and putting them back on siding 2.

So is there a way an AI train can couple with the first car behind a switch / track marker?

 

[norfolksouthern37]

there is a command for coupling to a car near a trackmark. try searching for 'couple at trackmark'.

 

[trev999]

There is a driver command: "Couple at trackmark <kuid2:57145:81100:1>

Atilabarut [Author: #131986] also has a number of driver commands dealing with coupling. Check the ones at build 2.5 or later. Some of them require setting the speed using other commands.

Hope this helps

Trevor

 

[kurby]

Have the command in driver commands Couple to car in front of trackmark. But it does not seem to do anything

 

[norfolksouthern37]

maybe your trackmark is pointing the wrong direction?

 

[wheelsonfire]

There is a rule used extensively in S&C to couple up to an unidentified consist: CoupleAhead <kuid2:131986:1015:1>. To use it properly you must first use the rule SetDCCThrottle <kuid2:131986:1018:1> to control the speed of the locomotive as it approaches the consist to prevent a derailment.

 

[JohnnyC1]

It helps if you consist is within the track mark radius, it defaults to 20m.

John

 

[Dieselbuilder]

kurby,

If using AI you'll have to remember that it's like a four year old, it requires lots of patience! To overcome the unknown aspect of any given consist, when the train you are attaching to arrives in the siding place a trigger that it can trip just as it gets in clear. The first command of your shunt engine would then be "wait for" trigger to be triggered by "Any Train". You might also place an invisible signal near your track mark as it will give AI something to aim for. The next command would be the "Couple To" command. Then whatever other commands you wish to carry out.
This system works for me, but I will say that every scenario is different so it might need adapting for your particular situation, but don't give up! AI can be worked around.

Dan.

 

[Dap]

I have been using this one quite successfully - Couple At Trackmark,<kuid2:57145:81100:1>. The car to which you intend to couple does not need to be within the radius of the trackmark. I have had it work reliably with the car several hundred feet away from the trackmark.

David

 

[stagecoach]

It helps if you consist is within the track mark radius, it defaults to 20m.

John

It only needs to be on the same track as the TM with a clear route between the TM and the consist.

 

[Bill69]

I am working on an AI set up. One of the things I need to do is couple an engine to the first car on a siding. Problem is I do not know what the car name is at any given moment. Is there a way I can tell TS12 to couple to the first car behind a switch, or a track mark?

What this will look like when done is a long haul train will come in with empty cars. Drop them off on one siding then pick up the full cars from another siding and take them to the industry. As this is going on, switchers will be taking the empty cars to various places and getting them filled and putting them back on siding 2.

So is there a way an AI train can couple with the first car behind a switch / track marker?

Hi kurby,

The way to do this and clear up any myths.

1. Your main line train comes into the siding by a command such as "drive to trackmark siding 1 east" "stop Train" "wait 10 seconds" "uncouple" "drive to trackmark XX" "stop train" this could be a refueling stop and can have a trigger to start the shunter operation.

2. Shunter has a "wait for trigger xx" command, when main line train trips the trigger shunter gets a "drive to trackmark xx" this could be a shunt limit track mark to line the shunter up where it can enter the siding "stop train" "wait for 10 seconds" couple at trackmark siding 1 East" "stop train" "wait 10 seconds" Where the main line train left the consist.

Between the siding switch and the siding trackmark place an invisible signal, this will cause the signal controling the switch to show yellow (caution) instead of showing red (stop) but do not place the invisible signal too close to the switch or you will get a message "next signal is within overlap distance" and the switch signal will show red.

Now for the myths, Trackmarks work the same either way, the trackmark does not have to be close to the consist you are coupling too, it can be just past the siding switch. One other thing, at some point on the siding when coupling the loco will stop then carry on slowly until it couples.

The commands I use and find easiest are the couplez, uncouplez, and uncouplz from commands by atilabarut.

Hope this helps,
Cheers,
Bill69

 

[Dap]

It only needs to be on the same track as the TM with a clear route between the TM and the consist.

If AI is working correctly, it will even find the trackmark behind a closed switch and throw the switch to give a clear path th the trackmark.

 

[stagecoach]

If AI is working correctly, it will even find the trackmark behind a closed switch and throw the switch to give a clear path th the trackmark.

That is correct, but what I was pointing out is the consist and the TM must be in the same clear track for the couple at TM to read the first wagons name. If two consists are in that section the nearest wagon to the TM will be read. This could even be the coupling loco if the junction is set for the loco to enter and it is nearer than the consist.

 

[norfolksouthern37]

Now for the myths, Trackmarks work the same either way...

even though that would be highly command dependent, some commands might only search from the pointy end of the marker (i do this sometimes). that is why i suggested turning it around.