-
-
Notifications
You must be signed in to change notification settings - Fork 779
No Chance to wake up controller after sleep #2789
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
Comments
How do you wake up a controller that is in sleep state?? |
I use bCNC.
I couldn't find any other way.
Joacim Breiler ***@***.***> schrieb am Do., 15. Mai 2025,
11:02:
… *breiler* left a comment (winder/Universal-G-Code-Sender#2789)
<#2789 (comment)>
How do you wake up a controller that is in sleep state??
—
Reply to this email directly, view it on GitHub
<#2789 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADR2BUJCYOYV2YEBWVLGG4T26RJ3BAVCNFSM6AAAAAB5FOTZQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBTGA4TKMZVGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I don't know how the software does that. |
According to the GRBL documentation you need to reset the controller. Isn't that button enabled? |
The bigger problem is that UGS closes the connection if the controller is in sleep mode!! You can do nothing, without a connection!! |
I adjusted the button for resetting the controller to be available in SLEEP mode. This is available in the latest nightly build: |
Solves this the disconnection when in sleep mode? When the controller is in sleep mode, UGS closes the connection immediately after connecting. |
I did not encounter that problem on my machine. If that still happens for you with the new version I need the response from the $I command to know exactly which firmware your are running. |
The problem appears, if you set the controller in sleep and then restart
UGS or restart the computer.
Then after connecting to the controller, UGS closes immediately the
connection.
Joacim Breiler ***@***.***> schrieb am Fr., 16. Mai 2025,
22:35:
… *breiler* left a comment (winder/Universal-G-Code-Sender#2789)
<#2789 (comment)>
I did not encounter that problem on my machine. If that still happens for
you with the new version I need the response from the $I command to know
exactly which firmware your are running.
—
Reply to this email directly, view it on GitHub
<#2789 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADR2BUIHBTBGCR5PYKR5CET26ZDZPAVCNFSM6AAAAAB5FOTZQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBXGYZTCMJQGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
And the output of $I? |
I finally found the problem, if you had told me the output of $I this would have been a lot quicker to resolve. I connected with a newer 32-bit board which does not reset when connecting to it as the older 8-bit systems does. UGS tries to establish a connection without resetting it, but the sleep mode will prevent it from responding to commands. The work around is that UGS will now automatically reset the controller if it is in a sleep state. |
I work shifts and can't deal with this every day. I will give it a try later. |
Uh oh!
There was an error while loading. Please reload this page.
Version
2.1.12
Hardware / Firmware
GRBL 1.1
What happened
Hi.
If i send $SLP to the controller, it goes into sleep. Ok
But I can't wake him up again!
All Buttons are Grey.
If i restart UGS I can't even get connected again.
UGS is fetching the status, shows
<SLEEP|....
Fetching device Version
$I
Connection closed
After that, I have to use bCNC to wake up the controller.
There i can click Reset and everything works again.
How to reproduce
No response
Operating System
Win 10
Anything else
The problem is the closed connection.
I can't send any commands to the controller with UGS.
The text was updated successfully, but these errors were encountered: