Jump to content
43oh

bobnova

Members
  • Content Count

    161
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by bobnova

  1. The debugger doesn't work well inside interrupts, or at least it certainly didn't for the last person that was trying to read inputs via the debugger inside an interrupt. I haven't tried it myself. I'd feed a counter variable and use that to see if the interrupt is working correctly.
  2. I would enable the pulldown resistor on both input pins, then put an interrupt on one pin, let's say quadrature pin A. When the pin A interrupt fires check the state of the other quadrature pin. If B is low, A happened first, if B is high B happened first. I don't see any particular reason that wouldn't work with idle-open quadrature. I know it works nicely on idle-LOW quadrature.
  3. The LGA part is unfortunate, but the module looks pretty cool.
  4. I like this concept. I am constantly forgetting my too-hot-to-drink drinks until they're far too cold. I'll definitely be following this project!
  5. That is amazingly inexpensive. I might have to get a few. Thanks for the heads up!
  6. I hadn't checked out TI's energy scavenging boost converters previously, so that was interesting. Overall, awfully dry and scripted. The Q/A box never went live for me. I'll rate it as vaguely interesting, but I wouldn't have sat through it without the potential bribes I don't think. Seemed like it was mostly aimed at marketing.
  7. Sure! What sort of details are you after? Design/construction wise: I used the excellent Yagi Calculator by John Drew / VK5DJ (link) for the basic design, the element lengths and locations and such. Once I had an output I took my digital calipers and sketched it out on some paper. I hot-glued the shell of a rubber duck antenna to the paper along the long axis, then trimmer aluminum electric fence wire to the proper lengths (roughly. Within 0.25mm anyway) and glued them to the antenna shell and paper. The dipole was made using the mini-coax cable, the yagi calculator gives numbe
  8. Just in the EU I guess. They aren't used nearly as widely here in the US as they used to be, but they're still around. From what I've read they turn out to have some very useful properties for small/cheap solar applications. Primarily that you can charge them at 0.1C indefinitely and they don't explode.
  9. They're roughly indestructible if you don't mind a large voltage drop? That's what those figures imply to me. Interesting. Atmel bits in this class start dying after 40mA according to their datasheet.
  10. Registered. This is a subject that I've an interest in anyway, so double-win. Thanks for the heads up!
  11. Yeah, that I'd found. I was surprised to not find a hard cap like Atmel specifies. Maybe it varies too much by chip or something.
  12. I think I might have edited my wiring_analog. Try #include <wiring_private.h> It's in energia somewhere. EDIT: I have no idea if it works on G2553s, as I mentioned up above I've only used it as a Tiva-C / Stellarpad function, it may well not exist for the G2553. The G2553 timers are certainly capable of different frequencies and resolutions though.
  13. I've been playing with NRF24L01+ modules and launchpads. I've got 'em to where they can run and send packets on a (&*@#% little solar panel out of a harbor freight solar path light, and make it through the night on a 300mAh NiCd. Next up was improving their range, as the PCB trace antennas aren't especially good (even more so when you have metal walls to punch though, like I do). Cut traces, soldered mini-coax from a dead WiFi router in place. Built a mini-yagi! The test package, a MSP430G2553 launchpad, a JeeLabs AA power board (3.3v boost converter, extremely efficient
  14. I was wondering about this too. The datasheet is less useful than it could be. Thanks!
  15. @@altineller not really, no. It's something of a hidden function. You have to include wiring_analog.c (#include <wiring_analog.c>) to kick things off. That includes the PWMWrite function. Then you can call it thusly: PWMWrite(PIN,numberOfSteps,dutyCycle,frequency); For example: PWMWrite(PD_1,500,250,6000); Would start PWM on pin PD_1, 500 steps from 0 to 100%, 50% duty cycle (500 / 2 = 250), 6000Hz frequency. It's worth noting that the function call does glitch when you call it on a pin already putting PWM out. It's not enough to hear driving a speaker, but it could cause
  16. The EnergyTrace support is what would make it attractive to me compared to the onboard programmers. I'm really enjoying it on the FR5969 LP and want to use it on 2553s. I'm making a happy assumption that this can be interfaced to a MSP430G type launchpad.
  17. I'm trying to find time to put together a proposal. There are a couple (hell, a few) different things I can think of to make with it. Need to sit down with the datasheet for an hour or five and figure out exactly what it does, and why it'd be easier to use it than an interrupt and a timer.
  18. That's very cool, I was having to visualize the data in Processing or on a little LCD screen, neither of which is ideal. I'll definitely have to check that section of CCS out.
  19. That explains something at least. I'm hoping my alarm issues were due to subtle differences between A and B, as I thought I understood it based on the datasheet. I'm hoping I can steal some time to play with this library today.
  20. Very cool! I'll definitely try this out. I've been kludging my way through the FR5969 RTC (and apparently looking at the wrong datasheet section while doing it, oops, maybe that's why I couldn't make the alarm function work...) and found it to be quite nice. Having a library surrounding it would definitely make things easier, and having read the readme included with said library it looks nice and powerful as well. Thank you!
  21. I don't know why the matching isn't working. I haven't actually done it myself before but that matches what I've read in the datasheet and such. Have you checked the value of value via the debug? Something that might be interesting to try is a very small delay at the beginning of the ISR. Maybe the P2_2 input circuitry is firing before the P1_x bits? Where exactly are the signal wires connected on the LED setup? Before or after the current limiting bits for the LEDs? It should be working however it is, but I was thinking that maybe if it's before the current limiting their LOW state i
  22. You should be able to, kick the interrupt off by checking which flags are set, that will tell you (and it) which pin triggered the interrupt. EDIT: Sneaky hidden page. What he said. Same port, yes. Same pin, no (or at least, much harder).
  23. I would make sure the wiring is correct before I went too far. 0x79 is = 0b01111001, so pin P1_0 high, 1_1 and 1_2 low, then 3/4/5/6 high, then 1_7 low. If you can measure your input pins with a multimeter and that's what you read, then I'm stumped as to why it isn't triggering in your code.
  24. I'll be keeping an eye on this, as I'm putting together solar wireless nodes and I want them to be able to check their battery level without draining said battery.
  25. I think I would probably do it in the loop, but that's mostly just because I've been told to keep ISRs as short and fast as possible. Given a 4KHz input you have some time in there so it probably doesn't matter too much, unless there is something special about being inside an ISR that I'm not aware of. I'd set value to P1IN inside the ISR, and put some code inside the loop that looks to see if value is anything but some number you know it won't get from the input (0xFF, for instance). If it is, then the loop code can figure out what the digit is, and then set value to 0xFF so it knows not
×
×
  • Create New...