Currently, RIOT does not support the 6TiSCH, which is the adaption of 6LoWPAN over 802.15.4 TSCH (time slotted channel hopping), which is advertised as a vast improvement over fixed-channel 6LoWPAN. This issue tracks the over-all steps that are needed in RIOT to run 6TiSCH.
- [ ] #4858: Support IEEE 802.15.4 frame version 2
- [ ] Support the 6TiSCH joining procedure
- [ ] Support time slotted frame transmission
- [ ] ...
Meta: Given that 6TiSCH is a much sought-after topic that comes up regularly in 6LoWPAN discussions, something web-searchable should reflect the state of things here. (At the time of writing, searches of riot and 6TiSCH yield links to outdated presentations, external libraries mentioning OpenWSN integration and similar).
chrysn
All 5 comments
I'm currently working on porting OpenWSN back into RIOT as a pkg. The initial approach I'm taking will be to take the whole stack. In #8570 it was taken only up to udp, but since the join procedure was added there is a hard dependency to OpenWSN coap this will initially need to be added.
I hope to be able to open an initial PR on this in the next week or two.
fjmolinas
on 6 Mar 2020
The initial approach I'm taking will be to take the whole stack.
As far as I know, a RPL root node is required in OpenWSN to initiate the network schedule. However, its implementation in OpenWSN is split into two software components. One of them runs on the embedded node and sends Beacons and advertises IPv6 prefixes. With #8570 and is successors, that worked fine. The second component deals with routing but it runs in a python tool on your machine which connects to the embedded node via openserial (a custom UART). How do you plan to deal with that?
PeterKietzmann
on 6 Mar 2020
The second component deals with routing but it runs in a python tool on your machine which connects to the embedded node via openserial (a custom UART). How do you plan to deal with that?
I currently use openvisualizer, and have no support for RIOT root nodes, I haven't gotten openserial working properly on RIOT nodes either.
The initial PR would require an OpenWSN root node...
fjmolinas
on 6 Mar 2020
13824 is merged so can we consider this one as resolved ?
aabadie
on 2 Jul 2020
@aabadie I think the premise of this Issue is addressed.
To put my two pence in, it might still be desired to either write lower layers providing 6tisch for gnrc or gutting openwsn to enable gnrc on top of it. At last to provide a RIOT-only option, without an openwsn specific rpl root node.
Anyway, I agree that this PR should for now resolve this issue.
SemjonKerner
on 2 Jul 2020
Related issues
silkeh
路
5Comments
kaspar030
路
6Comments
l3nko
路
7Comments
jue89
路
5Comments
jia200x
路
7Comments
Most helpful comment
I'm currently working on porting OpenWSN back into RIOT as a pkg. The initial approach I'm taking will be to take the whole stack. In #8570 it was taken only up to
udp, but since the join procedure was added there is a hard dependency to OpenWSN coap this will initially need to be added.I hope to be able to open an initial PR on this in the next week or two.