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.

Sign up for GitHub

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

Jump to bottom

WIFI REPETIER support #958

Closed
Virtualchronos opened this issue Aug 11, 2020 · 8 comments
Closed

WIFI REPETIER support #958

Virtualchronos opened this issue Aug 11, 2020 · 8 comments
Labels
Abandoned enhancement New feature or request

Comments

@Virtualchronos
Copy link

Hello !

I've baught a TFT 7.0 and there's plenty of incompatibility problems with Repetier :

Bltouch commands are not the same so it doesn't work
When there's "checksum errors" you must restart the screen to re-enable communication"
But the most important problem is ESP3D : I can't anymore use it since most of the commands doesn't work. The scren seems to filter the web commands so I can't anymore connect the ESP to repetier host. For the web interface, the only working commands seems to be movement and heat management. I can't remotely launch a print and that's a huge problem for me

I tried to put the esp on UART1 and THT7.0 on UART3 but the only result is endless beeps with "checksum error" message as soon as rx-tx on UART1 is connected
@Virtualchronos Virtualchronos added the enhancement New feature or request label Aug 11, 2020
@oldman4U oldman4U mentioned this issue Oct 11, 2020
Closed
@oldman4U
Copy link
Contributor

oldman4U commented Oct 20, 2020 •
edited
Loading

Hello Virtualchronos.

Could you please be so kind and close this ticket. Your feature request is covered in the pinned Feature Request ticket #1170

Thank you

@Virtualchronos
Copy link
Author

Virtualchronos commented Oct 21, 2020 via email

@oldman4U
Copy link
Contributor

It does not solve the issue, but it helps to bring your feature request to a more prominent place than an unanswered ticket in the middle of page 2.

@Virtualchronos
Copy link
Author

Virtualchronos commented Oct 21, 2020 via email

@oldman4U
Copy link
Contributor

Because in exchange of closing it, it will be part of the Feature Request List on the Main Page and therefore it will be easier to find it.

If you are not comfortable with closing it, you can keep it opened and the ticket will be unchanged. In this case I will remove it from the list, to avoid to have the same request twice.

@Virtualchronos
Copy link
Author

Virtualchronos commented Oct 21, 2020 via email

@stale
Copy link

stale bot commented Dec 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Abandoned label Dec 20, 2020
@stale stale bot closed this as completed Dec 27, 2020
@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 2, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Abandoned enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@oldman4U @Virtualchronos