Hi Ugo, Sorry, I took that picture a long time ago, I don't remember the avg. The measurement wasn't quite accurate eighter, I just wanted to show you what to except from an atmega128/1281 mote.
Andris On Sat, Sep 29, 2012 at 11:19 AM, Ugo Colesanti <colesa...@dis.uniroma1.it> wrote: > Hi, > I've used a cheap multimeter, I can check with my oscilloscope if I get > these spikes too. BTW, with the multimeter I have an avg value that shows > 1-2uA with telosb and, if I remember well, with Iris too (but I should > recheck next monday). In any case it was not as high as the zigbit amp that > steadily shows 160uA. Just to know, in your figure, what is the avg current? > > Ugo > > > > On 09/28/2012 10:01 PM, András Bíró wrote: >> >> Hi Guys, >> >> 160uA doesn't seems so much. I don't think it's the amplifier, I >> suspect the timer stack is running on your mote. As far as I remember >> the timer stack is always running on atmega128(1) based motes, and it >> consumes quite a lot of power (it's only an 8 bit counter, and the >> overflow interrupt is inaccurate, so the MCU wakes up for resetting >> the counter about 5 times in a second) >> How do you measure the power consumption? You can clearly see the >> spikes on an oscilloscope, for example this is the power consumption >> of the timer stack on iris: >> https://www.dropbox.com/s/cmidjtple52jvv5/uresj.png >> >> Andris >> >> On Tue, Sep 25, 2012 at 6:05 PM, Ugo Colesanti >> <colesa...@dis.uniroma1.it> wrote: >>> >>> Thanks Janos, >>> I already tried to change this pin but the power consumption increases >>> to approx. 5.5mA (I suppose because the amplifier is activated). >>> In particular here is what I made: >>> 1) I first modified MotePlatformP adding: >>> DDRC = 0x02 ; PORTC = 0x02 ; -> power consumption 5.5mA >>> DDRC = 0x02 ; PORTC = 0x00 ; -> power consumption 160uA >>> 2) Then I restored the MotePlatformP component and modified NullC by >>> adding the same lines in Boot.booted with same results. >>> 3) I replace those lines with GeneralO interface (it should be the same, >>> but just to be sure) and adding GeneralIO.makeOutput; GeneralIO.set() / >>> clr() , again, with same results. >>> No luck :( >>> >>> Ugo >>> >>> On 09/25/2012 04:55 PM, Janos Sallai wrote: >>>> >>>> Ugo: >>>> >>>> I think I had the same issue at one point. >>>> >>>> Try setting HplAtm128GeneralIOC.PortC1 to high. Make sure that you set >>>> it as an output pin first. >>>> >>>> Janos >>>> >>>> On Tue, Sep 25, 2012 at 3:58 AM, Ugo Colesanti >>>> <colesa...@dis.uniroma1.it> wrote: >>>>> >>>>> Hi all, >>>>> I'm using two zigbit amp with tinyos based on the latest eth code found >>>>> on the old tinyos-contrib cvs. Everything seems to work fine (I receive >>>>> and send packets even in LPL) except for one test that I'm used to >>>>> perform on new platforms: I burned the Null application (including the >>>>> ActiveMessageC component as it should be done for IRIS platforms) and >>>>> measured the current draw of the node. Based on the datasheet, the >>>>> expected current draw should be lower than 6uA but in my case I'm not >>>>> able to reach values below 160uA. I forced MCUSleep to return >>>>> ATM128_POWER_DOWN as lowest state and disabled the amplifier pulling >>>>> low >>>>> the PC1 port of the cpu but nothing changed. >>>>> I noticed that the CPS pin of the SE2413l (the front-end) stays high >>>>> which avoids the fron-end to go in sleep mode and I think that this is >>>>> the main reason of the unexpected power consumption. Unfortunately >>>>> Atmel >>>>> does not give the schematics of the ZigBit Amp and I have not been able >>>>> to pull this pin low (nor I've been able to understand how bitcloud >>>>> manages it). >>>>> Does anybody have worked on it and could help me? >>>>> >>>>> Ugo >>>>> >>>>> p.s. Janos: I've seen an old post where you say that you've worked on >>>>> that module, have you experienced the same issue? >>>>> >>>>> -- >>>>> Ugo Maria Colesanti >>>>> Dipartimento di Ingegneria Informatica, Automatica e Gestionale >>>>> "Antonio Ruberti" >>>>> Sapienza Universita' di Roma >>>>> Via Ariosto 25, I floor, room B112 >>>>> 00185, Rome >>>>> >>>>> http://wiserver.dis.uniroma1.it/cms/index.php/contacts/13-postdoc/4-ugo-colesanti >>>>> Phone: +39 06 77274119 >>>>> Fax: +39 06 77274002 >>>>> >>>>> _______________________________________________ >>>>> Tinyos-help mailing list >>>>> Tinyos-help@millennium.berkeley.edu >>>>> >>>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>>>> >>> >>> -- >>> Ugo Maria Colesanti >>> Dipartimento di Ingegneria Informatica, Automatica e Gestionale "Antonio >>> Ruberti" >>> Sapienza Universita' di Roma >>> Via Ariosto 25, I floor, room B112 >>> 00185, Rome >>> >>> http://wiserver.dis.uniroma1.it/cms/index.php/contacts/13-postdoc/4-ugo-colesanti >>> Phone: +39 06 77274119 >>> Fax: +39 06 77274002 >>> >>> _______________________________________________ >>> Tinyos-help mailing list >>> Tinyos-help@millennium.berkeley.edu >>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > > > -- > Ugo Maria Colesanti > Dipartimento di Ingegneria Informatica, Automatica e Gestionale "Antonio > Ruberti" > Sapienza Universita' di Roma > Via Ariosto 25, I floor, room B112 > 00185, Rome > http://wiserver.dis.uniroma1.it/cms/index.php/contacts/13-postdoc/4-ugo-colesanti > Phone: +39 06 77274119 > Fax: +39 06 77274002 > _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
