You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the HE100 receives a communication from the Kenwood, the LED light locks on, and we receive a bad sequence of bytes. Soft Reset is required to clear the light and any other unknown issues caused by this problem. Steps to reproduce the issue:
Start Kenwood
Connect to PC with PUTTY
Enter TNC mode
set hbaud to 9600
enter conv to enter converse mode
Send message 'kenwood'
The result is the same sequence of bad bytes:
48 65 20 04 00 19 3d a5 86 a2 40 40 40 40 60 ac 8a 64 86 aa 82 e1 03 f0 6b 65 6e 77 6f 6f 64 02 02 c2 4a
It's still very much unclear to us where these bytes come from that prepend and append to the "kenwood" string, and the verification of the payload checksum.
The text was updated successfully, but these errors were encountered:
This will be best tested when we can use the actual ground station hardware to test communication. The bad bytes are suspected to be a symptom of some issues on the Kenwood, and therefore are not an urgent concern
When the HE100 receives a communication from the Kenwood, the LED light locks on, and we receive a bad sequence of bytes. Soft Reset is required to clear the light and any other unknown issues caused by this problem. Steps to reproduce the issue:
He100
Run:
$ sudo gdb HE100/C/test_netman/bin/test_he100.x
Start Kenwood
Connect to PC with PUTTY
Enter TNC mode
set hbaud to 9600
enter conv to enter converse mode
Send message 'kenwood'
The result is the same sequence of bad bytes:
48 65 20 04 00 19 3d a5 86 a2 40 40 40 40 60 ac 8a 64 86 aa 82 e1 03 f0 6b 65 6e 77 6f 6f 64 02 02 c2 4a
It's still very much unclear to us where these bytes come from that prepend and append to the "kenwood" string, and the verification of the payload checksum.
The text was updated successfully, but these errors were encountered: