Driver command help

pensfan17

Go Pens!
Hello,

I'm trying to create a session using the UMR2010 route. While setting up Drivers, I do not have the uncouplez command available. Another session using this route has the uncouplez command. How do I get the uncouplez command listed in the driver command list for the session I'm creating?

Al
 
OK, to do this:
1.Click on the Edit Session button (it's one of the buttons at the top of the screen in Surveyor)
2.Click Driver Command, then click Edit.
3.Scroll down the list until you find the command you are after.
4.Click in the box to the left of the command so a tick appears, then click the tick icon twice (once in each box).

If the command does not appear immediately, exit Surveyor (don't forget to save) then re-enter surveyor.

Shane
 
i think that is on the DLS kuid:66277:80005 uncouplezfrom#.
There is a decouple number# kuid2:147570:80008:1 this will let you uncouple from car 1 to car 40 where as the other one alonds you to uncouple from car 1 to car 20.
 
OK, to do this:
1.Click on the Edit Session button (it's one of the buttons at the top of the screen in Surveyor)
2.Click Driver Command, then click Edit.
3.Scroll down the list until you find the command you are after.
4.Click in the box to the left of the command so a tick appears, then click the tick icon twice (once in each box).

If the command does not appear immediately, exit Surveyor (don't forget to save) then re-enter surveyor.

Shane

Shane,

When I do step 2 above, I get this: Error: PropertyBrowserRefresh() not handled. A script error while attempting to edit the properties of this asset.

Any ideas?

Al
 
Found out I had a faulty driver command script. After deleating faulty script, all works as should.
Problem solved.

Al
 
Hi There.
I have found in 2010EE that neither of the uncouple commands will work even when they are selected in driver commands. The couple command works perfectly but despite trying until late in the evening the other night be uncouple just doesn't seem to want to know.

What I want to do is have two DMUs with two cars each couple at a junction run to a major station unload their passengers and return to the junction then uncouple and proceed their different ways again. As stated the first part works perfectly but on returned to the junction they refuse to uncouple and the four cars all go off down one branch line as if no command had ever been given.

So if anybody's got any ideas on this one as well as the original posting I am sure we would both be very grateful.

All the best
bill
 
Last edited:
Bill first of all you can't have two drivers on the same train.to do what you want you will have to have a driver in another engine anywhere and with a wait tell X time then a command to move to the engine that had uncoupled from the first engine.
Your first engine command should be drive to station,load,drive to TM, stop, uncouple from 3,drive to whatever,
depens on how long the first train take to do it's moves is how long your second driver should have to wait. your second driver command should be like this wait 5 minutes,move to train (what ever)drive to station B.
You need to use the stop command to set the breaks on all cars and engines so they don't roll a way after they uncouple.
Hope this make sence.
 
Hi Danny and Everybody.
Thanks for the suggestions Danny but I already tried what you have said there. When the first consists arrives at the junction station I have that driver move to a third consists in a siding which he then moves to the station loads and goes off down one of the branch lines.

The second consists arrives and couples up with the first consist for the journey to the mainline station and that is when the problem starts. When you try to move the driver to the driving position in the first consists you get the message "that consists already has a driver".

However, I have found that the the four car consist will still run even though the driver is now in the middle of the train, so everything works perfectly until you arrive back at the junction station and the train stops and the uncouple command then is activated. The command just disappears from the drivers schedule and the rest of the schedule is then continued except with four cars instead of the planned two.

As stated with the uncouple command not working you cannot put a second driver into one of the original two-car consist to change anything as this is being controlled by a driver already.

Hope that all makes sense and again thanks for the help if you or anybody has any further suggestions they would be much appreciated. I've tried all workarounds I know to solve the problem but I have now run out of ideals.

With Thanks.
Bill:(
 
Bill, I just tryed it and all work fine. I used a 10 car train with a engine coupled to it without a driver had engine 1 couple to train with the unmaned engine,then stop, uncouple from #3 (car 3 in train)then drive to station a.
Gave driver 2 command to wait 2 min. then a command to move to the engine that was left by the first engine,then command to drive to station b.
Are you using the stop command and the uncouplefrom# command. remember that 0 mean the engine. Use the 0 will uncouple all the cars from the engine. use the 1 will uncouple the first car from the second & so on.
The 'move to' command will give you a list of no driver engines choose the one you want him to drive.
It just worked for me in TRS2010 build 42203
 
I'm also using UMR2010 route and experienced the same problem as you had pensfan17. Had it settled by following shaneturner12. Well, didn't follow actually, I've discovered it my self.
________________
Each individual has compelling reasons to love model railroading. But beneath these varied reasons are common threads that make it an awesome hobby everyone.

The Australian Model Train Guide
 
Driver commands.. No help?

Is there any help for Driver commands? I'm trying to figure out how all of them work, but honestly I don't know...

Nothing really in the TS2010 manual...

Any tutorials or anything regarding the commands...?

Ty
 
There is a basic description of what most of the driver commands do if you click on Edit session, then click on Driver Commands, then Edit. The page that appears should give you a brief description of each of the driver commands - although certain 3rd-party ones do not have descriptions.

Normally though the manual should have info for most of them (if you have a Manual button on the launcher, click that, the resulting folder/document may cover them in more detail)

Shane
 
Back
Top