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

"Couldn't acquire wake lock" message on Pi #174

Closed
andypiper opened this issue Jul 19, 2023 · 4 comments · Fixed by #189
Closed

"Couldn't acquire wake lock" message on Pi #174

andypiper opened this issue Jul 19, 2023 · 4 comments · Fixed by #189

Comments

@andypiper
Copy link

Raspberry Pi 4B
OS: Raspbian GNU/Linux 11
Node: 20.4.0
AxiDraw firmware version: 2.8.1

Server listening on http://[::]:9080
Found EBB at /dev/ttyACM0
Received plan of estimated duration 9m31s
Beginning plot...
Couldn't acquire wake lock. Ensure your machine does not sleep during plotting
Plot took 1m34s
Received plan of estimated duration 8m53s
Beginning plot...
Couldn't acquire wake lock. Ensure your machine does not sleep during plotting
Plot took 9m1s

I'm also seeing the same issues with the firmware check as described in #150

@alexrudd2
Copy link
Collaborator

I'm also seeing the same issues with the firmware check as described in #150

@andypiper Does the code here work for you? #176

@andypiper
Copy link
Author

yes, thanks @alexrudd2 that fixes the CLI firmware message / gets back the version and outputs an expected TODO error message. No change on the wake lock that I can see, but that's not unexpected.

@andypiper
Copy link
Author

Since the wake-lock module is macOS-only, it may be worth wrapping the call to WakeLock() in src/server.ts with an os-check, to avoid this warning - until I looked at both the saxi and wake-lock module code, I didn't know that this was not something I needed to worry about on a Pi.

@alexrudd2
Copy link
Collaborator

@andypiper Can you try either of the linked PRs and see if this works for you? (one's here, one's a fork). @jedahan did exactly as you suggested with an OS check wrapper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants