-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"PI Pico W" access point problem #34
Comments
I do not get the warnings you see, my SDK verison is 1.4.0. AP mode is not working properly, marked WIP (Work In Progress) in my_machine.h. I can connect but get an error after a short while on my Win7 laptop. Station mode is working for me. It could be that your settings has not been initialized properly, changed default values are not always propagated to settings (and should not be) - either set them manually or issue
Yes. And the WebUI seems to be working as it should too (not tested in a real machine). Finally, check your settings when connected via USB. $70, 73, 74 and 75 has to be correct. |
AP mode is working provided that settings are correct... FYI the WebUI is not yet working in AP mode, I'll commit a fix for that and the $314 bug later. |
Cause of the warnings are compile time options. With setting NDEBUG from 0 to 1 in CMakeLists.txt The warnings in networking/sha1.c.obj and webui/args.c.obj
and
are generated when switching ADD_WIFI form OFF to ON in CMakeLists.txt SDK version is 1.4.0, grblhal version and Networking services plugin from today. Perhaps the warning results from a compile time option not set, warning message says [-Wstringop-overflow=] ? When switching to AP mode with I have to note that I'm testing only with the new PI Pico W board. The question is if I can test "WiFi station-" and "WiFi AP- mode" standalone with only PI Pico W connected to my home network and ioSender on a Windows machine. (when connecting ioSender via USB to PI Pico W I get only a permanent E-Stop error) . |
Invert the E-stop control signal in ioSender or connect the pin to ground to fix this.
Did you change the settings or reset them to default as described above? If not then it will not work. The settings are in the Networking and WiFi groups. I have just committed an update with fix for the $314 bug and fixes to make AP mode work with the WebUI. Warnings can be ignored for now? - I do not get them so I have to check a bit more to find out why you get them. |
With the new fix I get some more warnings because of the standard NETWORK_AP_GATEWAY - IP in grblHAL.
How can I fix this ? |
Leave it commented out in my_machine.h, I have hardcoded the address in wifi.c. |
Thank you very much ! First tests looks good - I can connect from ioSender both in WiFi station mode with an IP from my home network and in WiFi AP mode with the hardcoded 192.168.4.1. Next I will test WebUI with WiFi station and WiFi AP mode. |
Unfortunately I get another compile error when activating WebUI. WebUI plugin README.md in the grblHAL docu says When I do this in my_machine.h I get several errors like
RP2040/driver.h:203:
but SD card plugin is not defined in my_machine.h
I do a grep over the whole sources in RP2040 directory but I can't find a place in source code where SDCARD_ENABLE is set to 1. Hmm .... |
#define WEBUI_ENABLE 1 // Enable ESP3D-WEBUI plugin along with networking and SD card plugins. Requires WiFi enabled. Enabled here. Enabling WebUI without a place to store gcode is not very useful? |
Then I have unfortunately a problem of understanding, sorry for this. In your post
you mentioned that PI Pico W has now support for WebUI v3. The README.md from WebUI says that WebUI plugin supports some drivers including PI Pico W when enabling WEBUI.
If I do this I get the Because PI Pico W has no SD card on board the compilation will always throw this error but how can I use WebUI v3 with the PI Pico W ? I am a little confused at the moment and thank you very much for clarification. |
The Pico (and now the Pico W) driver supports SD card and other options, but not neccesarily all board maps do as pins may be allocated differently - it is a trade-off what the board designer want to support as the limited number of pins is a hard constraint. I am testing with a prototype Pico CNC board that has pins allocated for the SD card interface and thus can be used with the WebUI. The WebUI can only execute gcode stored on a local SD card as the Pico processor does not have the amount of memory needed (except for small programs), thus the SD card dependency. |
Thanks for explanation ! Because I actually use the PicoBOB
in combination with PI Pico I got the SD error. Countertesting with |
Looking at the pin map it might be possible to connect a SD card to the PicoBOB to pins 0, 1, 2 and 7. You will loose motor enable for Y and Z and the UART input. Motor enable for all three motors enable can be connected to X enable. I do not know if this it electrically feasible with the card - or if it will work... |
@terjeio, as you mentioned in your reply
terjeio/ioSender#216 (comment)
PI Pico W is now supported by grblhal and your RP2040 driver - great !
But actually I'm not able to activate WiFi access on my new PI Pico W board (board is OK, e.g. demo "blink" is running with flashing LED).
In CMakeLists.txt I set
option(ADD_WIFI "Add WiFi networking" ON)
and in my_machine.h
Compliation was successsful
but I get some warnings
and
and very, very lot of
After copying the grblhal.uf2 file to PI Pico W there is no WiFi access point
grblHAL_AP
So I'm not able to connect via WiFi.
Do you have some hints how to make it run ?
An additional question: what is this for ?
Is it possible to connect via WiFi to my home network, get an local IP from my home network and is connectable with iosender, or is this only useable for boards with ethernet cable connection ?
Regards, Olaf
The text was updated successfully, but these errors were encountered: