Power consumption on Pytrack with SiPy
In what state are GPS and accelerometer when SiPy is put in deep sleep mode (or sleep mode) ?
I would like to put GPS in standby mode (to be able to perform quick fix), and setup accelerometer to raise interrupt on vibration (using INT1 or INT2 from LIS).
Is it possible, as libraries only do basic tasks (read GPS position, read Accelerometer value) ?
asaph last edited by
cross-referencing for relevant update (yay!)
asaph last edited by
ekwus last edited by
At least release the various schematics and information we would need to do this ourselves?
PyCom is quickly becoming great promises instead of great products. A lot of the reasons to pick your products over others are the fringe features you don't actually have but suggest you do.
Very poor and I'm sure I'm not the only one currently delaying projects and effectively loosing money after backing you as a supplier.
joeri last edited by joeri
@bucknall @daniel I'm having quite some power consumption issues with a prototype due to the accelerometer interrupt not being available. Now I need to regularly wake the board on a timer to check for movement which is not efficient.
Is there any update on a timeline for this feature to be released?
this.wiederkehr last edited by this.wiederkehr
Also eagerly (and a bit angry) waiting for this on pytrack but not to wake from deepsleep but just to have the interrupt routed to the esp32 as is shown on the pinout here:
This feature is advertised on the pinout but seems not available right now...
Also see this thread:
jcaron last edited by
@joeri The library for the Deep Sleep Shield 'wake from interrupt' is available now. Daniel is working to implementing it in the Pytrack and Pysense and will be coming shortly.
@bucknall Can you give any updates on the availability of the interrupts?
Is there an update on this topic? I was hoping to use the interrupts in a project next week.
tveito last edited by tveito
Hello, have a look at this post (tested power in deep sleep)
I have now tested on Pytrack.
After sending "$PMTK161,028\r\n" to L76, it seems that I2C scan loose 16 ID (remains [8, 30]).
Is it normal behaviour ?
Then after asking for deep_sleep (py.setup_sleep(SLEEP_TIME) and py.go_to_sleep()), is L76 still powered (so it really stay in standby) ?
Third question: are electric schematics of pytrack avail to understand a bit more what is happening ?
And is SW of PIC16LF1459 also avail ?
@Emmanuel-Goudot Yes, the interrupts are currently connected to the onboard PIC of the Pytrack, which makes it a bit more difficult to manage regarding simply connecting the accelerometer to the ESP32 interrupts. We're working on this and will let you know when it's ready!
For GPS, looking at L76GNSS.py, it seems it is possible through I2C (GPS_I2CADDR) to send command to GPS.
p.17 of Quectel doc states that:
"Sending $PMKT161,0*28 will enter into standby mode, sending any data via UART1 will make the module exit from standby mode"
Standby mode: 500µA
So I guess it is possible to do it (myself).
For accelerometer, some LIS registers will need to be setup.
But what about INT1 or INT2 connections to ESP32 on Pytrack to raise an interrupt & wake up µP (from sleep or deep sleep) ???
@Emmanuel-Goudot We'll be releasing the wake on interrupt feature for the accelerometer very soon, we're currently tweaking the way that the pytrack/pysense modules behave whilst in deep sleep mode.
Regarding the GPS, I'm currently reworking it to add increased functionality. I'll investigate the standby mode and look to implement this too.
Thanks for your patience!
I have exactly the same questions ?