12hr Sleep doesn't wake up

NeilE · September 12, 2018, 6:56am

Hi,

I am trying to get the MKR to report it'a battery voltage every twelve hours using the LowPower.sleep() function. i.er when it wakes up the default thing to do is report voltage.

In testing for short periods using LowPower.sleep(5 * 60 * 1000); it sleeps for exactly 5 mins no problem.

If I use LowPower.sleep(12 * 60 * 60 * 1000); it never wakes up.

Is there an upper limit to the timed interupt?

sslupsky · September 13, 2018, 2:20pm

There is something weird with the compile of this call. If you use L to implicitly declare a long number (ie: 30000L) the compiler throws an error. I do not understand why it throws the error.

Try this:

uint32_t sleepTime;
sleepTime = 12 * 60 * 60 * 1000;
println( sleepTime );
delay(1000);
LowPower.sleep( sleepTime );

And verify that the sleepTime being passed is correct.

NeilE · September 16, 2018, 3:26pm

Ok I can resolve this. The wake up works fine, it was the Multitech Conduit failing to pass the packet on.

sslupsky · September 16, 2018, 7:14pm

Hi NeilE, Were you able to get sleep current below 1.16mA on the MKR WAN 1300?

NeilE · September 18, 2018, 6:23am

Hi sslupsky,

No and i tried many combinations. It measures about 1158uA at best. I saw your other post saying that this a now a recognised issue with the version of the board. So good and bad news.

I was trying to do the firmware upgrade. I am on 1.12 (all 12 modules) and I see v1.16 is out there. I tried to load the MKRWAN.h example stand alone firmware updater but it won't compile as published so i got stuck.

Have you got this to work by any chance?

Thanks

sslupsky · September 18, 2018, 2:34pm

Hi NeilE, I was able to update the firmware using the sketch MKRWANFWUpdate_standalone.ino. Did you have all the files from that directory when you tried to compile the sketch?

sslupsky · September 18, 2018, 6:28pm

Hi NeilE,

It gets worse. I have not been able to get below 1.05mA in sleep with the VDD_TCXO modification. Moreover, I have uncovered some design problems with the MKRWAN power supply.

I cross posted the following observations on the Github MKRWAN issue in case anyone else is following this at:

github.com/arduino-libraries/MKRWAN

High sleep current

opened 07:29PM - 14 Sep 18 UTC

sslupsky

type: imperfection

Hello, I've been working with the MKRWAN1300 and evaluating the sleep performan…ce. I believe I have successfully achieved sleep. However the sleep current is 1.16mA. Is it possible to achieve a sleep current with the MKRWAN1300 of less than 1.16mA? I have found community reports for other SAMD21 products that achieve a lower sleep current. However, I have not found a report that confirms a sleep current less than 1.16mA for the MKRWAN1300 is achievable. My hardware configuration is 3.3V power is applied to the Vbatt input. USB is disconnected. A0 (DAC output) is connected to A1 (ADC input). At the moment I suspect a bug in the MKRWAN firmware preventing the Murata device from sleeping properly but I haven't found anything yet. Wiring.c in the Arduino library was updated to remove initialization of the IO as floating inputs. I have attached my sketch below for reference. ``` #include <Arduino.h> #include <ArduinoLog.h> #include <ArduinoLowPower.h> #include <MKRWAN.h> #include <ZeroRegs.h> #include <RTCZero.h> #include "arduino_secrets.h" #define SLEEP_PERIOD ( (uint32_t) 5000 ) // ADC configuration #define extSensorPin PIN_A1 #define extSensorEnablePin 1 LoRaModem modem; static uint32_t msgCount = 0; bool regsShown = false; // RTCZero rtc; // Uncomment if using the Murata chip as a module // LoRaModem modem(Serial1); // Please enter your sensitive data in the Secret tab or arduino_secrets.h String appEui = SECRET_APP_EUI; String appKey = SECRET_APP_KEY; void blink( int numBlink = 1, unsigned int speed = 200 ) { int i; while ( numBlink-- ) { digitalWrite(LED_BUILTIN, HIGH); // turn the LED on (HIGH is the voltage level) delay(speed); // wait digitalWrite(LED_BUILTIN, LOW); // turn the LED off by making the voltage LOW delay(speed); // wait } } void printTimeStamp(Print* _logOutput) { char c[12]; int m = sprintf(c, "%10lu ", millis()); _logOutput->print(c); } void printNewline(Print* _logOutput) { _logOutput->print('\n'); } void reboot() { NVIC_SystemReset(); while(1) ; } void pinStr( uint32_t ulPin, unsigned strength) // works like pinMode(), but to set drive strength { // Handle the case the pin isn't usable as PIO if ( g_APinDescription[ulPin].ulPinType == PIO_NOT_A_PIN ) { return ; } if(strength) strength = 1; // set drive strength to either 0 or 1 copied PORT->Group[g_APinDescription[ulPin].ulPort].PINCFG[g_APinDescription[ulPin].ulPin].bit.DRVSTR = strength ; } void InitIO() { // Note: wiring.c initializes all GPIO as inputs with no pull ups ... it has been modified to eliminate this // Configure digital pins used by the application pinMode(LED_BUILTIN, OUTPUT); pinMode(extSensorPin, OUTPUT); pinStr(extSensorPin, 1); digitalWrite(extSensorEnablePin, LOW); // Configure the ADC analogReadResolution(12); analogWriteResolution(12); analogReference(AR_INTERNAL1V65); } void alarmEvent() { // RTC alarm wake interrupt callback // do nothing } void setup() { Log.begin(LOG_LEVEL_VERBOSE, &Serial, true); InitIO(); Serial.begin(115200); int waitForSerial = 5; while (!Serial && !Serial.available() && waitForSerial ) { delay(2000); blink(2); waitForSerial--; } Log.notice(F("Start" CR)); // initialize the RTC - need to do this or the sleep function is unreliable after reset // rtc.begin(false); LowPower.attachInterruptWakeup(RTC_ALARM_WAKEUP, alarmEvent, CHANGE); // Log.notice(F("Reset modem ..." CR)); // modem.restart(); // This does not work for some reason Log.notice(F("Initialize modem ..." CR)); if (!modem.begin(US915_HYBRID)) { Log.error(F("Failed to start module, rebooting MKRWAN in 1 seconds ..." CR)); delay(1000); reboot(); }; Log.notice(F("Your module version is: %s" CR), modem.version().c_str()); Log.notice(F("Your device EUI is: %s" CR), modem.deviceEUI().c_str()); int connected = modem.connected(); if ( !connected ) { int joinFailed = 0; while ( !connected && joinFailed < 10 ) { connected = modem.joinOTAA(appEui, appKey); if (!connected) { Log.notice(F("LoRaWAN network not joined, retry join in 60 seconds ..." CR)); blink(1); delay(60000); joinFailed++; } } } if ( connected ) { Log.notice(F("LoRaWAN network joined" CR)); modem.setPort(10); modem.dataRate(3); modem.setADR(true); blink(3); } } void loop() { blink(3); Log.notice(F("Wake" CR)); // Dump SAMD21 registers if ( Serial ) { if (! regsShown ) { ZeroRegOptions opts = { Serial, false }; printZeroRegs(opts); regsShown = true; } } else { regsShown = false; } digitalWrite(extSensorEnablePin, HIGH); analogWrite(PIN_A0, 1024); // apply voltage to DAC to test analog input delay(10); int extSensor = analogRead(extSensorPin); digitalWrite(extSensorEnablePin, LOW); int err; String msg = "Sleep Test:" + String(msgCount) + ":" + String(extSensor); modem.beginPacket(); modem.print(msg); err = modem.endPacket(true); if (err > 0) { Log.notice(F("LoRa message sent: %l, vwc = 0x%x" CR), msgCount, extSensor); msgCount++; blink(2); } else { Log.notice(F("LoRa error sending message: %l, vwc = 0x%x" CR), msgCount, extSensor); blink(1); } delay(1000); blink(3); LowPower.deepSleep(SLEEP_PERIOD); } ```

There is another problem(s) with the MKRWAN1300 design.

Having investigated the issue regarding the VDD_TCXO, I encountered erratic behaviour when power was applied to the Vbatt or VCC pins on the MKRWAN.

Looking at the power supply schematic for the MKRWAN, the VDD_USB pin of the Murata module is connected to the +5V net of the MKRWAN module. When the MKRWAN is connected to a computer USB port, the voltage of than net will be close to 5V. This voltage exceeds the maximum operating voltage of the VDD_USB pin (see Murata datasheet Table 2 - 3.6V) for the Murata module. The voltage also exceeds the Absolute Maximum Ratings for the pin (see Murata datasheet Table 1 - 3.9V). Thus, simply plugging the MKRWAN into a USB port will likely damage the Murata module.

Moreover, note 1 under Table 2 of the Murata datasheet reads, in part, that:

If the USB is not used, VDD_USB must be tied to VDD_MCU to be able to use PA11 and PA12 as standard I/Os.

When power is applied to the MKRWAN Vbatt or VCC, VDD_USB is floating and thus violates condition of note 1. So, PA12 cannot be used to control VDD_TCXO in this condition.

sslupsky · September 18, 2018, 7:54pm

Hi NeilE,

Good news. When I corrected the VDD_USB issue by disconnecting it from the +5V net and attaching to the +3.3V net, the sleep current is about 8.5uA.

NeilE · September 19, 2018, 10:00am

@sslupsky Well done, great work there.

I read your github page from the link above and I roughly follow it. It looks like a two step process

a) you cut/break the connection for VDD_TCXO
b) swap the connection to VDD_MCU from the 5V to the 3.3V feeds.

I can follow that on the schematic but I can't relate that to the physical v1 (since v2 is coming) board.

Any chance you could summarise your process (pics would be very usefull) of the mods to the board?

Cheers.

sslupsky · September 19, 2018, 5:02pm

Hi NeilE,

Here are the instructions to do the mods and a photo.

Regarding the VDD_TCXO modification, in my opinion the best method is Option 2 that involves using a laser if you have access to one. With Option 1, there isn't much space between the via and the Murata module to solder a wire to the trace after you drill the via.

tcxo and usb repair v3.pdf (1.38 MB)

Topic		Replies	Views
MKRWAN 1310 is not waking up MKRWAN1310	2	1062	August 14, 2021
MKR 1300 power consumption too hight MKRWAN1300	7	4524	May 7, 2021
MKR1200 low power issue MKRFOX1200	1	5366	May 7, 2021
MKR1300 does not wake up IDE 1.x	1	474	May 5, 2021
MKR Zero Board Sleep Mode Arduino Zero	7	7358	May 6, 2021

12hr Sleep doesn't wake up

Related Topics