Jump to content


  • Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    Cw1X reacted to vicvelcro in [43oh_101] Low power   
    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.
  2. Like
    Cw1X reacted to RobG in MSP430F5510 USB Development Board   
    Here they are @@strobe
    Also, I have 8 bare PCBs left if anyone is interested.
  3. Like
    Cw1X reacted to strobe in MSP430F5510 USB Development Board   
    Can you share original Eagle schematic (might be without actual PCB Layout) and BOM of actual parts?
    I guess this board might be more popular if users will be able to quickly make devices based on this board design - for example 1-Layered PCB with additional items. 
  4. Like
    Cw1X reacted to oPossum in Casting problems: extract 4 bytes from a long int.   
    aa = (byte) (cast >> 24); bb = (byte) (cast >> 16); cc = (byte) (cast >> 8); dd = (byte) cast;  
    faster code:
    byte *p = (byte *)&cast; dd = *p++; cc = *p++; bb = *p++; aa = *p;
  5. Like
    Cw1X reacted to oPossum in Changing PWM duty cycle with value from variable   
    CCR1 = (N - 128) << 1;
  6. Like
    Cw1X got a reaction from Pynchillglili in Posted by in "Forum Recent Topics"   
    I would really like to see who posted the last reply together with the date and time in "Forum Recent Topics" on the main page. I think its easier that way to see if there are new replies from the last time you checked because I personally easier remember usernames that time.
    So that's my suggestion
  7. Like
    Cw1X got a reaction from jsolarski-backup in Rectyfing and sensing small AC signal   
    Here are some pictures of waveform when engine is at idle and you can clearly see frequency rises on the other picture with RPM's but I don't see a big voltage difference. But then again this is from a sound card oscilloscope so dont know how trusty is it
  • Create New...