I resumed this thread just to inform that Atmel confirmed that the CPS
pin of the se2431l front-end in the zigbit oem module (ATZB-A24-UFL) is
permanently pulled high, hence, the front-end never goes to sleep. A
possible workaround suggested by Atmel is the following:
In the zigbit module,pins
I don't think it should consume that much power from the CPS pin. By
the way, we're experimenting with se2431l, but we're using it for our
rfa1 based motes, here are the modified tinyos tree for the amplifier,
but I guess this doesn't give you any new information:
Thanks,
I just checked the Iris power consumption with Null app. The multimeter
displays basically 8uA with some periodical fluctuation around 45uA
(probably the averaged spikes you were talking before and that I
displayed on my oscilloscope too). Thus, the values are far below the
zigbit amp.
Thank you,
I will check Iris mote tomorrow and see whether it is as high as zigbit
amp or not.
I found the following sentence on the REB231FE2 application note (radio
extender board always from atmel and with the same frontend as the
zigbit amp):
The SE2431L operating mode is determined by
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
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
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
Yes, the async timer is running at 1024 Hz, but if you look at the
code, then you will see that its maximum sleep period is around 220
ticks (if I remember correctly), so that is why you will see these odd
times (4 times 220 then one 80) to get the 1024 ticks. Miklos
On Fri, Sep 28, 2012 at 3:01
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
You have to include the radio driver even if you do not use it since
that puts the radio into sleep mode. Miklos
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
Ok, if your Null application already includes the ActiveMessageC, then
it will turn off the radio. Then it is something else. Miklos
On Tue, Sep 25, 2012 at 9:35 AM, Ugo Colesanti
colesa...@dis.uniroma1.it wrote:
Thanks Miklos, but isn't it the ActiveMessageC component that I already
included?
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
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
13 matches
Mail list logo