To do that, the feedback needs to be immediate. Looking at data two weeks later in the doctors office won't be useful at all, I would think.
Yeah, totally agree with you. We found that people tend to stop doing their exercises because they're just not sure what they're doing is right. Also if you do it wrong you may do more damage than good. But we need the historical aspect of it too as sometimes the recovery process is so gradual, you may feel that the exercise is having no effect and so you stop. Also, keeping a log will enable the therapist to check that the patient is doing what they've been prescribed.
What kind of sensors? How many?
Been experimenting with flex sensors and an accelerometer. I don't think we will use the latter, and instead have three bend sensors in different orientations working at the same time. The values coming out of them relative to each other should indicate what's going on. Strong emphasis on the should, we need to test that out.
The more interesting part of the project is the 3D animation on the PC, I think. What language/software are you planning to use? I like C# and OpenGL myself for something like this.
This is the interesting part for me too for sure! To be honest, we're not sure what form the feedback will take. It might be clear-cut, drill-sergeant spoken instructions, or something more abstract (matching colours, or audio tones for example). The only program I am slightly familiar with is Processing.
At 115200 baud, you can send 11,520 bytes per second, or 5,760 ints. That's either a lot of sensors or a lot of idle time. Maybe not exactly idle, since some time is involved in reading the sensors, but there will be a fair amount of excess capacity.
Thanks, I will take this into consideration for sure.