Page 8 of 8

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Sun May 20, 2018 7:50 pm
by LakeATCS
Came right from the NS filing.

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Sun May 20, 2018 8:48 pm
by justalurker66
LakeATCS wrote:5/7

New automatics at
369
371
373
375
377
mp374-180513.jpg
Intermediates at 374

374 replaces 375 ... I believe 372 replaces 373 but I could not see the number plates and no train passed by calling signals while I was present (May 13th).

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Mon May 21, 2018 12:03 am
by LakeATCS
Yeah I botched up the 5/7 notice

369, 372, 374, 377 replace 369 371 373 375 and 377

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 05, 2018 7:15 am
by tttodisp
Saw a fair amount of activity on 75501600030202 over night (should be CP 397), with a signal data point from 004 (CP 395). The 003 data almost looks like it is in service.
75501600030202.jpg

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 05, 2018 9:16 am
by LakeATCS
Both look like they are getting cut over.

I am no longer getting the notices.

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 05, 2018 9:28 am
by tttodisp
That's too bad.

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 05, 2018 10:56 am
by LakeATCS
They are fairly simple.

395 and 397 have OK blocks between them

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 05, 2018 11:41 am
by tttodisp
Thanks, that makes sense.

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Wed Jun 06, 2018 11:30 pm
by LakeATCS
Both come in fairly well when conditions are good.

They are coming in now.

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Fri Jun 08, 2018 2:47 pm
by rob46580
From how the atcs blocks seem to work now the changes east of goshen will create more room on layout...

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Fri Jun 08, 2018 9:29 pm
by justalurker66
rob46580 wrote:From how the atcs blocks seem to work now the changes east of goshen will create more room on layout...

I'd rather have the granularity. The ones that annoy me are where the advance circuit stays high when the train is in the closest block to the interlocking (fairly common). But having some indication is better than a dark display.

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Mon Jun 11, 2018 9:55 pm
by LakeATCS
The old NYC system with all the discrete blocks cost a FORTUNE when it was put in, and it would have cost double what NS payed to replace it.

The dispatcher doesn't need all that information, because the computer keeps track of the trains with Alpha tags in the office.

Speaking of the old system. Cue the video. (This is Cleveland to Buffalo, but the Toledo to Eklhart section used similar stuff)
https://www.youtube.com/watch?v=ZM9H5SJwXgY

16 minutes into this one has the slightly more modern stuff on the line thru Elkhart.
https://www.youtube.com/watch?v=pD8GtIOxxJU

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 12, 2018 3:15 am
by justalurker66
Thank you for the videos (and everything else you have provided over the years).

It is interesting to see CEAK and DEAK at CP 367. I have not seen them in action but are they discrete blocks? Are CEAK and DEAK only active when a train is in the block between 374 and 372?

The center blocks remind me of the center blocks between CP 479 and CP 466 and between CP 488 and CP 437 where occupancy can be calculated (a train in each center block will trigger the advance block on the CPs in both directions). While not discreet it does look nice on the display to show progress of trains. (Where the calculation fails is if there is a train in each approach block showing occupancy in the advance blocks.)

If CEAK and DEAK at CP 367 are discrete I would assume that they are worth the investment.

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 12, 2018 7:55 am
by LakeATCS
367 should be the standard setup. Two blocks each side on each track. (despite the fact that there are only 2 intermediates between 367 and 360)

Here are some general standards NS follows.

One or more intermediates between MCPs. Two blocks. However in the case of there only being one intermediate we can just ignore the outer block as they are duplicate.
No intermediates between MCPs. OK blocks.
Holdout signals will have an extra set of discrete approach blocks which are REALLY short and close to the Holdout.

Foreign road crossings can be tricky. Even if there are no intermediates between it and the next OS, there will often be an extra distant approach block. However this isn't for the NS dispatcher, this is fed to the foreign road so that the foreign road dispatcher can see two approach blocks on each side. In this case it is a "virtual" block. (NS side of Hohman and State line have this)

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 12, 2018 8:37 am
by tttodisp
The latest ATCS kit has only double blocks now.

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 12, 2018 10:55 am
by justalurker66
Thank you for the updates. I am assuming that a train between 374 and 372 will activate advance blocks in both directions (similar to the setups near LaPorte and South Bend as mentioned above).

Re: NE Indiana NS Chicago Line PTC project

Unread postPosted: Tue Jun 12, 2018 2:37 pm
by LakeATCS
It could be worse. N&W put in a system in 76 and 82 that was the cheapest and most low information ever on the New Castle district.

You had ONE block between all MCPs no matter how long it was. (Also has single direction intermediates in places just to save cost)

Image