[riot-devel] Border Router

[Ilias Seitanidis]

Hi all,
I want to ask you if its possible and how can I use a node as a border
router but not serial connected to my PC with dist/tools/ethos, but when I
power it on to become a router and forward the received packets throught
e.g. ethernet?
Any guidelines would be really useful.
Thank you in advance!
Best,
Ilias
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Mikroelectronik lora flip and click

[Ilias Seitanidis]

Thank you very much for your reply!
--

Dear all,
I want to use the microlectronik lora flip and click with a samr21 xplained
pro board in order to transfer the ieee802.15.4 traffic over lora to the
internet.

The mikrolectronika lora flip and click is based on a microchip rn2483
module so, with this PR [1] it's certainly possible to use it with a SAM21
XPlained pro board.

Has anyone tried something like this, is this possible with riot?

I never tried that but it sounds interesting. You will have to take care of
the size and frequency of the packets you want to send via LoRaWAN. Under
certain conditions, the access to the physical layer is very limited
compared to 802.15.4.

Alex

[1] https://github.com/RIOT-OS/RIOT/pull/7505


Best regards,
Ilias

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel



___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Mikroelectronik lora flip and click

[Ilias Seitanidis]

Dear all,
I want to use the microlectronik lora flip and click with a samr21 xplained
pro board in order to transfer the ieee802.15.4 traffic over lora to the
internet. Has anyone tried something like this, is this possible with riot?
Thank you in advance!

Best regards,
Ilias
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Ethernet br with ipv6 to ipv4 module

[Ilias Seitanidis]

Hello everyone,
I want to implement the gnrc br example for a battery powered
device(openmote cc2538),without the existence of a computer , with Ethernet
support. Is it possible something like this or the br example requires to
initialize the br by using the start_networking.sh in the tools/ethos
directory? Also,  is there on riot os a ip64 module and if not is it
possible to use the ip64 module of contiki?  Thank you in advance!

Best regards,
Ilias
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] PWM Driver

[Ilias Seitanidis]

Hi Peter,
unfortunately no, in [1] I have TCC0 & TCC1 in one I define pin18 and on
the other pin19. What I tried and I would need your help is that both TCC0
 & TCC1 are using the tcc module[2], I want to try to use for one
pin(device) the tc module[3] and for the another the tcc. I tried to
replicate the static const pwm_conf_t pwm_config[] in [1] for tc, but I
received many errors. I think that this could be the solution.
Thank you in advance!

Best regards,
Ilias

[1]
https://github.com/RIOT-OS/RIOT/blob/master/boards/samr21-xpro/include/periph_conf.h#L144
[2]
https://github.com/RIOT-OS/RIOT/blob/master/cpu/sam0_common/include/vendor/samr21/include/component/tcc.h
[3]
https://github.com/RIOT-OS/RIOT/blob/master/cpu/sam0_common/include/vendor/samr21/include/component/tc.h

2017-04-25 17:45 GMT+02:00 Peter Kietzmann <peter.kietzm...@haw-hamburg.de>:

> Hi Ilias,
>
> did you already manage to get your setup working? I would recommend having
> a deeper look into the reference manual. IIRC it is not possible to
> configure the same PWM device with different frequencies, as you already
> indicated. So the question is which hardware PWM device can be configured
> in which way and run independently from others. This must be reflected in
> the peripheral configuration.
>
> Best regards
> Peter
>
>
> On 07.04.2017 15:29, Ilias Seitanidis wrote:
>
>> Hi again :)
>>
>> I am trying to produce two different frequencies on two different pins.
>> When I am trying [1] as it is but only changing the FREQU and STEPS, I
>> get the correct results.(first trial to get 19khz and second trial to
>> get 50khz)
>> However, when I duplicate the method pwm_init(pwm_t dev, pwm_mode_t
>> mode, uint32_t freq, uint16_t res),
>> in order to initialize the two pins with different freq and period at
>> the same time, I got double the freq and half the period.
>> I think that the problem is that for both pins I am using the TCC
>> devices in [2]. I created a duplicate of the pwm_config[] in [2] by only
>> changing the TCC to TC (for the second instance ) but it didn't work.
>> Any suggestions?
>>  Thank you in advance!
>>
>> Best regards,
>> Ilias
>> [1] https://github.com/RIOT-OS/RIOT/blob/master/tests/periph_pwm/main.c
>> [2] https://github.com/RIOT-OS/RIOT/blob/master/boards/samr21-
>> xpro/include/periph_conf.h
>>
>> P.S. When I tried to create at the same time the two different
>> frequencies in the main[1] I erased the for loops and I staticaly
>> used the PWM_DEV(0),PWM_DEV(1) and on the pwm_set(PWM_DEV(Y), X, state),
>> where X is the pin I need, and Y the device number 0 or 1.
>>
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
> --
> Peter Kietzmann
>
> Hamburg University of Applied Sciences
> Dept. Informatik, Internet Technologies Group
> Berliner Tor 7, 20099 Hamburg, Germany
> Fon: +49-40-42875-8426
> Web: http://www.haw-hamburg.de/inet
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] PWM Driver

[Ilias Seitanidis]

Hi again :)

I am trying to produce two different frequencies on two different pins.
When I am trying [1] as it is but only changing the FREQU and STEPS, I get
the correct results.(first trial to get 19khz and second trial to get 50khz)
However, when I duplicate the method pwm_init(pwm_t dev, pwm_mode_t mode,
uint32_t freq, uint16_t res),
in order to initialize the two pins with different freq and period at the
same time, I got double the freq and half the period.
I think that the problem is that for both pins I am using the TCC devices
in [2]. I created a duplicate of the pwm_config[] in [2] by only changing
the TCC to TC (for the second instance ) but it didn't work. Any
suggestions?
 Thank you in advance!

Best regards,
Ilias
[1] https://github.com/RIOT-OS/RIOT/blob/master/tests/periph_pwm/main.c
[2]
https://github.com/RIOT-OS/RIOT/blob/master/boards/samr21-xpro/include/periph_conf.h

P.S. When I tried to create at the same time the two different frequencies
in the main[1] I erased the for loops and I staticaly
used the PWM_DEV(0),PWM_DEV(1) and on the pwm_set(PWM_DEV(Y), X, state),
where X is the pin I need, and Y the device number 0 or 1.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Images

[Ilias Seitanidis]

