Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

logInterval() can't be set higher than 4294 seconds #55

Open
LeSuedois opened this issue May 14, 2018 · 5 comments
Open

logInterval() can't be set higher than 4294 seconds #55

LeSuedois opened this issue May 14, 2018 · 5 comments
Assignees
Labels
bug Something isn't working low priority
Milestone

Comments

@LeSuedois
Copy link

LeSuedois commented May 14, 2018

estimate: 3d

background

https://electronics.stackexchange.com/questions/306374/extend-esp8266-12-f-deep-sleep-time

for instance we logged once every hour or shorter, now we head a client that want's one log per hour. So I put 86400 seconds as logInterval but the card reboots every ~10 minutes..
I think our problem is related to this :
https://www.esp8266.com/viewtopic.php?f=32&t=7867
and also to this merge :
esp8266/Arduino#4234

@LeSuedois LeSuedois added the bug Something isn't working label May 14, 2018
@3rwww1
Copy link
Contributor

3rwww1 commented Jun 7, 2018

Test with logInterval 12h - 24h

@trap98
Copy link
Contributor

trap98 commented Jun 8, 2018

Not functionnal, with 12 and 24 hours. Sometimes the board go to sleep with white led and ap on

@3rwww1 3rwww1 added this to the sprint 1 milestone Jun 11, 2018
@Kameeno
Copy link
Contributor

Kameeno commented Jun 18, 2018

//Note: system_rtc_clock_cali_proc() returns a uint32_t, even though system_deep_sleep() takes a uint64_t.
uint64_t EspClass::deepSleepMax()
{
  //cali*(2^31-1)/(2^12)
  return (uint64_t)system_rtc_clock_cali_proc()*(0x80000000-1)/(0x1000);

}``` 
someone has checked esp.h and esp.cpp ?

@3rwww1 3rwww1 modified the milestones: sprint 1, sprint 2 Jun 22, 2018
@Axe-R
Copy link
Contributor

Axe-R commented Jun 28, 2018

  • I made a test with a loginterval of 4 hours, it did a measure 3h30 later and then nothing more.

  • Another test with a loginterval of 5 hours, it didn't do anything and when I reset the coolboard, it has a white led on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working low priority
Projects
None yet
Development

No branches or pull requests

5 participants