element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Members
    Members
    • Benefits of Membership
    • Achievement Levels
    • Members Area
    • Personal Blogs
    • Feedback and Support
    • What's New on element14
  • Learn
    Learn
    • Learning Center
    • eBooks
    • STEM Academy
    • Webinars, Training and Events
    • More
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • More
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • More
  • Products
    Products
    • Arduino
    • Dev Tools
    • Manufacturers
    • Raspberry Pi
    • RoadTests & Reviews
    • Avnet Boards Community
    • More
  • Store
    Store
    • Visit Your Store
    • Choose Another Store
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
Sudden Impact Wearables Design Challenge
  • Challenges & Projects
  • Design Challenges
  • Sudden Impact Wearables Design Challenge
  • More
  • Cancel
Sudden Impact Wearables Design Challenge
Blog Sudden Impact Wearables Design Challenge Musings
  • Blog
  • Forum
  • Documents
  • Events
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Blog Post Actions
  • Subscribe by email
  • More
  • Cancel
  • Share
  • Subscribe by email
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: dougw
  • Date Created: 10 Aug 2015 4:53 AM Date Created
  • Views 137 views
  • Likes 1 like
  • Comments 2 comments
  • sudden_impact
  • Wearable
Related
Recommended

Sudden Impact Wearables Design Challenge Musings

dougw
dougw
10 Aug 2015

Sudden Impact Wearables Design Challenge

Crown Tools and Heart Reactor

The sudden impact wearables design challenge faded from view as the evaluation process took a couple of months. The winners were announced but not widely broadcast and the evaluation results haven't been published, so there isn't much way to recognize what was accomplished. Given that it was a grueling 6 months or work, spending every spare minute on the project, I thought I would summarize accomplishments from my perspective.

This is in no way intended to disparage the evaluation process – I am certain the judges made every effort to pick good evaluation criteria and to judge impartially.


The Challenge - summary

Create a solution that has the following features:

  1.   It should provide vital health information about player / competitor while they are out on the field of play.
  2.   It should be an unobtrusive addition to a usual uniform.
  3.   It should have the ability to communicate via wireless or Bluetooth to a phone app to inform coaches and other supervisory personnel about the health status of the players.
  4.   It should issue alerts when necessary.
  5.   It should be cheap and easily assembled

Assessment was originally to be on accuracy, convenience, cost and durability. After the project concluded these criteria morphed into ambition & sophistication, initial setup, installation, starting & operation, usability, validation of measurements, and cost.


Other requirements included weekly blogging, use of Analog Devices sensors and of course completion by the March deadline. The blogging requirements and deadline were changed a couple of months into the project, probably to encourage participation.


Accomplishments:

  1. Providing information while “on the field of play” is an order of magnitude harder than working in a lab. Typically a corporation development team will take a year to get a product working “in the field”. Products need to be built on custom PCBs rather than prototyping cards and enclosures need to be custom designed for the application and the environment. My devices were designed to be manufacturable with custom PCBs and enclosures. I believe my heart sensor and helmet sensor were the only devices in the competition to be demonstrated in real use cases “on the field of play” during the contest period, so definitely a major accomplishment.
    • Additionally the sensors generated useful data. The helmet sensor was used in 4 hockey games before it had to be shipped off for independent evaluation, but the data collected in those 4 games was very interesting. I don't think any other contestant device was used to generate useful data from use ”on the field” during the contest. This is even a bigger accomplishment than simply being used in a real sports environment.
    • Correlating head injury to helmet impact is a very difficult task – the more one learns about this topic, the more difficult it appears. My blog on the topic is a summary of years of research on head injuries by many people including me. My innovative method of addressing the issue has a lot of underlying science behind it and may be the key to making low-cost helmet-mounted injury sensors as opposed to helmet impact sensors. I feel it is a great accomplishment and one of the truly innovative results of the whole challenge.
  1. Unobtrusive instrumentation is important in many sports and this requires a significant mechanical design effort, and in the case of the helmet instrumentation, an ambitiously small form factor – I had to learn how to use a mechanical CAD system to achieve unobtrusive, ergonomic, aesthetic devices that still performed well. The ultimate test is will the athlete actually wear the device. This is why I was so ambitious with designing aesthetically attractive housings for both products. When using my device in real hockey games, I received interest from many of the players, even on the opposing teams. My helmet sensor could be mass-produced and mounted as-is on millions of hockey helmets and immediately provide useful information in every game, and would likely have pretty good acceptance by end users. This probably cannot be said of any other device in the contest. Again for me successful mechanical design was a major accomplishment.
    • Convenience was also a judging criterion. My use of wireless charging was a unique technique amongst competitors that greatly simplified helmet sensor maintenance, but took significant design effort to integrate in a small form factor – a cool accomplishment that greatly improved ease of use.
    • Durability was another assessment criterion and given the nature of contact sports it was an important aspect of mechanical design. My design was tested at relatively high g despite the danger of destroying the device before it could be evaluated by the independent judges. High shock loading is perhaps the most demanding of all product tests, so to have a prototype survive multiple impacts is quite an accomplishment.
  1. Wireless communications were a requirement, but they are common everywhere so the key for me was to make them low cost. Both the heart sensor and the helmet sensor could be used with any Bluetooth device, even without requiring the android app I developed – a pretty neat accomplishment.
    • Cost was an assessment criterion and I kept costs to a minimum – the sophisticated Analog Devices sensors were by far the most expensive components in both the heart sensor and the helmet sensor, but utilizing these sensors was a primary objective. It was essential to plan ahead and work to a tight schedule to keep costs down, as components and PCBs had to be ordered from overseas with associated long delivery times. This concerted effort made the helmet sensor cost competitive with any commercial helmet sensor – a pretty significant accomplishment.
  1. Alerts were another requirement – my helmet sensor illuminates 4 LEDs upon significant impact, in addition to immediately displaying the impact data on its built-in LCD. My heart sensor and helmet sensors were the only entries in the contest to include a full alpha-numeric display on the device, making external instrumentation optional. And they still managed to be small enough to be wearable and to be very low power. This stand-alone operation is an important feature in real use cases, where cell phones are too fragile and to expensive to be on the field or even on the player bench. So a subtle but important accomplishment.
  •   Feature for feature my helmet sensor could well be better than the best commercial hockey helmet sensor, including performance. This is definitely a monumental accomplishment for a one-person, shoe-string, multi-disciplinary development.
  1. Low cost is always important and it was a judging criterion. My designs are optimized for easy assembly using PCBs and optimized for low cost. Even with low volume and expensive sensors these devices are cost competitive with commercial high-volume products. This is a worthwhile accomplishment for me as I had to have several circuit boards made and purchased quite a few components with my own money.

 

Blogging

The original rules required a weekly blog. This is a difficult requirement, especially on long projects because it takes significant effort that could be spent on actual development. I had committed to a weekly blog when accepting the challenge and faithfully managed to produce at least one meaningful blog each week, despite the fact that the project deadline was extended, requiring even more blogs. I ended up with about 40 blogs – a pretty good accomplishment.

This requirement was dramatically relaxed after about 12 weeks, presumably because it would have disqualified everyone else from the competition. This rule change helped everyone else but actually hurt me, not only by allowing more qualified entries, but also I wasted time on generating blogs when I could have been developing more and better features.


Deadline

Another rule that was changed quite late in the project was that the deadline got significantly extended. Again this rule change hurt me and helped all other entrants as I was the only one on track to complete on time. I actually had all aspects fully functional by the original deadline – which was a very major accomplishment.


Discussion

I am proud of all the multi-disciplinary accomplishments I achieved in this project although of course I'm devastated they weren't scored higher. I aimed as high as I thought I could and still complete the project, but did not anticipate the deadline extension or morphing of assessment criteria. There was no opportunity to respond to the altered assessment criteria as this occurred after the final project submission.

I learned you can focus on and demonstrate great or possibly even superior performance in meeting all of the stated challenge requirements and still get trounced by projects that excel on other criteria that can be introduced after seeing the finished projects.

I am not trying to denounce the process – I appreciate that the judges are trying to do a good job and e14 is trying to make popular challenges – I am just trying to come to grips with how I failed to present a winning project and logically figure out what I might have done to score better. I put far more effort into this project than any school course I ever took, including learning a lot, creating a lot and accomplishing a lot, however the scores and final judging criteria have not been published yet, so it is not apparent if this effort received a passing grade and it is difficult to know how to improve in future projects.

Hats off to the winners, who did figure out how to make a winning project. You can find Cosmin's cool project here and Ravi's cool project here. My project is here.

Anonymous

Top Comments

  • DAB
    DAB over 6 years ago +1

    Hi Doug,

     

    You bring up several good points about these competitions.

    It would have been very useful to know the judging criteria before submission.

    It provided all of you with a lack of information about what…

  • dougw
    dougw over 6 years ago in reply to DAB +1

    Well, I spent 9 years researching helmet sensors and the main thing that has eluded all researchers is how to correlate inexpensive helmet sensor data to head injury. There are only a handful of instrumentation…

  • dougw
    dougw over 6 years ago in reply to DAB

    Well, I spent 9 years researching helmet sensors and the main thing that has eluded all researchers is how to correlate inexpensive helmet sensor data to head injury. There are only a handful of instrumentation engineers fortunate enough to have this level of experience. When this challenge appeared, I came up with an innovative idea that might make such sensors practical, and I really wanted to try it out. It was pretty ambitious and probably a little controversial, but if it works it could provide a very large number of helmet wearers with useful data that would actually reduce the incidence of cumulative head trauma. So to answer your question, I would most like to improve performance of my device and scientifically prove the concept works, but this would involve "re-spinning" the design and that would be too costly and too time consuming to be feasible within the project. Part of me regrets disclosing the idea, because it has so much potential, and I didn't really benefit much from the disclosure, but I hope in the end it benefits everyone else and helps people manage head trauma better.

    Of course, with hindsight it would be easy to come up with an impressive list of cool new features to add to the project that would ensure better scoring with the new assessment criteria, but that option is never going to be the case. We just have to gamble that we understand the requirements and assessment criteria well enough to produce a competitive entry. If we guess wrong about what the assessment criteria will be, we can waste an awful lot of effort on features that don't matter without even realizing we have an insurmountable handicap.

    • Cancel
    • Up +1 Down
    • Reply
    • More
    • Cancel
  • DAB
    DAB over 6 years ago

    Hi Doug,

     

    You bring up several good points about these competitions.

    It would have been very useful to know the judging criteria before submission.

    It provided all of you with a lack of information about what the contest would value most.

     

    One thing I would like to ask all of the competitors would be "what would you change today in your design?"

     

    You have all had the chance to look at your implementations, assess the judging criteria and your overall satisfaction of your work.

    Where would you make improvements today?

    DAB

    • Cancel
    • Up +1 Down
    • Reply
    • More
    • Cancel
Element14

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2022 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • Facebook
  • Twitter
  • linkedin
  • YouTube