-
Notifications
You must be signed in to change notification settings - Fork 3
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
Multiplexer Deactivates Itself After Sleep #76
Labels
bug
Something isn't working
Comments
15999f7 temporarily fixes the issue. |
The solution proposed to this is to move all automatic re-initialization code in |
prototypicalpro
added a commit
that referenced
this issue
Feb 28, 2020
Cogswatch
added a commit
that referenced
this issue
Mar 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using the I2C multiplexer and
LoomManager::sleep
, the multiplexer will mark itself deactivated by settingLoom_Module::active
to false duringLoom_Multiplexer::power_up
:Loom/src/Multiplexer.cpp
Lines 402 to 410 in fc36a8d
Loom/src/Manager.cpp
Lines 197 to 200 in fc36a8d
The module will then remain deactivated even after calling
LoomManager::power_up
after the board has fully powered on.While it makes sense to me that
Loom_Multiplexer::power_up
would deactivate the module because it cannot communicate with the multiplexer before the Hypnos is powered on, it is not clear to me why subsequent calls toLoom_Multiplexer::power_up
do not reactivate the module. More investigation is needed.Hardware in Use
Tested on the SitkaNet setup, but should reproduce on any Feather/Hypnos/Multiplexer project (so long as the multiplexer power controlled by the Hypnos).
To Reproduce
Any project using
Loom::sleep
with the multiplexer should be able to reproduce this issue. Simply load any sketch using sleep and the multiplexer, allow the board to sleep/wakeup once, and the board will no longer measure any multiplexer sensors.The text was updated successfully, but these errors were encountered: