On Wed, Feb 8, 2017 at 6:46 PM, Graham <gra...@flex-radio.com> wrote:
> Looks like Andice Labs has two capes of interest. > > If you want to run from a single cell lithium, then their "Power Cape" > looks interesting. > http://andicelabs.com/beaglebone-powercape/ > > If you want to run from and maintain a 12V Lead-acid battery, then their > "Solar Power Cape" looks interesting. > http://andicelabs.com/beaglebone-solar-cape/ > > --- Graham > I, and I suspect Jason would prefer to have an open source software / hardware solution. Something that people could build for themselves, or just buy from circuitco, or another entity if they'd prefer not to. No idea if the andice labs solution is open sourced. So, I'm the software guy wulf mentioned before. Our implementation is rock solid. But the only boards we've implemented this circuitry into is in a closed source commercial application, where an NDA is in effect. However, the MCU source code IP is entirely mine, as well as the idea in general. This, is for the watchdog / power management aspect. After that, implementing the rest should be fairly trivial. One feature my design does not have, which eventually I plan on changing. Is power management / watchdog program-ability. Which would be super trivial once a communications protocol was established. I'm leaning towards 1-wire, but I2C would be just as good, except for the need of an additional data line. However, if that was hung off one of the existing, and already used I2C buses, I think that would be ideal. One less pin being used too I think. The only thing that is holding me back right now aside from not having the time. Is understanding how to implement a 1-wire, or I2C slave device in software. I had thought about open sourcing my software for the MCU we're using, or perhaps just selling programmed micro controllers. The problem with open sourcing the software however then becomes knowing how to setup a toolchain, then flash the binary onto the MCU. Which I'm not sure I honestly want to get into that whole mess. For a few reasons. I've spent literally 5-6 years working with this processor to get where I am now with understanding all of this. So helping others to understand how all this works, would be a pretty big burden / responsibility. Something at this point in time I'm not prepared to deal with. The rest, knowing how many GPIO's one needs for various features is pretty easy though. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpmyOprwtN6sLDpfomWLW%2BSZy10T_Wb4aswLNVDVyWdqw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
