Re: [riot-devel] Notification: 6tisch ETSI Plugtest @ Fri Nov 6 - Sun Nov 8, 2015 (RIOT Events)
:-)
On Thu, Nov 5, 2015 at 5:57 PM, Oleg Hahm wrote:
> Hi all,
>
> please note that there is actually a small mistake in this calendar entry:
> we
> will participate in the ETSI plugtest for 6lo, _not_ 6tisch.
>
> Thanks for pointing this out, Thomas!
>
> Cheers,
> Oleg
>
> Am Thu, Nov 05, 2015 at 08:01:00AM + schrieb Google Calendar:
> > This is a notification for:
> >
> > Title: 6tisch ETSI Plugtest
> > ETSI Plugtest co-located with IETF 94
> > http://www.etsi.org/news-events/events/1003-6lo-plugtests
> >
> > When: Fri Nov 6 - Sun Nov 8, 2015
> > Where: Yokohama, Kanagawa Prefecture, Japan
> > Calendar: RIOT Events
> > Who:
> > * Peter Schmerzl - creator
> >
> > Event details:
> https://www.google.com/calendar/event?action=VIEW&eid=dmpjM2dna3ZrZ3Vlb25pYmsxaWsxNmJjOWsgazNxbDhzZXR2N2w0OG9mbm9sMHRmdXU2dHNAZw
> >
> > Invitation from Google Calendar: https://www.google.com/calendar/
> >
> > You are receiving this email at the account peterschme...@gmail.com
> because
> > you set a notification for this event on the calendar RIOT Events.
> >
> > You can change your notifications for specific events in the event
> details
> > page in https://www.google.com/calendar/.
> >
> > Forwarding this invitation could allow any recipient to modify your RSVP
> > response. Learn more at
> > https://support.google.com/calendar/answer/37135#forwarding
>
> > ___
> > devel mailing list
> > devel@riot-os.org
> > https://lists.riot-os.org/mailman/listinfo/devel
>
>
> --
> panic("floppy: Port bolixed.");
> linux-2.2.16/include/asm-sparc/floppy.h
>
> ___
> devel mailing list
> devel@riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
>
--
___
Thomas Watteyne, PhD
Research Scientist & Innovator, Inria
Sr Networking Design Eng, Linear Tech
Founder & co-lead, UC Berkeley OpenWSN
Co-chair, IETF 6TiSCH
www.thomaswatteyne.com
___
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Count link layer retransmissions for at86rf231
Oleg, Seeing is believing, so I would simply use a sniffer to find out. You undoubtedly can change the number of retries, but at least with a sniffer you'll have a base to start exploring from. My 2c. Thomas On Mon, May 18, 2015 at 10:21 PM, Oleg Hahm wrote: > Dear IoT developers, > > sorry for cross-posting, but since all of these communities are working (at > least partly) with this chip, I want to increase my chances: > The at86rf231 supports automatic link layer retransmissions by setting > MAX_FRAME_RETRIES in XAH_CTRL_0 accordingly. While this is a nice feature, > I > wonder if it is possible to figure out how many retransmissions were > actually > made (on the sender side). > > Cheers, > Oleg > -- > printk(KERN_WARNING "Warning: defective CD-ROM (volume sequence > number). Enabling \"cruft\" mount option.\n"); > linux-2.2.16/fs/isofs/inode.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
Re: [riot-devel] Upcoming ETSI Plugtests
as well: * October 30 - November 1, 2015 - 6tisch in Yokohama co-located with IETF 94 (note that the dates for the second 6lo/6tisch plugtests are tentative, but the first ones have been announced and will happen) Lot's of fun coding ahead :-) Thomas On Tue, Mar 24, 2015 at 5:11 PM, Oleg Hahm wrote: > Dear reading IOTlers, > > the next upcoming Plugtests organized by ETSI which are of interest for > RIOT > are announced as follows: > * July 17-19, 2015 - 6tisch in Prague co-located with IETF 93 > * October 30 - November 1, 2015 - 6lo in Yokohama co-located with IETF 94 > * March 2016- 6lo in Buenos Aires co-located with IETF > 95 > > Cheers, > Oleg > -- > /* We are root, all done! */ > RIOT/sys/net/rpl/rpl.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] open PhD student position - Deterministic Networking for the Industrial IoT - Inria Paris-Rocquencourt
ncludes working with real-world hands-on experimentation, contributing to standardization bodies, and frequently interacting with companies and research teams around the world. We are hence looking for a candidate with excellent academic credentials as well as strong "soft" and "hard" skills. * Speaking French is not a requirement. Professional proficiency in English is, however, important. * By the time you start with this position, you must hold a Master's degree (MsC) in computer science, control engineering, mathematics, scientific computation or an equivalent diploma in a related field. * You must demonstrate very good programming skills and experience (C/Python/Java, etc.), ideally including web development (server-side, JavaScript, PHP, html, etc.) * Embedded programming experience is a plus, ideally involving low-power wireless devices and experience with IoT-related open-source projects (OpenWSN, RIOT, Contiki, TinyOS, etc.) * A strong interest in scientific problems and motivation for independent and goal-oriented research. * We are looking for the "tinkerer" kind. If you have built an Arduino-based fan which tracks you as you move about, a plant which tweets when you need to water it, tell us about it! Benefits Located at the heart of Europe, Paris is a unique place to work and live in. Inria offers a unique balance between working in a leading research center and living in one of the most beautiful and bustling cities in the world. A real communication hub, Paris is a gateway to France and Western Europe, and working in the Inria Paris-Rocquencourt research center is real asset to your career. * Monthly gross salary: 1958 € first and second years, 2059 € third year * approx. 45 days of annual vacation * ultra-convenient daily dedicated Inria shuttle bus to/from central Paris (free) * Inria covers part of your commute expenses (metro, bus, etc.) * When needed, Inria will help you apply for Scientific Resident card and a visa * on-site restaurant (Inria pays for part of you expenses) * on-site gym, tennis courts, soccer field, etc. Working at Inria Established in 1967, Inria is the only public research body fully dedicated to computational sciences. Combining computer sciences with mathematics, Inria's 3,500 researchers strive to invent the digital technologies of the future. Educated at leading international universities, they creatively integrate basic research with applied research and dedicate themselves to solving real problems, collaborating with the main players in public and private research in France and abroad and transferring the fruits of their work to innovative companies. Inria researchers have published over 4,500 articles in 2013 and are behind over 270 active patents and 110 start-ups. In 2013, Inria's budget was 235 million euros, 25% of which represented its own resources. The 180 project teams are distributed in eight research centers located throughout France. The Inria Paris-Rocquencourt research center is located next to the famous Chateau de Versailles gardens, right outside of Paris. Thanks to its top-quality researchers and numerous international guests, the Paris-Rocquencourt research center plays a leading role in international research, in particular around networking and communication systems. The 41 research teams of the center are continuously pushing the boundaries in developing new concepts and techniques. HiPERCOM2 is a leading research team in High PERformance COMmunications. The research team, lead by 3 faculty members (Pascale Minet, Paul Muhlethaler, Thomas Watteyne), is designing Tomorrow's Internet of (Important) Things. The team pushes the limits of low-power wireless mesh networking by applying them to critical applications such as industrial control loops, with harsh reliability, scalability, security and energy constraints. Grounded in real-world use cases and experimentation, HiPERCOM2 co-chairs the IETF 6TiSCH standardization working group and co-leads Berkeley's OpenWSN project. The team is associated with Prof. Glaser's (UC Berkeley) and Prof. Kerkez (U. Michigan) through the REALMS associate research team. Additional information == If you have questions about the scientific contents of the position, we encourage you to browse http://eecs.berkeley.edu/~watteyne/ and contact thomas.watte...@inria.fr before applying. For administrative/practical questions, e-mail cecile.bertrand-kalko...@inria.fr. You will find the official offer at http://www.inria.fr/en/institute/recruitment/offers/phd/campaign-2015/(view)/details.html?id=PNGFK026203F3VBQB6G68LOE1&LOV5=4509&LG=EN&Resultsperpage=20&nPostingID=9262&nPostingTargetID=15256&option=52&sort=DESC&nDepartmentID=28 . You must apply online through the Inria Web site. Evaluation of applications will begin immediately and continue until the position is fil
Re: [riot-devel] Switch to BSD?
Emmanuel, I support the change to BSD. One of the reasons is that OpenWSN is also on BSD, so integration of the different code bases might be easier when both have the same license. Thomas On Wednesday, December 3, 2014, Emmanuel Baccelli < emmanuel.bacce...@inria.fr> wrote: > Dear RIOTers, > > we have been receiving an increasing amount of negative feedback from > various companies concerning the practical usability of our LGPL license in > their context, being a show-stopper. > > For this reason, INRIA, Freie Universitaet (FU) Berlin and Hamburg > University of Applied Science (HAW) are currently considering changing the > license of their contributions to RIOT to a less restrictive license (i.e. > BSD, potentially as soon as next release). > > Such a switch to BSD is betting that the effect of a potentially smaller > percentage of user/devel contributing back to the master branch will be > dwarfed by the effect of a user/devel community growing much bigger and > quicker. This seems doable considering the current momentum around RIOT. > > In a second phase, if such a license switch takes place for INRIA/FU/HAW > contributions, we would then contact other contributors individually, to > check their status concerning a similar switch for their own contributions. > > But in the first place, we would like to debate this topic. In particular: > is anyone violently opposing the idea of migrating to a less restrictive > license, such as BSD? If so, why? On the other hand, if you explicitly > support the license change, feel free to indicate this as well. Please send > your opinion to the list before Dec. 10th. > > Cheers, > > Emmanuel > ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] RIOT/OpenWSN and TSCH support
Oleg, Excellent, glad to hear that you plan on participating. Happy to mention RIOT, I didn't know you were there :-) Thomas On Thu, Nov 6, 2014 at 11:27 AM, Oleg Hahm wrote: > Hi Thomas! > > > Note that the 6TiSCH WG, in conjunction with ETSI, will organize a 6TiSCH > > interop event during IETF93 (July 2015, Prague) around 6TISCH technology, > > so including IEEE802.15.4e TSCH. You (and RIOT of course!) might be > > interested in participating. The plan is to come up with writing the test > > spec by March 2015. > > We will most certainly participate - and not only because Prague is just a > stone's throw (how RIOTy...) away from Berlin. ;-) > > > BTW, I happen to be giving a talk about OpenWSN in 90min ( > > > https://swarmlab.eecs.berkeley.edu/events/2014/8/22/5118/openwsn-technical-overview-status-and-road-ahead > ), > > which is streamed live online. I'll talk about the RIOT integration, so > you > > might be interested to listen. > > By the way, thanks for the nice mentioning of RIOT this morning at the > IoT-Lab > inauguration. > > Cheers, > Oleg > -- > /* panic?? These should never occur in our application. */ > linux-2.6.6/drivers/scsi/aic7xxx/aiclib.c > > ___ > 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
[riot-devel] RIOT/OpenWSN and TSCH support
[was: Refectoring the network stack] Adam, all, I'm co-leading the OpenWSN project. CC'ing the OpenWSN ML. In 2014, the IETF 6TiSCH working group (which is standardizing how to use IEEE802.15.4e TSCH in combination with 6LoWPAN, RPL, CoAP) organized two "plugfests": - in London in March ( https://bitbucket.org/6tisch/meetings/wiki/140306a_ietf89_london_plugfest ) - in Toronto in July ( https://bitbucket.org/6tisch/meetings/wiki/140720a_ietf90_toronto_plugfest ) For those events, the RIOT team (Thomas Eichinger leading the effort) developed a mechanism to use the OpenWSN protocol stack in conjunction with RIOT's task scheduler. A very cool design, indeed! Following this success, the OpenWSN team is re-architecting its code so that the "kernel" can be dynamically changed at compile time. Choices will be openos (the native OpenWSN scheduler), RIOT and FreeRTOS. Lead on that project is Xavi Vilajosana, details at https://openwsn.atlassian.net/browse/FW-16. Note that the 6TiSCH WG, in conjunction with ETSI, will organize a 6TiSCH interop event during IETF93 (July 2015, Prague) around 6TISCH technology, so including IEEE802.15.4e TSCH. You (and RIOT of course!) might be interested in participating. The plan is to come up with writing the test spec by March 2015. BTW, I happen to be giving a talk about OpenWSN in 90min ( https://swarmlab.eecs.berkeley.edu/events/2014/8/22/5118/openwsn-technical-overview-status-and-road-ahead), which is streamed live online. I'll talk about the RIOT integration, so you might be interested to listen. Thomas On Thu, Nov 6, 2014 at 10:24 AM, Martine Lenders wrote: > > >> > >> Am 06.11.2014 18:38 schrieb "Adam Hunt" : > >> > > >> > Is support for TSCH in there somewhere? While I'm not entirely read > up on the spec it would seem to be fairly important these days. > >> > > >> > What is the current state of TSCH support in RIOT these days? I'm > stuck on my phone at the moment or I'd take a look for myself (really, it > probably has a bit more to do with my being hungover and slightly lazy this > morning). > >> > >> Currently use the already existing TSCH implentation OpenWSN. So that's > where it is hiding ;) > >> > >> Cheers, > >> Martine > >> > >> > > >> > --adam > >> > > ___ devel mailing list devel@riot-os.org http://lists.riot-os.org/mailman/listinfo/devel
