Just an Idea

[SurvivorSean]

It's been about half a year since I've been using MSTS. TD3 has occupied most of my time. Finding out the MSTS2 is canned, perhaps will make room for new development in MSTS, or another simulator to eventually take it's place.

The multiplayer concept surprised me. I didn't understand how it was possible at first, but then it made some sense. I haven't participated in this just yet, but am looking forward too. I enjoy dispatching in TD3, and model railroad clubs so this should be some fun. I was hoping to make dispatching a career, but the openings are not here in Canada, and I'd need a green card if I was to venture into the States.

My idea is based on a combination of my programming background, model railroading, and TD3. The latest release of TD3 has a remote option that allows through simple text file commands (created from another program or device) to update data on a dispatch screen, or send commands from TD3 to another remote device. My idea would be to have a small program in a small window display a signal. This program would communicate over the net through the server to TD3. It wouldn't be totally automated. The user would be required to do the following:

Hit a button when he is in view of the control point, or intermediate.
This would have the program on the TD3 end send signal aspect.
Hit a button when he takes the signal (drops it to red).
This would update the TD3 end that the block is now occupied.
Hit a button when his rear clears the control point (block release).
This would update the previous block to unocupied state.

In more dense CTC these buttons would form a stack (queue) as you may see multiple signals, and span multiple blocks etc. There would also be a text file that would have control point names, and other information so that the program would display the signal you are approaching next.

I can program the VB Application that would display the signal and buttons etc. I may need some assistance though co-ordinating this over the network, and perhaps configuring the more advanced features of the remote services for TD3. All the dispatcher would have to do is enter the train ID, length, and starting location and direction (most of this is prototypical). The actual train crew would have to acknowledge he is approaching a signal, taking, and clearing a signal (not so prototypical, but necessary. Consider it like a deadman switch, AWS, etc.).

Just another FYI - Even if you are doing track warrant dispatching, using TD3 can help in dispatching with the remote function. Of course you the dispatcher would update everything as the crews OS their location to you etc.

Let me know what you think. I'd love to try and set this up.

Thanks

Sean

[jdtrainman]

You're re-inventing the wheel. Why not implement something using ATCSMonitor (www.atcsmon.com). It uses TD3 displays already!

JBD

[NSFanFremont4life]

you could use ACTS but thats based on real live trains so it would be pointless in our simulated runs on any route i could be wrong but using TD3 would help the dispatchers out more and could bring more people to dispatch if TD3 or ATCS was used in our runs i know it would help me out but then i would miss the fun of being apart of running a train but i would survie thats just what im thinking laterz andrew

railraoding 90%experance 10%rules
NS dector milpepost 32.3 no defects

[jdtrainman]

What I'm suggesting is to use the online ATCS monitoring system, develop the dispatcher maps for the route being dispatched then he can develop the push-button concept and we simply host an ATCS server on whoever's machine is available. Data could be manipulated accordingly based upon this concept....

DS board could be viewed by anyone but ONLY DS can send control codes.

Train Crews input board would simply be a series of pushbuttons (probably radio choice buttons) that will allow the crew to select ONE and ONLY ONE control point to update. A short text box for Train ID or Engine number and the usual OK/CANCEL buttons. Probably would need/want an "idiot-proof" system that asks the crew to verify the information before it updates the display.

I'm going to invite some of the ATCS big players to look at this (possibly get them on this forum temporarily) and see if there's anything they can do to make it easier to work with and do what we want it to do. The ATCS monitor software already has the online functionality we need so (as I see it) we really only need a pair of utility windows to start. I still see a lot of verbal coms being needed unless the operators/dispatchers use multiple computers like Lee and I do. My main desktop machine has dual monitors so I could put the DS panel on one monitor and TeamSpeak on the other while I also run a train on my laptop.... If I'm correct here, most people who run trains leave TeamSpeak in the background and, therefore, don't ever see text messages sent to them unless they happen to minimize TrainSim temporarily then they may still miss them..... (just a little hint: I've already got a DS layout for ATSF Marceline Sub. - straight out of ATCSMon's free downloads!)

I could even use TD3 just to create my own map and use as a means of keeping track of my simulated line-ups and simply keep the clock paused. I'd never have to actually run a train but could manually knock down signals, throw switches, etc. just to have an easy means of keeping an eye on my traffic patterns....

There are lots of possibilities here. I should have thought about using TD3 and ATCSMon sooner!

JBD

[SurvivorSean]

I use ATCS (not remote, but over the net) too.

The one advantage of dispatching by ATCS over using a TD3 screen is it works well for Track Warrant operations. This would be because in the ATCS monitor you can flick the switches and click on the individual blocks to get it to light red etc. Dispatchers out there right now could dispatch your next MP session just like that, and it should assist from a dispatching point of view. For the mean time I strongly recommend just using the ATCS program to dispatch if you use track warrant operations. If anyone needs help who doesn't have Track Builder 3, and wants a route converted I have the program and can create a layout for you to use with ATCS. For those who are interested in KHP1 (possibly 2) there is also a TD3 layout out there for the route. Others I can look for on Dispatch Central, etc.

If you went 1 step further, Unless you plan on operating the trains with 2 monitors though 1 with MSTS, and the other with ATCS you would never know what your signal is. Due to MSTS limitations it is highly unlikely that this could be linked to the signals they actually see. If you use ATCS monitor also to link it to some pop up box with an aspect displayed we would have to talk to the author for permission as we would be using the ATCS program to decode what is on our ATCS server, to display a proper signal. It certainly worth a try if you have some connections with the ATCS guys. I'm on the ATCS group myself, and I can monitor the situation if you post a message there, or I can on this group's behalf.

The reason I suggest TD3 is because the programming is already in place to allow commands to be sent to and from the dispatch (who is required to have TD3) through the network and to the small routines that would be in place for each train operator to use see the next signal.

Just for the record I have not participated in a multi session yet (My connection is on a borrowed pc). Once I get a router hooked up at the end of the summer, I'd love to participate. My TD3 and programming experience is good, but I'll need some help with passing data through a network. I use the ATCS program to monitor net feeds, but have not actually used it in the field for railfanning as I don't have the scanner.

Thanks for your reply. I think this is an exciting topic. Multi-play in general brings new life to this program.

Sean

[SurvivorSean]

One other advantage of ATCS now that I think of it is people who eavesdrop now have another medium. Just like ATCS by itself can be dull and boring. Likewise the same can be said for listening to a frequency over the net. Same with webcams. Combine any of them, or if your real lucky all of them and your in heaven. Forstoria, and Fullerton are good examples of in the protype anyone with ATCS, and access to FostoriaLive can be in for a real treat.

Having an actual ATCS server out there for MSTS would be a first, but then combining that with the already available audio communication could get a real interest in those that can't commit to a particular time, might be a little bit intiimidated at first. Even I can pop in if I happen to get the PC free and can logon :)

In the longrun though setting up an ATCS may be harder then setting this up for TD3.

Thanks

Sean