-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
During startup, only one hard limit axis is shown at a time. #1388
Comments
Hmm... with 3.8.2 I can see the error for both axes:
|
It reported fine with 3.9.1 and I just tested it with v3.9.2-pre2. All switches on an XYYZ machine were made active on startup.
|
Can you test with the latest pre release? |
Will do tomorrow or day after.
Sent from my mobile office.
…On 11 Dec 2024, 7:07 pm, at 7:07 pm, bdring ***@***.***> wrote:
Can you test with the latest pre release?
--
Reply to this email directly or view it on GitHub:
#1388 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Please test. I want to close this issue. |
Yep, for sure. New controller is on its way to me. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wiki Search Terms
N/A
Controller Board
N/A
Machine Description
N/A
Input Circuits
No response
Configuration file
N/A
Startup Messages
User Interface Software
FT
What happened?
I had a hard limit situation on both X and Y axes during testing. FluidTerm informed me that a hard limit was triggered on X axis. I moved the axis off the switch and CTRL+R as ther terminal suggests. After reboot, I then got a warning that the Y axis limit switch was also triggered.
It would be best if all triggered axes/errors were reported in the startup message, otherwise we have to reboot multiple times if we don't notice an axis has triggered a limit.
GCode File
No response
Other Information
No response
The text was updated successfully, but these errors were encountered: