Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you remove the block signaling system and use in-cab signaling, you still need to know where the back of the train is. Otherwise a train could run into the back of another in the fog or heavy rainstorm. Currently, railroads use FREDs (flashing rear end device) on the last car of the train. Some FREDs are more intelligent than others but would benefit from being able to send out their location via GPS.

https://en.wikipedia.org/wiki/End-of-train_device



Pretty sure all the In-Cab systems still have axle counters and track circuits.


Longest trains are under five miles so you could use that or whatever the limit for that line is as a safe baseline. Unless you're worried about trains separating.


You are worried about trains separating.


Even more if you have distributed power. A train can separate, and both halves can keep moving.


That's not an actual problem. You simply have 2 trains each broadcasts it's location. It's unexpected separations that might be a problem, but those are currently very rare and dealt with seperatly than static signals.

It's like you need to design a nuclear reactor to deal with an aircraft hitting it. You don't need to automate the response becase that's a rare situation.


Plus with an actual separation the brakes will dump anyway and things will stop... well, not fast, but as quickly as they're capable of.


Well, I read about one instance where it happened, and the brakes didn't apply. (Not sure how that could happen other than a mess-up in building the train. You'd just about have to have both angle cocks closed.) Both fragments continued, for miles.

Can't cite a source (I think I read about it on the Altamont Press discussion board). And that's only one instance. And it could have been reported incorrectly. But it appears to be possible for this to happen.


You can use block signalling with in-cab signals.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: