Jump to content

dkedr

Members
  • Content Count

    84
  • Joined

  • Last visited

  • Days Won

    1

dkedr last won the day on August 3 2012

dkedr had the most liked content!

About dkedr

  • Rank
    Level 1

Profile Information

  • Gender
    Not Telling
  • Location
    Auckland, New Zealand
  1. Did any one else connect to the new launchpad while it was running the demo code? 115200 baud. Doesn't respond to hello, but does respond to help. Also has commands to set brightness and colour of the onboard RGB led and an option to enter the hibernation mode. If any one did look at the demo code are there any more tricks it knows?
  2. I got an estimated shipping date of 10/10 so I'd say the interest is larger than they previously though.
  3. O lawd look at them specs. 256K flash, 32K ram, 1MSPS 12 bit ADC. How the heck are lowly micro controllers meant to compete with that?
  4. dkedr

    MTK3339 GPS

    I wrote some code to modify which NMEA sentences the GPS module spits out and their frequency. If you disable some the logger will have less data to chew through and can spend more time sleeping. I should probably mention that it uses the button on P1.3 to select which one of the 8 available sentences comes out. I'm using hardware debounce so it might skip a few sentences if you don't debounce the pin. Modifying the code will allow you to select any combination. main.c
  5. What did you use to generate the random number?
  6. Basically many headers routing RF module pinouts to the launchpad. Like the nrf24 and, RM70, CC2500, BT modules, CC1100, nrf900. Most of them use the standard set of SPI pins, but most of them have different header pin configurations, and I think it'd be very helpful having one board you can plug into the LP and plug any of the RF modules straight into that. I think a board like this would be able to consolidate all the RF boosters into one. (and since there will be just one PCB the price should be lower?) I would try to make this, but I only have a Sparkfun NRF24 module and I probably won't be able to do much work on it for at least a couple month. List of RF modules: nrf24* boards with 2x4 header (0.1") nrf24* Sparkfun Board with 1x8 header (0.1") nrf24* boards with 1x8 header (0.05") (almost the same pinnout as the sparkfun module) RFM70 module 1x8 header (0.05") CC11* modules 1x6(data) & 1x2(power) (0.05") CC2500 modules 1x8 header (0.05") CC2500 modules 2x7 header (0.1") BT modules ?(I don't know the header requirements for these TI RF module connectors
  7. 1 Fram board + 1 RF2500 board for 20USD including international shipping sound ok?
  8. How about a v0.2? The only thing I didn't add is the CR2032 holder because I couldn't find one in my eagle libraries, but there is plenty of space to add one EDIT: added a header for the NC pins, just in case one of the forum members discovers that those pins do something cool. 43oh GPS booster.zip
  9. This is some amazing work, I'm keen to see how this turns out. About regulating the voltage with Si diodes, I had a USB hub that did that and it had some stability issues when things were connected and disconnected, I figured it was due to slow response times of these diodes. It might not be a problem for you, but I though I'd mention it anyway.
  10. I'll take the two FRAM boards if you still have them.
  11. Here is a click able link to the schematic from the first post. http://www.acmewebpages.com/leds/chmsl/uc_schematic.jpg Is there a particular reason you are using the PTN78000? The TLC5916 is actually rated up to 20V on the LED output pins, so you could use the 13.8V input to drive the LEDs directly. However depending on the current you might want to add some series resistors. The amount of regulators in your design is actually unnecessary. The first regulator is actually capable of producing the 3.3V for the MSP/TLC. Also, all your regulators are rated at 1A, which would mean a large chunk of their capacity is unused as you're just powering the logic inside the TLC5916 and the MSP430 is a very low power device so it doesn't draw much current. The way you have arranged those diodes is incorrect. The diodes are there to prevent negative voltages from destroying whatever electronics come after it, in your design however the diodes don't serve a purpose, and also don't allow the capacitors to do their job. If you look at the datasheets of the parts you used, you'll notice that there are no diodes in the example circuits, especially on the output. Diodes are normally used at the very start of the design, to protect the circuit from reverse polarity(the user reversing the + and - terminals). The diode should be connected with the arrow pointing into your circuit, so it should be in between the 13.8V and the input of your first regulator. The capacitors are there to smooth out any noise that might be superimposed(added) to the regulated signal. Noise comes from pretty much anything that has current flowing through it, so we filter it to prevent it getting into our circuits(you've done more of this with the .1uF caps next to the MSP and the TLC chips). Now the way you have the capacitors connected now, they will only charge up once, when you power on your circuit and will not discharge because the diodes are blocking the discharge path. To allow the capacitor to work you will need to take out the diodes and put a connection across the place where they used to be. It's also good practice to have capacitors close to the input of the regulators as well as the outputs. This makes the output they produce smoother(less noise). EDIT: Found a simple circuit with a well known regulator:
  12. I routed them motor connections, they didn't come out too pretty, so I think I might route everything else and then reroute them to take up all the space available. Also moved the fets/limit switche header around, added a fat cap for the fets and changed the reference voltage resistors so that every driver chip has it's own pair(reduced traces, can drive different sized steppers without changing current sense resistors) Suggestions are very welcome.
  13. I considered this, but if it was stand alone it'd need to have inputs from the user. And currently, there are only two unused pins. I'm thinking of using an add on board with an I2C driven LED numerical output, or something along those lines for DRO, but again, I have no extra input pins, so the commands would need to come in over the UART in g-code form. So you'd have to build your own g-code encoder. I'm planning a larger stepper driver board, 100mm by 50mm sized, with 4/5 stepper drivers and an on-board msp430(Fsomething) or one of them fancy ARMs, but I think I won't get to do any work on that this year due to an increased uni work load.
×
×
  • Create New...