-
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
SABM and SABME swapped in frame.py #17
Comments
As observed in actual TNC firmware behaviour.
So, I had a look… indeed, the However, the constructor for I've now corrected this in the branch. Many thanks for spotting these omissions. There might be other U-frames where |
As observed in actual TNC firmware behaviour.
As observed in actual TNC firmware behaviour.
As observed in actual TNC firmware behaviour.
As observed in actual TNC firmware behaviour.
As observed in actual TNC firmware behaviour.
As observed in actual TNC firmware behaviour.
In the file frame.py, SABM and SABME classes have their modifiers swapped. The correct values should be :-
Class AX25SetAsyncBalancedModeExtendedFrame should have a modifier of MODIFIER = 0b01101111
Class AX25SetAsyncBalancedModeFrame should have a modifier of MODIFIER = 0b00101111
It also appears that the P/F flag needs more investigation, and should possibly be set. The basis for this is that my PicoPacket TNC with 1996 firmware has the P/F bit set. In my case, the picopacket is using 0x3f as the value for SABM.
I suspect that existing code uses a mask to ignore the p/f bit.
Following your code, you could ADD these MODIFIER = 0b01101111 and MODIFIER = 0b00101111 respectively for SABME and SABM.
The text was updated successfully, but these errors were encountered: