So I have the V1E Jackpot board for my newly built LR4. Couldn’t get USB access, so I accessed via the wifi connection. Great. Got it to move via the web GUI. Tried to get it on my network, and I decided to set it to Client rather than STA>AP. Don’t know why I did this… it was late. I’m in no way a coder, developer, or have experience with Arduino/networks/etc.
Now I cannot access the board at all. I’m at a loss at this point… and I can’t seem to find a simple way to get this thing accessible.
We should figure out why your USB access doesn’t work.
That said, if you set the board to STA>AP, and it connected correctly to your WiFi then it will have an IP on that netowrk. In most case, that means you can find your machine at http://fluidnc.local/ in your browser.
If it failed to connect to your WiFi, then it should have fallen back to AP mode and you should see it as a network named FLUIDNC (or whatever you renamed it to.)
If you can’t find the Web UI with fluidnc.local, then the only remaining options are to log into your WiFi AP and see what DHCP address it gave out, do a ping scan to find hosts and try them one at a time, or to connect USB and look with FluidTerm.
So I think that’s the problem. I don’t know why I did it in the fog of last night, but I switched it from STA>AP to Client. Which, I believe, is what’s driving my problem of being inaccessible.
In terms of access, I believe my problem is I was trying to follow directions on the walkthru by using ArduinoIDE and Repetier. I ‘believe’ I got Arduino to recognize the board but I could never get Repetier to connect… so I gave up on the USB option.
Reiterating that I am a true n00b here… USB and FluidTerm… sounds promising? Not quite sure where to start though…
I believe so? I followed the directions on the original step by step guide. I am a 2015 Macbook Pro Retina user… so I’m absolutely sure that’s contributing to the issue. I believe I got ArduinoIDE to recognize it… however I could never get Repetier to connect. So I gave up on that route after discovering I could completely avoid this.
So to be clear, I added my wifi and wifi password. But I changed the ‘Wifi/Mode’ from ‘STA>AP’ to ‘Client’, which has now caused my issue of inaccessibility… Screenshot of someone else’s UI below for the reference.
Even after downloading the driver from above (Britt’s post), it seems my Macbook is still not recognizing the USB as a Serial Comms port. I feel like that’s the issue at this point to connect via USB.
Is there a way to reset the ESP32 back to the received settings (bought from V1) without having to completely re-install everything on a blank board - since my USB isn’t working at the moment?
To further elaborate, once I completed the command from above, I then checked the WiFi/mode setting by typing ‘$Wifi/Mode’ which produced what it was in. I then changed the WiFi mode by typing ‘$Wifi/Mode=AP’ and then restarted the ESP32. Boom. Back online.
