Why wouldnt I Power a Propeller staright from two 1.5v AA batteries
JohnR2010
Posts: 431
I have been running my test circuit for two weeks now straight off of two AA batteries (No 3.3v voltage regulator). I'm working on a battery powered ZigBee project and I have both the ZigBee's VCC and the Propeller's VCC tied directly to the two batteries. Both the Propeller's data sheet and the xBee ZB SMT say they support 2.7 to 3.6vDC. In doing this I don't have to worry about any stray currents my regulator would eat up. When both the Propeller and the ZigBee are sleeping I'm pulling .010mA and they sleep 80% of the time so I'm talking more than a year of run time on two AA batteries! This has got to be too good to be true!
What concerns does the forum have with this approach?
What concerns does the forum have with this approach?
Comments
Best would be to use some kind of boost switching regulator designed for this sort of use that uses two AA batteries and puts out 3.3V.
Note that it a 100mW discharge is currents around 100mA. The voltage will stay much higher (as seen through the internal resistance) when the current is low. Note that low temperatures increase the internal resistance too.
Li-Fe-S2 primary cells start out at about 1.7V open circuit, and hold up with low internal resistance for much longer. When they fail, they do so rapidly, so it is harder to judge end of life. Here is a graph comparing L91 to E91 AA cells.
The cells are very lightweight, and perform well over a wide temperature range.
But for use indoors in a controlled environment I'm intrigued with the performance I'm getting so far.
This ZigBee stuff is so freaking cool!!
But the Li Ion cell is likely to offer better performance than 1.5AA cells. The discharge curve is flatter, the battery has a higher density of stored power. The only problem is being certain to cease use before you go below the proper use voltage. That will destroy the battery, even just one event.
So a 18650 Li Ion with low voltage protection might be a good choice. But it is still a bit awkward. Most of the use is around 3.6 volts to 3.7 volts, and low voltage cut off is at 3.3 volts. But the fully charged cell can offer up 4.2 volts for a short period of time.
So no matter what you use, you have an S curve and the tail ends are where the problems lie. Can you get 100% power? Will the newer switching regulators, you get 90% power out of the cell, and it is regulated.
Flyback (boost) converters cannot have Vo less than Vin, and yet they spec 5.5v Vin on a 3v3 out device.
There are SMPS that can tolerate Vin above and below Vo, but they usually use two inductors.
Some form of battery reversal protection is always a good idea
You may be able to use the LBO to switch in/out a diode drop on Vin, so that on brand new batteries, it drops Vin to keep < Vo, as the battery drops, the diode is removed. ( eg a P-FET body diode can do both Diode and removal)
I'm gonna guess you are referring to common AA sized cells, ie: NiCd and NiMH. Please clarify performing poorly?
But I would also recommend going with a 3.8V Lithium battery + extreme low QC LDO.
I'm not a big fan of Microchip but this is one of the lowest Quiescent Current I ever seen at 1.6 μA.
http://www.mouser.com/ProductDetail/Microchip/MCP1700T-3002E-TT/?qs=%2fha2pyFadugJgcIR8OQT8eRAbM%252bVI1ZZ%2fdXeIVikR%2fKG3mDhJuVuJw%3d%3d
At low currents, there is very little effect of temperature on performance over the -40 to +60 °C range. I'd still go with a big capacitor in parallel to supply the pulses. These also have long shelf life, low self-discharge. 90% of capacity left still at16 years with room temperature storage.
Energizer has great technical reference materials. The above is from
http://data.energizer.com/PDFs/lithiuml91l92_appman.pdf
18 page guide with characteristics and applications.
I'm all for the rechargeable lithium chemistries too, especially if you can include energy harvesting for recharge.
https://www.sparkfun.com/products/10967
Micrel has a few that are lower current and better behaved. (MIC5231 and MIC5232) The 3.3v MCP1700 will draw >30uA when the input voltage is below 3.3v. (the 1.25 and 1.5 volt versions of the MCP1700 are well behaved so make cheap uA references)
I'd just disable the brown-out detector and use an external 2.0v brownout detector. A TC54 series voltage detector would be my choice. I've booted the prop at 1.5 volts. I bet it still does over 40MHz at 2 volts. (see my signature for details)
The speed of the internal RC clocks are also quite voltage and temperature sensitive. With some fixed external timing source it's easy to infer the power supply voltage. (an RC circuit on a pin or external clock)
Marty
I think i need to mention I'm communicating with the xBee through the API interface and I'm sending ZigBee formatted packets. ZigBee is more than just a RF communications protocol it also defines several standard ways applications can communicate with each other. For example if you have an on/off device an you want to turn it ON that command is all contained in one packet. So all the Propeller has to do is receive this packet, interpret it, and then switch on a pin. The Propeller doesn't do the polling it is simply waiting to be woke up and give data. The xBee's Freescale processor does all the low level polling for me.
So while the Propeller is sleeping the xBee wakes up every 5 seconds and connects to its ZigBee parent to see if it has data queued for it. This checking for data is extreamly fast (~10ms) basically one packet out and one packet back to acknowledge that it got the poll request and then the xBee goes back to sleep. The Propeller remains sleeping through this poll process and the xBee repeats until a data packet is received. When an actual packet is received the xBee's Wake Host timer is started (WH command sets the timer, its not well documented) and the CTS line is set high. The high CTS pin wakes up the propeller and it switches back out to the 5Mhz crystal, starts up the cogs and waits for data from the xBee. At this point the xBee's Wake Host timer has ticked down and it starts transmitting data to the Propeller.
If there isn't data for the Propeller to process it stays in sleep mode. It could sleep for hours or even days. If the Propeller needs to send a packet out and the xBee is sleeping it can wake the xBee by pulling the Pin Sleep (Pin 9 on the xBee low).