Flutterby™! : Talking to stop lights

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Talking to stop lights

2016-12-08 22:35:29.640477+00 by Dan Lyke 4 comments

Audi cars now talk to stop lights in Vegas. Which is to say that they talk over the 4G LTE network to Traffic Technology Services (TTS), of Beaverton, OR, and TTS talks to the stop lights. But still cool.

Although the idea of an Audi driver watching the countdown to a green light and punching it should put fear into slow pedestrians and people who accelerate through yellow lights...

[ related topics: broadband Automobiles ]

comments in ascending chronological order (reverse):

#Comment Re: Talking to stop lights made: 2016-12-09 02:03:04.975975+00 by: TheSHAD0W

Obviously the pedestrians need to be tied in, too.

#Comment Re: Talking to stop lights made: 2016-12-13 23:13:50.946497+00 by: TheSHAD0W

Related: Feds: Cars must be able to talk to each other

Yeahhhh... I'd have to opine against this. Cars should talk to a central, verified authority which would relay messages and make decisions. Otherwise you could fool vehicles into doing pretty much anything in order to avoid a crash.

#Comment Re: Talking to stop lights made: 2016-12-14 00:42:11.372679+00 by: Dan Lyke

Presumably TTS is that central verified authority. They're probably the standard solution for traffic timing systems.

#Comment Re: Talking to stop lights made: 2016-12-14 00:43:45.870288+00 by: Dan Lyke

Oh, wait, you're talking about the new NHTSA stuff. Yeah, talked a bit about this at lunch with a guy who's done a bunch of supporting research. He's important enough that the NHTSA called him directly to tell him the new stuff was being released.

We were both in the "WTF?" mode of analysis. Maybe I'll try to write up something on this...

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)




Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.


Flutterby™ is a trademark claimed by

Dan Lyke
for the web publications at www.flutterby.com and www.flutterby.net.