The intend is for you to design the first actual prototype of the entire solution [HW, FW, App and Cloud]. Up until now, the HW has only existed as mock-ups and it is now up to you to bring the product maturity level to the next stage.
The purpose of the 1st prototype is for us to test some of the key elements and project risks at this point of time.
The key elements are prioritized based on difficulty and complexity.
1. Priority “we are uncertain if this can be done to a useful level”
• Garment/fabric design ensures that the sensors do not move around. Movement artifacts are a great issue with the EMG-sensors!
• Technology selection of the sensors can provide the necessary signal and data quality
2. Priority “This must be done right, to give value to the product”
• Test user interaction with HW-product
• Allow for us to make data studies and tests with partners
• Data gathering to allow for initial steps on creating a Load Index
• Test if placement of sensors is correct
3. Priority “This is a matter of resources”
• Allowing for us to develop sensor calibration routine
What to deliver – what is expected
2-3x prototypes are to be delivered. We expect the first prototype to consist of (deliverables and the finalization-level):
• Garment with EMG and IMUs attached in the correct locations. Intercircuit wiring is not expected at this stage to be sewn in or woven into the fabric. Even though, attachment of the sensors is vital for the product, at this stage they just have to be fixated. Proper ready-for-manufacturing fixation will be a requirement for the next stage. All electronics are expected to be custom-made to fit the design. Battery size and enclosure are to be made and selected with the end-product battery life in mind.
• App that reuses existing source code from the MLI® Elbow product to reduce the possible work load of creating and entirely new app. The app has been made in .Net/C# in Visual Studio. The adapted app is expected to enable data streaming from the hardware’s BLE connecting and to the cloud solution. It should also have built-in questionnaire for the Back-solution, as well as a calibration routine. Pairing of Back device must be enabled. Basic FW/SW (error)-logging must be enabled like battery level, EMG-signal quality, BLE-status. A “live” signal to see if data is properly being streamed would be nice. All other functionality, like GUI, making the app look beautiful, UX, MLI-index, Historical graphing, Settings, etc. is for a later stage.
• Enable data streaming to the Azure cloud in collaboration with PRECURE’s Data Manager
and figure out dataformat and structure.