I´m doing a personal project where I´ll need to control 4 high power 20A motors (maybe 6 one day).
The Gadgeteer motor controllers are for lower powered motors in the 3A mark, so I thought that´s OK I´ll use PWM signals on the mainboard to control ESCs (electronic speed controler) to then control the motors.
Oh dear, there are only 3x PWM on my mainboard.
That´s OK Easy, I´ll buy the GHI Pulse InOut module giving 8x PMW Outputs (and Inputs)
Then, I met a fantastic girl, got a house and now a baby!
So I come back to my project a while later, and oh no … the Pulse InOut module is discontinued
I´ve looked around the net and not been about to find another PWM signal generating Gadeteer module.
I´ve got two mainboards one from LoveElectronics (3x P socket) and the FEZ Hydra (1x P socket).
I´ve answered my own question … just noticed the GHI Hub AP5 module is perfect for me with 5x P sockets!!! Wonderful, I´ll buy it now
Sorry for taking your time!
Hope you have a good new year!!!
On a side note, I´ve noticed on the GHI website a mistake on the FEZ Rapter. On the specs it say PWM = 4, however later on down the page there´s only a single P socket giving PWM. I can only see one P socket on the images Might be worth the website folks correcting.
Cheers Ian, good to know the gadgeteer system is capable (with care) of real time applications!
With all the sensors the project needs I’ll reckon even the most generous mainboard will run run out of “I” sockets so I’ll have to hack my own I2C module to talk to the multiple sensors. Wish there were more sensors out there that could be daisy chained!
The thing running around my mind is that it might be best to get a G400 board. All the PWMs I need, many gpio plus easy to access to direct I2C to solder and not hack own daisychain code.
The real monkey is the many of the I2C components have fixed addresses In my deluxe design there’ll be many sensors and I was hoping to access them all of them on I2C, of course difficult if the manufacturers hard code the same address on sensors of the same type!
I think it’ll end up easier using the sensor’s chip select (extra microcontroller or use G400 gpio) and using SPI comms.
My gut feeling is that although the end/best solution is a G400, best to prototype on a Gadgeteet mainboard/sockets as much as possible before getting one
The direction I have decided to go with my quad is to use an off the shelf $20 Naze32 based micro for basic flight functions and then use NETMF for the more interesting stuff. Unfortunately, my Naze32 is still in the box and I haven’t had time to play with the quad in quite a while but I feel like steering & balancing are CPU intensive enough that it deserves its own micro and using something that’s proven like the Naze32 takes a lot of the work that others have already done off my plate and lets me focus on interesting stuff like automatically locating a specific license plate in a parking lot, etc.
Depending on how many sensors and what you’re doing, it might make sense for you to roll your own DaisyLink module. I’d probably go with SPI with the GPIO CS, though.