ESP8266 Community Forum

- Sat Feb 24, 2018 2:46 pm #74170 I'm trying to follow:
http://lasergrbl.com/en/usage/wifi-with-esp8266/

and get the PC to WiFi connect to an Arduino/GRBL/CNC shield with and 8266. Anyone familiar? The program (as I understand it) first comes up as an AP, one connects to it, then one opens a page to assign the IP and password to the WiFi net to be used, and then the '8266 drops out as an AP, and joins the WiFi net. I don't get all that far, seldom connecting to my WiFi.

No feedback from lasergrbl yet.

What I want is to learn more about all the process, and understand the libraries for ESP8266WiFi, WebSocketsServer, ESP8266WebServer and/or WiFiManager.

Thanks.

- Sat Mar 05, 2022 12:17 pm #93821 This is four whole years later, so it's probably not relevant to what you're doing now. On the LaserGRBL page now there are options for both WebSocket and Telnet Wifi. I have built both and connected with both, but neither one stays connected, they both time out after 10 seconds, but the board works fine directly connected to USB. I'm starting to "conclude" that to the fact that my GRBL controller isn't really great shakes, I don't know exactly what it is but it's powered by AVR Arduino, it's probably either RATTM or Beauty Star. There was also an additional webpage relevant to the discussion:

https://www.instructables.com/Wifi-Grbl-With-Universal-Gcode-Sender/

but even adding that to the "mix" didn't make the WiFi work. But nowadays there are better options available for the controller board that internally incorporate WiFi, I haven't tried this myself but I'm hearing good things about the MKS DLC32 (I hope this doesn't sound like an ad, I'm just telling you what I'm looking at), I understand it will also work with LaserGRBL, and it's even available with a touchscreen offline controller option for not much more money:

https://www.aliexpress.com/item/1005003511726139.html?_randl_currency=USD&_randl_shipto=US&src=google&memo1=freelisting&src=google&albch=shopping&acnt=631-313-3945&slnk=&plac=&mtctp=&albbt=Google_7_shopping&albagn=888888&isSmbActive=false&isSmbAutoCall=false&needSmbHouyi=false&albcp=15229744697&albag=126912416582&trgt=1480551745650&crea=en1005003511726139&netw=u&device=c&albpg=1480551745650&albpd=en1005003511726139&gclid=CjwKCAiAjoeRBhAJEiwAYY3nDAAcagZ4hZF3QTrNsZ2pF43srMBGQMhEIaEzM3nGLcDZVxbG3hQOJBoCOWEQAvD_BwE&gclsrc=aw.ds&aff_fcid=1ff78938e35842d6b078fdd06cf46408-1646455773101-01036-UneMJZVf&aff_fsk=UneMJZVf&aff_platform=aaf&sk=UneMJZVf&aff_trace_key=1ff78938e35842d6b078fdd06cf46408-1646455773101-01036-UneMJZVf&terminal_id=6d3117ee30de49719dbea2cd3ed92b95&afSmartRedirect=y

That would also have its benefits because I had to pull a really nasty "hack" to connect the limit switches to the existing controller, and the new one has the genuine 3-terminal connectors. That, and if you're actually using a laser (I'm not), I understand the PWM frequency for the laser is more than ten times higher for better control. but I still don't really know definitively why the original WebSocket/Telnet wouldn't stay connected, maybe someone else will figure it out. Good luck!