My first Prop board
Conehead
Posts: 12
Hello all,
I have just finished verifying a Propeller based board that I designed to control 3 load frames.
It has:
1. 3 24 bit A/Ds, each with 4 differential or 8 single ended channels or a mix of diff/single-ended.· I used the ADS1256 from TI.· Good chip, but a bear to get the timing right.
2.·9 FET driven outputs from the Prop·to control 3 stepper motors.
3. 1 FTDI232R for connecting to the PC.
4. A PIC18F2221 connected to 15 inputs and 3 FET driven outputs for GPIO.
5. A whole bunch of ESD circuitry.
Each A/D and the PIC have their own SPI bus running to their own dedicated cog in the Prop.· Each motor is being run by their own cog as well, leaving me with one more to communicate with the PC.· However, I designed the board so that communications to the PC can run to either the PIC or the Prop (I am much better at writing PICBASIC PRO than SPIN or Assembler).· The PIC was originally added because I ran out of IO on the Prop.· I could have used a single SPI bus for the A/Ds which would have freed up enough IO, but I wanted them to run in parallel because of possibly long sample times.
I have created an assembler object (my first one...not just for the Prop) to run the A/Ds.· Once I have that polished, I will post it in the object exchange along with the portion of the schematic from the A/D to the Prop.
Still have a lot of programming to do for the steppers and the PIC/Prop comms, which I won't post because it is very application specific.
I have just finished verifying a Propeller based board that I designed to control 3 load frames.
It has:
1. 3 24 bit A/Ds, each with 4 differential or 8 single ended channels or a mix of diff/single-ended.· I used the ADS1256 from TI.· Good chip, but a bear to get the timing right.
2.·9 FET driven outputs from the Prop·to control 3 stepper motors.
3. 1 FTDI232R for connecting to the PC.
4. A PIC18F2221 connected to 15 inputs and 3 FET driven outputs for GPIO.
5. A whole bunch of ESD circuitry.
Each A/D and the PIC have their own SPI bus running to their own dedicated cog in the Prop.· Each motor is being run by their own cog as well, leaving me with one more to communicate with the PC.· However, I designed the board so that communications to the PC can run to either the PIC or the Prop (I am much better at writing PICBASIC PRO than SPIN or Assembler).· The PIC was originally added because I ran out of IO on the Prop.· I could have used a single SPI bus for the A/Ds which would have freed up enough IO, but I wanted them to run in parallel because of possibly long sample times.
I have created an assembler object (my first one...not just for the Prop) to run the A/Ds.· Once I have that polished, I will post it in the object exchange along with the portion of the schematic from the A/D to the Prop.
Still have a lot of programming to do for the steppers and the PIC/Prop comms, which I won't post because it is very application specific.
422K
Comments
That's a busy board.
I am curious, what FETs did you use, what are the loads, and how did you connect them to the propeller. I am just learning about FETs and their capabilities, so am lookin for good examples of how to interface them to the propeller.
Thanks,
Doug
Leon
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Amateur radio callsign: G1HSM
Suzuki SV1000S motorcycle
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Prop Tools under Development or Completed (Index)
· Emulators (Micros eg Altair, and Terminals eg VT100) - index
· Search the Propeller forums (via Google)
My cruising website is: ·www.bluemagic.biz
Leon, what is the advantages of using a driver like you mentioned over connecting the MOSFET to the I/O?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Timothy D. Swieter, E.I.
www.brilldea.com - Prop Blade, LED Painter, RGB LEDs, uOLED-IOC, eProto for SunSPOT, BitScope
www.tdswieter.com
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Timothy D. Swieter, E.I.
www.brilldea.com - Prop Blade, LED Painter, RGB LEDs, uOLED-IOC, eProto for SunSPOT, BitScope
www.tdswieter.com