Problems testing zeptoIP

[ctrilsbach]

I have installed zeptoIP but am having problems with the code snippets in the BUILDING_AND_USING_ZEPTOIP.

These three lines will not compile.

my-cyw43-net init-cyw32-net - this I think should be my-cyw43-net init-cyw43-net?

my-cyw43-net cyw43-control@ to my-cyw43-control - Don't know about these two lines
my-cyw43-net net-interface@ to my-interface

Is there any documentation for the my-cyw43* modules ?

[tabemann]

Thanks for catching these - init-cyw32-net should be what you mentioned, i.e. init-cyw43-net, and I forgot to mention that the code should include simple-w-cyw43-net import.

As for documentation, I have not gotten around to writing API docs - the only forms of documentation that currently exist are BUILDING_AND_USING_ZEPTOIP.md and the test/rp2040/pico_w_* test code. Thanks for reminding me that I should actually write API docs for all this.

[ctrilsbach]

Cannot get ZeptoIP to connect to the router despite having the PicoW less than a inch away.
The only setting is encryption which is WPA2-PSK(AES) on the router. My phones mobile hotspot is WPA2 personal.
Need to try with other routers.

[tabemann]

When I took my Pico W with me on vacation I had a very hard time getting it to talk to the cabins" WiFi for some reason, where it talks with the Wifi AP at my home just fine. I chalked it up at the time to heavy WiFi use, as the AP was shared between multiple cabins, but maybe that was not the issue.

[tabemann]

You could try adding

cyw43-consts::PM_AGGRESSIVE my-cyw43-control cyw43-power-management

or like before you attempt to join an AP. The power management constants are in cyw43-consts and have the following values:

  \ Custom. officially unsupported mode. Use at your own risk.
  \ All power-saving features set to their max at only a marginal decrease in
  \ power consumption as opposed to cyw43-pm-aggressive.
  0 constant PM_SUPER_SAVE

  \ Aggressive power saving mode.
  1 constant PM_AGGRESSIVE

  \ The default mode.
  2 constant PM_POWER_SAVE

  \ Performance is preferred over power consumption but still some power is
  \ conserved as opposed to cyw43-pm-none.
  3 constant PM_PERFORMANCE

  \ Unlike all other PM modes, this lowers the power consumption at all times at
  \ the cost of a much lower throughput.
  4 constant PM_THROUGHPUT_THROTTLING

  \ No power management is configured. This conserves the most power.
  5 constant PM_NONE

Note that the default is PM_POWER_SAVE.

[ctrilsbach]

Doesn't make any difference. I tried aggressive and performance. I am still getting the occasional my-cyw43-net RAM dictionary space is running low (<1K left) message

[tabemann]

Okay, I did not understand that your RAM - not your flash - was running low. The solution to this is to simply reboot between times you instantiate <pico-w-cyw43-net> as that by itself takes up a substantial amount of RAM each time you allot and initialize it.

[tabemann]

About the cyw43* documentation, the API functionality that is really meant for public consumption is here. Note that it is specifically not in the master branch because zeptoIP and the CYW43 driver are not in the master branch yet. Same goes for the zeptoIP documentation, which is here.

[tabemann]

And yes, the cyw43* documentation may seem somewhat incomplete, but that is really because I do not entirely understand the CYW43439 myself and thus only documented the portions that would most likely be useful to the user.