Hi David, Peter, many thanks for your answers. I was already thinking about using MQTT on top of UDP which shouldn't be a problem to implement. My question was a bit different.
From my understanding RIOT-OS is designed for meshed networks and the GNRC is the core element of networking. It uses devices via the Network interface API on top of layer 2, e.g., IEEE 802.15.4 radio. Therefore, I was wondering whether there is something like a tunneling approach where 802.15.4 packets are encapsulated in UDP packets and decapsulated by 802.15.4 gateway nodes so that WiFi based nodes could become part of the meshed network without having a MQTT broker. I could not find enough information whether ZigBee Encapsulation Protocol could do that job. @David: Even though I have a fork of RIOT-OS at https://github.com/gschorcht/RIOT-Xtensa-ESP8266, it is only used at the moment to document the current status of the port. There are a lot of things to tune before it is suitable for the public. At the moment the port can be used on top of Espressif's Non-OS SDK or as bare metal implementation without the SDK. The later one is small and fast. However, it is probably a dead end in case you want to use the WiFi interface. Since it is completely proprietary, there is no other option than to use the SDK :-( I hope that I can publish the first version next week, probably without networking. Regards Gunar On 26.03.2018 09:25, Peter Kietzmann wrote: > Hi Gunar, David, > > I think implementing against the sock API make most sense: > > http://riot-os.org/api/group__net__sock.html > > Have a look at this PR which intends to port the ESP as an AT-based > network device: > > https://github.com/RIOT-OS/RIOT/pull/5898 > > Best > Peter > > > https://github.com/RIOT-OS/RIOT/pull/5898 > > Am 26.03.2018 um 03:18 schrieb David Lyon: >> Hi Gunar, >> >> Do you have any links to your work ? >> >> Since I do also work on the ESP8266 I can only say that being able to >> send and receive UDP packets might be a place to start? >> >> I'm not a RIOT expert - so that's where I stand. >> >> If RIOT supports Sockets or MQTT that might also be worth looking into. >> >> Regards >> >> David >> >> On 2018-03-25 05:33, Gunar Schorcht wrote: >> >>> Hello, >>> >>> most parts of my RIOT-OS port to the ESP8266 has been implemented. GPIO, >>> SPI, I2C, UART, PWM seem to be ready and most of local applications are >>> working. >>> >>> However, RIOT-OS makes no real sense without networking. Unfortunately, >>> ESP8266 doesn't have Zigbee or 802.15.4 radio interface on board. >>> >>> Sure, one possibility would be to connect a Zigbee module via SPI. But, >>> it doesn't seem to be reasonable to connect a 25 EUR Zigbee module to a >>> 3 EUR MCU which has a WiFi interface on board. >>> >>> Therefore, my question is, what is the best way to realize networking on >>> a new platform that doesn't have 802.15.4 radio but full TCP/IP stack >>> and WiFi on board? >>> >>> Any suggestion helps. >>> >>> Regards >>> Gunar >>> >>> _______________________________________________ >>> devel mailing list >>> devel@riot-os.org <mailto: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 >> > -- Wenn du laufen willst, lauf eine Meile. Wenn du ein neues Leben kennenlernen willst, dann lauf Marathon. (Emil Zatopek)
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
