-
Notifications
You must be signed in to change notification settings - Fork 8
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
Decoding protocol #13
Comments
I have one Wroom32 board. Can do test of firmware to completly confirm what it was trash. But please give me link to firmware and uploader program. |
Hi @nekdfl |
Hi @arkypita |
Hello @nekdfl I'm so sorry for not replying to you However I am no longer interested in learning more about the original vigo protocol because another user has developed a replacement firmware that cleans up the original Vigo firmware and makes the machine 100% grbl compatible, so thank you but there is no need to carry out these analyzes (unless you want to do it for fame and glory) |
As far as I understood, the request for help was for decrypting a strange sequence of bytes.
I was interested in the data, at the moment I plunged into the development of NetToUART (ws and telnet and the creation of a protocol for slow networks).
Right now, I have assembled a structure on my desk that allows you to exchange directly between the ESP8266 and the arduino nano. There are no weird sequences.
In fact, these are both esp8266 and arduino connected via ch340, so the recording went to 2 files and only the output could be recorded.
In esp 8266, the project is based on your project / ESP8266-SerialTelnet and in arduino GRVL 1.1h
Depending on the programming language in which the firmware is written, these random characters can be:
2.reading the amount of memory more than allocated for the buffer (memory is read sequentially from the address, the specified number of bytes)
I did attach UART ports dump with timestamp. And photo how it was connected.
from_uart.txt

to_uart.txt
)
The text was updated successfully, but these errors were encountered: