When it comes to experimenting and prototyping I think it is. The lower the learning curve the more cross polinations take place, projects and ideas get shared.
Clearly RPI is not optimal for clinical machinery that is supposed to run unattended by engineers in the real world but for prototyping why not?
Because there isn't a lot in the way of "prototyping" necessary. We already know how to effectively monitor patients. A lot of the shitty parts are actually in software and licensing and process - not hardware.
If you "prototype" for raspi, you will have to completely start from scratch if you want to manufacture reliable devices later on. It's not like porting a program from one system to another.
Comments
When it comes to experimenting and prototyping I think it is. The lower the learning curve the more cross polinations take place, projects and ideas get shared.
Clearly RPI is not optimal for clinical machinery that is supposed to run unattended by engineers in the real world but for prototyping why not?
Because there isn't a lot in the way of "prototyping" necessary. We already know how to effectively monitor patients. A lot of the shitty parts are actually in software and licensing and process - not hardware.
If you "prototype" for raspi, you will have to completely start from scratch if you want to manufacture reliable devices later on. It's not like porting a program from one system to another.