Jump to content
43oh

bobnova

Members
  • Content Count

    161
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by bobnova

  1. Ouf, I hope everything goes well for you and you get out and home soon! Does sound like good reading time though. I've read through the ESI stuff a couple times and it's still fairly confusing, its a pretty wild bit of hardware .
  2. Recently there was a contest for applications using TI's ESI hardware rotation/flow sensing peripheral, I was one of the winners of that. Actually TI did a pretty cool thing and gave the prize (target board and programmer) to everybody who entered rather than just their favorite five. Go TI! In any event, here is product pitch I submitted: I also submitted a more advanced version that ties into the fuel injectors and computes instant and average mileage, but I may or may not get to that in a reasonable time period. This is my project thread for this project, if you hadn't gues
  3. You need to drive pin 5 HIGH, not just set it to OUTPUT.
  4. Thanks for this! The hardware oversample is a very cool feature, I'll be using it in the future I think as it simplifies my code significantly. No more sampling loops, for starters. Or a lot fewer at least.
  5. TI makes some no-caps-needed LDOs, they're something like a buck each for singles though and don't drop a ton in price till you're buying a lot, if I recall correctly. I've been meaning to get a couple to see how they do.
  6. I think that would be incredible.
  7. That sounds pretty awesome, really. Having a USB UART gateway that consumes that little power could be very useful to a project I'm working on. What kind of physical size do you think? Do you have a rough cost estimate?
  8. This is pretty awesome, being able to directly use Arduino shields on Launchpads would be great. This being possible as well would be even better!
  9. SCL and SDA are pins P1_6 and P1_7 respectively. That said, for a number from 0-99 I would just use normal old serial. Connect the sensor board's TX to the receiving board's RX, and use Serial.write(variable) to send the info, then Serial.read on the other end. Do note that the RX lines will be connected to both the PC (via the debug side of the launchpad) and to the other launchpad, so I think you'll want to disconnect the RX jumper on the receiving launchpad to prevent "interesting" issues, possibly including MCU death if they have differing ideas on whether the line should be HIGH or LOW
  10. That is absolutely glorious. You could do a finite number of frames with an MSP430 of some sort. If you want to do the motion capture style like in that video you'll need to aim a lot higher in processing power I think.
  11. OK Now I'm really confused. I sat down to work with this some more, and the code that did not work earlier this evening without Serial.begin now works without it. I have absolutely no idea why, or what changed. I'm confused now. This is what I get for posting I guess! The especially confusing part is that I've run into this twice, the first time I put off more testing and posting about it, then forgot about it and didn't remember till earlier today. I'll keep poking it and see if I can figure out what the deal is/was. EDIT: I'm a doofus. I think it was a combination of thin
  12. I've been working with this library some more, and I've run into an issue. It only seems to work correctly if Serial.begin() is called. I can remove the dump_radio_status bits and everything that actually uses serial and it still works just fine, but if I take out Serial.begin the radio does not function. It compiles just fine, but nothing comes out of the radio. I looked at the library a little bit but didn't see anything obvious, no huge shock there as it compiles. My guess is that it's something in the serial/i2c/spi hardware, but I haven't tested this. It came up as I'm trying
  13. I did some testing on this, there's something odd about the TM4C129 EEPROM. Using the EEPROM.h library it hangs on writing. If I use ROM_EEPROMProgram it writes just fine (I think, doesn't hang anyway), but when I call ROM_EEPROMRead it hangs. These calls work just fine on the Stellaris and TM4C123 launchpads. I think next up is opening the 2 kilopage datasheet and trying to find answers in there. I do not have the brain energy for that right now, though.
  14. OK, I have two three different projects that the ESI could be used with, I'm going to list 'em from least ambitious to most ambitious. The more ambitious the less likely I'll actually manage to do it, but who knows. Possible project one: Digital tachometer, speedometer, and intelligent shift light. Uses the ESI to read either the ignitor's tach output (one pulse per ignition event, so two per engine revolution) or the vehicle speed sensor's square wave (whichever is more difficult to do with interrupts/timers, unknown at this time) as well as the throttle position sensor. Displays engin
  15. I'd not seen this till just now. Very interesting project, and one I'd contemplated for one of my cars at one point. I'm short on time right now, but I'll be keeping an eye on this thread!
  16. Very cool, I like the combination of digital and analog.
  17. Spent some time digging through the users guide / datasheet / whatever TI calls it. I don't have any sensors or projects that would make using the ESI worthwhile. There are a couple that it could be used on, a digital tach/speedo/MPG/etc. dashboard for my car for instance, but there's no benefit I can see to using the ESI to grab rotational data rather than interrupts. Another one is water consumption monitoring, it'd be great for that if I were looking at using good, accurate, expensive, sensors. I don't have a kilobuck to throw down for one though so that's out. In the end, a big th
  18. What's the mirror for? 3D Printing? Light shows? It sounds interesting.
  19. @@bluehash Ahh well, thanks for looking into it for us.
  20. The VCC/GND/SPI pins on these wouldn't happen to be the same as the cheap NRF24 radios, would they? That'd be awfully convenient.
  21. Me too. If they're in that same general five bucks shipped area I'll buy at least two.
  22. Energia sets the chip up to run 16MHz via the internal oscillator(s?), the external crystal is typically for an optional 32.768kHz crystal for RTC use. It's not used for the core clock in Energia, nor in most setups. Regardless of what you're programming it with, you really shouldn't need anything more than VCC (2.0v to 3.6v), GND, a cap from VCC to GND, and a pullup resistor on RST(reset).
  23. Sounds like you're ahead of me on this one. My experience with encoders has been that mechanical units bounce like mad, and expensive optical units (idle-low) don't bounce at all. I haven't used one like you're describing though.
×
×
  • Create New...