Find content
Not Telling
Attached Files
-
__ReadMeFirst.txt 4.14KB
30 downloads
-
GeneralLibrary.zip 178.23KB
11 downloads
- Paul Newton likes this
#29279 General Utilities
Posted by
on 16 May 2012 - 05:43 PM
Hi to everybody.
You know I'm a software guy, so, after having been helped so many times here, I try to give something back, even if I know I don't have the electronics expertize to be sure that I'm going in the right direction.
So I invite you to read the readme, and, if you want, take a look at the code: I would like to receive some feedback by the experts, to understand if I'm going on the right direction, or if I'm missing something important, like performance, memory size, and I don't know what else...
Andrea
#27812 Many many PWMs
Posted by
on 21 April 2012 - 12:26 PM
PWM IC:
http://www.sparkfun.com/products/10136
On a breakout board:
http://www.sparkfun.com/products/10615
...ehm... I don't know how to tell it in English, but right now I have a big big red face... :-(
Andrea
- devnightmare likes this
#27805 Many many PWMs
Posted by
on 21 April 2012 - 11:09 AM
Since my other thread is getting long (Train models), I start here a new thread for a subproblem: how to drive, for example, 20 PWM signals from a single Netduino.
Yes, the first straight answer could be to buy more Netduinos, but it's not only a cost problem: then I'd have to sync all together, that would be another big problem!
What I'm thinking about, is there some solution where I first select an 'address' (to be considered in a wider sense...), and then I set a duty cycle? The 'subcircuit' (or something like that) should retain that value, be self-powered, and going on supplying the exact pulse until maybe I re-select the same 'address', and put out a new value.
The first idea coming to my mind is to use many shift register chained in SPI, where, using the output pins of each shift register, put out a 'value' to feed to something else to be used as a PWM source (and obviously I don't know how to create such a thing...).
I googled everywhere, but I couldn't find any good start, so I'm really at zero! :-(
Is there anyone pointing me to a good direction?
Thanks in advance
Andrea
Yes, the first straight answer could be to buy more Netduinos, but it's not only a cost problem: then I'd have to sync all together, that would be another big problem!
What I'm thinking about, is there some solution where I first select an 'address' (to be considered in a wider sense...), and then I set a duty cycle? The 'subcircuit' (or something like that) should retain that value, be self-powered, and going on supplying the exact pulse until maybe I re-select the same 'address', and put out a new value.
The first idea coming to my mind is to use many shift register chained in SPI, where, using the output pins of each shift register, put out a 'value' to feed to something else to be used as a PWM source (and obviously I don't know how to create such a thing...).
I googled everywhere, but I couldn't find any good start, so I'm really at zero! :-(
Is there anyone pointing me to a good direction?
Thanks in advance
Andrea
- Arron Chapman likes this
