Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.electronics.design > #488750 > unrolled thread
| Started by | bitrex <bitrex@de.lete.earthlink.net> |
|---|---|
| First post | 2017-12-19 07:00 -0500 |
| Last post | 2017-12-23 15:09 -0500 |
| Articles | 20 on this page of 175 — 17 participants |
Back to article view | Back to sci.electronics.design
OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-19 07:00 -0500
Re: OT: Muppets amdx <nojunk@knology.net> - 2017-12-19 08:37 -0600
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-19 09:49 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-19 10:00 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-19 09:56 -0500
Re: OT: Muppets John Larkin <jjlarkin@highlandtechnology.com> - 2017-12-19 08:53 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-19 12:20 -0500
Re: OT: Muppets whit3rd <whit3rd@gmail.com> - 2017-12-19 14:27 -0800
Re: OT: Muppets John Larkin <jjlarkin@highland_snip_technology.com> - 2017-12-19 15:24 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-19 18:39 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-19 20:53 -0500
Re: OT: Muppets John Larkin <jjlarkin@highland_snip_technology.com> - 2017-12-20 10:08 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 13:19 -0500
Re: OT: Muppets Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-12-20 10:32 -0800
Re: OT: Muppets John Larkin <jjlarkin@highland_snip_technology.com> - 2017-12-20 12:11 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-20 21:52 -0500
Re: OT: Muppets John Larkin <jjlarkin@highland_snip_technology.com> - 2017-12-21 10:56 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-21 19:24 -0500
Re: Muppets "Tim Williams" <tiwill@seventransistorlabs.com> - 2017-12-19 16:48 -0600
Re: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-19 18:08 -0500
Re: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-19 18:26 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-19 15:01 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-19 18:46 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-19 15:56 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-19 19:25 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-19 16:44 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-19 20:01 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-20 07:59 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 13:07 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-21 10:31 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-21 14:33 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-21 12:00 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-21 16:06 -0500
Re: OT: Muppets John Robertson <spam@flippers.com> - 2017-12-21 12:14 -0800
Re: OT: Muppets whit3rd <whit3rd@gmail.com> - 2017-12-21 17:58 -0800
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-22 12:58 -0800
Re: OT: Muppets whit3rd <whit3rd@gmail.com> - 2017-12-22 15:21 -0800
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-22 16:12 -0800
Re: OT: Muppets Steve Wilson <no@spam.com> - 2017-12-20 01:32 +0000
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-19 20:40 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-20 08:02 -0800
Re: OT: Muppets Steve Wilson <no@spam.com> - 2017-12-20 16:47 +0000
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 13:16 -0500
Re: OT: Muppets whit3rd <whit3rd@gmail.com> - 2017-12-20 10:50 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 14:17 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-20 22:00 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 08:08 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-20 08:09 -0800
Re: OT: Muppets John Larkin <jjlarkin@highlandtechnology.com> - 2017-12-20 09:17 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 13:26 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-21 10:37 -0800
Re: OT: Muppets John Larkin <jjlarkin@highland_snip_technology.com> - 2017-12-21 10:58 -0800
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-21 11:17 -0800
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 14:14 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 14:18 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 14:48 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 16:04 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 16:55 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 16:59 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 18:30 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 19:40 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-20 22:03 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-21 10:41 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-20 22:03 -0500
Re: OT: Muppets Michael A Terrell <mike.terrell@earthlink.net> - 2017-12-20 22:38 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-21 10:52 -0800
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-21 14:53 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-21 12:32 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-21 19:30 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-21 16:37 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-22 08:57 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-22 10:23 -0800
Re: OT: Muppets Michael A Terrell <mike.terrell@earthlink.net> - 2017-12-22 17:23 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-22 14:53 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-22 18:57 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-22 20:10 -0500
Re: OT: Muppets Michael A Terrell <mike.terrell@earthlink.net> - 2017-12-22 20:57 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-22 19:07 -0800
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-22 19:04 -0800
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-23 07:39 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-23 15:03 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-23 12:09 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-23 15:17 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-23 15:27 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-23 20:49 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-24 07:50 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-24 16:56 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-24 14:37 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-24 17:51 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-24 15:15 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-24 18:41 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-24 23:33 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-25 05:48 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-25 09:57 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-25 17:29 -0800
Re: OT: Muppets Joseph Gwinn <joegwinn@comcast.net> - 2017-12-25 20:38 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-25 21:23 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-25 18:47 -0800
Re: OT: Muppets whit3rd <whit3rd@gmail.com> - 2017-12-25 19:09 -0800
Re: OT: Muppets Michael A Terrell <mike.terrell@earthlink.net> - 2017-12-26 00:33 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-26 15:13 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-25 22:10 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-25 07:18 -0800
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-25 18:25 -0800
Re: OT: Muppets Jasen Betts <jasen@xnet.co.nz> - 2017-12-29 02:01 +0000
Re: OT: Muppets krw@notreal.com - 2017-12-28 21:42 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-28 19:47 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-29 01:04 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-28 23:56 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-25 10:55 -0500
Re: OT: Muppets Jasen Betts <jasen@xnet.co.nz> - 2017-12-28 21:41 +0000
Re: OT: Muppets krw@notreal.com - 2017-12-24 18:39 -0500
Re: OT: Muppets Joerg <news@analogconsultants.com> - 2017-12-24 07:46 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-24 12:23 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-25 21:57 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-23 20:47 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 13:31 -0500
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-20 18:36 +0000
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 14:10 -0500
Re: OT: Muppets John Larkin <jjlarkin@highland_snip_technology.com> - 2017-12-20 12:13 -0800
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 16:41 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 16:42 -0500
Re: OT: Muppets John Larkin <jjlarkin@highland_snip_technology.com> - 2017-12-20 14:16 -0800
Re: OT: Muppets Steve Wilson <no@spam.com> - 2017-12-20 22:56 +0000
Re: OT: Muppets whit3rd <whit3rd@gmail.com> - 2017-12-20 15:12 -0800
Re: OT: Muppets John Larkin <jjlarkin@highland_snip_technology.com> - 2017-12-20 15:26 -0800
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-20 23:37 +0000
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 18:42 -0500
Re: OT: Muppets whit3rd <whit3rd@gmail.com> - 2017-12-20 16:26 -0800
Re: OT: Muppets John Larkin <jjlarkin@highlandtechnology.com> - 2017-12-21 08:45 -0800
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-21 09:29 +0000
Re: OT: Muppets John Robertson <spam@flippers.com> - 2017-12-20 15:30 -0800
Re: OT: Muppets krw@notreal.com - 2017-12-20 22:08 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 18:36 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-20 22:09 -0500
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 15:28 -0500
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-20 14:02 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-20 16:33 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-20 21:09 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-20 22:55 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-21 09:38 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-21 18:06 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-21 21:59 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-22 02:56 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-22 11:45 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-22 18:02 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-22 22:39 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-22 23:01 -0500
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-23 09:05 +0000
Re: OT: Muppets krw@notreal.com - 2017-12-23 10:04 -0500
Re: OT: Muppets Michael A Terrell <mike.terrell@earthlink.net> - 2017-12-23 14:00 -0500
Re: OT: Muppets krw@notreal.com - 2017-12-23 20:51 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-23 06:15 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-23 14:38 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-23 17:43 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-23 21:25 -0500
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-24 09:58 +0000
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-24 08:29 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-24 06:06 -0800
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-24 17:53 +0000
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-24 03:41 -0800
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-24 09:12 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-24 15:32 -0800
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-23 08:52 +0000
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-23 14:40 -0500
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-23 19:49 +0000
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-23 14:55 -0500
Re: OT: Muppets Tom Gardner <spamjunk@blueyonder.co.uk> - 2017-12-23 20:03 +0000
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-23 17:53 -0800
Re: OT: Muppets Jasen Betts <jasen@xnet.co.nz> - 2017-12-22 20:49 +0000
Re: OT: Muppets rickman <gnuarm@gmail.com> - 2017-12-22 16:26 -0500
Re: OT: Muppets whit3rd <whit3rd@gmail.com> - 2017-12-22 15:36 -0800
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-23 08:19 -0500
Re: OT: Muppets bill.sloman@ieee.org - 2017-12-23 06:30 -0800
Re: OT: Muppets bitrex <bitrex@de.lete.earthlink.net> - 2017-12-23 15:09 -0500
Page 1 of 9 [1] 2 3 4 5 6 7 8 9 Next page →
| From | bitrex <bitrex@de.lete.earthlink.net> |
|---|---|
| Date | 2017-12-19 07:00 -0500 |
| Subject | OT: Muppets |
| Message-ID | <Eb7_B.2465$oE2.529@fx33.iad> |
<https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> $800 million spent on the project you'd think they could spend a few bucks on a crew that knew how to slow down going around a curve. The MBTA has been doing the public transit service/private contractor outsourcing thing now for several years and service has never been worse; couple weeks ago GF and I were waiting for a train which blasts by a scheduled stop at about 70 mph leaving everyone on the platform scratching their heads, and then comes sheepishly backing up the tracks about ten minutes later. In Japan an engineer would probably be fired and imprisoned for 60 days for making an error like that. <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> Bunch of lowest-bidder muppets
[toc] | [next] | [standalone]
| From | amdx <nojunk@knology.net> |
|---|---|
| Date | 2017-12-19 08:37 -0600 |
| Message-ID | <p1b877$dkj$1@dont-email.me> |
| In reply to | #488750 |
On 12/19/2017 6:00 AM, bitrex wrote:
> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755>
>
> $800 million spent on the project you'd think they could spend a few
> bucks on a crew that knew how to slow down going around a curve.
>
> The MBTA has been doing the public transit service/private contractor
> outsourcing thing now for several years and service has never been
> worse; couple weeks ago GF and I were waiting for a train which blasts
> by a scheduled stop at about 70 mph leaving everyone on the platform
> scratching their heads, and then comes sheepishly backing up the tracks
> about ten minutes later.
>
> In Japan an engineer would probably be fired and imprisoned for 60 days
> for making an error like that.
>
> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor>
>
>
> Bunch of lowest-bidder muppets
It does seem silly that if you know the speed limit on a corner is
30Mph, and computer technology ten steps ahead of such a simple command
as, "you must slow down now to go 30Mph around the corner ahead", it is
not part of the system. (F'ed/up sentence)
There have been too many train speeding accidents. It's time.
Trains could be run by computer with an engineer forced to stay at the
seat with continuous computer questioning that must be answered, just in
case human control is needed. (keep the union happy)
Mikek
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2017-12-19 09:49 -0500 |
| Message-ID | <p1b8t3$igj$1@dont-email.me> |
| In reply to | #488753 |
amdx wrote on 12/19/2017 9:37 AM: > On 12/19/2017 6:00 AM, bitrex wrote: >> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >> >> $800 million spent on the project you'd think they could spend a few bucks >> on a crew that knew how to slow down going around a curve. >> >> The MBTA has been doing the public transit service/private contractor >> outsourcing thing now for several years and service has never been worse; >> couple weeks ago GF and I were waiting for a train which blasts by a >> scheduled stop at about 70 mph leaving everyone on the platform scratching >> their heads, and then comes sheepishly backing up the tracks about ten >> minutes later. >> >> In Japan an engineer would probably be fired and imprisoned for 60 days >> for making an error like that. >> >> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >> >> >> Bunch of lowest-bidder muppets > > It does seem silly that if you know the speed limit on a corner is 30Mph, > and computer technology ten steps ahead of such a simple command as, "you > must slow down now to go 30Mph around the corner ahead", it is not part of > the system. (F'ed/up sentence) > There have been too many train speeding accidents. It's time. > Trains could be run by computer with an engineer forced to stay at the seat > with continuous computer questioning that must be answered, just in case > human control is needed. (keep the union happy) They are working on the problem, but railroads don't have tons of cash sitting around and installing this system is expensive. You might think the solution is simple, but railroads aren't steeped in technology and often parts of the railroad are distant from... anything really. There are many blind spots and by that I don't mean curves, I mean places where radio links can't reach. That's one problem they have had using radios on trains, the not infrequent loss of communications. Heck, the safely record of trains is pretty high I believe. If you want to focus on a real problem, do something about the automobile deaths. "There have been too many train ^H^H^H^H^H^Hcar speeding accidents." -- Rick C Viewed the eclipse at Wintercrest Farms, on the centerline of totality since 1998
[toc] | [prev] | [next] | [standalone]
| From | bitrex <bitrex@de.lete.earthlink.net> |
|---|---|
| Date | 2017-12-19 10:00 -0500 |
| Message-ID | <mQ9_B.4352$lH5.3776@fx31.iad> |
| In reply to | #488755 |
On 12/19/2017 09:49 AM, rickman wrote: > amdx wrote on 12/19/2017 9:37 AM: >> On 12/19/2017 6:00 AM, bitrex wrote: >>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >>> >>> $800 million spent on the project you'd think they could spend a few >>> bucks >>> on a crew that knew how to slow down going around a curve. >>> >>> The MBTA has been doing the public transit service/private contractor >>> outsourcing thing now for several years and service has never been >>> worse; >>> couple weeks ago GF and I were waiting for a train which blasts by a >>> scheduled stop at about 70 mph leaving everyone on the platform >>> scratching >>> their heads, and then comes sheepishly backing up the tracks about ten >>> minutes later. >>> >>> In Japan an engineer would probably be fired and imprisoned for 60 days >>> for making an error like that. >>> >>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >>> >>> >>> >>> Bunch of lowest-bidder muppets >> >> It does seem silly that if you know the speed limit on a corner is >> 30Mph, >> and computer technology ten steps ahead of such a simple command as, "you >> must slow down now to go 30Mph around the corner ahead", it is not >> part of >> the system. (F'ed/up sentence) >> There have been too many train speeding accidents. It's time. >> Trains could be run by computer with an engineer forced to stay at >> the seat >> with continuous computer questioning that must be answered, just in case >> human control is needed. (keep the union happy) > > They are working on the problem, but railroads don't have tons of cash > sitting around and installing this system is expensive. > > You might think the solution is simple, but railroads aren't steeped in > technology and often parts of the railroad are distant from... anything > really. There are many blind spots and by that I don't mean curves, I > mean places where radio links can't reach. That's one problem they have > had using radios on trains, the not infrequent loss of communications. LOL they spent EIGHT HUNDRED MILLION bucks on this expansion to have it fatally crash on its inaugural run! There's nothing here that tech can fix! You can help avoid "everyday stupidity" with tech, but you can't use tech to prevent a muppet from wrecking a train if said muppet is determined to do so (which looks to be the case here!)
[toc] | [prev] | [next] | [standalone]
| From | bitrex <bitrex@de.lete.earthlink.net> |
|---|---|
| Date | 2017-12-19 09:56 -0500 |
| Message-ID | <FM9_B.4351$lH5.1324@fx31.iad> |
| In reply to | #488753 |
On 12/19/2017 09:37 AM, amdx wrote: > On 12/19/2017 6:00 AM, bitrex wrote: >> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >> >> $800 million spent on the project you'd think they could spend a few >> bucks on a crew that knew how to slow down going around a curve. >> >> The MBTA has been doing the public transit service/private contractor >> outsourcing thing now for several years and service has never been >> worse; couple weeks ago GF and I were waiting for a train which blasts >> by a scheduled stop at about 70 mph leaving everyone on the platform >> scratching their heads, and then comes sheepishly backing up the >> tracks about ten minutes later. >> >> In Japan an engineer would probably be fired and imprisoned for 60 >> days for making an error like that. >> >> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >> >> >> Bunch of lowest-bidder muppets > > It does seem silly that if you know the speed limit on a corner is > 30Mph, and computer technology ten steps ahead of such a simple command > as, "you must slow down now to go 30Mph around the corner ahead", it is > not part of the system. (F'ed/up sentence) > There have been too many train speeding accidents. It's time. > Trains could be run by computer with an engineer forced to stay at the > seat with continuous computer questioning that must be answered, just in > case human control is needed. (keep the union happy) > Mikek > > Private-sector unionization is all but dead in the US; the only ones that are still allowed to exist are mostly the dysfunctional but well-connected public-sector ones full of muppets too incompetent to do their jobs properly, much less actually organize and employ any kind of actual leverage that would benefit non-muppets. Transit worker unions are overpaid dead weight and the Democrats would be better off without 'em <https://tinyurl.com/ydech5es> Choo choo idiots
[toc] | [prev] | [next] | [standalone]
| From | John Larkin <jjlarkin@highlandtechnology.com> |
|---|---|
| Date | 2017-12-19 08:53 -0800 |
| Message-ID | <0kgi3d1l8egjt07upcc9dl7f446efmgm15@4ax.com> |
| In reply to | #488753 |
On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: >On 12/19/2017 6:00 AM, bitrex wrote: >> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >> >> $800 million spent on the project you'd think they could spend a few >> bucks on a crew that knew how to slow down going around a curve. >> >> The MBTA has been doing the public transit service/private contractor >> outsourcing thing now for several years and service has never been >> worse; couple weeks ago GF and I were waiting for a train which blasts >> by a scheduled stop at about 70 mph leaving everyone on the platform >> scratching their heads, and then comes sheepishly backing up the tracks >> about ten minutes later. >> >> In Japan an engineer would probably be fired and imprisoned for 60 days >> for making an error like that. >> >> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >> >> >> Bunch of lowest-bidder muppets > > It does seem silly that if you know the speed limit on a corner is >30Mph, and computer technology ten steps ahead of such a simple command >as, "you must slow down now to go 30Mph around the corner ahead", it is >not part of the system. (F'ed/up sentence) > There have been too many train speeding accidents. It's time. > Trains could be run by computer with an engineer forced to stay at the >seat with continuous computer questioning that must be answered, just in >case human control is needed. (keep the union happy) > Mikek > The Positive Train Control system is gradually being introduced on some runs. It's complex and fabulously expensive. An ipad or smart phone, with GPS and a fairly simple program, could alert the driver to speed problems, ring a giant bell, maybe apply brakes. That's too easy. -- John Larkin Highland Technology, Inc lunatic fringe electronics
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2017-12-19 12:20 -0500 |
| Message-ID | <p1bhpj$kpv$1@dont-email.me> |
| In reply to | #488770 |
John Larkin wrote on 12/19/2017 11:53 AM: > On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: > >> On 12/19/2017 6:00 AM, bitrex wrote: >>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >>> >>> $800 million spent on the project you'd think they could spend a few >>> bucks on a crew that knew how to slow down going around a curve. >>> >>> The MBTA has been doing the public transit service/private contractor >>> outsourcing thing now for several years and service has never been >>> worse; couple weeks ago GF and I were waiting for a train which blasts >>> by a scheduled stop at about 70 mph leaving everyone on the platform >>> scratching their heads, and then comes sheepishly backing up the tracks >>> about ten minutes later. >>> >>> In Japan an engineer would probably be fired and imprisoned for 60 days >>> for making an error like that. >>> >>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >>> >>> >>> Bunch of lowest-bidder muppets >> >> It does seem silly that if you know the speed limit on a corner is >> 30Mph, and computer technology ten steps ahead of such a simple command >> as, "you must slow down now to go 30Mph around the corner ahead", it is >> not part of the system. (F'ed/up sentence) >> There have been too many train speeding accidents. It's time. >> Trains could be run by computer with an engineer forced to stay at the >> seat with continuous computer questioning that must be answered, just in >> case human control is needed. (keep the union happy) >> Mikek >> > > The Positive Train Control system is gradually being introduced on > some runs. It's complex and fabulously expensive. > > An ipad or smart phone, with GPS and a fairly simple program, could > alert the driver to speed problems, ring a giant bell, maybe apply > brakes. That's too easy. It's also too stupid to do the job that needs to be done. -- Rick C Viewed the eclipse at Wintercrest Farms, on the centerline of totality since 1998
[toc] | [prev] | [next] | [standalone]
| From | whit3rd <whit3rd@gmail.com> |
|---|---|
| Date | 2017-12-19 14:27 -0800 |
| Message-ID | <9ce5a538-dcf5-4437-9a65-b59155acb69a@googlegroups.com> |
| In reply to | #488774 |
On Tuesday, December 19, 2017 at 9:20:58 AM UTC-8, rickman wrote: > John Larkin wrote on 12/19/2017 11:53 AM: > > The Positive Train Control system is gradually being introduced on > > some runs. It's complex and fabulously expensive. > > > > An ipad or smart phone, with GPS and a fairly simple program, could... > It's also too stupid to do the job that needs to be done. But, if you can just count wheel revolutions, any given run on a track could get mapped effectively, and zoned speed control can't be a 'complex and fabulously expensive' operation. Something smells like an A-B problem. Did the 'positive train control' specification ever get published? Does it require some oddball doesn't-scale-up technology to be applied at scale? I suspect the costly part is the global-awareness-of-other-trains that has to work even when trains are out of communication. That wasn't the problem in the recent Amtrak derailment.
[toc] | [prev] | [next] | [standalone]
| From | John Larkin <jjlarkin@highland_snip_technology.com> |
|---|---|
| Date | 2017-12-19 15:24 -0800 |
| Message-ID | <jm7j3d5kd7hvk6nnq39d75l0sjagju46cv@4ax.com> |
| In reply to | #488808 |
On Tue, 19 Dec 2017 14:27:33 -0800 (PST), whit3rd <whit3rd@gmail.com> wrote: >On Tuesday, December 19, 2017 at 9:20:58 AM UTC-8, rickman wrote: >> John Larkin wrote on 12/19/2017 11:53 AM: > >> > The Positive Train Control system is gradually being introduced on >> > some runs. It's complex and fabulously expensive. >> > >> > An ipad or smart phone, with GPS and a fairly simple program, could... > >> It's also too stupid to do the job that needs to be done. > >But, if you can just count wheel revolutions, any given run on >a track could get mapped effectively, and zoned speed control can't >be a 'complex and fabulously expensive' operation. How about using GPS? > >Something smells like an A-B problem. Did the 'positive train control' >specification ever get published? Does it require some oddball >doesn't-scale-up technology to be applied at scale? PTC is another gigantic, gigabuck, bloated IT project. > >I suspect the costly part is the global-awareness-of-other-trains >that has to work even when trains are out of communication. That >wasn't the problem in the recent Amtrak derailment. Speeding causes a lot of wrecks. Like going 81 MPH around a 30 MPH-rated curve. -- John Larkin Highland Technology, Inc picosecond timing precision measurement jlarkin att highlandtechnology dott com http://www.highlandtechnology.com
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2017-12-19 18:39 -0500 |
| Message-ID | <p1c7vu$70j$1@dont-email.me> |
| In reply to | #488808 |
whit3rd wrote on 12/19/2017 5:27 PM: > On Tuesday, December 19, 2017 at 9:20:58 AM UTC-8, rickman wrote: >> John Larkin wrote on 12/19/2017 11:53 AM: > >>> The Positive Train Control system is gradually being introduced on >>> some runs. It's complex and fabulously expensive. >>> >>> An ipad or smart phone, with GPS and a fairly simple program, could... > >> It's also too stupid to do the job that needs to be done. > > But, if you can just count wheel revolutions, any given run on > a track could get mapped effectively, and zoned speed control can't > be a 'complex and fabulously expensive' operation. > > Something smells like an A-B problem. Did the 'positive train control' > specification ever get published? Does it require some oddball > doesn't-scale-up technology to be applied at scale? > > I suspect the costly part is the global-awareness-of-other-trains > that has to work even when trains are out of communication. That > wasn't the problem in the recent Amtrak derailment. What was the problem? I didn't find anything in particular when I searched. There have been a number of accidents over the years including some on the DC metrorail system. Nothing like the number of people killed on highways. A dozen here, a dozen there, meanwhile every day there are some 100 people who die in autos in the US. When I was looking for the report of the gasoline tanker accident on the DC beltway it was hard to find among all the many gas tanker accidents with the accompanying conflagrations. Seems the DC metro system is pretty good. The accident a few years ago was because a detector was wigging out in a rapid intermittent way that the system didn't detect. They would have gotten off with no blame but the investigation found other cases of unreported incidents with no accident that should have been reported and may have helped to prevent this accident. -- Rick C Viewed the eclipse at Wintercrest Farms, on the centerline of totality since 1998
[toc] | [prev] | [next] | [standalone]
| From | krw@notreal.com |
|---|---|
| Date | 2017-12-19 20:53 -0500 |
| Message-ID | <9kgj3d9njom7lbp3igaf087m5im1tu3mpi@4ax.com> |
| In reply to | #488774 |
On Tue, 19 Dec 2017 12:20:31 -0500, rickman <gnuarm@gmail.com> wrote: >John Larkin wrote on 12/19/2017 11:53 AM: >> On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: >> >>> On 12/19/2017 6:00 AM, bitrex wrote: >>>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >>>> >>>> $800 million spent on the project you'd think they could spend a few >>>> bucks on a crew that knew how to slow down going around a curve. >>>> >>>> The MBTA has been doing the public transit service/private contractor >>>> outsourcing thing now for several years and service has never been >>>> worse; couple weeks ago GF and I were waiting for a train which blasts >>>> by a scheduled stop at about 70 mph leaving everyone on the platform >>>> scratching their heads, and then comes sheepishly backing up the tracks >>>> about ten minutes later. >>>> >>>> In Japan an engineer would probably be fired and imprisoned for 60 days >>>> for making an error like that. >>>> >>>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >>>> >>>> >>>> Bunch of lowest-bidder muppets >>> >>> It does seem silly that if you know the speed limit on a corner is >>> 30Mph, and computer technology ten steps ahead of such a simple command >>> as, "you must slow down now to go 30Mph around the corner ahead", it is >>> not part of the system. (F'ed/up sentence) >>> There have been too many train speeding accidents. It's time. >>> Trains could be run by computer with an engineer forced to stay at the >>> seat with continuous computer questioning that must be answered, just in >>> case human control is needed. (keep the union happy) >>> Mikek >>> >> >> The Positive Train Control system is gradually being introduced on >> some runs. It's complex and fabulously expensive. >> >> An ipad or smart phone, with GPS and a fairly simple program, could >> alert the driver to speed problems, ring a giant bell, maybe apply >> brakes. That's too easy. > >It's also too stupid to do the job that needs to be done. Government? You bet!
[toc] | [prev] | [next] | [standalone]
| From | John Larkin <jjlarkin@highland_snip_technology.com> |
|---|---|
| Date | 2017-12-20 10:08 -0800 |
| Message-ID | <8j9l3d18ugbpk5pf219ui74umfog76p64l@4ax.com> |
| In reply to | #488830 |
On Tue, 19 Dec 2017 20:53:35 -0500, krw@notreal.com wrote: >On Tue, 19 Dec 2017 12:20:31 -0500, rickman <gnuarm@gmail.com> wrote: > >>John Larkin wrote on 12/19/2017 11:53 AM: >>> On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: >>> >>>> On 12/19/2017 6:00 AM, bitrex wrote: >>>>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >>>>> >>>>> $800 million spent on the project you'd think they could spend a few >>>>> bucks on a crew that knew how to slow down going around a curve. >>>>> >>>>> The MBTA has been doing the public transit service/private contractor >>>>> outsourcing thing now for several years and service has never been >>>>> worse; couple weeks ago GF and I were waiting for a train which blasts >>>>> by a scheduled stop at about 70 mph leaving everyone on the platform >>>>> scratching their heads, and then comes sheepishly backing up the tracks >>>>> about ten minutes later. >>>>> >>>>> In Japan an engineer would probably be fired and imprisoned for 60 days >>>>> for making an error like that. >>>>> >>>>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >>>>> >>>>> >>>>> Bunch of lowest-bidder muppets >>>> >>>> It does seem silly that if you know the speed limit on a corner is >>>> 30Mph, and computer technology ten steps ahead of such a simple command >>>> as, "you must slow down now to go 30Mph around the corner ahead", it is >>>> not part of the system. (F'ed/up sentence) >>>> There have been too many train speeding accidents. It's time. >>>> Trains could be run by computer with an engineer forced to stay at the >>>> seat with continuous computer questioning that must be answered, just in >>>> case human control is needed. (keep the union happy) >>>> Mikek >>>> >>> >>> The Positive Train Control system is gradually being introduced on >>> some runs. It's complex and fabulously expensive. >>> >>> An ipad or smart phone, with GPS and a fairly simple program, could >>> alert the driver to speed problems, ring a giant bell, maybe apply >>> brakes. That's too easy. >> >>It's also too stupid to do the job that needs to be done. > >Government? You bet! GPS can navigate a car block-by-block in any city in the USA, so surely it could track train speed and location. A lot of train crashes happen when the driver doesn't slow down for curves. -- John Larkin Highland Technology, Inc picosecond timing precision measurement jlarkin att highlandtechnology dott com http://www.highlandtechnology.com
[toc] | [prev] | [next] | [standalone]
| From | rickman <gnuarm@gmail.com> |
|---|---|
| Date | 2017-12-20 13:19 -0500 |
| Message-ID | <p1e9j7$h7n$2@dont-email.me> |
| In reply to | #488872 |
John Larkin wrote on 12/20/2017 1:08 PM: > On Tue, 19 Dec 2017 20:53:35 -0500, krw@notreal.com wrote: > >> On Tue, 19 Dec 2017 12:20:31 -0500, rickman <gnuarm@gmail.com> wrote: >> >>> John Larkin wrote on 12/19/2017 11:53 AM: >>>> On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: >>>> >>>>> On 12/19/2017 6:00 AM, bitrex wrote: >>>>>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >>>>>> >>>>>> $800 million spent on the project you'd think they could spend a few >>>>>> bucks on a crew that knew how to slow down going around a curve. >>>>>> >>>>>> The MBTA has been doing the public transit service/private contractor >>>>>> outsourcing thing now for several years and service has never been >>>>>> worse; couple weeks ago GF and I were waiting for a train which blasts >>>>>> by a scheduled stop at about 70 mph leaving everyone on the platform >>>>>> scratching their heads, and then comes sheepishly backing up the tracks >>>>>> about ten minutes later. >>>>>> >>>>>> In Japan an engineer would probably be fired and imprisoned for 60 days >>>>>> for making an error like that. >>>>>> >>>>>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >>>>>> >>>>>> >>>>>> Bunch of lowest-bidder muppets >>>>> >>>>> It does seem silly that if you know the speed limit on a corner is >>>>> 30Mph, and computer technology ten steps ahead of such a simple command >>>>> as, "you must slow down now to go 30Mph around the corner ahead", it is >>>>> not part of the system. (F'ed/up sentence) >>>>> There have been too many train speeding accidents. It's time. >>>>> Trains could be run by computer with an engineer forced to stay at the >>>>> seat with continuous computer questioning that must be answered, just in >>>>> case human control is needed. (keep the union happy) >>>>> Mikek >>>>> >>>> >>>> The Positive Train Control system is gradually being introduced on >>>> some runs. It's complex and fabulously expensive. >>>> >>>> An ipad or smart phone, with GPS and a fairly simple program, could >>>> alert the driver to speed problems, ring a giant bell, maybe apply >>>> brakes. That's too easy. >>> >>> It's also too stupid to do the job that needs to be done. > > GPS can navigate a car block-by-block in any city in the USA, so > surely it could track train speed and location. GPS isn't reliable. I've seen my GPS report location some significant distance from my true location because of the surrounding terrain. -- Rick C Viewed the eclipse at Wintercrest Farms, on the centerline of totality since 1998
[toc] | [prev] | [next] | [standalone]
| From | Lasse Langwadt Christensen <langwadt@fonz.dk> |
|---|---|
| Date | 2017-12-20 10:32 -0800 |
| Message-ID | <6e60bdfc-7b65-46a6-8c57-fdbc5b63091f@googlegroups.com> |
| In reply to | #488874 |
Den onsdag den 20. december 2017 kl. 19.19.23 UTC+1 skrev rickman: > John Larkin wrote on 12/20/2017 1:08 PM: > > On Tue, 19 Dec 2017 20:53:35 -0500, krw@notreal.com wrote: > > > >> On Tue, 19 Dec 2017 12:20:31 -0500, rickman <gnuarm@gmail.com> wrote: > >> > >>> John Larkin wrote on 12/19/2017 11:53 AM: > >>>> On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: > >>>> > >>>>> On 12/19/2017 6:00 AM, bitrex wrote: > >>>>>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> > >>>>>> > >>>>>> $800 million spent on the project you'd think they could spend a few > >>>>>> bucks on a crew that knew how to slow down going around a curve. > >>>>>> > >>>>>> The MBTA has been doing the public transit service/private contractor > >>>>>> outsourcing thing now for several years and service has never been > >>>>>> worse; couple weeks ago GF and I were waiting for a train which blasts > >>>>>> by a scheduled stop at about 70 mph leaving everyone on the platform > >>>>>> scratching their heads, and then comes sheepishly backing up the tracks > >>>>>> about ten minutes later. > >>>>>> > >>>>>> In Japan an engineer would probably be fired and imprisoned for 60 days > >>>>>> for making an error like that. > >>>>>> > >>>>>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> > >>>>>> > >>>>>> > >>>>>> Bunch of lowest-bidder muppets > >>>>> > >>>>> It does seem silly that if you know the speed limit on a corner is > >>>>> 30Mph, and computer technology ten steps ahead of such a simple command > >>>>> as, "you must slow down now to go 30Mph around the corner ahead", it is > >>>>> not part of the system. (F'ed/up sentence) > >>>>> There have been too many train speeding accidents. It's time. > >>>>> Trains could be run by computer with an engineer forced to stay at the > >>>>> seat with continuous computer questioning that must be answered, just in > >>>>> case human control is needed. (keep the union happy) > >>>>> Mikek > >>>>> > >>>> > >>>> The Positive Train Control system is gradually being introduced on > >>>> some runs. It's complex and fabulously expensive. > >>>> > >>>> An ipad or smart phone, with GPS and a fairly simple program, could > >>>> alert the driver to speed problems, ring a giant bell, maybe apply > >>>> brakes. That's too easy. > >>> > >>> It's also too stupid to do the job that needs to be done. > > > > GPS can navigate a car block-by-block in any city in the USA, so > > surely it could track train speed and location. > > GPS isn't reliable. I've seen my GPS report location some significant > distance from my true location because of the surrounding terrain. > unless you lay down tracks as you go, the possible locations for a train is quite limited ... https://i.imgur.com/567DHDu.gif
[toc] | [prev] | [next] | [standalone]
| From | John Larkin <jjlarkin@highland_snip_technology.com> |
|---|---|
| Date | 2017-12-20 12:11 -0800 |
| Message-ID | <mrgl3dtcginachc2404glstr8uf4qcojhh@4ax.com> |
| In reply to | #488878 |
On Wed, 20 Dec 2017 10:32:07 -0800 (PST), Lasse Langwadt Christensen <langwadt@fonz.dk> wrote: >Den onsdag den 20. december 2017 kl. 19.19.23 UTC+1 skrev rickman: >> John Larkin wrote on 12/20/2017 1:08 PM: >> > On Tue, 19 Dec 2017 20:53:35 -0500, krw@notreal.com wrote: >> > >> >> On Tue, 19 Dec 2017 12:20:31 -0500, rickman <gnuarm@gmail.com> wrote: >> >> >> >>> John Larkin wrote on 12/19/2017 11:53 AM: >> >>>> On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: >> >>>> >> >>>>> On 12/19/2017 6:00 AM, bitrex wrote: >> >>>>>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >> >>>>>> >> >>>>>> $800 million spent on the project you'd think they could spend a few >> >>>>>> bucks on a crew that knew how to slow down going around a curve. >> >>>>>> >> >>>>>> The MBTA has been doing the public transit service/private contractor >> >>>>>> outsourcing thing now for several years and service has never been >> >>>>>> worse; couple weeks ago GF and I were waiting for a train which blasts >> >>>>>> by a scheduled stop at about 70 mph leaving everyone on the platform >> >>>>>> scratching their heads, and then comes sheepishly backing up the tracks >> >>>>>> about ten minutes later. >> >>>>>> >> >>>>>> In Japan an engineer would probably be fired and imprisoned for 60 days >> >>>>>> for making an error like that. >> >>>>>> >> >>>>>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >> >>>>>> >> >>>>>> >> >>>>>> Bunch of lowest-bidder muppets >> >>>>> >> >>>>> It does seem silly that if you know the speed limit on a corner is >> >>>>> 30Mph, and computer technology ten steps ahead of such a simple command >> >>>>> as, "you must slow down now to go 30Mph around the corner ahead", it is >> >>>>> not part of the system. (F'ed/up sentence) >> >>>>> There have been too many train speeding accidents. It's time. >> >>>>> Trains could be run by computer with an engineer forced to stay at the >> >>>>> seat with continuous computer questioning that must be answered, just in >> >>>>> case human control is needed. (keep the union happy) >> >>>>> Mikek >> >>>>> >> >>>> >> >>>> The Positive Train Control system is gradually being introduced on >> >>>> some runs. It's complex and fabulously expensive. >> >>>> >> >>>> An ipad or smart phone, with GPS and a fairly simple program, could >> >>>> alert the driver to speed problems, ring a giant bell, maybe apply >> >>>> brakes. That's too easy. >> >>> >> >>> It's also too stupid to do the job that needs to be done. >> > >> > GPS can navigate a car block-by-block in any city in the USA, so >> > surely it could track train speed and location. >> >> GPS isn't reliable. I've seen my GPS report location some significant >> distance from my true location because of the surrounding terrain. >> > >unless you lay down tracks as you go, the possible locations for a train >is quite limited ... > >https://i.imgur.com/567DHDu.gif > > > https://www.dropbox.com/s/i1sw7shpex29wf1/2N7000.jpg?raw=1 And trains take miles to accelerate and brake. -- John Larkin Highland Technology, Inc picosecond timing precision measurement jlarkin att highlandtechnology dott com http://www.highlandtechnology.com
[toc] | [prev] | [next] | [standalone]
| From | krw@notreal.com |
|---|---|
| Date | 2017-12-20 21:52 -0500 |
| Message-ID | <af8m3dpdilq5s9shjr3985jou91a05fj6q@4ax.com> |
| In reply to | #488874 |
On Wed, 20 Dec 2017 13:19:20 -0500, rickman <gnuarm@gmail.com> wrote: >John Larkin wrote on 12/20/2017 1:08 PM: >> On Tue, 19 Dec 2017 20:53:35 -0500, krw@notreal.com wrote: >> >>> On Tue, 19 Dec 2017 12:20:31 -0500, rickman <gnuarm@gmail.com> wrote: >>> >>>> John Larkin wrote on 12/19/2017 11:53 AM: >>>>> On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: >>>>> >>>>>> On 12/19/2017 6:00 AM, bitrex wrote: >>>>>>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >>>>>>> >>>>>>> $800 million spent on the project you'd think they could spend a few >>>>>>> bucks on a crew that knew how to slow down going around a curve. >>>>>>> >>>>>>> The MBTA has been doing the public transit service/private contractor >>>>>>> outsourcing thing now for several years and service has never been >>>>>>> worse; couple weeks ago GF and I were waiting for a train which blasts >>>>>>> by a scheduled stop at about 70 mph leaving everyone on the platform >>>>>>> scratching their heads, and then comes sheepishly backing up the tracks >>>>>>> about ten minutes later. >>>>>>> >>>>>>> In Japan an engineer would probably be fired and imprisoned for 60 days >>>>>>> for making an error like that. >>>>>>> >>>>>>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >>>>>>> >>>>>>> >>>>>>> Bunch of lowest-bidder muppets >>>>>> >>>>>> It does seem silly that if you know the speed limit on a corner is >>>>>> 30Mph, and computer technology ten steps ahead of such a simple command >>>>>> as, "you must slow down now to go 30Mph around the corner ahead", it is >>>>>> not part of the system. (F'ed/up sentence) >>>>>> There have been too many train speeding accidents. It's time. >>>>>> Trains could be run by computer with an engineer forced to stay at the >>>>>> seat with continuous computer questioning that must be answered, just in >>>>>> case human control is needed. (keep the union happy) >>>>>> Mikek >>>>>> >>>>> >>>>> The Positive Train Control system is gradually being introduced on >>>>> some runs. It's complex and fabulously expensive. >>>>> >>>>> An ipad or smart phone, with GPS and a fairly simple program, could >>>>> alert the driver to speed problems, ring a giant bell, maybe apply >>>>> brakes. That's too easy. >>>> >>>> It's also too stupid to do the job that needs to be done. >> >> GPS can navigate a car block-by-block in any city in the USA, so >> surely it could track train speed and location. > >GPS isn't reliable. I've seen my GPS report location some significant >distance from my true location because of the surrounding terrain. So it's useless because it's not perfect? Utter nonsense.
[toc] | [prev] | [next] | [standalone]
| From | John Larkin <jjlarkin@highland_snip_technology.com> |
|---|---|
| Date | 2017-12-21 10:56 -0800 |
| Message-ID | <6q0o3d1pu7cl6iectn0bdcot69sn73mu70@4ax.com> |
| In reply to | #488925 |
On Wed, 20 Dec 2017 21:52:59 -0500, krw@notreal.com wrote: >On Wed, 20 Dec 2017 13:19:20 -0500, rickman <gnuarm@gmail.com> wrote: > >>John Larkin wrote on 12/20/2017 1:08 PM: >>> On Tue, 19 Dec 2017 20:53:35 -0500, krw@notreal.com wrote: >>> >>>> On Tue, 19 Dec 2017 12:20:31 -0500, rickman <gnuarm@gmail.com> wrote: >>>> >>>>> John Larkin wrote on 12/19/2017 11:53 AM: >>>>>> On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: >>>>>> >>>>>>> On 12/19/2017 6:00 AM, bitrex wrote: >>>>>>>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >>>>>>>> >>>>>>>> $800 million spent on the project you'd think they could spend a few >>>>>>>> bucks on a crew that knew how to slow down going around a curve. >>>>>>>> >>>>>>>> The MBTA has been doing the public transit service/private contractor >>>>>>>> outsourcing thing now for several years and service has never been >>>>>>>> worse; couple weeks ago GF and I were waiting for a train which blasts >>>>>>>> by a scheduled stop at about 70 mph leaving everyone on the platform >>>>>>>> scratching their heads, and then comes sheepishly backing up the tracks >>>>>>>> about ten minutes later. >>>>>>>> >>>>>>>> In Japan an engineer would probably be fired and imprisoned for 60 days >>>>>>>> for making an error like that. >>>>>>>> >>>>>>>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >>>>>>>> >>>>>>>> >>>>>>>> Bunch of lowest-bidder muppets >>>>>>> >>>>>>> It does seem silly that if you know the speed limit on a corner is >>>>>>> 30Mph, and computer technology ten steps ahead of such a simple command >>>>>>> as, "you must slow down now to go 30Mph around the corner ahead", it is >>>>>>> not part of the system. (F'ed/up sentence) >>>>>>> There have been too many train speeding accidents. It's time. >>>>>>> Trains could be run by computer with an engineer forced to stay at the >>>>>>> seat with continuous computer questioning that must be answered, just in >>>>>>> case human control is needed. (keep the union happy) >>>>>>> Mikek >>>>>>> >>>>>> >>>>>> The Positive Train Control system is gradually being introduced on >>>>>> some runs. It's complex and fabulously expensive. >>>>>> >>>>>> An ipad or smart phone, with GPS and a fairly simple program, could >>>>>> alert the driver to speed problems, ring a giant bell, maybe apply >>>>>> brakes. That's too easy. >>>>> >>>>> It's also too stupid to do the job that needs to be done. >>> >>> GPS can navigate a car block-by-block in any city in the USA, so >>> surely it could track train speed and location. >> >>GPS isn't reliable. I've seen my GPS report location some significant >>distance from my true location because of the surrounding terrain. > >So it's useless because it's not perfect? Utter nonsense. Trains are big, accelerate and decelerate slowly, and their path is entirely predictable. You could put a GPS receiver and iPad on both ends of a mile-long train. There are lots of opportunities for algorithms. -- John Larkin Highland Technology, Inc picosecond timing precision measurement jlarkin att highlandtechnology dott com http://www.highlandtechnology.com
[toc] | [prev] | [next] | [standalone]
| From | krw@notreal.com |
|---|---|
| Date | 2017-12-21 19:24 -0500 |
| Message-ID | <0rjo3d19ffuqa5o7hbciffjsces9gtbj90@4ax.com> |
| In reply to | #488970 |
On Thu, 21 Dec 2017 10:56:44 -0800, John Larkin <jjlarkin@highland_snip_technology.com> wrote: >On Wed, 20 Dec 2017 21:52:59 -0500, krw@notreal.com wrote: > >>On Wed, 20 Dec 2017 13:19:20 -0500, rickman <gnuarm@gmail.com> wrote: >> >>>John Larkin wrote on 12/20/2017 1:08 PM: >>>> On Tue, 19 Dec 2017 20:53:35 -0500, krw@notreal.com wrote: >>>> >>>>> On Tue, 19 Dec 2017 12:20:31 -0500, rickman <gnuarm@gmail.com> wrote: >>>>> >>>>>> John Larkin wrote on 12/19/2017 11:53 AM: >>>>>>> On Tue, 19 Dec 2017 08:37:25 -0600, amdx <nojunk@knology.net> wrote: >>>>>>> >>>>>>>> On 12/19/2017 6:00 AM, bitrex wrote: >>>>>>>>> <https://jalopnik.com/what-causes-amtrak-trains-to-derail-1821404755> >>>>>>>>> >>>>>>>>> $800 million spent on the project you'd think they could spend a few >>>>>>>>> bucks on a crew that knew how to slow down going around a curve. >>>>>>>>> >>>>>>>>> The MBTA has been doing the public transit service/private contractor >>>>>>>>> outsourcing thing now for several years and service has never been >>>>>>>>> worse; couple weeks ago GF and I were waiting for a train which blasts >>>>>>>>> by a scheduled stop at about 70 mph leaving everyone on the platform >>>>>>>>> scratching their heads, and then comes sheepishly backing up the tracks >>>>>>>>> about ten minutes later. >>>>>>>>> >>>>>>>>> In Japan an engineer would probably be fired and imprisoned for 60 days >>>>>>>>> for making an error like that. >>>>>>>>> >>>>>>>>> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >>>>>>>>> >>>>>>>>> >>>>>>>>> Bunch of lowest-bidder muppets >>>>>>>> >>>>>>>> It does seem silly that if you know the speed limit on a corner is >>>>>>>> 30Mph, and computer technology ten steps ahead of such a simple command >>>>>>>> as, "you must slow down now to go 30Mph around the corner ahead", it is >>>>>>>> not part of the system. (F'ed/up sentence) >>>>>>>> There have been too many train speeding accidents. It's time. >>>>>>>> Trains could be run by computer with an engineer forced to stay at the >>>>>>>> seat with continuous computer questioning that must be answered, just in >>>>>>>> case human control is needed. (keep the union happy) >>>>>>>> Mikek >>>>>>>> >>>>>>> >>>>>>> The Positive Train Control system is gradually being introduced on >>>>>>> some runs. It's complex and fabulously expensive. >>>>>>> >>>>>>> An ipad or smart phone, with GPS and a fairly simple program, could >>>>>>> alert the driver to speed problems, ring a giant bell, maybe apply >>>>>>> brakes. That's too easy. >>>>>> >>>>>> It's also too stupid to do the job that needs to be done. >>>> >>>> GPS can navigate a car block-by-block in any city in the USA, so >>>> surely it could track train speed and location. >>> >>>GPS isn't reliable. I've seen my GPS report location some significant >>>distance from my true location because of the surrounding terrain. >> >>So it's useless because it's not perfect? Utter nonsense. > >Trains are big, accelerate and decelerate slowly, and their path is >entirely predictable. You could put a GPS receiver and iPad on both >ends of a mile-long train. There are lots of opportunities for >algorithms. Agree 100%. You could put one on every car and have it jump up and down and bitch if it detected anything dangerous. Maybe *someone* would notice and fix the problem (slow down, in this case). It wouldn't even need positive control, with all the histrionics that entails. If cars can go autonomous on open highways and compete with real people drivers, controlling a train that's restricted to well known tracks without other moronic drivers seems like kindergarten script-kiddie stuff.
[toc] | [prev] | [next] | [standalone]
| From | "Tim Williams" <tiwill@seventransistorlabs.com> |
|---|---|
| Date | 2017-12-19 16:48 -0600 |
| Subject | Re: Muppets |
| Message-ID | <p1c505$ine$1@dont-email.me> |
| In reply to | #488750 |
"bitrex" <bitrex@de.lete.earthlink.net> wrote in message news:Eb7_B.2465$oE2.529@fx33.iad... > In Japan an engineer would probably be fired and imprisoned for 60 days > for making an error like that. > > <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> > > Bunch of lowest-bidder muppets Please. Japan isn't the US. Be grateful they provide unprofitable services at all: https://www.youtube.com/watch?v=mbEfzuCLoAQ If they had the wide open spaces we do, they'd have the same problems we do. If we had the same high density they do, well... we'd have a shitload of problems because that's a few Earths of people in one country... but at least we'd have good train service?! Tim -- Seven Transistor Labs, LLC Electrical Engineering Consultation and Contract Design Website: https://www.seventransistorlabs.com/
[toc] | [prev] | [next] | [standalone]
| From | bitrex <bitrex@de.lete.earthlink.net> |
|---|---|
| Date | 2017-12-19 18:08 -0500 |
| Subject | Re: Muppets |
| Message-ID | <WZg_B.3413$_b6.957@fx43.iad> |
| In reply to | #488810 |
On 12/19/2017 05:48 PM, Tim Williams wrote: > "bitrex" <bitrex@de.lete.earthlink.net> wrote in message > news:Eb7_B.2465$oE2.529@fx33.iad... >> In Japan an engineer would probably be fired and imprisoned for 60 >> days for making an error like that. >> >> <http://www.milforddailynews.com/news/20170512/keolis-workers-sound-off-on-commuter-rail-contractor> >> >> >> Bunch of lowest-bidder muppets > > Please. Japan isn't the US. > > Be grateful they provide unprofitable services at all: > https://www.youtube.com/watch?v=mbEfzuCLoAQ > > If they had the wide open spaces we do, they'd have the same problems we > do. If we had the same high density they do, well... we'd have a > shitload of problems because that's a few Earths of people in one > country... but at least we'd have good train service?! > > Tim > They suck for the same reason most public-infrastructure things suck in the US; there's no popular will to make it better. If there was it would be different. But there isn't because Americans who aren't millionaires are all temporarily down-on-their-luck millionaires, there's little point in working (or campaigning on such a platform as a politician) for better "legacy" ground transit, which is for poors, when you could be voting for investment in hyperloops, hypersonic passenger jets, point to point rocket travel, flying Uber taxis, and all the other nice things that await after you make it big, real soon now. Bad train and bus service is a good motivator to "work hard", imagine how many more "parasites" there'd be if it were inexpensive and pleasant!
[toc] | [prev] | [next] | [standalone]
Page 1 of 9 [1] 2 3 4 5 6 7 8 9 Next page →
Back to top | Article view | sci.electronics.design
csiph-web