• 0 Votes
    5 Posts
    77 Views
    J
    Just to give feedback, I've had the Pytrack + Gpy powered via the VUSB_AUX for a few hours and all is working fine. Thank you for all the help!
  • Deep Sleep and Battery Consumption.

    LoPy ttn lopy deep sleep battery consumption lora
    18
    0 Votes
    18 Posts
    198 Views
    H
    @jcaron So you get a curve that varies during the whole awake time between 30 and over 100 mA. Ah I see. I think I confused myself when I saw the LoRa transmit in the documentation of 105mA and thought it was somehow the overall current draw of the awake time because it was similar to the 100mA you had mentioned before but I get it now. So the current draw is about 100mA (conservative) on average over the awake time. You've been a really great help. Thanks for all your patience :)
  • 0 Votes
    2 Posts
    316 Views
    robert-hhR
    @RichardBH The Pycom development modules are supplied by the Vin Pin. The 3.3V Pin of the modules is the output of the internal regulator. AFAIK, this is an LM3281 device with an absolute maximum input voltage of 6V. Between the Battery plug and the Vin pin is the charge chip and some switching circuitry. They should not cause a major voltage drop. So: If you are absolutely sure that the battery voltage is never above 6V, you could connect it. But typically, the voltage of a fully charged/fresh battery is above its nominal voltage. Like: 6V Lead battery, full charged 7.2V, 1.5 V Alkaline: fresh ~1.6V, ... So you will need some means to limit or lower the input voltage.
  • 0 Votes
    1 Posts
    198 Views
    No one has replied
  • 0 Votes
    2 Posts
    326 Views
    robert-hhR
    @KiraKiraSoul said in Expansion Board 3.0 Vin (3.5-5.5V) pin: In other words, is the input voltage regulated in any way on the expansion board? No. It's the same signal, just differently labeled. When connected to USB, you should see 5V at that pin coming from USB. Otherwise you can supply a xxPy device at that pin with input voltages from 3.5-5.5 V.
  • Battery level on Pytrack/Lopy

    Projects battery pytrack battery pytrack
    5
    0 Votes
    5 Posts
    733 Views
    M
    @jcaron Perfect thanks
  • Query battery status without board

    WiPy 2&3 wipy lopy battery
    4
    0 Votes
    4 Posts
    354 Views
    robert-hhR
    @Wolli01 This is not rebuildung everything, It's just two resistors and one capacitator. Pretty simply.
  • 0 Votes
    6 Posts
    475 Views
    robert-hhR
    @Wolli01 Both SX1272 and SX1276 oprate at a range of 1.8 to 3.7 V, the esp32 at a range of 2.6 to 2.6 V. So 3.33V should not be a problem. The voltage should however be taken at the 3.3 V output of the LoPy, to be sure, that the supply arrives. But there may be short supply drops during send bursts. If you have an oscilloscope available, try to trigger for voltage drop sat the 3.3V output. The current demand for WiFI is higher than that for Lora, 250mA worst case for the ESP32 vs. 120mA worst case for the SX127x, but I doubt that these high power output modes for Lora are supported. So yes, worst case can be in the range of 500mA. Given your power consumption, battery impedance, especially at low voltage, may more be an issue than total capacity.
  • 0 Votes
    1 Posts
    281 Views
    No one has replied
  • 0 Votes
    7 Posts
    798 Views
    M
    @weingami Note that I2C level shifting is particularly easy as it uses an open drain-pullup signaling scheme. Shifting can simply be done with two FETs: https://electronics.stackexchange.com/questions/255607/i2c-level-shifting-mosfet
  • 0 Votes
    1 Posts
    310 Views
    No one has replied
  • 0 Votes
    9 Posts
    1k Views
    J
    @tvetter1976 If you use Pytrack/Pysense-controlled sleep, the PIC will power down completely the FiPy (it's not sleeping, it's completely off), stop USB, etc, and go to sleep. On a Pytrack you can choose to power down the GPS as well. Don't remember about the other sensors on the board. 3V3_Pymodule will be shut down. 3V3_Sensors can be kept on, though I don't remember if it's always on or if there's an option to shut it down as well. If you use machine.deepsleep, the FiPy will go to sleep, but I believe the Pytrack/Pysense will continue to work as usual, with everything powered. You probably need to take a few steps to reduce its power draw. Don't think there's anything in the libraries for that, you'll probably have to talk to the PIC and/or sensors directly, and I'm not sure there's a way to make the PIC go to sleep without shutting down the FiPy (though I don't know how much the PIC itself draws).
  • 0 Votes
    2 Posts
    798 Views
    J
    @lukesaber To compute your power requirements, if you are running a "wake up, send data, go back to sleep" pattern: define T as the duration in seconds of reference period of your choice (1 hour = 3600, 1 day = 86400...) define N as the number of times your device will wake up in that period define D as how long your device will we awake each time it wakes up (in seconds) define IA as the power consumption when awake (in mA, but you can use any unit as long as it's the same for IS and the result) define IS as the power consumption when sleeping (ditto) Then the average power consumption is: (N * D * IA + (T - N * D) * IS) / T Example: T = 3600 (1 hour) N = 3 (wakes up 3 times an hour) D = 10 (stays awake for 10 seconds) IA = 100 mA (average power consumption while awake) IS = 0.010 mA (10 µA, average power consumption while sleeping) Then the average power consumption is: (3 * 10 * 100 + (3600 - 3 * 10) * 0.010) / 3600 = 0.84325 mA If you want to have enough power for 2 days, then you need a battery with a 40 mAh capacity (0.84325 * 24 * 2). I think nearly any battery will do. Now, the exact figures for D, IA and IS can vary a lot, based on: what sensors/peripherals you may have that you need to power, and whether you power them all the time or only when you are awake what you need to do while awake how you send (LoRa, SigFox, LTE, Wi-Fi, BLE...), at what power level, at what data rate how long it takes for handshakes, ACKs, receive windows, etc. and probably a lot more things. Ignoring any sensors or other peripherals, while awake, the power consumption is usually somewhere between 50 mA (module active, not sending or receiving) and 200 mA (when sending). How long you stay awake will usually range between 3 and 10 seconds. Power consumption during deep sleep should be somewhere between 10 and 20 µA depending on the exact setup. So with 3 wake-ups per hour, for 2 days of battery life, your worst case scenario, not counting any sensors or peripherals, (200 mA when active, 10 seconds active, 20 µA in deep sleep) is about 80 mAh. You need to add the requirements for your sensors/peripherals on top of that. If you don't go to deep sleep for whatever reason, then the figures are drastically different, but you can keep the same logic. Just replace IS with the power consumption while idling.
  • 0 Votes
    4 Posts
    802 Views
    P
    @gda45-78 Hi, don't you have loaded a back WLAN process on the board that consume too much ? (see your post 3 months ago in your profile). regards.
  • WIPY & Battery

    WiPy 2&3 wipy 3.0 battery
    2
    0 Votes
    2 Posts
    792 Views
    J
    @tschili There's a similar issue being discussed here: https://forum.pycom.io/topic/3436/expansion-board-3-0-battery-power-not-enough-juice It seems it's related to the Expansion Board 3.0 rather than the WiPy in that case, not sure if it's the same problem you have.
  • 0 Votes
    1 Posts
    615 Views
    No one has replied
  • WiPy shutting down after a few hours

    WiPy 2&3 solar battery wipy
    9
    0 Votes
    9 Posts
    1k Views
    J
    @robert-hh The hearbeat LED flashes when the board and code are working properly. If I notice that the data is not updating, I'll go look at the board and the heartbeat LED won't be flashing. I'll hit the reset button on the board and everything will work normally again. I think I'll setup an identical rig but power the USB power port from a variable DC supply. Then I can turn the voltage down and see what happens.
  • Li-ion battery discharge

    Expansion Board battery power iot charging
    3
    0 Votes
    3 Posts
    1k Views
    sebS
    @robert-hh said in Li-ion battery discharge: bq24040 All of our boards use the same bq24040 circuit, therefore it is recommended to use batteries with a PCM to protect the battery from over discharge