Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
ficeto
@ficeto
surely
same
Markus
@Links2004
its the same when you define WiFiClient client; globaly?
ficeto
@ficeto
load 0x40100000, len 29692, room 16 
tail 12
chksum 0x35
ho 0 tail 12 room 4
load 0x3ffe8000, len 1564, room 12 
tail 0
chksum 0x13
load 0x3ffe8620, len 2792, room 8 
tail 0
chksum 0xd8
csum 0xd8

�scandone
scandone
add 0
aid 4
cnt 

connected with nbis-test, channel 11
dhcp client start...
ip:192.168.254.184,mask:255.255.255.0,gw:192.168.254.5
192.168.254.184
NTP:29/05/2015 12:57:35
LmacRxBlk:1
client failed
LmacRxBlk:1
LmacRxBlk:1
Markus
@Links2004
the os has some data but you dont get it strange.
ficeto
@ficeto
same with global client
i never get that it's connected
Markus
@Links2004
can it be some strange interaction with the NTP code?
ficeto
@ficeto
not checking for success yields exception
will kill nTP and try
yup....
with NTP after the client:
�scandone
scandone
add 0
aid 3
cnt 

connected with nbis-test, channel 11
dhcp client start...
ip:192.168.254.184,mask:255.255.255.0,gw:192.168.254.5
192.168.254.184
HTTP/1.1 400 Bad Request
Server: nginx/1.4.6 (Ubuntu)
Date: Fri, 29 May 2015 10:07:49 GMT
Content-Type: text/html
Content-Length: 181
Connection: close

<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.4.6 (Ubuntu)</center>
</body>
</html>
NTP:29/05/2015 13:02:09
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
the NTP code:
udp.begin(localPort);
  sendNTPpacket(timeServer);
  int cb = udp.parsePacket();
  while(!cb){
    sendNTPpacket(timeServer);
    cb = udp.parsePacket();
    yield();
  }
  udp.read(packetBuffer, NTP_PACKET_SIZE);
Markus
@Links2004
some idea: the UDP and TCP share the same event to the "android task" and you still getting UDP packets, what brings the connect to fail.
so may try to close the udp
ficeto
@ficeto
did not expect such behaviour from UDP
Markus
@Links2004
it not a problem of the UDP protokoll its the wifiClient stuff, but have no time to confirm this.
have some other task to do for today.
ficeto
@ficeto
yup
udp.close did it
maybe should be added to the example
as that is what I used
Markus
@Links2004
yes
ficeto
@ficeto
really funky thing with Adafruit_SSD1306
sends the setup packet
and that's it... no more talking to the LCD
Russ Mathis
@RussMathis
Is there a way to sleep but keep pwm running ?
Or a certain level of sleep that will still keep the pwm running ?
alon24
@alon24
So ssd1306 still not working here?
tzapu
@tzapu
i ve got a ssd1306 that works just fine
i couldn t get it to work with @ficeto pull request, but it worked just fine with the adafruit1306 lib he modified before
this is what i use
ficeto
@ficeto
will find what's wrong, now that I can see it :)
there is nothing in the code that suggests the behavior I'm seeing
ficeto
@ficeto
actually that was dumb on my end... should call lcd.display()
the lib as it is in the repo is working fine on my end
ficeto
@ficeto
#include <SPI.h>
#include <Wire.h>
#include <Adafruit_GFX.h>
#include <Adafruit_SSD1306.h>
Adafruit_SSD1306 lcd(-1);

void setup() {
  lcd.begin(SSD1306_SWITCHCAPVCC, 0x3C);
}

void loop() {
  lcd.clearDisplay();
  lcd.setTextSize(1);
  lcd.setTextColor(WHITE);
  lcd.setCursor(0,0);
  lcd.print("Heap: ");
  lcd.println(ESP.getFreeHeap());
  lcd.print("Time: ");
  lcd.println(millis() / 1000);
  lcd.display();
  delay(100);
}
tzapu
@tzapu
good to know, thanks
if i m reading and writing eeprom in a lib, what would be a good practice , eeprom.begin and eeprom.end at the start and end of my functions? in case there are other eeprom operations in the main app?
ficeto
@ficeto
well... what end does is to commit the data in the buffer to the flash chip. You can open the EEPROM in the beginning of the sketch and just use EEPROM.commit() when you change something.
That will ensure that the data is saved n the flash
Russ Mathis
@RussMathis
Can someone help with the reset pin? I'm calling ESP.deepSleep and watching the rst & 16 pin. When awake I blink an led. Sleep for 5 sec Wake for 5 secs.
When I watch the scope it seems to indicate a pwm on rst&16? What is the proper way to wake if I want to override the deepSleep?
I want to sleep for 5 minutes but if the light in a room comes on I want to ake. Do I pull rst down or raise it high? Confused since the scode seems to show a pwm when in sleep mode :worried:
ficeto
@ficeto
have no clue what pwm you are seeing, but i have tied pins 16, EN and RST together and pulled UP with resistor
to wake manually, i pull the pins down
tzapu
@tzapu
@ficeto i m using eeprom in a lib, what happens if both the main app and the lib do eeprom.begin?
Russ Mathis
@RussMathis
Currently I have 16 and reset connected together(No resistor). When the ESP is in sleep mode I put the scope on either the 16 or gnd and see a sinus wave.
Not familiar with scope well enough yet LOL. Just got it and started using it.
ficeto
@ficeto
@RussMathis pul those pins UP! EN pin also!