Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Tesla Software updates - Australia

This site may earn commission on affiliate links.
Apparently the problem with the LED signs is that they are effectively pulsing and that combined with the camera frame rate means that they cannot be read. I may be wrong but I've seen suggestions that this will not work with the older cameras and will need new cameras. As an IT guy, I would be hopeful that software technology can overcome the issue and make it work. These types of signs must surely be used in the USA so I'd be curious to know what happens there. FSD could surely not succeed if LED signs could not be read.................
 
  • Like
Reactions: Sir Surfalot
Apparently the problem with the LED signs is that they are effectively pulsing and that combined with the camera frame rate means that they cannot be read.

At least we are the same as Europe (50Hz) and not some unique frequency whereas FSD is currently in North America (60Hz). Differences like this will likely impact what the cameras can detect and make the FSD rollout to the rest of the world harder.
Of course, they currently have the cameras able to detect our 50 Hz LED traffic lights (Traffic Light and Stop Sign Control), so it shouldn't be insurmountable.
 
Of course, they currently have the cameras able to detect our 50 Hz LED traffic lights (Traffic Light and Stop Sign Control), so it shouldn't be insurmountable.
However, there is a lot of difference between a traffic light and a speed sign. Red/Orange/Green blocks of LEDs in defined spots is a lot easier than a speed sign. But that aside, I am not sure I understand why LED speed signs would be pulsating at all; unless they PWM (Pulse Width Modulate) them in order to control the brightness depending upon the weather. But I really don't know anything about the LED speed signs other than I've been told that they pulse and that is the problem depending upon when they are caught in a frame.

From an article about the new cameras in "Not a Tesla App":

"More importantly, the new sensor will also support LED flicker mitigation. Camera sensors often have a hard time capturing the light emitted from LED lights in a constant fashion. Since LEDs are widely used in electronic signs and traffic lights this will be an important feature and should make it easier for Tesla to interpret such signs.

The following article (from 2020) is of interest and implies this issue affects multiple systems:

 
Last edited:
I thought it was reading the electronic signs on Rosanna Rd.. Now I think it goes back to 60 when I cross the intersection from GPS then back to 40 when it sees the sign 40km 7am-7pm :(
Annoying as speed camera there which get you at 60km after 7pm at it beeps at 40km a few times then stops.

Also was on autopilot along the Western Ring road it dropped to 70km I took over.. Wondered how.. Then did it again..
Reading the signs on the off ramp :(
 
Given the processing power in our Teslas I'd think it should be pretty simple with the existing cameras, compared to all the other analysis going on in an FSD stack.

1. Identify a pulsating speed sign
2. Drop frames with lower brightness
3. Normal video to data analysis
 
on 12.5 my car did not read any of the LED signs, I noticed the LED signs that have the regular sign under and text that if blank then speed limit is this, the car actually reads that regular sign regardless of what the LED says, though often they were the same thing, so it looked like it was reading the right sign, however any LED sign without the regular sign next to it was not recognized on screen at all.
That would concur with my experience, thanks.
Occasionally, I see other LED signs through onw of the cars cameras, and they strobe badly, and I think that is the root of the problem in reading LED speed signs - the camera's frame rates are insufficient to resolve the content clearly.
 
  • Like
Reactions: Sir Surfalot
That would concur with my experience, thanks.
Occasionally, I see other LED signs through onw of the cars cameras, and they strobe badly, and I think that is the root of the problem in reading LED speed signs - the camera's frame rates are insufficient to resolve the content clearly.
yes & no - the sign probably runs in separate segments - turning each section on for short periods - so you would need to composite several frames together to read it.
 
  • Like
Reactions: NeilA
......, I am not sure I understand why LED speed signs would be pulsating at all; unless they PWM (Pulse Width Modulate) them in order to control the brightness depending upon the weather. But I really don't know anything about the LED speed signs other than I've been told that they pulse and that is the problem depending upon when they are caught in a frame.

Each LED in the array for a sign is pulsed or refreshed for a number of reasons. It reduces duty cycle / power consumption of the LEDS which is important when many of these speed signs are solar powered. It also increases the life of the LEDS because they are not switched hard on all of the time etc.
 
Apparently the problem with the LED signs is that they are effectively pulsing and that combined with the camera frame rate means that they cannot be read. I may be wrong but I've seen suggestions that this will not work with the older cameras and will need new cameras. As an IT guy, I would be hopeful that software technology can overcome the issue and make it work. These types of signs must surely be used in the USA so I'd be curious to know what happens there. FSD could surely not succeed if LED signs could not be read.................
When I was at TMC in 2015, I spoke to a Tesla Software developer who said they were working on the LED sign problem.
I would have thought they would have fixed it by now.
 
I suspect it might be too hard with 1.2Mpixel cameras, speed sign often being a small percentage of the frame size, individual LEDs combined with pixellation, limited frame rate, shutter speeds, LED PWM rates up to 200Hz et al. If that proves to be the case, then it might develop into an "interesting" situation for all of us with the "old" cameras.

The link I provided above has another link (below) to a paper discussing the whole situation from the perspective of the various jurisdictions responsible for signage. In Australia (of course..) there are no standards. There are also multiple (at least 12) providers of signs and they are all different with different character shapes, LED shapes, variations in colour and brightness and different frames around them. The list seems endless. However it is good to see that Oz and NZ are doing some work to try and improve signs so as to be more consistent and readable by ADAS systems. As to when our cars (and those of other manufacturers) here in Australia can reliably read all electronic signs- I predict it will be a LONG time yet.

 
At least we are the same as Europe (50Hz) and not some unique frequency whereas FSD is currently in North America (60Hz). Differences like this will likely impact what the cameras can detect and make the FSD rollout to the rest of the world harder.
Of course, they currently have the cameras able to detect our 50 Hz LED traffic lights (Traffic Light and Stop Sign Control), so it shouldn't be insurmountable.

There is no connection between the frequency of the AC voltage supply in a country and the pulsation rate of LED lights.

LEDs operate off DC power, not AC, and they rate they pulse at is totally up to the designer. Typically rates between about 300 Hz and 1 kHz are used. They use PWM on LEDs to control the brightness and also to reduce power consumption.
 
  • Like
Reactions: johnchidgey
There is no connection between the frequency of the AC voltage supply in a country and the pulsation rate of LED lights.

LEDs operate off DC power, not AC, and they rate they pulse at is totally up to the designer. Typically rates between about 300 Hz and 1 kHz are used. They use PWM on LEDs to control the brightness and also to reduce power consumption.
Totally correct and as the studies have shown, there is a further complexity in that the sign designers can and do also multiplex between sections of the sign, often at a fast rate. So that if you were to video them at an extremely (and impractical) frame rate, you might (also depending upon the shutter speed) see only a few LEDs on in a particular section of any particular frame. Most if not all of these electronic signs were designed for human eyes rather than electronic reading. I think it is a major problem and not at all easily solved.

I've just been reading an article by a Motoring Editor about Kia and Hyundai cars misreading signs and incessantly bleeping the driver if 1 km/hr (non configurable) over the incorrectly detected speed limit. Always on by default and takes several menu levels to turn off. I experienced exactly the same 18 months ago when I had a top of the line Kia ICE car as a loaner for a couple of months. This plus the wandering in the lane drove me nuts (the lane-keeping could not be turned off permanently. It turned on again automatically every time you started the car. )

The article I quoted suggested that some manufacturers take three successive frames and merge them in an attempt to "anti LED flicker" and detect the speed sign. However, I can see how one could still easily "luck out" and only detect some of the LEDs. Perhaps it is not surprising that Tesla has not solved the issue after 8yrs (according to raynewman), particularly given the cameras they are trying to use.

On a more positive note, as of the latest firmware release, my car SEEMS to have stopped detecting the 40 signs on the back of Sydney buses!