Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


vicvelcro last won the day on November 22 2013

vicvelcro had the most liked content!

About vicvelcro

  • Rank
    Level 1
  • Birthday 06/20/1969

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Southeast Michigan, USA, 3rd planet from Sol
  1. The items are still available as of 04-05-2014. On 04-12-2014, these items will no longer be up for trade or as a gift. If anyone is interested, contact me before that date.
  2. @@t0mpr1c3 You can count me in. I would prefer to send a money order or ca$h. But can do Paypal if there's no way around it. I'm in: 125x YES; 25 extra NO; B's YES; pcb NO
  3. I enter contests, from time to time. I have been an instructable user since 2007, have won a contest, and been featured twice. A member on instructables introduced me to the LaunchPad and invited me to join the forum here. I agree completely with Fred in post number 3. I will give some thought to the remainder of your post and send you a message later.
  4. @@jbleaux I still have one that I did not use. If nobody has contacted you yet, send me a private message. I can help you out, if needed.
  5. I'm a bit late to this party but... Here's mine: Lasered by own stand-offs and cut some holes in the sled for those to fit in. Tossed a couple of graphics on it. My stand-offs fit the holes loosely enough to fall out when they are not holding a board. Snapping in a board puts enough tension on the 'ankles' to hold them in very snuggly by friction. Cyanoacrylate (super glue) or plastic cement will hold the stand-offs permanenty. Board can be pulled out if the stand-offs are not glued to the sled - or they can be snapped out by *carefully* pulling back on the 'peaks' of the stand-offs. I cut 4 extra stand-offs, just in case I fail to be *carefull*. My laser is 50 watt with a 20" x 12" max material size. Without glueing the stand-offs, mine is holding just fine while actually working with it.
  6. Well, I'm not exactly sure when I will (or already have?) hit the middle of my life, but I will probably crack a joke about it sometime afterward and have a beer. In my area, radio stations identify by frequency then call sign then a catchy name. An example is "101 FM WRIF, The HOME of Rock and Roll". www wrif com but put "." where the spaces are.
  7. Why!?! Why?!? !WHY! ... ... did you do this to me ... I've convinced myself that the last 28 birthdays have been me turning 17 over and over and over again. Now you went and made me reconsider the validity of my presumption. But thank you for the ticket on the way-back bus, nonetheless.
  8. If you can squeeze this into the video: What is gained or lost by using the 32KHz crystal or a Real Time Clock? Are the lowest power modes only available if they are NOT present? I am under the impression that the internal oscillator applies to all of the power modes. I do not know if the crystal or an RTC have anything to do with how LPM works. It that can be covered, even vaguely, it would be helpful knowledge.
  9. One question I have been wondering about and would like to see presented: What can be (and what cannot be) done in each power mode, using general terms? I have reviewed TI's info about power modes, but they pretty much use acronyms. For those of us who do not ALREADY know the meaning and significance of these acronyms, their explanation of power modes is about as clear as Mississippi River mud. Trying to look-up and then assimilate the acronyms when I am already focused on trying to do something specific - well, it just hasn't worked out for me. Too much cross-reference chasing (usually a minimum of 3 PDF files, each in excess of 50 pages) has been the barrier to my comprehension of low power modes. I have not found any general material regarding low power modes that brings it all together in one place. If my question would be better understood by including a bit of context, I'll pose one example scenario: I have an LASER beam (not powered by the MCU) directed at a receiving sensor. If and when the beam is interrupted, I would like an actuator to be triggered. While the beam is intact, there isn't much for the MCU to do, and shouldn't need to be in a fully awake state. What would be the lowest power mode for the MCU to recognize an interruption to the LASER beam at the sensor? What would be the lowest power mode for the MCU to send a trigger signal to the actuator? If I wanted to log the event to non-volatile RAM, what is the lowest power mode that allows the MCU to perform the write? For this scenario, assume that the LASER is powered independent of the MCU and focused on a passive IR receiver which outputs a varying voltage into an analog pin on the MCU to sense the presence or absence of the beam - assume that the actuator is a 9g micro-servo powered independent of the MCU - assume that the non-volatile RAM is MCU onboard. Being able to determine what can be done in each power mode vs what can not be done - well, then I would be able to switch to the appropriate power mode required while using the least amount of battery.
  10. @@roadrunner84 I would be more than interested in low power, from a learning perpective. I think I have a few other things to learn first, before implementing low power modes would make much sense to me. However, if you presented a lecture, others might become more interested than they appear to be.
  11. ***Moderator(s)*** ***If any of the following is off-topic or inappropriate, please feel free to remove any offending text but please do not remove the portions that are acceptable.*** --- I'd be willing to donate a couple of New In Box 430G2 v1.5 launchpads (including the 2452 and 2553 chips) to anyone in the United States that is willing to present a tutorial but is short on available MCUs. The 'presenter' would be welcome to keep the launchpad or pass it on to somebody else. I offer these because there are some very savvy people out there that might lack the hardware but posess the wetware. I lack the wetware but have some surplus hardware. I would be happy to learn anything from a well presented tutorial. Particularly for me: I2C (and SPI), Shift Registers, and writing to EPROM and FLASH have been insurmountable - due to not being able to see any demontrated examples presented in a manner I can relate to. I am completely lost with Code Composer Studio, so a bit of that would help me (and probably quite a few others). Sometimes, I am confused by some of what I find in the data sheets (when I began working with MCUs, data sheets were very aggravating). Possibly somebody who can give a presentation on how to actually USE the contents of a data sheet (in general) might receive the gratitude of a few n00bz. If a pool were available for me (and maybe others) to donate a $$$ tip of a small amount, I would drop a few bucks in the 'Tip Jar' from time to time.
  12. All of the items listed in the first post are still available.
  13. I went through that workshop many months ago. After completion, I was worse off than when I began it. I was confused, frustrated, and annoyed.The use of CCS may not have been the best choice for the workshop. I gave up on CCS after 3 months of making ZERO progress with it, and went back to Energia 100%. Something more topical and simplified would be a big help. Small specific tutorials for those of us truly "Getting Started" would likely be welcomed by at least a few of us. I believe a "Getting Started" workshop should begin with beginners in mind. Otherwise, it isn't really "Getting Started" - it's more of a retrospective repeat lesson, to be visited after the subject has been learned. The workshop located at the link you provided presumes the viewer already knows quite a bit about the hardware and the syntax of the coding. I could see that workshop being more appropriate for persons who already have a grasp of basic concepts pertaining *specifically* to {CCS and the LaunchPad}. Perhaps not very useful to some of us with less pre-established background in this particular combination of hardware and programming tool. Some of us understand coding - from prior experience with something other than CCS and/or with different target hardware, while some may not know anything at all about CCS or the hardware. I still can't get anything based on CCS to run - except 'monkey pasting' their examples and blindly following the given instructions. For me, there was absolutely no comprehension of how the results related to the code. If there were other "Getting Started" tutorials or videos that were more 'education' oriented and less 'infomercial' influenced, I would certainly be interested in having a look.
  14. I looked up that PIR you mentioned. Thank you for that tip!
  • Create New...