Jump to content
43oh

cubeberg

Members
  • Content Count

    1,431
  • Joined

  • Last visited

  • Days Won

    40

cubeberg last won the day on September 5 2018

cubeberg had the most liked content!

About cubeberg

  • Rank
    Level 4
  • Birthday 12/29/1980

Profile Information

  • Gender
    Male
  • Location
    Virginia, USA
  • Sparkfun
    https://www.sparkfun.com/wish_lists/53725
  • Github
    https://github.com/cubeberg

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Sorry - busy weekend/work week Enabling pull up/down resistors should be sufficient for that problem - it's recommended for low-power optimization anyway. Looks like @NurseBob has done an excellent job answering everything else FWIW - I like Elecrow over Seeed, etc. I've always had good luck with them - and they have good customer service for the few times I've had any issues.
  2. The MSP430G family will run down to 1.8v actually - but the CPU speed you can run at is reduced. Here's a good discussion from E2E - https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/599159?MSP430G2553-MSP430G2553-Clock-Speed Assuming you've got the space on your board - I'd at least break unused pins out to SMD test points - you never know when you're going to need an extra pin or two. If there's any chance you may want to debug while connected to an external battery - I'd probably suggest at least adding an extra GND pin so you have VCC/GND for battery and TST/RST
  3. I'd suggest taking a look at the launchpad schematic - there are probably a couple different places you can find it - but here's one - http://www.ti.com/lit/ug/slau318g/slau318g.pdf (Page 15) Pay attention to filter caps on the power lines (10uf and 100nf), as well as the reset pin (I usually just add the the 47k pull-up - although I think the cap is recommended as it prevents problems with power supplies that are slow to start up). For programming - you just need GND, TST and RST - I usually break out a 4 pin header - VCC/TST/RST/GND - for programming/debugging. Pull all of the j
  4. The DeviceHive python examples for the Pi are keeping my CPU at ~98% I couldn't get their dashboard tool connected either. I may mess around with Node-Red and see if that's not too hard. I used that before with my old IoT project and was able to get it to work pretty well.
  5. @hmjswt - you could easily say that about a lot of things (C vs Assembly, roll your own database, etc.) I'm a web developer - but trying to figure out everything from hardware to reporting can kill a project pretty quickly. Like @zeke - I've got a lot of unfinished projects - usually because I get bored trying to get over obstacles in the project. Since DeviceHive supports MQTT - it should be pretty easy to port a project over to something else at a later point in a project. I was able to get a simple POC working with a Raspberry Pi on DeviceHive. Not too bad - it'll be a good
  6. I'm going to have to check this out! I was wondering if something open source would pop up after Phant died. I killed off my IoT devices once I realized that wasn't going anywhere.
  7. I unfortunately don't have any more stock. @bluehash - do you have any stock left? I'll take them off your hands if you do.
  8. I think you'll be surprised about how many software guys you'll find around here I'm a web developer
  9. So I've been horribly quiet in the forums lately - mostly because of a lack of free time. Since I don't have a dedicated work space - having to break down and set up tools, projects, etc. severely limits how much time I have on projects. Thankfully - I'm getting a new house with my own room for projects as well as a garage! I'm hoping this will mean more time to complete projects. Most of my components are in cardboard boxes and plastic tubs - well organized but not exactly what I'd like for a nicely organized full workspace. I know we've had threads for showing off your workspace - b
  10. @@RobG - I'd say all 4, otherwise the 1st tube isn't treated for cathode poisoning as much as the other tubes.
  11. @@RobG - I'd have to agree on the piezo - this type of clock is probably too bright for an area where you'd want an alarm. I have a spot for one on my VFD clock but only populated it for my first test device. I have three on my desk at work, one with a buzzer that beeps on startup - I should honestly pull the thing off of the board.
  12. @@RobG - hah - that's what I was going to try to add
  13. Well, I know there's a way to go into low power in Energia - might be a good idea to post in the Energia forum. Attach Interrupt would take care of the button push part and Sleep looks like it would work for low power/timing portion - but I don't use Energia a lot outside of ARM chips.
  14. I'd suggest downloading the code examples from the product page - http://www.ti.com/product/MSP430G2553/toolssoftware (download link - http://www.ti.com/lit/zip/slac485) There are a lot of examples depending on what particular aspect you're looking for. Here are a couple of examples that might be helpful: msp430g2xx3_P1_04.c - toggle LED when button pushed - using LPM4 msp430g2xx3_lpm3_vlo.c - LPM3 - LED toggled every 6 seconds
  15. I'll admit I haven't finished the training on TI-RTOS (next plan after I'm done with this course) - but the concepts introduced in the course are clarifying some of the settings I was seeing with TI-RTOS (Like WTF is StackSize used for). So I can see this helping my understanding of using another RTOS.
×
×
  • Create New...