Hi,
I apologise  my question was really too abstract.  Could it be possible to
use a riot device(more or less the most common devices are m3, m0)
connected to a camera( a raspi cam,  or even a usb camera)  take a picture
and forward the picture to a more powerful computer for further processing?
For example there is a windows iot with raspberry face recognition
project.  Of course I am not comparing rasp with an m3 or m0 device and
thats the reason that the processing will take place in a more powerful
machine,  but just taking a picture and forward  it.
Thank you in advance!
Best,
Ilias

On Mar 10, 2017 15:10, "Emmanuel Baccelli" <emmanuel.bacce...@inria.fr>
wrote:

> Hi Ilias,
> what do you mean by "image"?
> what do you mean by "external module"?
> If you gave a concrete example, it would help.
> Best,
> Emmanuel
>
> On Fri, Mar 10, 2017 at 9:44 AM, Ilias Seitanidis <
> iliasseitani...@gmail.com> wrote:
>
>> Dear all,
>> Is Riot capable of handling images taken by an external module and
>> transmitting them?  Of course this also depends on the hardware but I would
>> like to know thats possible at the os level.  Thank you in advance!
>>
>> Best,  Ilias
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Removed Driver

[Ilias Seitanidis]

Ok, the code removed is totaly useless or are there any parts that I can
use?(Just a question before I go over the datasheet of the ltc4150). I will
try to fix it as soon as possible, I dont know if there should also be a
PR, because with the ltc4150 device we can estimate the battery level of a
RIOT device, which seems important on IoT.

Best,
Ilias

2017-02-20 14:23 GMT+01:00 Kaspar Schleiser <kas...@schleiser.de>:

> Hi Ilias,
>
> On 02/20/2017 02:07 PM, Ilias Seitanidis wrote:
> >  I want to ask why the ltc4150 driver was removed( I will need to use it
> > and I would like to know if I should do any modifications on the
> > existing code for the ltc4150). Or is there any other new driver
> > supported by RIOT for coulomb counting or voltage meter?
>
> We've removed the driver (you've seen the PR: [1] ?) because it was not
> using our periph-based hardware abstraction, didn't even have an
> implementation for the needed board-specific code and had several other
> code quality issues, and noone found the time to fix it.
>
> We'd be happy to see an updated version!
>
> Cheers,
> Kaspar
>
> [1] https://github.com/RIOT-OS/RIOT/pull/6591
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Removed Driver

[Ilias Seitanidis]

Hi all,
 I want to ask why the ltc4150 driver was removed( I will need to use it
and I would like to know if I should do any modifications on the existing
code for the ltc4150). Or is there any other new driver supported by RIOT
for coulomb counting or voltage meter?
Thank you in advance!

Best regards,
Ilias Seitanidis
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] PWM Driver

[Ilias Seitanidis]

Thank you very much Peter!


2017-01-23 23:17 GMT+01:00 Peter Kietzmann <peter.kietzm...@haw-hamburg.de>:

> Hi Ilias,
>
> it's defined in the CMSIS header and it has the value '2':
>
> https://github.com/RIOT-OS/RIOT/blob/2c02520f73efd0b24b535f79414e43
> a0aa3f3553/cpu/sam0_common/include/cmsis/samr21/include/
> component/tcc.h#L1312
> .
>
> There is no further documentation about this single implementation. I
> guess you've already found the API description?!
>
> https://riot-os.org/api/group__drivers__periph__pwm.html
>
> In general we try to keep drivers as simple and efficient as possible.
> If you plan to implement and contribute code it might be worth to ask
> around if this kind of feature makes sense, before opening a PR that
> does not gain attraction.
>
> What is the problem with GitHub? If you need help getting started with
> git and you don't know how to contribute code, you can find help by
> searching 'git' and 'Development procedures' in our wiki.
>
> Best regards
> Peter
>
>
>
> Am 23.01.2017 um 12:15 schrieb Ilias Seitanidis:
> > Hi Peter,
> > Thank you very much for your reply, unfortunatelly I have some problems
> > with github and cannot create pr.
> > In my implementation of ([1],i) I use a parameter for the wave type, in
> the
> > Atmel documentation, the value for a normal wave is 2,
> > however I wasn't able to find in RIOT where the #define
> > TCC_WAVE_WAVEGEN_NPWM expresion for this parameter is, in order to
> validate
> > the value.  The idea is to implement as many features as possible on the
> > pwm.c. Do you know any source of documentation for this driver  Thank you
> > for your understanding :)
> >
> > Best,
> > Ilias
> >
> > [1]https://github.com/RIOT-OS/RIOT/blob/master/cpu/samd21/
> periph/pwm.c#L139
> > [i]  /* select the waveform generation mode -> normal PWM,  wave is an
> int
> > variable*/
> > _tcc(dev)->WAVE.reg = wave;
> >
> > 2017-01-23 8:53 GMT+01:00 Peter Kietzmann <peter.kietzmann@haw-hamburg.
> de>:
> >
> >> Hi Ilias,
> >>
> >> the periph_conf.h file should be the only one that you need to adapt. I
> >> didn't look it up but it might be that you need to make use of different
> >> PWM devices (TCC0 and TCC1) if you different periods and stuff. There is
> >> no need to adopt the loop in the driver. If you only want one channel
> >> per device, you can use this macro
> >>
> >> https://github.com/RIOT-OS/RIOT/blob/master/boards/
> >> samr21-xpro/include/periph_conf.h#L140
> >>
> >> and simply define one channel. Looking at the driver shows that
> >> TCC_WAVE_WAVEGEN_NPWM is not configurable:
> >>
> >> https://github.com/RIOT-OS/RIOT/blob/master/cpu/samd21/
> periph/pwm.c#L139 .
> >>
> >> Until now the "normal PWM mode" did suffice our needs. If you want that
> >> feature you should open a PR for that.
> >>
> >> Best
> >> Peter
> >>
> >>
> >> Am 20.01.2017 um 19:08 schrieb Ilias Seitanidis:
> >>> Dear all,
> >>>
> >>> I am trying to understand Riot by porting examples from Atmel
> >> Studio(SAMR21
> >>> board) to Riot( hopefully when I finish it I will upload it as a full
> >>> example of Riot with threads, GPIOs, PWM, GNRC and what ever will come
> up
> >>> on the way). Currently, I am trying to produce a waveform in an
> >> oscilosope,
> >>> I read the [1], [2], [3]. However, I would like to use only pins PA18,
> >>> PA19, BUT for each pin to set different period, waveform generation
> mode.
> >>> The first step I suppose is to define as TCC0 and TCC1 the pin PA18 and
> >>> PA19 only respectively[3]? or just use it as it is and in [2] instead
> of
> >>> having a loop for each channel, to write seperately the configuration
> for
> >>> it? I will need every possible help( i.e. where can I find the
> >>> TCC_WAVE_WAVEGEN_NPWM
> >>> value).
> >>> Thank you in advance!
> >>>
> >>> Best regards,
> >>> Ilias
> >>>
> >>> [1] https://github.com/RIOT-OS/RIOT/blob/master/tests/periph_
> pwm/main.c
> >>> [2] https://github.com/RIOT-OS/RIOT/blob/master/cpu/samd21/
> periph/pwm.c
> >>> [3]
> >>> https://github.com/RIOT-OS/RIOT/blob/master/boards/
> >> samr21-xpro/include/periph_conf.h
> >>>
> >>>
> >>>
> >>> _

Re: [riot-devel] Strange errors

[Ilias Seitanidis]

Dear all,
thank you very much for your fast reply.

Best,
Ilias
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] BIN FILES

[Ilias Seitanidis]

Thank you all for your replies!
@Ludwig I do wear glasses :)

The problem is that I have a board based on samr21 but there is no edbg usb
port, on the datasheet it mentions only
reprogramming using a usb pen drive and a .bin file, I know nothing about
the bootloader.

2016-10-07 15:45 GMT+02:00 Joakim Nohlgård <joakim.nohlg...@eistec.se>:

> If you want a binary file which is an exact byte-for-byte copy of the
> microcontroller ROM you can use objcopy to convert from ELF to raw binary.
> The RIOT build system also produces a HEX file for flashing, which is a
> plain-text variant of the raw binary.
>
> arm-none-eabi-objcopy -O binary myprog.elf myprog.bin
>
> You will not, however, need any of this manual handling for flashing the
> supported boards, `make flash` is all you need.
>
> Best regards,
> Joakim
>
> On Fri, Oct 7, 2016 at 3:35 PM, Oleg Hahm <oliver.h...@inria.fr> wrote:
>
>> Hi Ilias!
>>
>> On Fri, Oct 07, 2016 at 03:29:38PM +0200, Ilias Seitanidis wrote:
>> > Is it possible to create a bin file, which includes everything and then
>> > flash the .bin file
>> > on the board? (From what I've seen RIOT OS doesn't support this,
>> right)
>>
>> What exactly do you mean by ".bin" file? By default RIOT produces an ELF
>> [1] file
>> for most platforms that contain the full binary that is flashed onto the
>> device.
>>
>> Cheers,
>> Oleg
>>
>> [1] https://en.wikipedia.org/wiki/Executable_and_Linkable_Format
>> --
>> Chuck Norris doesn't do TCP handshake - he does TCP roundhouse-kick to
>> initiate
>> the connection.
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] RIOT and Peripherals

[Ilias Seitanidis]

Hello Rioters,
I am using a samr21 and I want to connect some peripheral devices
(one motion sensor, its connected to the pin_17 and if there is motion I
will get an 1 as input, and a speaker, I will create a frequence with the
osciloscope and then send it to the speaker). Is there any library which
takes care of these staff?? Any example or any help overall will be
appreciated. Thank you in advance!

Your Faithfully,
Ilias seitanidis
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] GNRC_NETWORKING

[Ilias Seitanidis]

Hi again,
The problem is probably on the Br,
after sending two udp messages, 4 bytes each with two minutes difference, I
am not able to see the node in the br's ncache. I am using the br of
miri64, I can't find the email where she mentioned that the br doesn't
remove records. Anyone using the br without problems?
Thank you in advance!

On Sep 21, 2016 15:56, "Ilias Seitanidis" <iliasseitani...@gmail.com> wrote:

> @ Sebastian the first one is the udp.c where I execute an interval so
> every 2 minutes I send a message. The second one is empty right now.
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] GNRC_NETWORKING

[Ilias Seitanidis]

@ Sebastian the first one is the udp.c where I execute an interval so every
2 minutes I send a message. The second one is empty right now.
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] GNRC_NETWORKING

[Ilias Seitanidis]

Thank you all for your replies,
@Sebastian, I have the loop in the udp.c and when I use the make term I see
that one of my threads is running. That's the strange thing!!!
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] GNRC_NETWORKING

[Ilias Seitanidis]

Hi all,

I am using the gnrc BR and I have another node running the gnrc_networking
example. I did some modifications on the main.c of the gnrc_networking, I
replaced  the lines 44-46 [1] with the line: _netif_config(0, NULL); .
After that I execute some threads. My question is why I cannot ping the
node running the gnrc_networking example with this modifications I did.
Moreover, I can't see the node on the ncache of the BR. I was able to ping
and see  the node in BR's ncache when I used the gnrc_networking example as
it is. Any suggestions???
Thank you in advance!

[1]
https://github.com/RIOT-OS/RIOT/blob/master/examples/gnrc_networking/main.c
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] 6LOWPAN RIOT

[Ilias Seitanidis]

Hi,
You can :
1)add an ethernet shield to the parent samr21
2)Add a record to your computer connected to your parent samr21 to route
traffic between your riot network anf the external world
3) use an 802.15.4 compatible adapter to your computer and do the(2)
On Feb 27, 2016 7:20 AM, "Giritharan"  wrote:

> Hi I am new to RIOT.
>
>  I have two SAMR21-XPRO Devices.I am using RIOT OS to
> communicate between two board.I tried RPL Routing for mesh network.I set up
> one device is parent and another is child by RPL networking.I tried this
> link
> to set up RPL (https://github.com/RIOT-OS/RIOT/wiki/Tutorial%3A-RIOT-and-
> Multi-Hop-Routing-with-RPL).As per the above link all are working fine for
> me.
> My question is i want to communicate my parent node to wifi or ethernet
> based
> devices.For that which device i can use.I think boarder router is used to
> convert ipv6 to ipv4 or vice versa.So for boarder router which device
> shall i
> use to communicate with samr21.
> I am confusing over this.Please help me to find out the right solution.
> Thanks in advance.
>
>
>
>
>
>
> With Regards,
> R.Giritharan
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] ADC

[Ilias Seitanidis]

