Possible CSX Session tonight (May 13)

[BlakeTyner]

Just a heads up, but I'm trying to get an informal session going tonight. I've emailed Lee to see if his server is available and as soon as I hear back from him I'll post a reply to this thread with all the information.

This will be strictly informal, as I'm still green on DSing so seniority will NOT apply tonight and this trip won't count on the roster. I doubt we'll have a big crowd anyway so it shouldn't be a problem.

There may not even be enough interest, so feel free to reply here and say "I'm in" or whatever.

Once again, I'm relying on someone else's server (I can host, but I think with my 56k connection the more people we have the choppier my voice gets) so if it's not available we'll have to scrap it.

Thanks!

[jdtrainman]

Feel free to use mine.... It's up now


65.164.201.120:8767

JBD

[BlakeTyner]

Alright Jim, sounds good to me.

The following is copied from Lee's post, with the correct date and the IP for tonight:

CSX M&M Sub
Impromptu Multiplayer Session
Thursday, May 13th
65.164.201.120:8767
Login 7:00 p.m. Central
Start running whenever someone shows up



Download the client at www.teamspeak.org. Simply login on the teamspeak client under "quick connect", using the address above. Be sure to set mic on "push to talk". Go into the "settings" menu and select "sound input/output" to find this preference setting.

Your screen name should be the CSXT train identification followed by the lead unit's reporting marks.

Ex: Q144-BNSF4086

1. Please text message me with the following information when you enter the server. . .

CSX train identification-Lead unit (per above)
Length of train in feet (Let’s keep it to a max. of about
4500’-5000’ so that we can fit in sidings without too much
drama!)

2. It would be good, if time allows, for you to check out the starting points on the route, paths, consists, etc. before joining the session. Also get your radio problems sorted out by coming in around 9:15 p.m. EDT to do radio checks, etc. Be sure to turn off voice activation in the “settings” window of teamspeak. See above.

3. Download from the file library and use the “Guide to the CSX M&M Sub Route” by Chris Bogley. (mmguide.zip) This should help you quite a bit with locations, etc. Also download the signal and timetable files available at http://groups.yahoo.com/group/csx_mm/ for good information. You will need to join the group to do this.

4. Listen for a clear channel before beginning a radio communication.

5. Call signals as radio traffic allows. I must keep up with where you are. It’s ok in this situation to call it even a bit after you have passed it, if radio traffic does not allow you to call it immediately. Please use this format: “CSXT Q144-(lead unit sometimes and direction sometimes) got a clear signal south Georgiana (or milepost when not at a named controlled point/signaled siding). CSXT Q144 out.”

Often they will use the short format, with just the train ID, direction, signal name, and location, sometimes leaving off the 'T' in CSXT.

6. Try to determine what the correct signal indication would be when approaching a meet/pass point, and call it accordingly- “diverging approach medium”, “diverging approach”, etc. Of course what you will see will be “clears” since there is no actual traffic! Again see the signal data at http://groups.yahoo.com/group/csx_mm/ in the files section.

7. Let’s use channel two, dispatcher channel, for non-prototypical questions, problems, conversations, and for more lengthy prototypical communications concerning a particular train’s authority. Simply call the dispatcher and say, “Dispatcher, I’d like to go to channel 2, over.” I will move you in my window, or you may move yourself.

8. Let’s avoid random derailments, etc. If you have a problem, we will discuss it on channel 2. Be sure to save in the game with some frequency in order to recover if something happens.

9. Rather than saying, “I’ve got to quit now”, tell me you’re running short of time (Hours of Service) or "about to go on the law". We will find a spot for your train to be tied down. Again, go to channel two, if necessary.

10. Before the session, I may send a few private text messages to individuals who will be asked to announce the development of a problem of one sort or another at a specified location.

11. I will treat the route as CTC territory, which it is, and will simply give you directions as to what I will be doing with your train and with others from my console. Examples:

“I’ll let you go up to Nokomis, but I’m going to put you in the siding at Nokomis for the Q144. I should be moving you on after he gets by.” This means you will proceed by signal indication from where you are to Nokomis and into the siding. You should not move out of the siding and proceed beyond Nokomis until you hear from me again. Treat the signal as an absolute stop indication.

If I say “I’m going to hold you on the main at Nokomis”, then stay on the main, get in the clear between the switches, and do not pass the signal where the siding ends until told to do so.

12. Check back on this thread if something strange happens and we need to re-group.

13. I’d like to have an mow foreman on duty if possible, hint, hint. We’ll issue a track bulletin and set up work limits.

14. Let's work on keeping conversations on a prototyTonight's Lineup (Check www.bullsheet.com for more info.):

PO01- Amtrak Sunset Limited Westbound (Start- "From Pensacola Sub South" To-"Mobile". Make stop at Atmore. Exit Brookley after making stop at Mobile platform.)

PO02- Amtrak Sunset Limited Eastbound (Start- "Brookley" To-"Flomaton" main two. Make stop at Atmore. Exit south leg of wye onto PD Sub.)

Q101- Jacksonville to New Orleans intermodal (Start- "From Pensacola Sub South" To-"Mobile". Exit Brookley.)

Q102- New Orleans to Jacksonville (Start- "Brookley" To- "Flomaton" main two. Exit south leg of wye onto PD Sub.)

Q144- New Orleans to Atlanta intermodal (Start- "North Nokomis" in siding To- "Montgomery". Take main two (right) at Catoma MP 492.7 and exit through Chester Yard onto A&WP Sub.)

Q193- Atlanta to New Orleans intermodal (Start- "Chester Yard" To-"Brookley". Exit onto NO&M Sub.) Make sure you get on the correct track leaving Chester Yard or you will wind up heading north. Please check it out before starting the session.

Q579- Birmingham to New Orleans merchandise (Start- "Elmore", S&NA South Sub. To- "Mobile". Exit onto NO&M Sub.)

Q600- Mobile to Atlanta merchandise (Start- "Sibert Yard" To-"Montgomery". Take main two (right) at Catoma MP 492.7 and exit through Chester Yard onto A&WP Sub.)

Q619- Hamlet, NC to Mobile manifest mixed freight (Start- "Georgiana" To- "Mobile") Yard train at Sibert Yard.

M729- Flomaton to Montgomery mixed freight (Start- "Pensacola Sub. North" To- Montgomery) Be sure to take switch onto north leg of wye in Flomaton. You may want to take a look before we start.

M703- Mobile to Atmore, Wawbeek, Bay Minette, and back to Mobile--Mobile Switcher (Start- “Sibert Yard” To- “Montgomery”)

M700- Montgomery to McGehees and Letohatchee-Montgomery mixed freight local. (Start- “Montgomery Yard” To- “Mobile”)

[train]

count me in

i;ll take PO01

[BNSF4723]

Damnit, I read this one a bit late.. if you can fit me in, I'll take the same train as last night for simplicity. The M729.

[BlakeTyner]

I have a 729, a P001 and a U239 already.

If you'd like to join feel free, I feel like at this point you'll probably have the run of the route.

[atl126]

i'll run the Q579- Birmingham to New Orleans merchandise (Start- "Elmore", S&NA South Sub. To- "Mobile". Exit onto NO&M Sub.) very short train one unit and 14 cars ns8885 also short on timhour left on time

[BNSF4723]

Well looks like I didn't get in tonight, like I had said, I was gonna run the 729 but apparently someone already snatched it up. It would be nice if people would post here with their trains so something like this doesn't happen again... instead of just coming into the server and taking what someone else might of already gotten ready to use. Anyway, I'll get out for the next one I guess, I didn't really have too much warning for this one.