Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
M Hightower
@mhightower83
system_get_free_heap_size() needs to always return the DRAM heap size (at present it returns current heap value), regardless of which heap is currently being selected. This is the way all the other vPort... APIs were set up to work. SDK only knows how to handle DRAM. And, ESP.getFreeHeap() needs to use a different API. It is late for me, I'll look at this again tomorrow and make sure I am not missing something.
Paulo Cabral Sanz
@paulocsanz
Thank you! Is ESP.getMaxFreeBlockSize() wrong too since it's giving DRAM values for both?
Paulo Cabral Sanz
@paulocsanz
Nevermind I forgot IRAM and cache were shared, so there is no IRAM haha, for some weird reason ESP.getFreeHeap() is giving different values, which is unexpected, might be related to this bug you found
Hasenradball
@hasenradball
Hello is the function setAutoReconnectalso deprecated in the ESP8266 core?
Hasenradball
@hasenradball

Hello Experts, if I use the interrupt functionality on the ESP like this:

attachInterrupt(digitalPinToInterrupt(PIN), ISR_gate_state, CHANGE);

And I need an interrupt on this pin.

Is it then possible to do like this:

pinMode(PIN, INPUT_PULLUP);
attachInterrupt(digitalPinToInterrupt(PIN), ISR_gate_state, CHANGE);

Or will the pinMode setting overwritten when using the interrupt?
And I have to use an external pullUp?

2 replies
Juraj Andrássy
@jandrassy
Hello. Is it intended that WiFi.mode doesn't join AP / start SoftAP in core 3?
2 replies
Max Prokhorov
@mcspr:matrix.org
[m]
mode() -> begin() or just mode()?
Juraj Andrássy
@jandrassy
just mode (in core 2 it works)
I think the SDK does that normally so it must be somehow supressed
enableWiFiAtBootTime doesn't make a difference
Max Prokhorov
@mcspr:matrix.org
[m]
from sdk doc, it is wifistation{get,set}_auto_connect and ours {set,get}AutoConnect
but it only mentions boot, not mode change
I suppose it needs begin() somewhere, to start connecting
and I don't see any added disconnect() calls either. weird
Juraj Andrássy
@jandrassy
it is wifi_set_opmode
I test with persistent STA settings and the STA starts at boot. in core 2 .
sorry I see I test with 3.0.2. I check the latest git
Juraj Andrássy
@jandrassy
sorry. nevernind. it requires begin() in core 2 too
Max Prokhorov
@mcspr:matrix.org
[m]
I mean automatic connection stuff, that option controls whether sdk does it or not
well, good that it still works :)
Juraj Andrássy
@jandrassy
my testing of mode switching (with some confusion about STA) started with SoftAP not working correctly after starting it with setting 'mode' with core 3.0.2. The conclusion is that there is some bug in 3.0.2. In 3.1.0 it works again.
mihir deshpande
@ds_mihir_twitter
dhcp server starts sometimes twice in ESP8266, also I see that some times it reboots at this point.
dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)␊
[15:08:09:885] bcn 100␊
[15:08:10:748] bcn 0␊
[15:08:10:748] del if1␊
[15:08:10:748] usl␊
[15:08:10:748] add if1␊
[15:08:10:748] dhcp server start:(ip:192.168.4.1,mask:255.255.255.0,gw:192.168.4.1)␊
Hasenradball
@hasenradball
Hello when using the configTime() function and want to change the the time servers can I call the function again also when the program is already in the loop()?
Hasenradball
@hasenradball
An is there a way to check or get an info if which of the servers mentioned by configTime()are sucessfull?
Max Prokhorov
@mcspr:matrix.org
[m]
everything is re-configurable, configTime stops and then starts sntp
Clemens Kirchgatterer
@everslick
I can't seem to get WiFi::hostanme() get to work. when am I'm supposed to call it exactly, relative to WiFi::begin() ?
Drzony
@drzony
After begin works on my side
Clemens Kirchgatterer
@everslick
thx
Clemens Kirchgatterer
@everslick
I tried all combinations now. before, after and both. no luck :-D
Drzony
@drzony
What do you expect to happen?
hostname sets the hostname reported to DHCP server
Clemens Kirchgatterer
@everslick
I expect to find it in the list of DHCP names on my router. :)
Drzony
@drzony
That might depend on your router
Clemens Kirchgatterer
@everslick
yes it might, point is, I see a wholotta devices there, with the correct names
Drzony
@drzony
also make sure the hostname is RFC compliant:
vvvv RFC952 vvvv
        ASSUMPTIONS
        1. A "name" (Net, Host, Gateway, or Domain name) is a text string up
        to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
        sign (-), and period (.).  Note that periods are only allowed when
        they serve to delimit components of "domain style names". (See
        RFC-921, "Domain Name System Implementation Schedule", for
        background).  No blank or space characters are permitted as part of a
        name. No distinction is made between upper and lower case.  The first
        character must be an alpha character.  The last character must not be
        a minus sign or period.  A host which serves as a GATEWAY should have
        "-GATEWAY" or "-GW" as part of its name.  Hosts which do not serve as
        Internet gateways should not use "-GATEWAY" and "-GW" as part of
        their names. A host which is a TAC should have "-TAC" as the last
        part of its host name, if it is a DoD host.  Single character names
        or nicknames are not allowed.
        ^^^^ RFC952 ^^^^
Clemens Kirchgatterer
@everslick
I set it to "caroline", so that for sure is compliant, but thanks for the idea!
Drzony
@drzony
Does the hostname() call return true?
Clemens Kirchgatterer
@everslick
lemme check
Drzony
@drzony
If yes, then it might be some incompatibility with your router
Clemens Kirchgatterer
@everslick
i guess it returns true, because reading the hostname returns it correctly
Drzony
@drzony
not neccesarily
Clemens Kirchgatterer
@everslick
it's returning true. so I guess there nothing to be done here.
Drzony
@drzony
apart from setting up a different DHCP server and sniffing traffic I would guess that your router expects some specific type of option
Clemens Kirchgatterer
@everslick
Thx Hightower.
M Hightower
@mhightower83
For me, I had to test that the connection was idle before setting hostname. Then, do WiFi.begin(). It has been a while, I think setting after WiFi.begin() was a race situation that sometimes worked and sometimes failed.
Juraj Andrássy
@jandrassy
the DHCP request is in WiFi.begin so the hostname should be set before begin. but if the esp8266 already joined the same AP with remembered ssid and password, it will skip connecting again
Federico Frigo
@FIAV1
Hi all, I was looking for PPP dial-on-demand feature and I noticed that it’s already present in lwip stack, but it isn’t currently supported; any expert in lwip stack that could help me understand what could be done to make it work? That would be really appreciated guys
Juraj Andrássy
@jandrassy
@FIAV1 did you try the lwIP_PPP library?