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

KISS character encoding? #31

Closed
SARTrack opened this issue May 9, 2016 · 1 comment
Closed

KISS character encoding? #31

SARTrack opened this issue May 9, 2016 · 1 comment

Comments

@SARTrack
Copy link

SARTrack commented May 9, 2016

Hello,

I am trying to write the Direwolf TCP KISS interface in my program SARTrack. So that users do no longer have to use the AGWPE interface.

Problem is that for some reason the incoming data from TCP port 8001 cannot be decoded properly with the same KISS functions as I use for a TNC.

How is the TCP server transmitting the KISS packet? Is this in ASCII, Ansi or is there a text encoding active like UTF8 ?

When I decode in ASCII (my default), I get a packet like:
C0 00 << Start of packet
A2 6E A0 64 AA 64 40 << From callsign: OKAY, but SSID = 32 Not okay
B4 3F 68 3F 3F B0 70 << Should be "ZL4FOX-5" but is corrupted to "Z 4 X" or something.

When I decode as UTF8, it really become a mess:

FFFD 00 FFFD 6E FFFD 64 FFFD 64 40 FFFD FFFD 68 FFFD FFFD FFFD 70

Any ideas what is wrong here?

Bart Kindt
SARTrack developer & CEO
http://www.sartrack.co.nz/

@SARTrack
Copy link
Author

SARTrack commented May 9, 2016

I have solved this issue. The problem was on my side (incorrect convert from bytes to ansistring)

Thanks, Bart

@SARTrack SARTrack closed this as completed May 9, 2016
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