-
Notifications
You must be signed in to change notification settings - Fork 7
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
Websocket: no pong response to ping packet #10
Comments
kamplom
changed the title
Websocket pong response to ping not working
Websocket: no pong response to ping packet
Apr 24, 2024
Try this:
|
It appears to be working. From the python client, the ping packet sent
and the pong response
As you can see the data field is always empty. Before merging it, I think a test where the ping packet has a no empty data field should be conducted as well, and check if pong response contains the same data. |
terjeio
added a commit
that referenced
this issue
May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What
grblHAL not respondig with pong opcodes to ping messages. Nothing arrives to the client side. No error message was triggered.
Client
Tested with python websocket-client library. It sends a packet with the ping OpCode and no data
Hack
I cannot understand the code easily so I just hardcoded a tcp_write with the OpCode for pong. websocket-client does not care about the payload in the pong response, but it should be the same as the one sent with the ping packed which triggered it.
A proper solution should be implemented.
The text was updated successfully, but these errors were encountered: