ESP8266 Community Forum

- Tue Oct 13, 2015 7:22 am #31225 Unfortunately not in this case. I see this is all running via Arduino ESP stuff, and I don't really know how stable that is in its translation for pwm. I couldn't play with it due to not being able to find some of the header files etc. so I'll have to keep taking a look at your updates now and then.

Thanks for the work you are putting in.

- Sat May 14, 2016 1:13 am #47422

I believe that the stability issue is resoled now.

As for a static IP I will see about implementing that. Should not be that hard.

Unless I'm missing something (due to the age of this post perhaps), the way to set a static IP is to use the Connect command. The problem is, upon boot up (or reboot, which is the real issue) I might have two or more nodes in a mesh see each other but not an AP. I would like for them to have default (and independent) IP addresses so that they can negotiate into the mesh network. Once they find a router or good AP, they can have throughput to the world.

The issue is that not all nodes will be in range of a router and nodes could move in and out of range or reboot due to power loss or reset on crash detection. An active mesh *could* have a critical node disappear and appear again later. This could strand other nodes so I want them to be able to re-establish the mesh, each starting with its own unique IP address.

For UDP purposes, I think I need to have all nodes on the same Class C subnet. I had thought of trying to chain AP's together but I think it will turn into a DHCP mess.

First, can this be done. Can I have a unique default IP address for each node upon boot? How about with an ESPbasic function? That way I could use Read/Write to save an IP address to flash and call it back when I want to modify the IP.

- Sat May 14, 2016 9:26 pm #47452 Esp basic is not currently configured for doing mesh networking. There might be some thing in the future for this. An explicit mesh mode posibly. I know that the arduino guys and espresive have cooked some thing up that might be able to be intergrated.

As for storing the network info for the connect command. You are correct in that it will not store static ip information. Much care has gone in to make espbasic by default alway work in a traditional network configuration. The explicit wifi commads for connecting or starting the ap modes are intened for the finite control. The settings page is primaraly for simpler projects or projects that dont create there own wifi set up screens.

If it is alnot already in the latest version it will be in the next to disable the delay on start up for running the default program. Perhaps this will make your problem go away.

Serial terminal in the chrome browser see https://serialTerminal.com

http://esp8266basic.com
A BASIC interpreter for your ESP

Working now on Autodrop3d. A 3d printer with automatic part ejection system. https://autodrop3d.com

- Thu May 19, 2016 3:39 am #47636 Yeah, from what I see in the ESP8266 docs, mesh networking would probably be a pain to implement just for all the effort to figure it out in the first place. I would not expect that any time soon.

I can do my own rudimentary mesh but the one thing I would need would be the ability to change the IP address of a node with a simple Basic command. Perhaps the Connect command but with no network & password specified. My guess is that you could do this if there's a corresponding function available for that in the ESP8266 firmware.

My situation is that I will not always have nodes within reach of an AP.

Failing that, is there a way to change the default IP of a single board? Not a pretty way to do it, but it would work.