Group Actions
Engagement
  • Author Author: dwinhold
  • Date Created: Date Created
  • Views 393 views
  • Likes 4 likes
  • Comments 5 comments
Related
Recommended

IOT on Wheels Design Challenge - Fatigue Alert System Blog #2

dwinhold

Hello everyone,

 

This weeks update is a flow chart on how the computer will work with the sensors and how I plan the programming. I am also going to blog about the software I plan to use to program the Nucleo.

 

First the flow chart:

 

image

 

I hope this is fairly easy to follow (it makes sense to me anyway image) The Nucleo is at the heart of my design and everything branches off from there. I will have the WiFi module and the sensor board attached. I will be making a sensor for the steering wheel to make sure your hands are on the wheel. There is also going to be a heart rate monitor a vibration sensor and a confirmation light and button. With this all put together and the programming done right it will sense how tired you are and let you know when to stop driving.

 

As for  programming the Nucleo I will first use Mbed OS 5 https://os.mbed.com/  This looks to be what I need to use and I will also review the ease of this.

 

A quick note on the Nucleo-64 and the expansion boards. They came nicely packaged and with a card of info on each one. The Nucleo-64 and expansion boards are very impressive and will more then do the job I am set out to do. The only thing missing is a USB type A to mini B cable. Luckily I have a lot laying around but it could have been awkward if I didn't.

 

That is it for this blog, next one will be on the programming and making of some sensors.

 

Thank you

Dale W

Parents

  • Dale

    I'm curious about the 3 second timer used in your flowcharts.

    On the right side you've already detected excess vibrations which may indicate the vehicle has strayed off to the right.

    By my calculation at 100kmph the vehicle will travel 27.77m/sec and therefore after 3 secs has quite likely travelled 83m.

     

    IMO doing something much more drastic at 1 or 1.5 second after the wrist vibrations might be more useful.

     

    Mark

  • in reply to mcb1

    Hi Mark

     

    Very good point . My original thought is that you have 3 seconds to press the acknowledge button (reaction time) before more drastic measures. You are absolutely correct in that 3 seconds is way to much time, I will definitely change this. If you aren't dozing off when this alert happens, the computer will still calculate your reaction time. I also plan that if the vibration doesn't stop and you keep pressing the acknowledge button the computer will ignore the vibration until it stops (eg. You may be on a dirt road), then it will start to monitor again.

     

    Thank you for the comment and help!!

     

    Dale

Comment
  • in reply to mcb1

    Hi Mark

     

    Very good point . My original thought is that you have 3 seconds to press the acknowledge button (reaction time) before more drastic measures. You are absolutely correct in that 3 seconds is way to much time, I will definitely change this. If you aren't dozing off when this alert happens, the computer will still calculate your reaction time. I also plan that if the vibration doesn't stop and you keep pressing the acknowledge button the computer will ignore the vibration until it stops (eg. You may be on a dirt road), then it will start to monitor again.

     

    Thank you for the comment and help!!

     

    Dale

Children
No Data