Dear Oleg,
Thank you for your reply.
I am sorry I didn't mention that or didn't include my "include" statements,
but I took it for granted that you will know that I used "include
periph/adc.h"
as well as "include periph/gpio.h".Furthermore, I used the
"FEATURES_REQUIRED = periph_adc periph_gpio"
statement in my Makefile.
Thats the weird, I have the files in the right directories but doesn't
work.(I even copied them from the watrli branch(The cpu foder)).
Mit besten Grüßen,
Ilias

2016-02-24 16:21 GMT+01:00 Oleg Hahm <oliver.h...@inria.fr>:

> Dear Ilias,
>
> without looking into this in any detail: are you sure you have included
> "periph/adc.h"?
>
> Cheers,
> Oleg
>
> On Wed, Feb 24, 2016 at 04:19:19PM +0100, Ilias Seitanidis wrote:
> > Dear all ,
> > I want to test adc with R21 board, something already done by many people.
> > The repository I use is [1].
> > After having tried almost all adc examples I get the following output.
> >
> > /home/RIOT/examples/gnrc_networking/sensor.c: In function
> 'r21_sensor_init':
> > /home/RIOT/examples/gnrc_networking/sensor.c:6:5: error: implicit
> > declaration of function 'adc_init'
> [-Werror=implicit-function-declaration]
> >  if (adc_init(ADC_NUM, RES) == 0) {
> >  ^
> > In file included from /home/RIOT/examples/gnrc_networking/sensor.c:1:0:
> > /home/RIOT/examples/gnrc_networking/sensor.h:14:25: error:
> 'ADC_RES_12BIT'
> > undeclared (first use in this function)
> >  #define RES ADC_RES_12BIT
> >  ^
> > /home/RIOT/examples/gnrc_networking/sensor.c:6:27: note: in expansion of
> > macro 'RES'
> >  if (adc_init(ADC_NUM, RES) == 0) {
> >^
> > /home/RIOT/examples/gnrc_networking/sensor.h:14:25: note: each undeclared
> > identifier is reported only once for each function it appears in
> >  #define RES ADC_RES_12BIT
> >  ^
> > /home/RIOT/examples/gnrc_networking/sensor.c:6:27: note: in expansion of
> > macro 'RES'
> >  if (adc_init(ADC_NUM, RES) == 0) {
> >^
> > /home/RIOT/examples/gnrc_networking/sensor.c: In function 'r21_getValue':
> > /home/RIOT/examples/gnrc_networking/sensor.c:18:5: error: implicit
> > declaration of function 'adc_sample'
> [-Werror=implicit-function-declaration]
> >  *value = adc_sample(ADC_NUM, ADC_CH);
> >  ^
> > cc1: all warnings being treated as errors
> > make[1]: ***
> >
> [/home/RIOT/examples/gnrc_networking/bin/samr21-xpro/gnrc_networking/sensor.o]
> > Error 1
> > make: *** [all] Error 2
> >
> >
> > I attach my last configuration (Its from watr.li project ).
> > Thank you in advance!
> > Your Faithfully,
> > Ilias
> > [1]  https://github.com/kaspar030/RIOT/tree/ethos_br_hack
>
> > ___
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
>
>
> --
> Dprintk("oh dear, we are idle\n");
> linux-2.6.6/drivers/net/ns83820.c
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] ADC

[Ilias Seitanidis]

Dear all ,
I want to test adc with R21 board, something already done by many people.
The repository I use is [1].
After having tried almost all adc examples I get the following output.

/home/RIOT/examples/gnrc_networking/sensor.c: In function 'r21_sensor_init':
/home/RIOT/examples/gnrc_networking/sensor.c:6:5: error: implicit
declaration of function 'adc_init' [-Werror=implicit-function-declaration]
 if (adc_init(ADC_NUM, RES) == 0) {
 ^
In file included from /home/RIOT/examples/gnrc_networking/sensor.c:1:0:
/home/RIOT/examples/gnrc_networking/sensor.h:14:25: error: 'ADC_RES_12BIT'
undeclared (first use in this function)
 #define RES ADC_RES_12BIT
 ^
/home/RIOT/examples/gnrc_networking/sensor.c:6:27: note: in expansion of
macro 'RES'
 if (adc_init(ADC_NUM, RES) == 0) {
   ^
/home/RIOT/examples/gnrc_networking/sensor.h:14:25: note: each undeclared
identifier is reported only once for each function it appears in
 #define RES ADC_RES_12BIT
 ^
/home/RIOT/examples/gnrc_networking/sensor.c:6:27: note: in expansion of
macro 'RES'
 if (adc_init(ADC_NUM, RES) == 0) {
   ^
/home/RIOT/examples/gnrc_networking/sensor.c: In function 'r21_getValue':
/home/RIOT/examples/gnrc_networking/sensor.c:18:5: error: implicit
declaration of function 'adc_sample' [-Werror=implicit-function-declaration]
 *value = adc_sample(ADC_NUM, ADC_CH);
 ^
cc1: all warnings being treated as errors
make[1]: ***
[/home/RIOT/examples/gnrc_networking/bin/samr21-xpro/gnrc_networking/sensor.o]
Error 1
make: *** [all] Error 2


I attach my last configuration (Its from watr.li project ).
Thank you in advance!
Your Faithfully,
Ilias
[1]  https://github.com/kaspar030/RIOT/tree/ethos_br_hack
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] 6LOWPAN FOR SAMR21-xpro

[Ilias Seitanidis]

Hi,
You can use the gnrc_networking example for regular nodes and
the gnrc_border_router with ethos_br_hack from [1].
Best,
Ilias

[1] https://github.com/kaspar030/RIOT/tree/ethos_br_hack

2016-02-17 9:23 GMT+01:00 Giri Sugu :

> Hi,
>
>  I want to test 6lowpan in samr21-xpro using RIOT OS.
> How to find neighbour discovery?
> How to use 6LOWPAN?
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Tunslip6 in BR

[Ilias Seitanidis]

Dear all,

I followed the [1]{a} . But I get the following error:

tunslip6: serial_to_tun: write: Invalid argument
ifconfig tu323 down
netstat -nr | awk '{ if ($2 == "tu323") print "route delete -net "$1; }' |
sh


then after a small search I found this on Contiki page(Given that is ported
by Contiki):
tunslip6 -L -B 115200 -v5 -s /dev/ttyACM0 ::1/64
{b}
but still :

tunslip6: serial_to_tun: write: Invalid argument
0033.032 ifconfig tun0 down
0033.044 netstat -nr | awk '{ if ($2 == "tun0") print "route delete -net
"$1; }' | sh


The only difference was that in {b} I received that error after a few
seconds and not immediately as in {a}.


Thank you in advance!!!


[1] https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Tunslip6 in BR

[Ilias Seitanidis]

Hello Cenk,
Thank you for your reply!
I use Ubuntu 14.04 .
When I use the [1] it stops immediately so there is no fun interface when I
type ifconfig.On the other hand when I type :

tunslip6 -L -B 115200 -v5 -s /dev/ttyACM0 ::1/64, the interface exists
when I type ifconfig. With the second one I can also see some activity ,
write slip/write tun0, but after a few seconds it stops working , interface
down.
Thank you!
Best,
Ilias


On Feb 5, 2016 1:07 PM, "Cenk Gündogan" <cenk.guendo...@fu-berlin.de> wrote:

> Hello Ilias,
>
> * What kind of operating system do you use?
> * Can you verify after calling the tunslip6 tool that the tun interface
> was created successfully?
>You can verify by typing `ifconfig` or `ip a`.
>
> Best,
> Cenk
>
> On 05.02.2016 10:59, Ilias Seitanidis wrote:
>
>
> Dear all,
>
> I followed the [1]{a} . But I get the following error:
>
> tunslip6: serial_to_tun: write: Invalid argument
> ifconfig tu323 down
> netstat -nr | awk '{ if ($2 == "tu323") print "route delete -net "$1; }' |
> sh
>
>
> then after a small search I found this on Contiki page(Given that is
> ported by Contiki):
> tunslip6 -L -B 115200 -v5 -s /dev/ttyACM0 ::1/64
> {b}
> but still :
>
> tunslip6: serial_to_tun: write: Invalid argument
> 0033.032 ifconfig tun0 down
> 0033.044 netstat -nr | awk '{ if ($2 == "tun0") print "route delete -net
> "$1; }' | sh
>
>
> The only difference was that in {b} I received that error after a few
> seconds and not immediately as in {a}.
>
>
> Thank you in advance!!!
>
>
> [1]
> https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router
>
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttps://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Atmel R21

[Ilias Seitanidis]

Dear Hauke,
Thank you for your reply.
I am newbie(4months) to WSN and the first thing I saw was [1] (fan of watr)
and [2], unfortunately in both I had the same error :
tunslip6: serial_to_tun: write: Invalid argument
ifconfig tun10 down
netstat -nr | awk '{ if ($2 == "tun10") print "route delete -net "$1; }' |
sh
The only that seemed to work was Kaspar's [3] but I am not able to ping the
node(Computer->BR->Node), I read the bug list ,I changed the
fibroute,ncache entries that the ping message could be delievered and sent
back  still nothing .
Thank you!

[1]
https://github.com/RIOT-OS/RIOT/wiki/Howto:-Slip-border-router-with-Raspberry-Pi-and-samr21-xpro
[2] https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router
[3] https://github.com/RIOT-OS/RIOT/pull/4725


2016-02-04 17:45 GMT+01:00 Hauke Petersen <hauke.peter...@fu-berlin.de>:

> Hej Ilias,
>
> you could have a look at this wiki page [1] and adapt it accordingly. Hope
> that helps!
>
> Cheers,
> Hauke
>
> [1]
> https://github.com/RIOT-OS/RIOT/wiki/Howto:-Slip-border-router-with-Raspberry-Pi-and-samr21-xpro
>
>
> On 02.02.2016 15:55, Ilias Seitanidis wrote:
>
> Thank you very much now I can ping the serial interface(I used the first
> one).
> My problem now is that I cannot ping the other(wireless
> interface[interface 5]).
>
>
> 2016-02-02 10:25 GMT+01:00 Francisco Javier Acosta Padilla <
> <francisco.aco...@inria.fr>francisco.aco...@inria.fr>:
>
>> Hi Ilias!
>>
>> There are work in progress on the BR right now.
>>
>> You can look at [1] in order to get a version of a BR using only one
>> serial connection.
>>
>> Otherwise you can try the "classical" way which is to use another serial
>> interface on the R21 and a SLIP connection. You can find more details
>> here [2].
>>
>> Best,
>>
>> Francisco.
>>
>> [1] https://github.com/RIOT-OS/RIOT/pull/4725
>> [2]
>> https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router
>>
>>
>> On Tue, 2016-02-02 at 10:13 +0100, Ilias Seitanidis wrote:
>> > Dear all!
>> > After following all the tutorials on the net for Atmel R21 as BR in Riot
>> > ,with serial connection , I cannot ping the Inteface 6 of the BR, which
>> is
>> > the interface from both linux and R21.Any suggestions?
>> > Thank you in advance!
>> > ___
>> > devel mailing list
>> > devel@riot-os.org
>> > https://lists.riot-os.org/mailman/listinfo/devel
>>
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttps://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Atmel R21

[Ilias Seitanidis]

Thank you very much now I can ping the serial interface(I used the first
one).
My problem now is that I cannot ping the other(wireless interface[interface
5]).


2016-02-02 10:25 GMT+01:00 Francisco Javier Acosta Padilla <
francisco.aco...@inria.fr>:

> Hi Ilias!
>
> There are work in progress on the BR right now.
>
> You can look at [1] in order to get a version of a BR using only one
> serial connection.
>
> Otherwise you can try the "classical" way which is to use another serial
> interface on the R21 and a SLIP connection. You can find more details
> here [2].
>
> Best,
>
> Francisco.
>
> [1] https://github.com/RIOT-OS/RIOT/pull/4725
> [2]
> https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_border_router
>
>
> On Tue, 2016-02-02 at 10:13 +0100, Ilias Seitanidis wrote:
> > Dear all!
> > After following all the tutorials on the net for Atmel R21 as BR in Riot
> > ,with serial connection , I cannot ping the Inteface 6 of the BR, which
> is
> > the interface from both linux and R21.Any suggestions?
> > Thank you in advance!
> > ___
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] Atmel R21

[Ilias Seitanidis]

Dear all!
After following all the tutorials on the net for Atmel R21 as BR in Riot
,with serial connection , I cannot ping the Inteface 6 of the BR, which is
the interface from both linux and R21.Any suggestions?
Thank you in advance!
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] SamR21 Not using the build in radio

[Ilias Seitanidis]

Thank you very much Hauke !!!

2016-01-26 15:52 GMT+01:00 Hauke Petersen <hauke.peter...@fu-berlin.de>:

> Hi Ilias,
>
> for you GPRS device you need to implement a device driver (which should
> implement the netdev2 interface to be able to integrate with out network
> stack(s).
>
> Roughly you then need to do the following:
> For not using the build in radio, you don't have to change anything in the
> code, all you need to do is not use the `USEMODULE=netif_default` in your
> applications Makefile... Instead you then simply tell the make system to
> use your GPRS device (something like `USEMODULE=your_driver_name`) and add
> auto-initialization code for your device to sys/auto-init/netif/.
>
> Cheers,
> Hauke
>
>
>
>
> On 25.01.2016 14:50, Ilias Seitanidis wrote:
>
> Dear all,
> I want to use the sam R21 Xpro with a GPRS plugin (Some friends from the
> electronics department will take care of the hardware connectivity). What
>  changes should I perform to the Riot code?
> Thank you in advance!
>
>
> ___
> devel mailing 
> listdevel@riot-os.orghttps://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] SamR21 Not using the build in radio

[Ilias Seitanidis]

Dear all,
I want to use the sam R21 Xpro with a GPRS plugin (Some friends from the
electronics department will take care of the hardware connectivity). What
 changes should I perform to the Riot code?
Thank you in advance!
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] drivers/SAUL

[Ilias Seitanidis]

Dear all ,
I would like to ask you if there is any example of the drivers/saul .
Thank you in advance!
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] RIOT RELEASE 2015.12

[Ilias Seitanidis]

Dear all,
I would like to know if the IEEE 802.15.4e is supported in the RIOT RELEASE
2015.12. Thank you in advance!
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] RIOT RELEASE 2015.12

[Ilias Seitanidis]

Thank you very much Oleg!

2016-01-13 12:40 GMT+01:00 Oleg Hahm <oliver.h...@inria.fr>:

> Dear Ilias!
>
> On Wed, Jan 13, 2016 at 11:39:56AM +0100, Ilias Seitanidis wrote:
> > I would like to know if the IEEE 802.15.4e is supported in the RIOT
> RELEASE
> > 2015.12. Thank you in advance!
>
> Currently IEEE 802.15.4e (aka TSCH mode in IEEE 802.15.4-2015) is only
> supported by the OpenWSN package [1], but Thomas Eichinger, Tengfei Chang,
> and I are working on cutting out the TSCH part from the OpenWSN stack as a
> standalone MAC protocol for RIOT. If you're interested you could take a
> look
> at Thomas' WIP corresponding branch:
> https://github.com/ThomasEichinger/RIOT/tree/riot-6tisch
>
> Cheers,
> Oleg
>
> [1] https://github.com/RIOT-OS/RIOT/tree/master/pkg/openwsn
> --
> If no space is available nothing happens.
> RIOT/sys/net/include/pktbuf.h
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Guide to add Ethernet 1 Xpro support to RIOT

[Ilias Seitanidis]

Does anyone have used the encx24j600?


2015-10-30 10:42 GMT+01:00 Ilias Seitanidis <iliasseitani...@gmail.com>:

> Hello, I would like to add support for Ethernet 1 Xpro  module on Riot,
> what should I consider?Should I follow the encx24j600 driver?
> Thank you!
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

[riot-devel] CoAP

[Ilias Seitanidis]

Hi ! To use CoAP in my R21 boards should I rite the code of socket
programming (open a udp port ,etc) or just use the coap library and it
takes care about the socket?
Thank you in advance!!!
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] CoAP

[Ilias Seitanidis]

2015-10-29 15:32 GMT+01:00 Baptiste Clenet :

> Hi Lennart,
>
> >Also, you'd probably have to port it to RIOT first
> Just to let you know, libcoap has already been ported to RIOT (as a
> pkg as microcoap) [1]
> Yes it does network registering automatically but I don't if this port
> does it with the new network stack, need testing.
>
> [1] https://github.com/RIOT-OS/RIOT/tree/master/pkg/libcoap
>
> 2015-10-29 15:19 GMT+01:00 Lennart Dührsen  >:
> > Hi Ilias,
> >
> >> To use CoAP in my R21 boards should I rite the code of socket
> >> programming (open a udp port ,etc) or just use the coap library and it
> >> takes care about the socket?
> >
> > all the microcoap library does is create and parse payloads (CoAP
> > packets), and it let's you register callback functions for each URI.
> >
> > You have to handle all the networking stuff, i.e. sending and receiving
> > UDP packets, yourself.
> >
> > I'm currently working on the mostly absent documentation of microcoap,
> > you can find it in this fork:
> >
> > https://github.com/i2ot/microcoap
> >
> > It's not finished yet, but it might help you. For the networking stuff
> > on RIOT OS, check out
> >
> > https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking
> >
> > and
> >
> > https://github.com/RIOT-OS/RIOT/tree/master/examples/posix_sockets
> >
> > if you haven't already done so.
> >
> > The example code Baptiste pointed you to is indeed out of date, but the
> > CoAP parts in it are still correct and should work, so you'd just have
> > to change the socket calls etc.
> >
> > Regarding libcoap: It's a *lot* more code than microcoap, and yes, it
> > does all the socket stuff for you. But its documentation, too, is pretty
> > much nonexistent. Also, you'd probably have to port it to RIOT first, so
> > I suggest you use microcoap for devices that will run RIOT OS.
> >
> > If you run into problems with microcoap, feel free to send me an e-mail.
> >
> > Best,
> > Lennart
> > ___
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> --
> Baptiste
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] CoAP

[Ilias Seitanidis]

I am used to testing, It would be my pleasure.
Debugging since 2013 on android :)

2015-10-29 15:34 GMT+01:00 Ilias Seitanidis <iliasseitani...@gmail.com>:

>
>
> 2015-10-29 15:32 GMT+01:00 Baptiste Clenet <bapcle...@gmail.com>:
>
>> Hi Lennart,
>>
>> >Also, you'd probably have to port it to RIOT first
>> Just to let you know, libcoap has already been ported to RIOT (as a
>> pkg as microcoap) [1]
>> Yes it does network registering automatically but I don't if this port
>> does it with the new network stack, need testing.
>>
>> [1] https://github.com/RIOT-OS/RIOT/tree/master/pkg/libcoap
>>
>> 2015-10-29 15:19 GMT+01:00 Lennart Dührsen <lennart.duehr...@fu-berlin.de
>> >:
>> > Hi Ilias,
>> >
>> >> To use CoAP in my R21 boards should I rite the code of socket
>> >> programming (open a udp port ,etc) or just use the coap library and it
>> >> takes care about the socket?
>> >
>> > all the microcoap library does is create and parse payloads (CoAP
>> > packets), and it let's you register callback functions for each URI.
>> >
>> > You have to handle all the networking stuff, i.e. sending and receiving
>> > UDP packets, yourself.
>> >
>> > I'm currently working on the mostly absent documentation of microcoap,
>> > you can find it in this fork:
>> >
>> > https://github.com/i2ot/microcoap
>> >
>> > It's not finished yet, but it might help you. For the networking stuff
>> > on RIOT OS, check out
>> >
>> > https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking
>> >
>> > and
>> >
>> > https://github.com/RIOT-OS/RIOT/tree/master/examples/posix_sockets
>> >
>> > if you haven't already done so.
>> >
>> > The example code Baptiste pointed you to is indeed out of date, but the
>> > CoAP parts in it are still correct and should work, so you'd just have
>> > to change the socket calls etc.
>> >
>> > Regarding libcoap: It's a *lot* more code than microcoap, and yes, it
>> > does all the socket stuff for you. But its documentation, too, is pretty
>> > much nonexistent. Also, you'd probably have to port it to RIOT first, so
>> > I suggest you use microcoap for devices that will run RIOT OS.
>> >
>> > If you run into problems with microcoap, feel free to send me an e-mail.
>> >
>> > Best,
>> > Lennart
>> > ___
>> > devel mailing list
>> > devel@riot-os.org
>> > https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>>
>> --
>> Baptiste
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Energy Consumption on samr21_xpro

[Ilias Seitanidis]

Is it possible to guide me on porting it to r21?
Thank you!


2015-10-28 12:46 GMT+01:00 Kaspar Schleiser <kas...@schleiser.de>:

> Hey,
>
> On 10/28/15 12:28, Ilias Seitanidis wrote:
> > Did anyone tried Battery gas gauge: Linear Technology LTC4150 Coulomb
> > Counter on R21 board or at any other board?
>
> FU-Berlin's msba2 boards have those on-board. They work quite well. We
> dropped the driver some time ago as it was based on obsolete SPI
> interfaces, but it should be in the history, and can probably be adapted
> easily.
>
> Kaspar
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Energy Consumption on samr21_xpro

[Ilias Seitanidis]

Hi again!
Did anyone tried Battery gas gauge: Linear Technology LTC4150 Coulomb
Counter on R21 board or at any other board?
Thank you!

2015-10-27 11:13 GMT+01:00 Ilias Seitanidis <iliasseitani...@gmail.com>:

> Thank you all for your replies!!! :)
> @Hauke Is there a way to measure at least MCU+radio with software without
> using any external tool?
> Thank you in advance!
>
> 2015-10-26 16:15 GMT+01:00 Baptiste Clenet <bapcle...@gmail.com>:
>
>> @Hauke, we add some results around 1,62mA some months ago [0]
>>
>> Cheers,
>>
>> Baptiste
>>
>> [0] https://github.com/RIOT-OS/RIOT/pull/2309
>>
>>
>> 2015-10-26 11:24 GMT+01:00 Hauke Petersen <hauke.peter...@fu-berlin.de>:
>> > Hi,
>> >
>> > if you decide to measure the energy consumption through those external
>> pins,
>> > keep in mind, that you are measuring the consumption of the complete
>> board -
>> > not only the MCU+radio. Last time I tried, I always got something around
>> > 100mA. This is fairly high for this kind of board (the STM32F4discovery
>> was
>> > around ~15mA for the full board). Not sure where this high consumption
>> comes
>> > from - but maybe you can measure your board and share your results with
>> us?
>> >
>> > Cheers,
>> > Hauke
>> >
>> >
>> >
>> > On 26.10.2015 10:59, Baptiste Clenet wrote:
>> >>
>> >> @Illias, the current monitor header pins are the only way I know to
>> >> measure the current consumption. If you see a better way to do that,
>> >> It would be great to try it, let us know.
>> >>
>> >> Baptiste
>> >>
>> >> 2015-10-23 11:37 GMT+02:00 Peter Kietzmann
>> >> <peter.kietzm...@haw-hamburg.de>:
>> >>>
>> >>> Hi Ilias,
>> >>>
>> >>> I'd love to have such possibility, but from my knowledge there is no
>> >>> coulomb
>> >>> counter (or similar) on that board or on any common hardware. If you
>> find
>> >>> a
>> >>> way, please let me know :-) !
>> >>>
>> >>> Cheers,
>> >>> Peter
>> >>>
>> >>> Am 23.10.2015 um 11:31 schrieb Ilias Seitanidis:
>> >>>
>> >>> Hi Peter,
>> >>> First of all I want to thank you for your fast reply.I want to measure
>> >>> the
>> >>> energy consumption from the board using software without external
>> tools
>> >>> as
>> >>> an ammeter.
>> >>> Thank you.
>> >>> Best ,
>> >>> Ilias
>> >>>
>> >>> 2015-10-23 11:22 GMT+02:00 Peter Kietzmann
>> >>> <peter.kietzm...@haw-hamburg.de>:
>> >>>>
>> >>>> Hi Ilias,
>> >>>>
>> >>>> and welcome to RIOT! This board has a jumper on it's current monitor
>> >>>> header pins (next to the user programmable button). You can replace
>> the
>> >>>> jumper by an ammeter and measure the current. Compare the boards user
>> >>>> guide
>> >>>>
>> >>>>
>> http://www.atmel.com/Images/Atmel-42243-SAMR21-Xplained-Pro_User-Guide.pdf
>> >>>>
>> >>>> Best,
>> >>>> Peter
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> Am 23.10.2015 um 11:07 schrieb Ilias Seitanidis:
>> >>>>
>> >>>> Hi , I am new to wsn and I am wondering if there is a way to measure
>> the
>> >>>> energy consumption of the atmel samr21_xpro .Thank you in advance!
>> >>>>
>> >>>>
>> >>>> ___
>> >>>> devel mailing list
>> >>>> devel@riot-os.org
>> >>>> https://lists.riot-os.org/mailman/listinfo/devel
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Peter Kietzmann
>> >>>>
>> >>>> Hamburg University of Applied Sciences
>> >>>> Dept. Informatik, Internet Technologies Group
>> >>>> Berliner Tor 7, 20099 Hamburg, Germany
>> >>>> Fon: +49-40-42875-8426
>> >>>> Web: http://www.haw-hamburg.de/inet
>> >>>>
>> >>>>
>> >>>> ___
>> >>>> devel mailing list
>> >>>> devel@riot-os.org
>> >>>> https://lists.riot-os.org/mailman/listinfo/devel
>> >>>>
>> >>>
>> >>>
>> >>> ___
>> >>> devel mailing list
>> >>> devel@riot-os.org
>> >>> https://lists.riot-os.org/mailman/listinfo/devel
>> >>>
>> >>>
>> >>> --
>> >>> Peter Kietzmann
>> >>>
>> >>> Hamburg University of Applied Sciences
>> >>> Dept. Informatik, Internet Technologies Group
>> >>> Berliner Tor 7, 20099 Hamburg, Germany
>> >>> Fon: +49-40-42875-8426
>> >>> Web: http://www.haw-hamburg.de/inet
>> >>>
>> >>>
>> >>> ___
>> >>> devel mailing list
>> >>> devel@riot-os.org
>> >>> https://lists.riot-os.org/mailman/listinfo/devel
>> >>>
>> >>
>> >>
>> >
>> > ___
>> > devel mailing list
>> > devel@riot-os.org
>> > https://lists.riot-os.org/mailman/listinfo/devel
>>
>>
>>
>> --
>> Baptiste
>> ___
>> devel mailing list
>> devel@riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
>
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

Re: [riot-devel] Energy Consumption on samr21_xpro

[Ilias Seitanidis]

Thank you all for your replies!!! :)
@Hauke Is there a way to measure at least MCU+radio with software without
using any external tool?
Thank you in advance!

2015-10-26 16:15 GMT+01:00 Baptiste Clenet <bapcle...@gmail.com>:

> @Hauke, we add some results around 1,62mA some months ago [0]
>
> Cheers,
>
> Baptiste
>
> [0] https://github.com/RIOT-OS/RIOT/pull/2309
>
>
> 2015-10-26 11:24 GMT+01:00 Hauke Petersen <hauke.peter...@fu-berlin.de>:
> > Hi,
> >
> > if you decide to measure the energy consumption through those external
> pins,
> > keep in mind, that you are measuring the consumption of the complete
> board -
> > not only the MCU+radio. Last time I tried, I always got something around
> > 100mA. This is fairly high for this kind of board (the STM32F4discovery
> was
> > around ~15mA for the full board). Not sure where this high consumption
> comes
> > from - but maybe you can measure your board and share your results with
> us?
> >
> > Cheers,
> > Hauke
> >
> >
> >
> > On 26.10.2015 10:59, Baptiste Clenet wrote:
> >>
> >> @Illias, the current monitor header pins are the only way I know to
> >> measure the current consumption. If you see a better way to do that,
> >> It would be great to try it, let us know.
> >>
> >> Baptiste
> >>
> >> 2015-10-23 11:37 GMT+02:00 Peter Kietzmann
> >> <peter.kietzm...@haw-hamburg.de>:
> >>>
> >>> Hi Ilias,
> >>>
> >>> I'd love to have such possibility, but from my knowledge there is no
> >>> coulomb
> >>> counter (or similar) on that board or on any common hardware. If you
> find
> >>> a
> >>> way, please let me know :-) !
> >>>
> >>> Cheers,
> >>> Peter
> >>>
> >>> Am 23.10.2015 um 11:31 schrieb Ilias Seitanidis:
> >>>
> >>> Hi Peter,
> >>> First of all I want to thank you for your fast reply.I want to measure
> >>> the
> >>> energy consumption from the board using software without external tools
> >>> as
> >>> an ammeter.
> >>> Thank you.
> >>> Best ,
> >>> Ilias
> >>>
> >>> 2015-10-23 11:22 GMT+02:00 Peter Kietzmann
> >>> <peter.kietzm...@haw-hamburg.de>:
> >>>>
> >>>> Hi Ilias,
> >>>>
> >>>> and welcome to RIOT! This board has a jumper on it's current monitor
> >>>> header pins (next to the user programmable button). You can replace
> the
> >>>> jumper by an ammeter and measure the current. Compare the boards user
> >>>> guide
> >>>>
> >>>>
> http://www.atmel.com/Images/Atmel-42243-SAMR21-Xplained-Pro_User-Guide.pdf
> >>>>
> >>>> Best,
> >>>> Peter
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Am 23.10.2015 um 11:07 schrieb Ilias Seitanidis:
> >>>>
> >>>> Hi , I am new to wsn and I am wondering if there is a way to measure
> the
> >>>> energy consumption of the atmel samr21_xpro .Thank you in advance!
> >>>>
> >>>>
> >>>> ___
> >>>> devel mailing list
> >>>> devel@riot-os.org
> >>>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>>
> >>>>
> >>>> --
> >>>> Peter Kietzmann
> >>>>
> >>>> Hamburg University of Applied Sciences
> >>>> Dept. Informatik, Internet Technologies Group
> >>>> Berliner Tor 7, 20099 Hamburg, Germany
> >>>> Fon: +49-40-42875-8426
> >>>> Web: http://www.haw-hamburg.de/inet
> >>>>
> >>>>
> >>>> ___
> >>>> devel mailing list
> >>>> devel@riot-os.org
> >>>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>>
> >>>
> >>>
> >>> ___
> >>> devel mailing list
> >>> devel@riot-os.org
> >>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>
> >>>
> >>> --
> >>> Peter Kietzmann
> >>>
> >>> Hamburg University of Applied Sciences
> >>> Dept. Informatik, Internet Technologies Group
> >>> Berliner Tor 7, 20099 Hamburg, Germany
> >>> Fon: +49-40-42875-8426
> >>> Web: http://www.haw-hamburg.de/inet
> >>>
> >>>
> >>> ___
> >>> devel mailing list
> >>> devel@riot-os.org
> >>> https://lists.riot-os.org/mailman/listinfo/devel
> >>>
> >>
> >>
> >
> > ___
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
>
>
>
> --
> Baptiste
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel