Re: [riot-devel] Radio duty cycling
Hi Joakim, What is the current state of radio duty cycling in RIOT? I know that radio drivers implement on and off functions for the chip, but how do we make the best use of them? In order to reduce power consumption it will be necessary to duty cycle the radio I would agree with Martine: usually, duty cycling should be rather part of the MAC layer than of the driver. However, embedded transceiver devices usually are designed for one particular MAC layer and splitting this up in a sensible way is not always easy/feasible. Do you have any concrete ideas of functionality for a generic radio transceiver the driver (netdev) API should provide? We are facing the same problem. Without radio duty-cycling, a battery powered operation seems not useful. Most transceivers consume a current of at least 10mA in receive mode (excluding MCU). I implemented a CSMA/CA-MAC layer using the ng_netdev interface. It should fit for most transceivers. But up to a certain part, hardware support in the transceiver is neccessary. I have done some HW tests on that topic: 1. Approach: There was a problem when I triggered CCA in software and in case of an idle channel the TX-state was triggered. The timespan between CCA-ready and TX-begin turned out to be too long. The result was interruptions in the middle of the transmit process, which leads to garbage on the channel. 2. Approach: Most transceivers support automatic CCA before TX, even most old ones. The approach to do it in Hardware works very well. I tested this with using the default values for backoff-intervalls, retry counts... defined in the IEEE 802.15.4 standard. I will update the CSMA-MAC PR in the end of the week, maybe after Thomas opened the PR for the Atmel driver. For comparison, in Contiki there are multiple RDC drivers that can be switched between at compile time, the most well-known is ContikiMAC [1]. Something similar would be very useful in battery powered scenarios for RIOT. There's definitely a need for generic MAC layer solutions in RIOT, besides the specific solutions like CSMA in the cc110x driver or TiSCH for 802.15.4e as part of the OpenWSN stack. As far as I know, at least two people are currently working on MAC layer implementations for RIOT. I will also take a look into this topic with the goal to use only the MAC layer part of the OpenWSN stack as a standalone module in RIOt. If the CSMA-MAC layer and the ng_radio driver for the KW2x device is ready I will focus on implementing a beacon enabled MAC layer according to the IEEE 802.15.4 standard. I discussed that already with Johann, maybe we will face some problems there. The problem could be to find a timer that runs in sleep modes, consumes very low power and has a sufficently high resolution for the beacon enabled mode. Using a high resolution timer (32mHz or so, depending on the hardware) will not work, as it consumes to much power. Maybe a 32kHz clock in combination with an RTC or so could work. Best Jonas ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Benchmarks
Hi Ludwig! I think our only m0+/802.15.4 board is the samr21-xpro and there are problems with the current/old network stack because of its memory demands. I haven't followed the discussion about RPL and UDP on the SAMR21 lately, but doesn't these memory problems only exist when using with RPL in storing mode and the default routing table size of up to 128 nodes? Cheers, Oleg -- The best thing about mathematical jokes is left as an exercise for the reader. pgpAEUZPdUyLz.pgp Description: PGP signature ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Google Summer of Code 2015
Hi Dinal, thanks for your interest and welcome to RIOT! You can start with RIOT by scrolling through the wiki pages and picking up one (or more) issues from the issue tracker [1] which are marked as Newbie-Task-Candidate. Also there will be a virtual meeting today @ 14:00 CET. Please follow [2] to see how to participate the call. Cheers, Peter [1] https://github.com/RIOT-OS/RIOT/issues [2] https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation Am 18.03.2015 um 02:15 schrieb Kasun Dinal Kurukulasooriya: Hi, I am a Computer Science Engineering undergraduate from University of Moratuwa. I am very interested in IoT related projects and writing low level high performance code with C/C++. Most interesting idea I found was 'Support for Bluetooth Low Energy aka Bluetooth Smart'. I think when it comes to IoT wireless transmission is very crucial so I hope to work hard on this project. I have worked with Bluetooth modules with controllers and sure it will give me a good base to start. As an intern I have experience with writing low level code to be ran on embedded systems for Denso, Japan and I hope use my skills in contributing to RIOT too. Thank you. Dinal Kurulasooriya, University of Moratuwa, Sri Lanka. ___ devel mailing list devel@riot-os.org http://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 http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] BLE stack
Hi , This is the basic architecture layer which I have found out : Host side we have : GAP and GATT protocol interact with the Security manager (SM) and the attribute protocol (ATT) Which interacts with the L2CAP protocol to send the data to the controller . Controller side we have the following : HCI protocol which forms the interface with the link layer Is this architecture fine to proceed ? Also what is the next step I need to do to refine this ? Thank you Regards Kausthub Naarayan ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Virtual GSOC Meeting
Hi, which one should I join now :-) ? Hear you, Peter Am 18.03.2015 um 14:01 schrieb Hauke Petersen: Hi everyone, as promised we will have a dedicated GSOC meeting now. To join please follow this link: http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- Look at this wiki page [1] for further information on PlaceCam. @RIOT maintainer: Please make sure you don't login with the RIOT PlaceCam account! Cheers, Hauke [1] https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation On 16.03.2015 21:03, Hauke Petersen wrote: Dear RIOTers, there is a lot of interest in our GSOC projects (which is great!). As the next developer meeting is still some time away and the official application period is just starting, we will have a dedicated virtual meeting to discuss the proposed projects, the application procedure and anything else that is of interest. The meeting will take place on Wednesday, March 18 @ 14:00 CET. We will send around a PlaceCam link before the meeting starts as always. Also feel free to discuss your projects here on the mailing list. You can also share youre (beta) application with us if you want to get some feedback beforehand. See you on Wednesday! Cheers, Hauke ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://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 http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Virtual GSOC Meeting
Oops, synchronization problem I guess. We'll use this link then! Am Wed, Mar 18, 2015 at 02:01:57PM +0100 schrieb Hauke Petersen: Hi everyone, as promised we will have a dedicated GSOC meeting now. To join please follow this link: http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- Look at this wiki page [1] for further information on PlaceCam. @RIOT maintainer: Please make sure you don't login with the RIOT PlaceCam account! Cheers, Hauke [1] https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation On 16.03.2015 21:03, Hauke Petersen wrote: Dear RIOTers, there is a lot of interest in our GSOC projects (which is great!). As the next developer meeting is still some time away and the official application period is just starting, we will have a dedicated virtual meeting to discuss the proposed projects, the application procedure and anything else that is of interest. The meeting will take place on Wednesday, March 18 @ 14:00 CET. We will send around a PlaceCam link before the meeting starts as always. Also feel free to discuss your projects here on the mailing list. You can also share youre (beta) application with us if you want to get some feedback beforehand. See you on Wednesday! Cheers, Hauke ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel -- The problem with TCP jokes is that people keep retelling them slower until you get them. pgp8AKKrTikZP.pgp Description: PGP signature ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Virtual GSOC Meeting
Hi everyone, we had a synchronization issue. Please connect to this link: http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- Cheers, Hauke On 16.03.2015 21:03, Hauke Petersen wrote: Dear RIOTers, there is a lot of interest in our GSOC projects (which is great!). As the next developer meeting is still some time away and the official application period is just starting, we will have a dedicated virtual meeting to discuss the proposed projects, the application procedure and anything else that is of interest. The meeting will take place on Wednesday, March 18 @ 14:00 CET. We will send around a PlaceCam link before the meeting starts as always. Also feel free to discuss your projects here on the mailing list. You can also share youre (beta) application with us if you want to get some feedback beforehand. See you on Wednesday! Cheers, Hauke ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Virtual GSOC Meeting
Hi everyone, as promised we will have a dedicated GSOC meeting now. To join please follow this link: http://placecam.de/call.php?c=lmakKMrDG8a35aIBNqLBvOnApExkKFntj9xXawGNgTc- Look at this wiki page [1] for further information on PlaceCam. @RIOT maintainer: Please make sure you don't login with the RIOT PlaceCam account! Cheers, Hauke [1] https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation On 16.03.2015 21:03, Hauke Petersen wrote: Dear RIOTers, there is a lot of interest in our GSOC projects (which is great!). As the next developer meeting is still some time away and the official application period is just starting, we will have a dedicated virtual meeting to discuss the proposed projects, the application procedure and anything else that is of interest. The meeting will take place on Wednesday, March 18 @ 14:00 CET. We will send around a PlaceCam link before the meeting starts as always. Also feel free to discuss your projects here on the mailing list. You can also share youre (beta) application with us if you want to get some feedback beforehand. See you on Wednesday! Cheers, Hauke ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Virtual GSOC Meeting
Dear GSOC participants and mentors, please join the meeting at http://placecam.de/call.php?c=VBYEpXi43MZ2MOrV~pegsMm6Z7woUbw.VRY0Qxal2pE- (see https://github.com/RIOT-OS/RIOT/wiki/Instructions-for-remote-participation for instructions how to use PlaceCam) Cheers, Oleg Am Mon, Mar 16, 2015 at 09:03:46PM +0100 schrieb Hauke Petersen: Dear RIOTers, there is a lot of interest in our GSOC projects (which is great!). As the next developer meeting is still some time away and the official application period is just starting, we will have a dedicated virtual meeting to discuss the proposed projects, the application procedure and anything else that is of interest. The meeting will take place on Wednesday, March 18 @ 14:00 CET. We will send around a PlaceCam link before the meeting starts as always. Also feel free to discuss your projects here on the mailing list. You can also share youre (beta) application with us if you want to get some feedback beforehand. See you on Wednesday! Cheers, Hauke ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel -- rio_dprintk (RIO_DEBUG_ROUTE, LIES! DAMN LIES! %d LIES!\n,Lies); linux-2.6.6/drivers/char/rio/rioroute.c pgpWNRSlZlFkR.pgp Description: PGP signature ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Virtual GSOC Meeting
Dear GSOC enthusiasts, please find the minutes from our meeting at http://pad.spline.de/Ouide7Nzd8 Cheers, Oleg -- panic(If this is a 64-bit machine, please try a 64-bit kernel.\n); linux-2.6.6/arch/parisc/kernel/inventory.c pgpYdZZJZK5WD.pgp Description: PGP signature ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Hello_RIOT
Hello RIOT, my name is Otmane EL MOUATAMID , i have 26 years i from Morocco , i'm PhD student , my research axes : - IoT-A, - ad-hoc - MANet, - VANet, - WSN, - M2M, - RFID, - NFC. i'm interested to work in RIoT, Project N2: Implementation of LwM2M. but i'm new n the summer code and RIOT, i'm reading about RIOT now i liked the idea, now i need knowledge how to i can start my work and how i can contribute in this project . best regards! Otmane .elmouaatamid ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] [GSOC] Introduction
Thanks for the Xbee driver,I'll wait the PR for testing! The security aspect is about including in RIOT the possibility to dynamically insert a set of encryption keys at run time through an external channel (I have a collegue working on NFC driver on RIOT). Basically,the keys I want to exchange are those concering the 802.15.4 protocol,but we can use the same technique for RPL or CoAP. 2015-03-16 19:21 GMT+01:00 Hauke Petersen hauke.peter...@fu-berlin.de: Hi Francesco, welcome to RIOT first of all. Cool that you are working with the UDOO boards! BLE development with these boards would indeed be a little difficult, as I don't know any shields without fully integrated network stack, that would allow for access to the BLE link layer. Porting the Xbee device to RIOT is unfortunately already almost finished [1] - I am just sitting on the last fixes and will release a PR in the next couple of days... The security aspect however is not yet included. Taking this to a more general approach (valid for not only the xbee device) is however a very hot topic. Here I would indeed see a project for GSOC. Do you have already any further ideas what you would like to do in this direction? It would be nice, if you could roughly sketch our your ideas, so we can discuss them further. Cheers, Hauke [1] https://github.com/haukepetersen/RIOT/tree/add_driver_xbee On 12.03.2015 15:46, Francesco Ermini wrote: Hi, my name is Francesco Ermini, and I'm student in electronics and telecommunication engineering at the University of Florence,Italy. My current Ms.C. thesis is about IoT secure communications. Our testbed is made by some UDOO Quad boards, with Linux + RiOT as operating systems (the UDOO can host two OSes at once). I checked the GSOC ideas page, and I found the Bluetooth Low Energy driver one. Although interesting, using BTLE wouldn't rally match my current work. However, we also found that the XBee shield is not yet supported in RiOT (open bug / feature request). This would match a bit more my thesis work, and my (evil) tutor would be happier. My question is: what about implementing the XBee driver (including the dynamic security keys setup) ? Best regards, Francesco ___ devel mailing listdevel@riot-os.orghttp://lists.riot-os.org/mailman/listinfo/devel -- Francesco Ermini Via Abebe Bikila, 8 50012 (FI) cell. 3338710609 tell. 055642820 ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] More convenient access to the IoT-LAB from a RIOT application
Dear rewewing IoTlers, I just opened a pull request in RIOT that should ease the work with RIOT applications on the IoT-LAB testbed a little bit: https://github.com/RIOT-OS/RIOT/pull/2640 Including the proposed Makefile like include $(RIOTBASE)/dist/Makefile.iot-lab in an application's Makefile allows to create IoT-LAB experiments, flash, reset and access the nodes right from the command line with Make in one go, e.g. executing export BOARD=iot-lab_M3 make iotlab-auth make iotlab-exp IOTLAB_NODES=10 IOTLAB_DURATION=60 IOTLAB_SITE=grenoble make iotlab-flash make iotlab-term will reserve an experiment for 10 nodes and 60 minutes in Grenoble, flash the current application to all nodes and starts serial_aggregator for these nodes. Let me know what you think about this idea and what could be improved. Cheers, Oleg -- panic(Lucy in the sky); linux-2.2.16/arch/sparc64/kernel/starfire.c pgpjAQvht8NHh.pgp Description: PGP signature ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Regarding Project A2
Hello RIOT community, I am Dinuka Sawlathura from University of Moratuwa, Sri Lanka. I am doing Computer Science Engineering(Integrated Computer Engineering). I like to work on following project, Project A2: Intelligently Interacting Light Switches I would like to know whether for what platform(ARM,Intel Galileo) we have to develop the applications? Thank you, best regards, Dinuka ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] NFC Atmel AT86RF232B
Hi all, Does somebody is working on a RIOT NFC device driver ? and the ATMEL sub-G AT86RF212B driver ? Joël ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] NFC Atmel AT86RF232B
I think the at86rf231 driver works with the 212B or will otherwise require minimal changes. I have not tested it but anticipate using it. In the linux kernel they are both supported in the same file. Craig Younkins On Wed, Mar 18, 2015 at 5:04 PM, Joël Chotard joel.chot...@xsoen.com wrote: Hi all, Does somebody is working on a RIOT NFC device driver ? and the ATMEL sub-G AT86RF212B driver ? Joël ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Benchmarks
Hi, I think our only m0+/802.15.4 board is the samr21-xpro and there are problems with the current/old network stack because of its memory demands. That said: which protocol on top of IP are you interested in? I assume you want to ignore RPL and any other side-tasks for this evaluation? Cheers, Ludwig Am 17. März 2015 17:46:52 MEZ, schrieb Simon Vincent simon.vinc...@xsilon.com: Hi Craig, We have a 802.15.4 transceiver that is capable of 250kbps. We are thinking of using this with a Cortex M0+ but wanted to make sure that the M0+ would have the processing power to handle the 802.15.4/6lowpan/ipv6 stack at a datarate of 250kbps. I just wondered if anyone had done any datarate measurements on existing development boards using the Cortex M0+? - Simon On 17/03/15 16:20, Craig Younkins wrote: Hi Simon, Throughput will be highly dependent upon the RF environment and what transceiver you are using. The M0+ most likely has enough power to do it under ideal conditions, but retransmissions due to collisions will limit the effective bandwidth. You can use 900 mhz and 2.4 ghz transceivers with 15.4. ~900 is significantly less crowded but lower theoretical bandwidth. The Atmel 212B is 900 Mhz and specs 1000 kbps as the max air data rate. Which transceiver are you using? Craig Younkins On Tue, Mar 17, 2015 at 11:42 AM, Simon Vincent simon.vinc...@xsilon.com mailto:simon.vinc...@xsilon.com wrote: Has anyone done any performance tests to see what throughput can be achieved using RIOT? I would be interested to know if the Cortex M0+ is powerful enough to sustain 250Kb/s TCP over 6lowpan/802.15.4. Does RIOT have any mechanism to measure CPU usage? - Simon ___ devel mailing list devel@riot-os.org mailto:devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
