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

Bad incoming byte sequences #3

Open
SpaceShawn opened this issue Nov 17, 2013 · 1 comment
Open

Bad incoming byte sequences #3

SpaceShawn opened this issue Nov 17, 2013 · 1 comment
Assignees

Comments

@SpaceShawn
Copy link
Contributor

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.

@ghost ghost assigned SpaceShawn Nov 17, 2013
@SpaceShawn
Copy link
Contributor Author

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

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