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

Parsing packet error #91

Open
hsia-summerboy opened this issue Nov 16, 2023 · 0 comments
Open

Parsing packet error #91

hsia-summerboy opened this issue Nov 16, 2023 · 0 comments

Comments

@hsia-summerboy
Copy link

Hello, I downloaded version 2.2.1 but found the following problems.
I encountered that if I receive an error packet, I will no longer be able to parse the packet correctly.
To verify the correctness, I used Wireshake to monitor network packets.

1.Receive Error Packet.
2023/11/16 12:29:37.619 → <-- [0x20202020] 'S32F32'
Error msg

2.Reply S9F1
2023/11/16 12:29:37.635 → --> [0x580C5BB5] Unrecognized Device Id:'S9F1'
<B [10] 0x20 0x20 0x20 0x20 0x00 0x20 0x20 0x20 0x20 0x20>
.
Reply_S9F1

3.No receive packet but still decoder.
2023/11/16 12:29:37.635 → <-- [0x20202020] 'S32F32'
<B [0] >
.

4.Reply S9F1 again.
2023/11/16 12:29:37.635 → --> [0x580C5BB6] Unrecognized Device Id:'S9F1'
<B [10] 0x20 0x20 0x20 0x20 0x00 0x20 0x20 0x20 0x20 0x20>
.
Reply_S9F1_Again

5.Send S1F1
2023/11/16 12:29:45.102 → --> [0x580C5BB7] :'S1F1'W
Send S1F1

6.Wirshake have get correct packet but SecsDevice.exe decoder a error packet.
2023/11/16 12:29:45.196 → <-- [0x80000102] 'S0F0'
<L [0]
>
.
Receive S1F2

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