Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by username

  1. Delay based fading works.... however, i'd recommend interrupt based. That way you can run your main function independently of the LED fading. Never used Energia before but here is some code for regular msp430g2553 #include "msp430g2553.h" const int led_dutys[]; void main(void) { WDTCTL = WDTPW + WDTHOLD; // disable WDT BCSCTL1 = CALBC1_1MHZ; // Set DCO to 1MHz DCOCTL = CALDCO_1MHZ; WDTCTL = WDTPW + WDTHOLD; // Stop WDT P1DIR |= BIT6; //BIT6 output P1SEL |= BIT6; //TA0.1 CCR Output CCR0 = 1000; // PWM Period CCTL1 = OUTMOD_7; // CCR1 reset/set CCR1 = 10; // CCR1 PWM duty cycle TACTL = TASSEL_2 + MC_1; // SMCLK, up mode TA1CCTL0 = CCIE; // CCR0 interrupt enabled TA1 TA1CCR0 = 25000; // TA1 period TA1CTL = TASSEL_2 + MC_1; // SMCLK, upmode, _BIS_SR(LPM0_bits + GIE); // Enter LPM0 w/ interrupt } #pragma vector=TIMER1_A0_VECTOR __interrupt void TIMER1_A0_ISR(void) { static int i = 1; CCR1 = led_dutys[i]; //change TA0.1 duty cycle i++; i = i % 99; //count to 32, then reset } const int led_dutys[] = { 1 , 2 , 5 , 8 , 13 , 18 , 25 , 32 , 40 , 49 , 60 , 71 , 83 , 96 , 109 , 124 , 140 , 156 , 173 , 191 , 210 , 230 , 250 , 272 , 293 , 316 , 339 , 363 , 388 , 413 , 438 , 465 , 491 , 519 , 547 , 575 , 603 , 632 , 662 , 691 , 722 , 752 , 782 , 813 , 844 , 875 , 906 , 938 , 969 , 1000, 1000, 969 , 938 , 906 , 875 , 844 , 813 , 782 , 752 , 722 , 691 , 662 , 632 , 603 , 575 , 547 , 519 , 491 , 465 , 438 , 413 , 388 , 363 , 339 , 316 , 293 , 272 , 250 , 230 , 210 , 191 , 173 , 156 , 140 , 124 , 109 , 96 , 83 , 71 , 60 , 49 , 40 , 32 , 25 , 18 , 13 , 8 , 5 , 2 , 1 , };
  2. Howdy all, Got out of college recently so I got a tad bit more time. Figured I finish off my reflow project properly since i've been getting alot of requests for kits. I'm in the process of developing a through-hole based reflow oven kit that would be easy for any hobbyist to assemble. Source Code: https://github.com/NateZimmer/Reflow_Oven_Kit Schematic: Printing Print Schematic.pdf Deluxe Kit includes and features: - 1x 2.2" Touch LCD Display - Discrete Cold Compensation Circuit - A high temp low thermal mass thermocouple - A high Current Solid State Relay - A RGB LED - Optional Female Header interface for launchpad - Optional External Power interface for wall supply. Price: 50 USD + Shipping Standard kit includes and features: - 1x Nokia 5110 Display - Discrete Cold Compensation Circuit - A high temp low thermal mass thermocouple - A high Current Solid State Relay - Optional Female Header interface for launchpad - Optional External Power interface for wall supply. Price: 40 USD + Shipping I'll try to get a video up soon. Anyhow, standard kit is on hold for now. A couple deluxe kits would be available in a few days hopefully. Pushed back 4 weeks so I can do some more testing, development, and get parts from china =P
  3. I assume 2 IR LEDs then for the pulse monitoring? 1 for shinning into your finger, another for picking up the change in the received LED brightness which the variations can be observed as beats? Something like that? Very sweet project, thanks for sharing!
  4. Hmmm its more efficient to buck than it is generally is to boost. If your going to use a regulator, use more batteries then what you need and use a buck. Or for simplicity, just use a mcp1702 LDO or a diode. Not sure boost would be the best way to go. Using a diode would also allow you to have USB power on the line.
  5. When I was first starting up on embedded projects, the msp430 was great for prototyping. Now that i'm abit more experienced I just use the launchpad as a programer for value line chips when I use them on SMT projects. Only other time i'd touch the launchpad is for boosterpack creation.... which i'm finally about to release my first. =D
  6. Very cool, finally found a project where I could use the internal temp sensor and this is a good reference. Thanks Also, pretty sweet html in the forloop there =D . First time i've seen C and HTML mesh. I checked my memory and had 0s for all 85 measurements but there was data for the 30C measurements. Going to see if I can work something out linear interpolation.
  7. 20-30 seconds above liquidous(217C+) is abit conservative but it regrettably relies on the type of component and their moisture sensitivity level. A popular standard/compliance regarding this is JEDEC J-STD-20. See here: www.jedec.org/sites/default/files/docs/jstd020d-01.pdf? If a component is J-STD-20 compliant, it must survive the ranges stated it on page 7. A decent amount of components are compliant to this standard and some will even site the standard directly in the datasheet. However, there is likewise a decent amount of components out there that are not up to the J-STD-20 spec which means implementing a profile within that spec is dangerous unless you verify every component can handle the specified heat. For example, electrolytic caps are notorious for not being able to handle long durations above liquidous. Consequently, you can implement a more conservative profile @ less risk of damaging the components and @ perhaps more risk of not reflowing all the components properly. In contrast, you can implement a profile that does meet the spec @ the permanent and long term risk of your components. I prefer to play it more safe with regards to the components so 30-60 seconds above 217C has worked fine for me. Its a delicate balance that is up to you. While i'm at it i'll take the opportunity to rant and say that RoHS is an example of poor government intervention in electronics under the ignorant "green" banner. While it has kept products out of landfils with leaded solder (which accounts for a very small amount of the overall lead in landfills) it has sent numerous amounts of pb-free products into landfills due to deficient solder joints. In my experience, pb-free joints are more susceptible to thermal-shock & physical shock/drop & have other fun surprises such as tin-whiskers. There is a reason why the government excludes their own products from this standard. Moral of the story is, do not use PB-Free paste unless you absolutely have to...
  8. The display is RobG's awesome 2.2" touch display. Check out his booster pack at: http://store.43oh.com/index.php?route=product/product&product_id=107 if your interested in playing around with it.
  9. My half cent would be to stick with 3.3V. 3.3V chips make up a large majority of the market. Luckily, the MSP430 can still maintain 16MHz at 3.3V. Its not necessarily reliable long-term to push 3.3V chips to 3.6Vs or to trust intermediate voltage levels when attempting to interface 3.6V with 5V logic. Level shifters cost a couple cents and guarantee functionality. Best to play it safe rather than the potential for random failures. TI's 3.6V micros are just TI being.... TI.. :?
  10. 90% coded =D Profile shown is actually the pb-profile. The true PB-free profile will peak probably at 230C.
  11. username

    WDT as RTC

    Thanks for the link & the tips. My bad, I read Ike's post too quickly. For some reason I thought he meant 1ms ticks :? . ~16ms was nice in order to schedule other system events.
  12. username

    WDT as RTC

    XIN & XOUT are the default functionality of P2.6 & P2.7 if i'm not mistaken. By default, ACLK is set to XIN & XOUT. Furthermore, the 12pF is not necessary depending on the crystal. Finally, I didn't need 1000ms tick so I used 15.6ms. Less interrupts -> less overhead.
  13. username

    WDT as RTC

    Normally the first thing many of us hobbyists do is disable the WDT. However, considering the very limited amount of timers on the msp430 value line series, this is quite wasteful. Heres a simple application of the WDT as a basic RTC because godforbid we use the WDT as a WDT. in order for this to be accurate, you need an external crystal of 32.768khz #include "stdint.h" uint8_t counts=0; uint8_t secs=0; uint8_t mins=0; uint8_t hours=0; void rtc_setup() { WDTCTL = WDT_ADLY_16; // WDT 0.015625ms or 64 Hz IE1 |= WDTIE; // Enable WDT interrupt __enable_interrupt(); } // Watchdog Timer interrupt service routine #pragma vector=WDT_VECTOR __interrupt void watchdog_timer(void) { counts++; // Interrupts every 1/64s if(counts>63) { counts=0; secs++; } if(secs>59) { mins++; secs=0; } if(mins>59) { hours =hours%12 +1; mins=0; } } void get_time(char * buffer) // format hours:mins:secs { uint8_t local_data=hours; buffer[0]= local_data/10 + '0'; local_data %=10; buffer[1]= local_data + '0'; buffer[2]= ':'; local_data =mins; buffer[3]= local_data/10 +'0'; local_data %=10; buffer[4]= local_data +'0'; buffer[5]= ':'; local_data = secs; buffer[6] = local_data/10 + '0'; local_data %= 10; buffer[7]= local_data +'0'; buffer[8]=0; }
  14. username

    Laser Controller

    Sounds neat! Be sure to show us when your done. I assume this is meant to be a lab laser controller?
  15. Pretty darn awesome opossum! You by chance got a big archive somewhere of all your awesome msp430 code?
  16. Howdy all, School wanted acouple IR reflow ovens so I figured heck, why not make a new control board? In addition, I want to make my new security system V3 so why not combine the 2 into 1 small compact board? (besides the inevitable routing nightmare). Any review of the schematic would be appreciated. I figured i'd make 1 last project with an MSP430 but i'm tempted to put an ARM on there cause I need more GPIO and I will probably need more RAM. Many thanks to RobG for his awesome development of the 2.2" lcd display. My new Security System V3 will use an ultrasound sensor, a infrared sensor, and a magnetic door sensor. No one is getting through my door without me knowing it XD. Will use an NRF chip to send a watch dog signal to my omega alarm box I have yet to build. Will also have a separate NRF key that will deactivate the system automatically if i'm around. Click for full size, all values are by majority simply representational
  17. Howdy all, sorry I neglected this post. I updated the code for the rev 1.5 and made some improvements. My coding skills hopefully have improved abit over the last year. I'm avoiding interrupts & low power modes for simplicity. This code is meant for beginners
  18. oooo I got enough points! But so little time =( . Awesome idea though and best of luck with it! I love the idea of free hardware 8-)
  19. Larissa, thanks for taking the time to explain some of the background info to us. Communication effort on the part of the manufacture is greatly appreciated and shows us your listening! I'd say 43oh.com & its awesome members are quite decent partners to have for making the 430 ecosystem grow & even in the educational realm. Do note that the majority of us have no interest in making mega bucks off the msp430 and we all were certainly okay with that. Were all in this simply because its fun. Many of us enjoy working on a MCU development platform that was sub par to none in terms of price point. The price point of this platform inspired us to teach other members, write documentation for it, and create boosterpacks...ect. While you may gain some members with this move you will certainly lose others. Because as many members have already mentioned, more than doubling the price simply isn't competitive with what already exists out there. Don't forget your original member base! There was something significantly novel about you and your friends being able to develop on micro controllers for just $4.30.
  20. Not to be debbie downer but at 10bucks, there isn't much reason to get a launchpad. First male headers, now doubling the price on the launchpad? A STM32F0 discovery board has 4x the flash program space, 15x the RAM, 3x the core? CLK speed, 2x w/ 32bit instruction set and is now CHEAPER than the msp430 launchpad. The MSP430 launchpad has lost its only selling point which was its price. 32 bit ARM processors are far more powerful, have more open source support, and compete with the msp430 in their low power models. Why use TI msp430s at school or work now? *cries* why TI...why...? There numerous other dev boards in the 10usd range as well that flat how destroy the msp430... another example is the Freescale Freedom board which is 12 bucks. For an extra 2 usd you get a Cortex M0+ w/ USB support...ect Only thing that drew people to the launchpad was the price. Not the dev tools or the MCU itself and especially not the company TI as a whole. ..Edit: sorry rage moment... Always been a decent fan of TI until they pull things like this :-(
  21. Sorry to double post, hey RobG, think you could put a micro SD card on the next rev? Or atleast a pad for 1? Been working with SD cards as of late and i'd be cool to have the option of one of those as storage. There probably better ones out here but heres a push/pull micro that is easy to hand solder: http://www.digikey.com/product-detail/en/DM3D-SF/HR1941CT-ND/1786515 (footprint is abit painful though)
  22. Can someone please post a 20minute un-boxing video review? I'm curious about the bubble wrap they come in.
  • Create New...