-
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
Performance of Modbus sniffer #1
Comments
Hello @MinzaGayas, I had the same problem and heavily modified @snhobbs code. |
Hi Chris,
Thanks for sharing the link. I downloaded the code but I am still getting
the same frame error messages (screenshot attached). Do you have any
suggestions about it?
…On Tue, Jun 21, 2022 at 3:00 PM Chris ***@***.***> wrote:
Hello @MinzaGayas <https://github.com/MinzaGayas>, I had the same problem
and heavily modified @snhobbs <https://github.com/snhobbs> code.
If you can look at my fork, it may solve your problems.
The usage is more detailed too...
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYZRIX6T7SDJI6H56MS3YBTVQG4GTANCNFSM5ZME5JCQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
even with the python I wrote you have the same error as the original script ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I am trying to sniff data of a client which sends requests @660ms rate. Baudrate is 9600 and serial socket timeout is 1s and I am running the Modbus sniffer on rpi CM4 (Linux 11). Using sniffer, I see only half of the requests are processed. For the rest of the requests, framer checker fails or frames are not ready. Is it because client is too fast for the sniffer to process or some timeout needs to be reduced?
The text was updated successfully, but these errors were encountered: