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

Problems when working via ethernet #84

Open
zab-ig opened this issue Mar 16, 2022 · 1 comment
Open

Problems when working via ethernet #84

zab-ig opened this issue Mar 16, 2022 · 1 comment

Comments

@zab-ig
Copy link

zab-ig commented Mar 16, 2022

If any error occurs, for example, a limit switch has tripped or an unknown command in the r-code, a message appears:
ALARM:1
[MSG:Reset to continue]
But if you press the reset button, the controller stops responding. Only restarting the controller helps.
When working through uart, there is no such problem.

При возникновении любой ошибки, например сработал концевой выключатель или неизвестная команда в г-коде, появляется сообщение:
ALARM:1
[MSG:Reset to continue]
Но если нажать кнопку ресет, контроллер перестает отвечать. Помогает только перезагрузка контроллера.
При работе через юарт такой проблемы нет.

@zab-ig
Copy link
Author

zab-ig commented Mar 30, 2022

I found that when an error occurs, the connection between f446 and w5500 is lost.

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

1 participant