Laczen commented on issue #15973: URL: https://github.com/apache/nuttx/issues/15973#issuecomment-2714410403
> Thanks for reporting, [@Laczen](https://github.com/Laczen)! > > Just for the records: > > > I suggest inserting a check for it on espnow_recv_cb and espnow_send_cb and saving the current channel to the espnow's structure. If the current channel is different, we can call espnow_ifdown/espnow_ifup (that should solve the problem). This doesn't need to be done here in my opinion. I don't think this would work. There can be many nodes using espnow and all nodes would need to modify their wifi channel. IMO it might not even be needed to support wifi and espnow at the same time (although it would be great). The target of espnow nodes would be low data, low power, fast wake-up, long range without connecting to an access point. At the moment the build system does not allow creating espnow nodes without the wifi network device but in future this might change. A device responsible for connecting the nodes to a wifi network could also be built up from 2 esp devices with a slip connection, or limited to connecting to an access point that uses the same wifi channel. BTW all other solutions (micropython, freertos, ...) are having the same limitation, but none of them provide full network support like is available on NuttX. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
