Close

CommuteGuardian UI/UX and Rider Early-Warning

A project log for Luxonis DepthAI

Spatial AI Meets Embedded Systems

brandonBrandon 02/10/2019 at 23:080 Comments

Hi everyone,

Quick background: AiPi is us sharing a useful product we're developing on our path to make the commuteguardian.com product.  Here's some background on that product:

Wanted to share the idea of how the rider is warned, before the horn goes off. The background here is the horn should never have to go off. Only the MOST distracted drivers won’t notice the ultra-bright strobes, which activate well before the horn will activate.

However, the horn WILL go off should the driver not respond to the strobes. It will activate early-enough such that the driver still has enough time/distance to respond and not hit you.

To warn the rider, there are two separate systems. The first one is an optional user interface via smartphone, which we’ll discuss first as it paints the picture a little easier:


So this gives you the states. In normal operation, it is recording and gives you map operation.

When there’s a warning state, the ultra-bright strobes come on, and there’s an overlay to make you aware of the elevated danger.

An example of this is a vehicle on your trajectory at a high rate of speed, which is still far away.

And when that vehicle is closer, the strobes didn’t deter them from an impact trajectory, the horn will sound, and you’ll be visually warned.

So the -second- system of warning the rider doesn’t rely on this optional (although cool) app.

It’s simply an audible alert that the biker will hear (but the car likely won’t) that will sound in the WARNING state, to alert the biker of the danger, and hopefully bring them into a state of being able to avoid the DANGER state (moving over, changing course, etc.)

Thoughts? [Feel free to add comments!]

Best,

Brandon

Discussions