But Officer....I was going WAY below the speed limit!

[Muzzman1]

I wonder where the camera found that, especially considering I was on the 405! lol

 

[jerry33]

Speed limit was 6 mph, you're 22 mph over.

 

[Edmond]

Well the '405' sounds like a spur bypass of I5, so would be in city limits. Should have a max of 60 mph. Maybe there's a speck of dust on the camera lens.

 

[Muzzman1]

I wonder where the camera found that, especially considering I was on the 405! lol

View attachment 168449

Funny thing is the AP jumped to 90 MPH, I had to reduce it manually!

 

[JeffS]

Speed limit was 6 mph, you're 22 mph over.

Ha!! I see what you did right there. You win one internets today.

 

[alexdav]

Ha!! I see what you did right there. You win one internets today.

I didn't at first... but once you mentioned there was something, I took another look. Now it I get it

There are 10 types of people in this world... those that understand

Spoiler: _____

binary

and those that don't.

 

[StaceyS]

Something like this recently happened to me in a loaner 70D driving down I-5 in Oregon. I was in a 50 mph zone and the car told me the speed limit was 85...

 

[int32_t]

Sorry to break the news, but there's no such thing as perfectly flawless software, particularly in something as complex as a car. Not even a Tesla. But what's the success rate? Nine times out of ten? Not bad.

 

[ggr]

Well the '405' sounds like a spur bypass of I5, so would be in city limits. Should have a max of 60 mph. Maybe there's a speck of dust on the camera lens.

I-405 is the main freeway to/past Los Angeles airport, definitely not a "spur", but I guess you could call it a bypass. Anyway, it intersects I-110, and CA-101, maybe the autopilot saw one of these and thought it was a speed sign.

 

[mikeash]

Sorry to break the news, but there's no such thing as perfectly flawless software, particularly in something as complex as a car. Not even a Tesla. But what's the success rate? Nine times out of ten? Not bad.

More like 9/110!

 

[mark]

Jerry - that explains why the silicon valley guys get confused driving on interstate 5 and the 101.

 

[RedSoxFan18]

Are there any metric signs in SoCal? I've seen them on rare occasion near the canadian or mexican borders. 110 KPH is eerily close to the 405 Speed limit in MPH.

 

[garygid]

272 mph in hex (base 16)?
only 72 in octal (base 8)?

All of freeway 405 is normally posted 65 mph, unless there is a 55 mph construction zone. This freeway is mostly 8 lanes, but sometimes 10 or 12, and occasionally only 6 lanes, I think.

 

[ggr]

Are there any metric signs in SoCal? I've seen them on rare occasion near the canadian or mexican borders. 110 KPH is eerily close to the 405 Speed limit in MPH.

Arizona and New Mexico do, but I've never seen one in CA, not even places like Calexico where there's a border crossing essentially down town. Certainly there are none on the 405 (which I drive quite often).

 

[JeffS]

I didn't at first... but once you mentioned there was something, I took another look. Now it I get it

There are 10 types of people in this world... those that understand

Spoiler: _____

binary

and those that don't.

Well done. Some would say that if you missed it the first time...you binarily got it the second time...

 

[ThosEM]

km/hr?

 

[aesculus]

Speed limit was 6 mph, you're 22 mph over.

Bithead

 

[Ulmo]

I-405 is the main freeway to/past Los Angeles airport, definitely not a "spur", but I guess you could call it a bypass. Anyway, it intersects I-110, and CA-101, maybe the autopilot saw one of these and thought it was a speed sign.

Since machines aren't dislexic, I'd consider the I-110 sign the likely culprit.

As someone who has considered machine interpretation of the world around them, I would find this highly unlikely, since for my machine to determine that it is reading a speed limit sign, it would have to discern:

A. The words "SPEED LIMIT" on the sign (or, alternatively, "MAXIMUM SPEED")
B. No other conjunctive words except for (C)
C. A speed limit (in numbers, for instance)
D. The proper square with rounded corners black border line
E. All the legal language and numerals contained within the contiguous border line.
F. The physical characteristics of the sign to indicate that it is physically about the same shape and slightly larger than the border line
G. The correct color coding, i.e., black text and border on white background.
H. The correct size, height and width proportion, font, font size, positioning, for regular posting signs.
I. Correlatively probability of which road it is pointed to to make certain it is regarding this roadway.
J. Cross analyze with data from similar sources as TomTom uses and other mapping companies use that they get from various databases that has this data, used mostly in a probabilistic way to denoise the data (along with (K)).
K. Cross analyze the other drivers' interpretation of the speed limit sign to help decide differences between (J) and what the machine read physically.
L. Take a snapshot of every ambiguous reading (where that ambiguity was introduced for any strongly valid reason), upload it to Mothership (Tesla), and have a human look at it physically. They could reference Google data, camera angles from many shots, etc..

While I would love a 110MPH speed limit, having the car suddenly decide you ought to be going 110MPH in a 70MPH zone or 25MPH in a 70MPH zone is very, very dangerous, and with the above laundry list of machine interpretation that I would deign to program in, I would find very unlikely to happen, yet we're getting reports of this happening from Tesla drivers.

This tells me the machine interpretation programmers aren't really putting a lot of top-notch effort into their work.

 

[Muzzman1]

Since machines aren't dislexic, I'd consider the I-110 sign the likely culprit.

As someone who has considered machine interpretation of the world around them, I would find this highly unlikely, since for my machine to determine that it is reading a speed limit sign, it would have to discern:

A. The words "SPEED LIMIT" on the sign (or, alternatively, "MAXIMUM SPEED")
B. No other conjunctive words except for (C)
C. A speed limit (in numbers, for instance)
D. The proper square with rounded corners black border line
E. All the legal language and numerals contained within the contiguous border line.
F. The physical characteristics of the sign to indicate that it is physically about the same shape and slightly larger than the border line
G. The correct color coding, i.e., black text and border on white background.
H. The correct size, height and width proportion, font, font size, positioning, for regular posting signs.
I. Correlatively probability of which road it is pointed to to make certain it is regarding this roadway.
J. Cross analyze with data from similar sources as TomTom uses and other mapping companies use that they get from various databases that has this data, used mostly in a probabilistic way to denoise the data (along with (K)).
K. Cross analyze the other drivers' interpretation of the speed limit sign to help decide differences between (J) and what the machine read physically.
L. Take a snapshot of every ambiguous reading (where that ambiguity was introduced for any strongly valid reason), upload it to Mothership (Tesla), and have a human look at it physically. They could reference Google data, camera angles from many shots, etc..

While I would love a 110MPH speed limit, having the car suddenly decide you ought to be going 110MPH in a 70MPH zone or 25MPH in a 70MPH zone is very, very dangerous, and with the above laundry list of machine interpretation that I would deign to program in, I would find very unlikely to happen, yet we're getting reports of this happening from Tesla drivers.

This tells me the machine interpretation programmers aren't really putting a lot of top-notch effort into their work.

The 110MPH appeared going north for the 101 near roscoe.
So well north of the 110fwy