Yes, the story on EE Times Europe says "To detect an approaching pedestrian, the driver needs to be warned or the emergency brake has to be triggered even before the pedestrian steps onto the roadway. At the same time, the likelihood of an unnecessary full braking must be kept extremely low to allow car drivers to find the system reliable enough to use it." A good test would be tagging deer with transponders and seeing if the system is fast enough to brake the car before a deer collides with it, without causing problems for the car and other cars around it. The only thing -- isn't it better defensive driving to just hit the deer than try to brake at the last second? (Not an option with pedestrians, but they hopefully aren't moving as fast as a deer might be.) The system is probably completely useless when the car goes beyond a certain speed.
The picture shown is an obvious jaywalking situation. The pedestrians are at fault. Of course, if we can increase safety by adding functionality to the vehicles, we can save these law breaking pedestrians. It's a good idea, but the pedestrians should pay for the upgrade instead of the driver.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.