Terminus Operations

[Anonymous]

Pete the Porter

Hi thanks For the track It’s very cool. Great thing you can do with control tracks I love em.

Thanks Dave

[Anonymous]

I’ve got it!! 😆 My terminus layout can be downloaded from ➡ here.

[Anonymous]

Hi Pete,

This is the same idea from Dave but other lanscape. I´ll study it exactly on weekend and and if you permit me,i´ll modify a little bit or build that in digi mode. Good work Pete.

[Anonymous]

Hi Pete,

Thanks, that’s really a good example of a terminus station. And it’s great that you added screenshots and a description. But you would have made my life easier, if you would have added a 480 x 360 Jpg picture with the name terminus3.roa.jpg and and named the ReadMe terminus3.roa.txt.

I have changed it and will release it with the next version of Layout Viewer. But I really don’t see why I should do all the work for other people?

Kind regards,

Willi

[Anonymous]

Sorry Willi,

I do not have Layout Viewer on my computer 😳 so I am unaware of the file types you need for it. As a newcomer I decided to wait until version 2 is available.

Regards to you and to all.

[Anonymous]

Hi Pete,

I can do it for you ,what Willi requeted. Willi will receive it to evening.

Good stuff this terminus.

[Anonymous]

Thanks for the kind offer Peter 😉

[Anonymous]

Hi Pete,

Willi has now all infos for the layoutviewer,and i´d set the downloadlink in his forum directly. As the new moderator i ´m able to do that. I hope that helps you. 😉

[Anonymous]

Chris wrote:

I attempt to make control tags as descriptive as possible: . This helps me sort through the various actions associated with a particular control

engine ID: 1, 2, 3, ALL (I,2, and 3).

control side: B or R

device ID: whatever you’ve named the switch, power unit, coupler, etc.

action: power-F(orward) or R(everse); switch-S(traight) or C(urve); etc.

An example: power unit P1 slowing engine ID1 to a stop from the red side of the control:

1R P1 F5

1R P1 F4 1

1R P1 F3 2

IR P1 F2 3

1R P1 F1 4

1R P1 Off 5

These generally display completely in the control edit menu.

Chris,

This is a really good suggestion. Really. It never dawned on me to change the names of the controls. I assume you go in and change these names anytime during or after creation of the control. For my layouts, I would get duplicate names if Device ID refers to the thing being controlled. Are duplicate names OK? If they are not OK, then I’d need to add one more element to the list to identify a place on the track. All the controls at one place would have the same track-location-ID. No useful controls would have the same name — why would you want to do exactly the same thing more than once at the same spot from the same direction, etc.

Thanks again for the suggested naming convention. I don’t know how many times I have clicked through the list just to see what the existing controls did.

Roger

[Anonymous]

Hi Roger,

You can rename the controls whenever you’d like but I find it best to do it at the time of creation since the naming convention depends on it. It would be a pain to rename a device at some point then lose sync with all the control titles you’ve come up that ‘touch’ it.

I agree with your logic; a title should be unique. The example I provided slows the engine from a speed greater than 5 to 0 in a period of six seconds.

Clicking through all those was exactly what inspired this naming convention. It sure is easier to scroll the list then have to open each and every one of them looking for the one you need to modify.

[Anonymous]

Chris,

I did a test to see if the control names had to be unique. They don’t! I tested with two controls at different places with the same names. RTR did not get confused. I then changed the name of a controlled switch. The control still pointed to the right switch. I also tested making both of the switches in the test layout have the same name. RTR didn’t get confused on that either. Looks like you can cause yourself as much confusion as you want! The names are only a crutch for us modelers.

The same is not true when you delete something that was controlled and then create a new one with the same name. IE, you delete an Insulator (red bar) and a power source disappears. All the controls that referenced the power source still exist but they don’t reference anything. I have not been able to repair these controls. These have to be deleted and recreated. I just did a test by deleting a controlled switch. The control actually disappeared on that test. There are some inconsistencies in how these things are handled. Maybe the difference is when I delete a track element, the controls referencing it go away too. But when RTR automatically deletes the element, it leaves the damaged control in place.

Anyway, descriptive names are wunderbar.

Roger

[Author]

Posts