$REBOOT!
ets Jun 8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:8896
load:0x40080400,len:5816
entry 0x400806ac
dhcps: send_offer>>udp_sendto result 0
This is what I see for the ESP when it reboots from the web page command.
Is this normal? Especially the "send_offer".
I ask because if I try to start LiveView, the ESP never sends out the command to the Teensy. Other commands, like List and Reformat the SD Card work fine. The format command shows up like this on ESP console:
$FORMAT!
and response comes back from Teensy that says card formatted and size.
Meanwhile the Teensy console says this when you command LiveView and then List:
$STOPLIVEDATA!STOPPED Live Data. (Wifi Request)
$LIST!file list requested on Wifi
Any ideas?
Partially answered my own question. It has to do with the DNS. First of all, the connection to the WIFI from my phone etc. has to be to 192.168.0.1 not onspeed.local
So I changed line 196 of the WIFI code to the same URL and then LiveView works fine.
Now, I don't know why DNS is not working for me
Not just my phone BTW. Also for the Win 10 desktop. But the iPad finds onspeed.local just fine and line 196 can be either way without effect.
The desktop and phone DNS for the network is 192.168.0.1 BTW and does not help.
Tom, not sure what could be causing that. I've always used onspeed.local. Make sure the computer or phone is set up for DHCP when you connect, and only connect from one device at a time. Also one browser at a time. The ESP32 chip sends the dhcps: send_offer>>udp_sendto result 0 out on the serial when someone connects on Wifi. You can disable the boot messages if you tie one pin to ground, but this dhcp message stays. Not a big deal though.
LiveView is started by the Websocket connection, and initiated by the web browser. Open an Inspect window in your browser, go to the Network tab, and you can monitor the Websocket connection there.
Lenny