Our background: we have lot of (more than ten years ) experience of the following fields: .NET1.0, 1,1. 2, 3.5 and 4 on Win platform + real time electronic stuffs.
(e.g. focused on industrial high performance inkjet printing, non contact spectral colour measurements, general industrial automatisation: e.g. non contact temperature measurements, PID temperature control, motion control, micro fluid handling, etc. -I’m sure you can imagine: beside the electronic related tasks we have a lot a mechanical design and manufacturing, assembly, test and calibration work).
Normally we do the following (from the point of view of development, not related with NETMicro!): .NET WinXP/7 for GUI, bussiness logic, etc and we use Xilinx FPGA + lot of in-house developed hardware for real-time related tasks.
So, we just received FEZ Hydra and we love it basically (e.g. we managed to work it successfully for NON-Gadgeteer SPI based TFTs, other in-house tried and tested components like our FPGA based systems , 3rd party SPI and I2C based parallel FIFOs, etc.
Back to you question:
1., When we receive a new ‘platform’ or component the first step normally we do to test it carefully before we start the actual development (I mean with a real living project with a certain component or platform included). So, normally we would like to know what we have to hande with our real-time electronic parts and what we can expect from e.g. FEZ Hydra.
2., Actually: the planned first project with FEZ Hydra: to build a standalone measurement device with image sensor and flashing illuminant. (we have to syncronize the image sensor capture with our flash light at very low level).
This is the reason why we would like to get some more real (or tipical) numbers / details concerning the I/Os performance.
Another say: we are ready to design the real needed custom parts for a certain tasks (e.g. electronic handling of image sensor, flash, buffering memory for frames, etc.) but we have to know the Hydra part of it: as at the end-of-the-story we have to push datas for Hydra (for example to show it a display controlled by Hydra or sent it over usb or our WiFi modul).
If you have more pratical performace data (we love to read white papers) regarding FEZ Hydra, it’s should be a nice help for us.
3., Another say: from our development point of view: we can do everything (independently from Hydra), BUT: we would like to do as much as possible with Hydra because of rapid and easy development enviroment of Hydra/.NET Microframework.
All it’s about the time (and money) from our point of view.
If you want I can share some more of our next project details.
Thanks in advance,