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

Z-axis stops due to Alarm-1 #14

Closed
jaygcnc opened this issue Mar 18, 2020 · 4 comments
Closed

Z-axis stops due to Alarm-1 #14

jaygcnc opened this issue Mar 18, 2020 · 4 comments

Comments

@jaygcnc
Copy link

jaygcnc commented Mar 18, 2020

So I have a few issues going on. Any insight on how to resolve them would be greatly appreciated.

My alarm code is "Alarm-1" reset with homing
Also on startup sometimes I get a Door:0 error , but it goes away when I reset the power.

This is my main issue. While using the nun chuck or the touchscreen the x-axis and y-axis move correctly, but the Z-axis will move only a little bit then trigger the alarm. It was working properly, but now I can barley get it to move without triggering the alarm.

This is another issue I am having. When I hit home all of the axis will move in the correct order and stop when triggering end stops. However, sometimes the x-axis will stop before any of the end stops are reached. Once the y-axis is reached the x-axis will move toward the end stop. Most of the time it will trigger the ends stop, but sometimes it will give up.

@mstrens
Copy link
Owner

mstrens commented Mar 18, 2020

The issues you report are not related to the controller but to GRBL itself.
It looks like you have noise on your endstop signal and other pin (like Door).
Do you use shielded cables for you end stops?
If not I recommend using such cable. You can also use an optocoupler module for you end stops.
There is a parameter in GRBL that you can use to increase noise protection for the endstops (probably in config.h file)

@jaygcnc
Copy link
Author

jaygcnc commented Mar 19, 2020

Yes, I used shielded cable for the end stops. My end stops are wired normally closed. I didn't see a parameter in the config.h file to increase noise protection. Then again I am very new at coding.

I think I am going to go the optocoupler module route. There are two different basic types that I see. One looks like it can just get wired into the end stops. The JBtek one looks more advanced. I was wondering if I need to add a code in the GRBL to accept the optocoupler module? Thank you for your help. I appreciate you taking the time to help me out.

https://www.amazon.com/Cylewet-Optocoupler-Mounting-Coupler-Arduino/dp/B06X6M2NNY/ref=sr_1_16_sspa?keywords=optocoupler+module&qid=1584657277&s=electronics&sr=1-16-spons&psc=1&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEyWTREQ0QwS0dTNlVEJmVuY3J5cHRlZElkPUEwNTUwNzA2MTNXWlNQRERTRE9FQyZlbmNyeXB0ZWRBZElkPUEwMTY0ODczMUxLQjhEWEEwUlg1WCZ3aWRnZXROYW1lPXNwX210ZiZhY3Rpb249Y2xpY2tSZWRpcmVjdCZkb05vdExvZ0NsaWNrPXRydWU=

https://www.amazon.com/JBtek-Channel-Module-Arduino-Raspberry/dp/B00KTEN3TM/ref=sr_1_9?keywords=optocoupler+elegoo&qid=1584657802&s=electronics&sr=1-9&swrs=130392AC71F7C229A904A8AC49296427

@jaygcnc
Copy link
Author

jaygcnc commented Mar 20, 2020

Thank you for the advice. I will try one out and let you know how if it works.

@mstrens mstrens closed this as completed May 20, 2021
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

No branches or pull requests

2 participants