Low Power: How much current? [Solved]

brolly759

YESSSSSSSSSSSSSSS!!!!! I got sleep down to 1.5ua - 1.6uA with NO hardware changes!!!!! WOOOT sorry, kinda excited here lol

scalz

great I'm happy for you.

brolly759

Okay, so originally I was getting 2.7-2.9uA with Arduino/NRF. Stock MySensors library and Arduino 1.0.6 IDE. ( I am using the BinarySwitchSleep Sketch from MySensors lib)

To get even lower power.... If you open up mysensors.cpp the sleep function is there. For the BinarySwitchSleep sketch you are looking for this sleep function as there are a few:

You want to add this:

SPI.end();	
	for (byte i = 9; i <= 13; i++)
    {
    pinMode (i, OUTPUT);    
    digitalWrite (i, LOW); 
    }  // end of for loop

to this:

bool MySensor::sleep(uint8_t interrupt, uint8_t mode, unsigned long ms) {
	// Let serial prints finish (debug, log etc)
	bool pinTriggeredWakeup = true;
	Serial.flush();
	RF24::powerDown();
	attachInterrupt(interrupt, wakeUp, mode);
	if (ms>0) {
		pinIntTrigger = 0;
		sleep(ms);
		if (0 == pinIntTrigger) {
			pinTriggeredWakeup = false;
		}
	} else {
		Serial.flush();		
		LowPower.powerDown(SLEEP_FOREVER, ADC_OFF, BOD_OFF);
	}
	detachInterrupt(interrupt);
	return pinTriggeredWakeup;
}

and it will look like this:

bool MySensor::sleep(uint8_t interrupt, uint8_t mode, unsigned long ms) {
	// Let serial prints finish (debug, log etc)
	bool pinTriggeredWakeup = true;
	Serial.flush();
	RF24::powerDown();
	attachInterrupt(interrupt, wakeUp, mode);
	
	SPI.end();
	
	for (byte i = 9; i <= 13; i++)
    {
    pinMode (i, OUTPUT);    
    digitalWrite (i, LOW); 
    }  // end of for loop

	if (ms>0) {
		pinIntTrigger = 0;
		sleep(ms);
		if (0 == pinIntTrigger) {
			pinTriggeredWakeup = false;
		}
	} else {
		Serial.flush();		
		LowPower.powerDown(SLEEP_FOREVER, ADC_OFF, BOD_OFF);
	}
	detachInterrupt(interrupt);
	return pinTriggeredWakeup;
}

Because you are shutting off and turning all pins low, you will need to add this to the beginning of your program loop to reinitialize the NRF:

void loop() 
{  
  sensor_node.begin();

If you add just the SPI.end(); your current will be 2uA.
If you add both SPI.end(); and LOW pin loop, your current will be 1.5uA

brolly759

Some more facts here:

If you ONLY do the for/loop to shut off PIN9-13 in the sleep function and do NOT shut off SPI... you do NOT need to reinitialize the radio on wake-up.

The current draw for For/Loop LOW w/o shutting off SPI is 2.1uA-2.2uA.

This is a good and bad. If you have a sensor that is going to be switched on and off a lot, the re initialization time is noticeable on a fluke meter. You can see it staying high much longer. So, if someone knows how long it takes to initialize, then we can determine if shutting off SPI is worth it. ~600nA savings vs high reconnect time.

NeverDie

@brolly759 said:

So, if someone knows how long it takes to initialize, then we can determine if shutting off SPI is worth it. ~600nA savings vs high reconnect time.

I have an o-scope, so once I get everything set up, I can try measuring that time duration for you if you like.

Really the comparison should be an energy comparison, which might be roughly::

((~600nA)(# microseconds powered-down)) vs ((arduino's current draw while powered up)(# microseconds extra setup time if NRF was turned off))

brolly759

I have an O-scope just dont know how to use it completely lol. Leaving work now. Stayed extra 2 hours to play with power settings lol

@NeverDie did you still need me to write up what I did or you followed it pretty much?

NeverDie

@brolly759 said:

I have an O-scope just dont know how to use it completely lol. Leaving work now. Stayed extra 2 hours to play with power settings lol

@NeverDie did you still need me to write up what I did or you followed it pretty much?

I'd prefer to have a nice consolidated write-up for two reasons:

So I can be sure I'm following it right. If I do it differently, then any measurements I might get won't do you much good, if any. And,
So others, including noobs, can follow along to both understand it as well as replicate it for themselves, because then you leverage the true power of open source. It's well proven: the mores eyes on something, the better it gets, and the more everyone benefits from the experience. For that to work, the clearer the "something" is, the better. The more details the better too.

OK, finished editing. :smile:

brolly759

I keep watching you edit your post, its freakin me out! lol

scalz

@Neverdie @brolly759 : I will follow your progress with interest and help if I can. For the moment, I have a lot of work before playing with my uCurrent. And for respect for Charles work, I am waiting his release. But when I will receive my boards (at then end of the month), if lib is not released yet, I will clean my code. And don't forget, I am using boosters and mosfets, so it is different. but roads are crossing of course. with booster what I like is, I will have 3.3v vcc during the whole battery life too.
Too late for me! 2am, lol. time to powerdown. See you soon:smiley:

brolly759

Running Arduino+NRF24l01 w/ interrupt consuming 1.5uA in sleep

I am using this Arduino Nano Pro 8mhz 3.3v :link text
I am using this NRF chip: link text

Here is my test environment:

Arduino Nano with desoldered jumper for bypassing voltage regulation (If you dont have bypass jumper on the knock off Nano, look at this post: link text )
NRF connected via pinout on MySensors guide
3V direct supply from 2 AA Batteries
uCurrent Gold testing voltage current
Fluke 179 reading in mV
Using the BinarySwitchSensor sketch in the MySensors library

If I upload the sketch as is with the recommended setup guide, Pin 2 or 3 is an interrupt pin and that goes to GND and acts as a switch. Pin 2/3 is HIGH and uses the internal pull up resistor. We will refer to the 2 different states of the switch as follows:

"oState" (Open, when Pin 2/3 does NOT touch GND)
"cState" (Closed, when Pin 2/3 touches GND)

When running everything I get these sleep numbers:
oState: 23-24uA
cState: 117uA

I downgraded my Arduino IDE from 1.6.5 to 1.0.6 and here are my new numbers:
oState: 2.5-2.7uA
cState: 98-100uA

Everything is looking good but my cState is still too high for any battery applications that I am trying to get.

Removed digitalWrite on pin 2/3. Connected 10M resistor from pin 2 to VCC. GND is switch to pin 2.
oState: 2.5-2.7uA
cState: 3.1-3.2uA

Reference measurements:

At this point I ran the "DallasTemperatureSensor" to test current using the WDT, I did NOT connect Temp sensor
Sleep current with WDT enabled @ 30 seconds: 7.6-7.8uA

Using "BinarySwitchSensor", remove NRF completely and only have Arduino:
Sleep current: 110-120nA OR .4-.5uA (had issues reading this but I believe it is the nA)

Connecting VCC/GND only to NRF to read standalone current:
NRF only: 800-900nA Shutdown current

Useless numbers while running the BinarySwitchSleepSensor sketch:
Sleep current: 2.7-2.9uA with NRF/Arduino fully connected
Sleep current with nRF GND disconnected: 1.7uA
Sleep current with nRF VCC and GND disconnected: 294nA
Sleep current with nRF VCC/GND/Pin9 disconnected: 281nA
Sleep current with nRF VCC/GND/P9/P10 disconnected: 196nA
Sleep current with nRF VCC/GND/P9/P10/P11/P12/P13 disconnected: 110-112nA
Sleep mode with ONLY Arduino: 110-112nA
NRF plugged into VCC/GND only: 800-900nA

At this point we are getting 2.7-2.9uA with Arduino/NRF. Stock MySensors library and Arduino 1.0.6 IDE. ( I am using the BinarySwitchSleep Sketch from MySensors lib)

To get even lower power....

Open up mysensors.cpp with NotePad++ application
Look for this code:

bool MySensor::sleep(uint8_t interrupt, uint8_t mode, unsigned long ms) {
    // Let serial prints finish (debug, log etc)
    bool pinTriggeredWakeup = true;
    Serial.flush();
    RF24::powerDown();
    attachInterrupt(interrupt, wakeUp, mode);
    if (ms>0) {
        pinIntTrigger = 0;
        sleep(ms);
        if (0 == pinIntTrigger) {
            pinTriggeredWakeup = false;
        }
    } else {
        Serial.flush();     
        LowPower.powerDown(SLEEP_FOREVER, ADC_OFF, BOD_OFF);
    }
    detachInterrupt(interrupt);
    return pinTriggeredWakeup;
}

We are going to add this code:

SPI.end();  
    for (byte i = 9; i <= 13; i++)
    {
    pinMode (i, OUTPUT);    
    digitalWrite (i, LOW); 
    }  // end of for loop

The final code should look like this:

bool MySensor::sleep(uint8_t interrupt, uint8_t mode, unsigned long ms) {
    // Let serial prints finish (debug, log etc)
    bool pinTriggeredWakeup = true;
    Serial.flush();
    RF24::powerDown();
    attachInterrupt(interrupt, wakeUp, mode);
    
    SPI.end();
    
    for (byte i = 9; i <= 13; i++)
    {
    pinMode (i, OUTPUT);    
    digitalWrite (i, LOW); 
    }  // end of for loop

    if (ms>0) {
        pinIntTrigger = 0;
        sleep(ms);
        if (0 == pinIntTrigger) {
            pinTriggeredWakeup = false;
        }
    } else {
        Serial.flush();     
        LowPower.powerDown(SLEEP_FOREVER, ADC_OFF, BOD_OFF);
    }
    detachInterrupt(interrupt);
    return pinTriggeredWakeup;
}

IMPORTANT: Because you are ending SPI, you will need to call the sensor at the beginning of your loop to reinitialize the NRF

void loop() 
{  
  sensor_node.begin();

Adding both SPI.end(); and for(); loop:
Sleep current: 1.5uA

If you add just the SPI.end();
Sleep current: 2uA

If you just add the for(); loop:
Sleep current: 1.9uA - 2.2uA

If you are using ONLY the "for(); loop", you do NOT need to reinitialize the radio when you come out of sleep. I have noticed a much longer up time when having to reinitialize.

OTHER MEASUREMENTS using the DallasTemperatureSensor with WDT at 30 seconds, no sensor connected:

Edited Sleep with for(); loop:
Sleep current: 6.4-6.5uA

Edited Sleep with for(); loop AND SPI.end();:
Sleep current: (Could not get SPI.end(); to work on sleep(w/WDT))

Quick comment: There are a few sleep options in the MySensors.cpp Depending on which one you are calling will depend on which one you need to edit. Here are some examples of the sleep functions in the .cpp file:

void MySensor::sleep(unsigned long ms)

bool MySensor::sleep(uint8_t interrupt, uint8_t mode, unsigned long ms)

int8_t MySensor::sleep(uint8_t interrupt1, uint8_t mode1, uint8_t interrupt2, uint8_t mode2, unsigned long ms)

NeverDie

@brolly759 said:

When running everything I get these sleep numbers:
oState: 23-24uA
cState: 117uA

I downgraded my Arduino IDE from 1.6.5 to 1.0.6 and here are my new numbers:
oState: 2.5-2.7uA
cState: 98-100uA

Nice write-up!

Is it known why there's a difference in the measurements depending on whether you're using IDE 1.6.5 or IDE 1.0.6? Which IDE version should I use?

brolly759

Someone else complained about the exact same issue here:
http://forum.mysensors.org/topic/1345/sensebender-micro/250

Sparkman

@brolly759 That's a different issue altogether. It's related to measuring battery voltage...

Cheers
Al

brolly759

@Sparkman said:

@brolly759 That's a different issue altogether. It's related to measuring battery voltage...

Cheers
Al

tlund posted 2 months ago reply quote 0
@tbowmo

My NRF's are the same $1 nrf's listed in the mysensors store, so probably fake. But I have still measured them to draw ~900nA in powerDown.

But I think I have found the culprint now. It seems the extra 20uA is caused by Arduino 1.6.5 (it may be that my installation is faulty).

My test setup:

pro mini
nrf
a simple sketch that does gw.sleep(60s)
1st test: sketch compiled & uploaded via Arduino 1.0.5-r2: 6uA
2nd test: sketch compiled & uploaded via Arduino 1.6.5: 24uA

Sparkman

@brolly759 Sorry, I was confused as your link is to post 250 in that thread, which is my post related to measuring battery voltage. What you are referencing is post 191: http://forum.mysensors.org/topic/1345/sensebender-micro/191

Cheers
Al

scalz

@Neverdie : at the beginning, as you were suspicious about the fact I get it. You can see here (look at the dates) that I had problems with low power and Charles helped me.
It's in french sorry : https://community.hallard.me/topic/53/question-à-propos-du-bod/30
At the same time I opened a thread on arduino forum : http://forum.arduino.cc/index.php?topic=336789.0
Another older topic that I solved myself (which contains some part of codes I was testing) : http://forum.arduino.cc/index.php?topic=336329.0
I hope you trust me now. and that I cannot I give a cake which is not finished cooking. I am not hurry. And I prefer the whole thing well packed in a lib, with derivative class, because the less the Mysensors libs are hacked inside, more beautiful it is I think. And then it is easier for users too.

@brolly759 : thank you for writing you results as I have no time for this on my side. Very strange your problem with ide. When I got low power, I was using ide 1.6.0. Maybe I will try 1.6.5 this week end to see, for curiosity. And I know Charles is using 1.6.x too. Another question, is your sensor a binaryswitchsensor only?? In this case, your way makes sense. But if you want to add sensors, you won't be able to keep 1uA without mosfet I think. Maybe I am wrong and you will find a great idea...
I follow your work, no doubt :smile:

NeverDie

@scalz said:

@Neverdie : at the beginning, as you were suspicious about the fact I get it. You can see here (look at the dates) that I had problems with low power and Charles helped me.
It's in french sorry : https://community.hallard.me/topic/53/question-à-propos-du-bod/30
At the same time I opened a thread on arduino forum : http://forum.arduino.cc/index.php?topic=336789.0
Another older topic that I solved myself (which contains some part of codes I was testing) : http://forum.arduino.cc/index.php?topic=336329.0
I hope you trust me now. and that I cannot I give a cake which is not finished cooking. I am not hurry. And I prefer the whole thing well packed in a lib, with derivative class, because the less the Mysensors libs are hacked inside, more beautiful it is I think. And then it is easier for users too.

@brolly759 : thank you for writing you results as I have no time for this on my side. Very strange your problem with ide. When I got low power, I was using ide 1.6.0. Maybe I will try 1.6.5 this week end to see, for curiosity. And I know Charles is using 1.6.x too. Another question, is your sensor a binaryswitchsensor only?? In this case, your way makes sense. But if you want to add sensors, you won't be able to keep 1uA without mosfet I think. Maybe I am wrong and you will find a great idea...
I follow your work, no doubt :smile:

@Scalz Not sure what you're referring to. I've taken what you've said at face value and still do. For the moment, if you are willing and able, it would help Broly759 and me if you would replicate Brolly759's approach (as he detailed above) and see if you can figure out why the IDE version is affecting his measurements. Which measurements are "correct"? Is that something you can help us figure out?

It would be best if we could all use the latest version number when taking measurements, unless there is good reason not to. I'm currently running IDE Version 1.6.5., and to date I haven't had problems with it. I did have some compile-time problems with some of the earlier Version 1.6 releases prior to the 1.6.5 release, but I don't recall now exactly what those problems were.

scalz

ok, I hope I will have enough time this week end because this week I have lot of work too, and Mysensors is jut fun for me. and I am running after time. It doesn't take time to reply for me, more for testings.. but I promise I will try the writeup. And I am trying to create my startup in greentech (automotive, cogeneration.. field) field. So most of my time is dedicated to my project. But I like playing too with arduino, so fun!

One thing I am sure, is when I got 140nA, it was BinarySwitch sketch too, from 2xaaa, ide 1.6.0. Then I added a BS250, to cut off nrf. And I got 140nA again in sleepmode. No problem, for sleep/wake up radio. And of course, I made the same tricks as Brolly in code. But maybe I had luck because I powered it through mosfet. Then I made same thing, BS250, for sensors, and uses BH1750 sketch. I had trouble with i2c. Charles helped me and then I got 140nA again. No problem with radio, sensors... All of this directly from 2xaaa. Then I played with boosters...
I will try brolly's case too, to see if I get same thing.
@brolly759 : you are using an arduin pin to power your nrf, am I right? to be in the same config as yours...

brolly759

GOOD MORNING crazy tinkerer's. Okay here we go again, I am actually going to need someone to verify what I am looking at here, nA and uA are giving me different readings:

Running the "for(); loop" in sleep() function with NRF VCC UNPLUGGED
Sleep current: .8uA - .9uA OR 273nA

Running the "for(); loop" in sleep() function with NRF VCC UNPLUGGED
Sleep current: .6uA - .9uA OR 114nA

@scalz I was powering the NRF directly from VCC. I will play around with connecting it directly to a pinOut on Arduino

brolly759

OKAY so... more numbers to play with... This is Arduino turning on/off NRF using an output pin.

Connect Pin4 to VCC on NRF
Add SPI.end(); and for();loop to include Pin 4 to turn LOW in sleep function

Add this code in define area:

#define WIRELESS_POWER 4

Add this code in loop():

void loop() {
  digitalWrite(WIRELESS_POWER, HIGH);
  delay(5);  
  sensor_node.begin();

Sleep current oState: .5uA - .6uA
Sleep current cState: .8uA - .9uA

@scalz Yes all my testing is on "binaryswitchsensor" sketch. I use the "DallasTempSensor" sketch when I want to test sleep() with a timer. There are SO MANY things you can do with a simple reed switch sensor. Doors, locks, windows, mailbox, fridge, cabinets, drawers... pretty much anything that moves and goes back in a certain place can be used with the "binaryswitchsensor".

Low Power: How much current? [Solved]

19

11.7k

11.2k

113.1k