cubeberg

Are you using a PNP transistor or NPN? Also - why are you using diodes instead of resistors? Usually you just need a resistor - you can find a calculator here - http://kaizerpowerelectronics.dk/calculators/transistor-base-resistor-calculator/ Make sure you check your pinout as well - there are a couple different pin configurations for transistors.

That's really cool!

I finished kitting a bunch more - I'll send you an email and we'll get some over to you

Oh - and if anybody is going to the NC Maker Faire next month - @@RobG is going to have some

Thanks guys! I'll definitely have to see what kind of settings I have on my cameras for exposure time/frame rate - should be able to get something figured out.

A picture of Mark Easley working with someone at the SF Maker Faire on soldering their badge: Check out TIs twitter feed for a few more pics https://twitter.com/TXInstruments

This project was a collaboration with Texas Instruments. I've kept it hush-hush so far, but as of yesterday - it's finally out in the wild! Yesterday at the SF Maker Faire, Texas Instruments started giving away boards at their booth. If you're visiting the Maker Faire today - please drop by booth 220! Thanks a ton to TI for sponsoring and feedback on the design. Will Cooper, Adrian Fernandez, Mark Easley, Dung Dang and Rachel Platis were all involved - this wouldn't have happened without them. Also - Elecrow did a wonderful job on the boards and initial kitting (I added the batteries

@@Kunal Raunak - do you have the hardware available? I'm not sure if the displays are still available on ebay or not.

Just got an email from @@bluehash - the hosting company is offline - fiber cut. Hopefully it'll be back up soon.

So I'm still working on getting my Wifi project working - thanks to the new Energia import with CCS 6 - I was able to track it down to a loop that gets stuck waiting for a condition that sometimes doesn't happen. In the wifi library - under evnt_handler.c. while (1) { if (tSLInformation.usEventOrDataReceived != 0) { The .usEventOrDataReceived gets flipped to a 1 when data is received via SPI. Anybody else have a suggestion on what needs to happen to fix it? If someone else has a F5529LP board that they could test the repeating example with as well - I'd sincerely apprecia

I've been working on a project with Cap Touch pads lately. It's a straight slider - not sure how you'd do coordinates - you might have to do concentric rings of pads to achieve what you're looking for - figure out which rings they're over and then measure the difference between those two to determine where they are. The Cap Touch boosterpack might be a good frame of reference - it's circular. I have one pad on my device with a bit of ENIG exposed and it has caused problems so far - if they physically come in contact with the exposed metal, the capacitance goes way up for the pad - it s

I'm working on a project I started using the WebClientRepeating example. I've got one fix that might help some people, and an issue as well. DHCP connection Occassionally I would get a good connection, but most of the time I would get "0.0.0.0" as an IP address. I finally figured out that if I waited longer, I would eventually get an IP. Here's an enhancement to the existing SimpleLink sketches that will fix this problem. Basically - I read the IP from the CC3000 and loop until I have something other than 0.0.0.0. I've found that when I'm developing - constantly reconnecting to the

Oh - and FYI - one issue I've run into is scan rate on the monitor (I think) - I'll get good reads with intermittent low values. I've had success from both laptop monitors and a phone.

sven - I've actually got a working board that's doing this - using a couple of ambient light sensors. I'm still working on completing the functionality, but I might have some code that would help you out. I'll be posting details soon - but for now I'm keeping it hush-hush - maybe PM me and we can email?

I've dealt with writing to flash a bit myself lately - it can absolutely be done in C. Quick question - GCC or CCS? I use CCS, but I believe the concepts cross both. This example is helpful: http://forum.43oh.com/topic/412-saving-data-to-flash-on-power-down/#entry3669 - this bit in particular. Flash is erased in 16-byte blocks (That's the reference to ERASE and the "= 0" assignment above) and then written to which can be a bit tricky if you've got several values that will fit in one block. There are a couple of "INFO" segments that are specifically reserved for storing a few valu

Sounds like a good case for a Big Box of Parts http://dangerousprototypes.com/category/big-box-of-parts/

FYI - The TI-TXT file format can also be used with a gang programmer if needed.

This energia library is probably worth a look - http://forum.43oh.com/topic/3180-energia-library-virtualwire-110-library-ported-to-msp430energia/

finally broke out my 5529LP and CC3000 boosterpack - working on a software build monitor for my new job. Got it to successfully connect to the wifi!

BTW - I was able to get my 5529LP and CC3000 device to connect to a WPA2 router successfully with the new 0012 version of Energia that was released.

Working on code for my secret project Had a busy weekend introducing my kids to Mythbusters and Cosmos as well.

anybody else have trouble chaining both rings together? I used a WS2811 example in Energia for 120 leds and the second ring freaked out - the first few LEDs were fine, but after that - they were very bright colors (static as well - non-changing). maybe I need to add a resistor like a couple people mentioned?

@@t0mpr1c3 If you get it working - make sure to post - sounds interesting! $0.99 isn't too much to lose

@@t0mpr1c3 - watch out - heat will kill the magnets. An adhesive is typically recommended. https://www.kjmagnetics.com/FAQ.asp#weld

Check the data sheet for the chip you're working with for interrupt priority - http://www.ti.com/lit/ds/symlink/msp430g2553.pdf for the 2553. It's on page 11. For USCI - you would write each of the 256 bytes sequentially (the TX interrupt for USCI). There is an interrupt to indicate that the byte has been sent - you can use that to send the next byte in your list. Once you complete your array of bytes - just don't send the next. Regarding one interrupt stopping another - here's a discussion on the e2e forum that looks promising - http://e2e.ti.com/support/microcontrollers/msp430/f/