Custom fitting commercial needs using Gadgeteer is rather simple as engineering is only needed on part of the design, the module. The rest are all off-the-shelf pre-qualified designs.
Steven Johnston talks about his experience in making a custom high-power RF link.
[quote]Most .NET Gadgeteer users are familiar with plugging additional modules into their creation and then calling the methods supplied by the installed driver. Whilst this is probably as far as many people go it is worth keeping in mind that most drivers are open source (.NET Gadgeteer Codeplex http://gadgeteer.codeplex.com/) and so if a feature is not implemented you can change the driver and implement it yourself. The drivers are implemented in C# and you can just add the project to your solution and edit/debug to your heats content.
Even better… if there is not a .NET Gadgeteer module for the task you have in mind, dont panic. It is very easy to create drivers for new hardware especially if they have standard interfaces such as I2C, serial, PWM etc. Just to let you know upfront, you only need to code the parts that make you module work, all the other goodness such as an installer, toolkit addition and version support are all taken care of in the templates.
I thought I would write up an example in the hope it may help others. I have a need for a long range transmitter and currently Gadgeteer does not have such a module. So the next stage was to build one, we have a few prototypes and transmission timing can be an issue…[/quote]
Read more: http://stevenjohnston.co.uk/2012/10/12/building-a-net-gadgeteer-module-driver/
Learn about Gadgeteer: http://www.ghielectronics.com/products/dotnet-gadgeteer