by Jtgshu
I have found that I have less "pre-actions" and I can run harder and faster when I know whats going to be happening, meaning when there are waysides and automatics as well as cab signals, or somekind of visual reference. I know where, when and how my cab signals are going to change, because I can see where the automatic is, and I can adjust my running accordingly - I can "pound" the signal, or i can "pussyfoot" it, or somewhere inbetween. But either way, I know what its going to do, so im not surprised. And like i said above, I don't like surprises.
Maybe PTC could be developed with a visual reference of some sorts. Say for example - 1000 feet from a stop signal, a colored sign or pole, and a rule that states you must be no faster than 15mph if coming up to a stop signal. At 500 feet from the signal, another different colored reference, which requires the enginere to be at 10mph or less. So and so on. Also say there is a different colored pole or sign that is say 75 feet from the signal, and trains MUST stop no closer than that point for the stop signal. Passing that point, will automatically trigger a penalty or emergency brake application. If permission past the signal is required, punching in the code the dispatcher gives will make the system happy and hten the train could be moved again. If the train is going more than 15mph and is 1000 feet from the stop signal, the eng has say 5 seconds to get brakes on and suppression, just like what happens now with cab signals. If he doesn't, the train goes into penalty and stops.
Something like this might be easier than a "floating" system that has all these variables and braking curves, and trying to account for all those variables which seem impossible to account for in a computer software. It could be done in 10mph tiers, down to stop signals or speed restrictions. A radio wave could be transmitted out when a signal is at a stop signal or a speed restriction is in placed, and a receiver on board the train also shows which "colored block" (say orange for 500 ft and 10mph) and thereofre speed allowed, just like a cab signal system, and would correspond with the wayside colored poles or signs
Just a few thoughts.....
Don't look at an engineers "pre-actions" as a hinderance or a negative. Use them in a positive manner.
Maybe PTC could be developed with a visual reference of some sorts. Say for example - 1000 feet from a stop signal, a colored sign or pole, and a rule that states you must be no faster than 15mph if coming up to a stop signal. At 500 feet from the signal, another different colored reference, which requires the enginere to be at 10mph or less. So and so on. Also say there is a different colored pole or sign that is say 75 feet from the signal, and trains MUST stop no closer than that point for the stop signal. Passing that point, will automatically trigger a penalty or emergency brake application. If permission past the signal is required, punching in the code the dispatcher gives will make the system happy and hten the train could be moved again. If the train is going more than 15mph and is 1000 feet from the stop signal, the eng has say 5 seconds to get brakes on and suppression, just like what happens now with cab signals. If he doesn't, the train goes into penalty and stops.
Something like this might be easier than a "floating" system that has all these variables and braking curves, and trying to account for all those variables which seem impossible to account for in a computer software. It could be done in 10mph tiers, down to stop signals or speed restrictions. A radio wave could be transmitted out when a signal is at a stop signal or a speed restriction is in placed, and a receiver on board the train also shows which "colored block" (say orange for 500 ft and 10mph) and thereofre speed allowed, just like a cab signal system, and would correspond with the wayside colored poles or signs
Just a few thoughts.....
Don't look at an engineers "pre-actions" as a hinderance or a negative. Use them in a positive manner.
On the RR, "believe nothing you hear and only half of what you see"
John, aka "JTGSHU" passed away on August 26, 2013. We honor his memory and his devotion to railroading at railroad.net.
John, aka "JTGSHU" passed away on August 26, 2013. We honor his memory and his devotion to railroading at railroad.net.