Coupling Two Consists

NJCurmudgeon

New member
I have a fictitious layout I'm working on and have hit an odd snag...here's the scenario: A switcher pushes a string of coal cars through the coal mine and loads them. A doublehead diesel combination comes and couples with the loaded cars. It pulls them down to where there is a timber company. I have a yard where the timber company diesels pull consists of log wagons out to the logging camps, using the forestry asset to load them. They bring them back to the yard and leave them there. The coal train is supposed to stop and then back up so as to add the log wagons to the coal cars and then head out.

Using the commands, I can get it up to the point where the coal train is waiting in a siding. The timber diesel drops off the loaded log consist and, as it leaves, it hits a trigger. The coal train is waiting for that trigger and is supposed to couple with the log wagons. Even though there is a clear path for the coal train to back up and couple, it either backs onto the wrong track or heads off in the wrong direction. The tracks are clear and the switches can be set in its favor. I use the couple command and have double checked I'm telling it to couple with the correct log wagon. I've tried inserting a reverse direction command as well, all with no effect.

My two immediate questions would be:

1) Can I couple two consists like this?
2) I have the two locos on the coal train set back to back - so the lead engine is cab forward and the second is facing the consist, similar to how I've seen a bunch of freights in real life. Would that be messing it up? Should I have both facing forward?

If more information is needed, let me know. Thanks!
 
Don't know if this is what you are looking for but use the change direction command as the first command after the trigger is hit. Also put a track mark where the coal car couple to log car and give a command couple at track mark.
 
First of all, I have not tried Danny5’s suggestion, so it may be a solution to the problem. If not, take a look at this thread http://forums.auran.com/trainz/showthread.php?85080-Waiting-For-Track-Clearance-Issue , especially JohnnyC1’s post regarding using an invisible signal. I’ve had success doing the same thing in situations like the one you describe. I’ve never been able to get an AI driver to change direction and move through a red signal (even if it’s permissive). Instead, as you describe, it will wonder around trying to find a path it likes. The use of an additional signal so that it’s facing a yellow rather than a red is the only solution I’ve found.

Trying to get the A(utomated)I(diot) to do what it should can drive you (or at least me) crazy sometimes, so I hope this helps.

BTW: If you haven’t tried pgipg’s RaiseEvent (kuid:178892:80007) and WaitForEvent (kuid:178892:80006) driver commands you might give them a look. I find them a lot easier to use than triggers in situations like the one you describe.
 
I have used the placement of a signal behind (ie the end of the consist not being coupled to) with success. It can be a normal signal if this fits in with the rest of your layout in that area or you could use an invisible signal.

Cheers
Russell.
 
I'm really at my whits end with this problem...to the point where Trainz is becoming more frustration than fun.:'(

Whatever I combination of commands I try, it always end the same way. The coal train is the one I want to couple with the log wagon consist. The coal train comes into the timber yard and stops where I want it to (trackmark). It waits for the timber loco to trip the correct trigger. I want the coal train to simply back up onto the track where the log consist is (there are 8 tracks) and couple with it. Simple...or so I would think! Instead, it backs up three tracks over, then pulls back to the original track mark and does it again and again. I added a trackmark on the end of the timber consist track and inserted a command for the coal train to navigate to it and then wait before coupling. It backs up to the correct track, but then goes back out to the first trackmark, backs up as far as the second mark and just keeps going back and forth like it's on a loop. I've made sure the names of the cars are all consistent, inserted change direction commands and there are no error messages...it just keeps going back and forth between trackmarks...

I understand about the signal suggestions above, but I've had experimental layouts with no signals that functioned fine regardless. I know about the thread Ricke82 mentioned because I started it. It turned out it wasn't a signal problem but something got messed up with the track. I replaced the mine, relaid the track and it worked without adding signals. So I am not sure the signals (or lack of them) necessarily factors into this situation.

I know I can experiment with it on my own, but one idea that crosses my mind now is if it's just something with the locomotive I selected. I've been using a Norfolk Southern - I don't have the kuid at the moment. But is it at all possible that there is something screwy with that loco that's causing this problem? Or should the commands be independent of the locomotive?

Thanks!
 
Had similar using couple at trackmark, once I changed stock and locos and they would not directly (reverse) couple at tm whereas before they would.
The solution was to move the tm down the siding until I found the spot where they would couple.
No logical explanation, I put it down to changing stock.
 
I have found that the only reliable way to couple consists is to

1. Use "Couple" command. The problem with this is that you have to nominate the explicit car that you want to couple to and then this does not always work as you found out. The other problem is that if the consist changes then you don't always know the which car it is that is at the end of the consist. So....


2. Firstly set a path ( I use "select path" command) to the consist then use "SetDCCThrottleTo" a value that gives a proper coupling speed around 5mph (- for reversing the direction of the loco or + to continue last direction and somewhere around .25 to .3 depending on loco). The last command is "CoupleAhead" which causes the loco to stop when it meets the required consist. Works every time!:)

Geoff
 
Well geez. I have a habit of saying/doing stupid things, but referring someone back to their own thread may be a new personal best.:o Sorry 'bout that. I'm also sorry it was no help in solving your problem.
 
One point ive often found is that the junction near a consist wont change direction. This causes the other train to not be able to pass through it to the consist. Move the consist further back or reduce the lever radius will often work.
 
Try placing a red trackmark near the front of the consist you are coupling to. Make a note of the number. Instruct the other train to "couple at trackmark" and it should work. Just remember not to have a signal between it and the log train and it doesn,t stop too close to a point switch that it needs to change. You may need a "change direction" command before the "couple at trackmark" command.
 
The consist I want it to couple with is in the middle of the length of track - I left room so the entire length of the coal train would fit on the track ahead of it when coupling so not to block other movements. There are switches between where the coal train waits and how it backs onto the correct track. It makes is all the way through all the switches, but stops short of the consist I want it to couple to and then starts to go back and forth. There are no signals involved in that part.

I have a trackmark where the log wagons get dropped off and I tried placing another at the end of the track, telling the coal train to navigate both to and via, but the same problem.

When I get time to play again, I'm going to try swapping the engines and see if that makes any difference. @Pug - where do I find the "select path" command? I don't see it in my list and didn't find it on Content Manager to download. I did find the other two. If the engine swap doesn't work, I will try your suggestion.

Thanks everyone!!
 
Yay! It finally worked! I used Pug's suggestions and it worked beautifully. I can see where those commands are going to come in handy in other yards I have planned for this layout. I sometimes think half the "fun" of Trainz is as much problem-solving puzzles like this as actually getting to drive a train!

My sincere thanks to everyone who made suggestions! :D
 
Back
Top