• Content count

  • Joined

  • Last visited

  • Days Won


USWaterRockets last won the day on November 3 2016

USWaterRockets had the most liked content!

About USWaterRockets

  • Rank
    Level 1

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Location
  • Interests
    Rocketry, Electronics, Photography
  1. Has anyone uncovered any news about upcoming MSP432 devices? I have some upcoming projects that don't quite fit the current offering. If they had something with USB or Ethernet onboard, it would be a good fit. Competitors already have such ARM devices, but I know the MSP line and could save time if I didn't have to start over with another device.
  2. So, has anyone found hidden support for new MSP430 or MSP432 devices buried in CCSV7? It's been too long since we had a hardware upgrade!
  3. Why don't you just set up a timer interrupt and implement the fancy 16/24 bit UART using software running in the interrupt? If you're using 1200baud, that's 1 bit every 833uS. On a MSP430 running at 8MHz, that's one interrupt every 6000 clock cycles (8000000/1200 = 6000). If your interrupt routine takes an average of 100 cycles to complete, you're using 1.5% of the CPU cycles for the UART (((1200 * 100) / 1000) = 0.015). Recall that the original MSP430 LaunchPad shipped with the MSP430G2231 which does not have a hardware UART peripheral, so all the serial port examples for it were using a bit bang driver. It should be very trivial to look through the existing examples for software UARTs for the LaunchPad and find one you like that you should then be able to modify the bit counter to send 16 or 24 bits instead of 8.
  4. Why not put the entire thing inside a sealed enclosure with a tilt activated switch? One end of the enclosure is tethered to the bottom of the water filling zone and the length of the tether is adjusted so it tilts the enclosure when the water level is higher than the tether. You could put the whole thing inside a common plastic food container and it could run for years off a coin cell.
  5. I heard some rumors about new parts coming, and some new features which were a surprise to me. Definitely not something I can prove easily, but it ties back to something I wanted a while ago. I hope we hear something more solid soon.
  6. I had at least one of my MSP432 Launchpads before they went on sale.
  7. I could live with that solution. Maybe I could just ask for samples. I bought them from the TI store, so they even know I'm the owner. Are there any other differences between the red and black Launchpad boards?
  8. It's slightly annoying that having several of these boards now, and I have to scrap them because support is going away, and I don't recall there was any warning given that this could happen. I just picked up a few more, and now I'm stuck with them and no software upgrade path or discount for people who had gotten the black ones.
  9. Is this just a simple case of TI using the same BSL for all devices to avoid exceptions and differences? Using GPIO for the BSL makes sense if you consider that the lower value line devices like MSP430G2x/i2x have no UART in hardware.
  10. Does changing the interrupt trigger to the current state of the pin generate an interrupt? If so, then you would have to be careful when toggling the trigger state because doing so could set the flag and cause another interrupt as soon as you leave the interrupt handler. This would only happen if the pulse on the pin were shorter than the time it took you to interrupt and flip the trigger condition. You can probably work around this by checking the pin state before leaving the interrupt and setting the trigger level accordingly.
  11. I was going to suggest a IRLML2502, but I see they are only rated for 20V. The one you suggest has terrible drain current ratings because the RDSon is relatively high. You might need to look for something with an RDSon less than 100 milliohms, because the relays may draw quite a bit of current.
  12. One thing I've done in the past for state machines and command processors was to make the commands or the state variable the value of the function pointer itself, so there is no lookup table wasting space. Making the commands "human readable" in the code was simply creating readable #defines for each value. This wouldn't work great for a human to input commands, but two devices communicating with one another don't care that the "Reset" command is some random 32 bit integer.
  13. I'm going to wait. I jumped right on the previous SensorTag, and had software issues, documentation issues, toolchain issues, and I believe the piggyback dev board I bought with it have a hardware problem that was changed in newer revs.
  14. An SD card once initialized will automatically go into sleep mode when there is no activity on the clock line. In sleep mode a SD card will draw between 100 and 200 microamps. Depending on the interval of your powerup/initialize/log sequence, you may be wasting more power re-initializing the card on every power-up than you would be to just let it sleep and not having to initialize it each time you write. It's always good to have the FET control of the SD card power, because that's the only way to reset it if it somehow locks up, but you need to do a careful analysis of power use to find out the best way to save over time.