Train Sets 2
Posted
Full Member
Regards
Pete.
ECOS2 with RR&Co Traincontroller and a load of other electronics so i can sit back and watch the trains go by.
Pete.
ECOS2 with RR&Co Traincontroller and a load of other electronics so i can sit back and watch the trains go by.
Posted
Inactive Member
Max
Port Elderley
Port Elderley
Posted
Inactive Member
Just so everyone is clear,
I'm going to start with the loco in Block 2 and drive it to Block 4, where two boxcars are waiting; and couple it on. (So far I haven't been able to do this much).
Then I'm going to open the couplers between the boxcars and pull the one closest to the loco out into Block 12, uncouple and run around it.
Then I'm going to push it into Block 10, uncouple and drive the loco to it's next task.
If/When I've achieved this, I should have the tools to expand the plan, creating havoc on a grander scale.
Max
Port Elderley
Port Elderley
Posted
Full Member
Last edit: by wogga
Regards
Pete.
ECOS2 with RR&Co Traincontroller and a load of other electronics so i can sit back and watch the trains go by.
Pete.
ECOS2 with RR&Co Traincontroller and a load of other electronics so i can sit back and watch the trains go by.
Posted
Full Member
Sorry, I had gone to bed!! but the link Pete has posted is the one I meant. Good luck with the new schedule.Hi Geoff. When I go to that date I can only see two threads, neither of them is the one you mentioned. Are you able to put up a link, please?
Posted
Inactive Member
Max
Port Elderley
Port Elderley
Posted
Inactive Member
:hmm
Maybe I should make the two boxcars into a Train Set and assign it to Block 4? Let's see . . .
Max
Port Elderley
Port Elderley
Posted
Inactive Member
At least the wheels are getting a good polish. Lewis is on tonight.
Max
Port Elderley
Port Elderley
Posted
Guest user
Herr Freiwald:
If the Virtual Contact (or any other additionally contact) is turned on and if this Virtual Contact is used as a stop marker for this schedule, then the software will not only recognize, when the entering train has to stop; it will also join both parts to a new train set and will indicate this on the computer screen accordingly.
It is important, that a contact (whether real or virtual) in this block is triggered by the entering train and that a stop marker is triggered there, too.
From John Dew:
Finally I did it…………..many thanks for your patience. It was the first time I had used virtual contacts and I was attempting to perform the stop and end schedule as an operation within the virtual contact rather than have a stop marker in the JB that was triggered by the virtual contact.
—————————————————
The first highlight makes it clear that the VC must be linked to a stop marker.
the second highlight makes it clear that the virtual contact is treated in the same way as a real contact. That means that the virtual contact is part of the block, in other words a second contact section within the block. Within the manual and elsewhere H. Freiwald often refers to the pink rectangles as contact indicators. We seem to reserve that term for the red dots that we often place outside the block, and I think this is leading to some confusion of terms.
The last shows that John did that and it worked.
For what it's worth, I set up this arrangement last year on my layout, with a real contact indicator and a virtual CI both in the same block and had the train stopping as required at the stop marker within the virtual section when the block was already occupied.
If you look at the discussion thread, page 54 post 1077 you will see my description. Post 1078 is John's response.
Posted
Guest user
Posted
Inactive Member
When John gets back from sailing, I'll send him my Track Plan so he can check every last detail. It's usually me doing something wrong. :shock:
Max
Port Elderley
Port Elderley
Posted
Guest user
Posted
Inactive Member
Here's the new Track Plan:-
Max
Port Elderley
Port Elderley
Posted
Inactive Member
Extra files appear in the folder, branded .bak .yrs and .yrw. Does anyone know the function of these files?
Max
Port Elderley
Port Elderley
Posted
Full Member
.bak is a backup of the layout file
.yrs is the status file - storing the status of all turnouts, loco positions, signal states, etc when the application was last closed
.yrw is the window file - keeping a memory of how you had the screen laid out when you last closed the application
Incidentally, I believe that the reason opening zipped files we share appear to have info missing, is because we are only zipping up the .yrr file. If we included the .yrs and .yrw files as well, I think we would see things exactly as they were with the originator.
Last edit: by Geoff R
Posted
Full Member
Max - As I'm looking to do something similar would you please get it all sorted by the weekend
Posted
Inactive Member
Right-o Dave. You didn't mean this weekend, did you? :shock:
Max
Port Elderley
Port Elderley
Posted
Inactive Member
When I zipped the Track Plan, I got a dialogue box telling me that the others were being included. Are you suggesting that we individually zip the others and attach them?Incidentally, I believe that the reason opening zipped files we share appear to have info missing, is because we are only zipping up the .yrr file. If we included the .yrs and .yrw files as well, I think we would see things exactly as they were with the originator.
Max
Port Elderley
Port Elderley
Posted
Guest user
Posted
Inactive Member
Max
Port Elderley
Port Elderley
1 guest and 0 members have just viewed this.