NatureTM

The one I used is not cheap, but about 3x less than the one you linked to: http://www.digikey.com/product-detail/en/HMC1021Z-RC/342-1061-ND/1663120

I did a lot of work on battery-operated parking sensors for a startup recently. We used magnetic sensors that are sensitive enough to detect distortions in the earth's magnetic field. The iron an an automobile distorts the field and either increases or decreases the detected field which is read from the sensor by ADC. They're quite low power to begin with, plus you can switch them on with a transistor for low duty-cycle sampling, leading to very long operation from battery. http://www.magneticsensors.com/vehicle-detection-solutions.php In our project we used the HMC1021 in our case.

I just wanted to share a clock I made as a Christmas present for my dad. I just finished it, but luckily he's patient. I have a video, schematic, code, and more details on my blog, www.naturetm.com.

Hi everyone, it's been awhile. I just wanted to share something interesting lasershark mentioned on my blog awhile ago. It's basically a way to make music with one line of code. It took about 15 minutes to implement on a g2553 and only requires a launchpad and a speaker. I found it pretty entertaining. Just connect one terminal of the speaker to Port 1.2 and the other to ground, or drive it with a transistor. Original project @ http://canonical.org/~kragen/bytebeat/ #include "msp430g2553.h" #define MCLK 8000000 #define OUTPUT_SAMPLES_PER_SECOND 8000 #def

Yeah, I haven't been doing a lot of hobby stuff recently, and when I did, it was usually fpga. I'm thinking I'll be on more this winter.

Here's something I had going awhile back. I didn't finish it do to some bug/got bored/meh. The circuits are the same as what gordon posted. My intent was to send the distance data to another uC through serial. Here's the code I had going and a pic. Hopefully I left things in a working state. PS Don't look at the code if you wanted to figure it out yourself. I think I was pretty close to finished. #include "msp430g2231.h" //#include #define PIN_RECEIVER BIT4 #define PIN_TRANSMITTER BIT2 // SPI pins for reference, do not affect code: #define PIN_SCLK BIT5 #define PIN

If you look at the "application information" section of that datasheet, it shows what pins are connected to the timer A hardware. You're looking for TA0.1 (Timer A0, CCR1) under the "function" column. You'll see your only options are P1.2 and P1.6. I usually try to build my design around the hardware, but if that's not an option, you could use interrupts and software to make it work. It would be a matter of toggling the pin appropriately during the CCR0 and CCR1 ISR's. To use P1.6, change the instances of BIT2 to BIT6 like you did, but use P1.6, not P1.5. If you really want to use P1.

My synth used Timer A in capture mode if you don't mind having to wade through all the unrelated stuff. viewtopic.php?f=9&t=513&start=10#p5281 I think this is the important part: P1SEL |= PIN_MIDI_DATA; // Timer A capture input TACCTL1 |= CCIE + CAP + CM_3; // enable capture and interrupt on rising and falling edge ... // CCR1 capture interrupt. Triggers on both edges, adds fresh midi data #pragma vector=TIMERA1_VECTOR __interrupt void CCR1_interrupt(void){ TAR = 0; TACCTL0 &= ~CCIFG; unsigned int tEdge = TACCR1; midiRXB

My friend works at a pretty nice coffee shop and he told me the reason you don't store coffee in the fridge is because it acts like baking soda, taking on all the flavors/smells of the other stuff in the fridge. Not entirely related to what you're saying, but maybe somewhat relevant.

I'm a pretty avid gamer. Games I've been playing recently: Battlefield Bad Company 2 multiplayer CoD Black Ops multiplayer Supreme Commander Frozen Synapse I play one or more of those almost daily, and I play a whole mess of other games ranging from Angry Birds to Silent Hunter a little less frequently. I refuse to play WoW though, sounds like digital crack. I've got fairly decent hardware: Sandy Bridge i7 2600K overclocked 8G RAM SSD OS disk 2x physical HDD's in RAID0 for speed 2x GTX 260's in SLI 24" 1920x1200 monitor I claim 0 dependents on my taxes during the year,

That amazing synth and now this TV ouput game? Quit outdoing all my projects! Kidding! Exciting stuff. I'm looking forward to learning from your posts. You're awesome.

So many good projects this month, I'm really impressed. I'm going to have to think it over awhile before I vote. You guys are awesome!

That's incredible, and I will be studying your code, thanks!

I think xpg's got it, and you also might want to call that __low_level_init() function as the first line of main().

:-/

congrats on HaD!

Well, this isn't exactly a microcontroller, but close enough. I had the day off of work today due to rain, so I decided to make my first FPGA project, a Larson Scanner/Cylon Eye/Kitt Light. I was surprised I actually got this working in only a morning worth of work. (Decrement FPGA scariness.) Code and stuff on http://naturetm.com/?p=197.

(Stomach growls)

Word up, yo! You ain't just another noob. Keep your head up boi!

Maybe you shouldn't lie to your friends. Try combining different types of meat. Wrap everything in bacon. Deep fry in oil whenever possible, especially with twinkies and oreos. The goal is to make everything as unhealthy as possible. When making burgers, substitute doughnuts for buns, a very popular dish. Frozen pizza is also very popular. Buy an extra bag of shredded cheese and add that to the frozen pizza. The trick is to cook the pizza half-way and then add the cheese. The secret to flavor is calories. I'm serious about that! You're welcome.

Yeah, that is really looking nice.

I had thought about that. I was also thinking you could fill up the unused space in Segment A with the other calibrations and edit the linker and header files.

Oh yeah, I saw that too. You're good, either thread is fine I agree.

I guess it does belong in this thread. The other thread sets the DCO at runtime, while this thread and the code you posted actually flashes the calibrations after setting the DCO. The code looks nice, and I wonder if I should edit the first post of the thread to link to what you found instead.

I guess there would be two stages to the selection: first selecting the part, and then selecting the user who will write the driver for it. The voting system seems like it would be good for selecting the part. Then, if multiple users want the chance to get the part and author the code, maybe the "thanks" leader-boards could be used to make the selection. It could be a reward for the most helpful users. RobG and zeke are high up in the toplist, and I think that really reflects their skill and helpfulness. This system might be discouraging to new members, however.